*** From dhcp-server -- To unsubscribe, see the end of this message. ***
History: were at 1.0pl2, then changed to 2.0b1pl23.
At that point we started getting reports on campus
that old NCSA Telnet type of "packet driver" machines were
failing to perform DNS lookups successfully. At the time
of the upgrade we also add NetBIOS name server and NetBIOS
node-type.
In any event, other folks have seen similar problems.
We rolled back to 2.0b1pl6, but I really don't know if
that got is back into a good place. So I'm just sort of
fishing for info here. It's hard for me to test this stuff
as most of the culprits are out in the field, not in my
building so...
Here's what I think a packet-driver request looks like,
with an answer from a 2.0b1pl6 server, "malekim-test" is
00:20:af:de:ef:db, i.e. the requesting client. What we see
sometimes is that it will request over and over and over, and
in fact the 2.0b1pl6 will keep adding dynamic-bootp leases over
and over, at something like every 5 seconds.
So I guess I have two problems:
1) packet driver dyn-bootp loses DNS server info
2) packet driver dyn-bootp won't boot
Anyone figure out a fix for these yet? I'm thinking we're going
to have to build another machine for testing. I just hate to be
dealing with these ancient anachronisms.
Thanks,
John Kemp ([EMAIL PROTECTED])
10:28:40.470319 malekim-test Broadcast ip 344: 0.0.0.0.bootpc > 255.255.255.255.
bootps: xid:0x8fac2037 secs:256 (ttl 100, id 1)
4500 0148 0001 0000 6411 55a5 0000 0000
ffff ffff 0044 0043 0134 a540 0101 0600
8fac 2037 0100 0000 0000 0000 0000 0000
0000 0000 0000 0000 0020 afde efdb 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000
10:28:41.894466 8:0:20:7b:b3:a7 Broadcast ip 342: network-services.uoregon.edu.b
ootps > 255.255.255.255.bootpc: xid:0x8fac2037 secs:256 Y:d60-199.uoregon.edu S:
network-services.uoregon.edu ether malekim-test vend-rfc1048 SM:255.255.254.0 DG
:cisco3-gw.uoregon.edu NS:phloem.uoregon.edu,dns.cs.uoregon.edu DN:"uoregon.edu"
T28:2162114047 T44:2162113584 T46:8 (DF) [ttl 1] (id 24786)
4500 0148 60d2 4000 0111 5adf 80df 3c15
ffff ffff 0043 0044 0134 2b10 0201 0600
8fac 2037 0100 0000 0000 0000 80df 3cc7
80df 3c15 0000 0000 0020 afde efdb 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 6382 5363 0104 ffff
fe00 0304 80df 3c01 0608 80df 2023 80df
0609 0f0b 756f 7265 676f 6e2e 6564 751c
0480 df3d ff2c 0480 df3c 302e 0108 ff00
0000 0000 0000 0000
10:28:41.902018 malekim-test Broadcast arp 60: arp who-has d60-199.uoregon.edu (
Broadcast) tell d60-199.uoregon.edu
0001 0800 0604 0001 0020 afde efdb 80df
3cc7 ffff ffff ffff 80df 3cc7 0000 ffff
ffff 0020 afde efdb 0800 ffff ffff
10:28:41.902169 malekim-test Broadcast arp 60: arp who-has cisco3-gw.uoregon.edu
(Broadcast) tell d60-199.uoregon.edu
0001 0800 0604 0001 0020 afde efdb 80df
3cc7 ffff ffff ffff 80df 3c01 0000 ffff
ffff 0020 afde efdb 0800 ffff ffff
example lease:
lease 128.223.60.199 {
starts 5 1999/04/23 17:28:40;
ends 2 2038/01/19 03:14:07;
hardware ethernet 00:20:af:de:ef:db;
dynamic-bootp;
}
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
Archives for this mailing list are available at
http://www.webnology.com/list-archives/dhcp/dhcp-server
------------------------------------------------------------------------------
