John Wittenberg wrote: <snip>
Also, since I was not seeing the DHCPDISCOVER type messages in the syslog, I found this messageUm...I hate to tell you this, but everything *IS* working now, at least according to your logs...
http://www.mail-archive.com/leaf-user@;lists.sourceforge.net/msg09455.html
from which I got a 'new' dhclient.lrp file from here
http://www.mail-archive.com/leaf-user@;lists.sourceforge.net/msg09477.html
The 'new' dclient worked well, as the DCHPDISCOVER type messages are now showing up in the syslog. The syslog is at the end of this part of the message.
As a note, booting a machine with only one 3c900 NIC and connected to the cablemodem resulted in the same dhclient messages. However, booting a machine with only one 3c905 NIC connected to a LAN did not produce the messages. Both used the 3c59x.o module. I don't think that my company would like me bringing in a computer to hook to their network.
Granted the surplus NICs could be a problem, but I find it hard to beleive that I have problems after using 4 different NICs and three different drivers. I guess I'm still looking (hoping) for some set-up problem with the cablemodem or the ISP DHCP server. If it is really "just a NIC problem", what NIC should work?
<snip>
NOTE: dhcpd: (server) messages removed for clarity.
Nov 5 00:40:31 firewall dhclient: Internet Software Consortium DHCP Client 2.0pl5
Nov 5 00:40:31 firewall dhclient: Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
Nov 5 00:40:31 firewall dhclient: All rights reserved.
Nov 5 00:40:31 firewall dhclient:
Nov 5 00:40:31 firewall dhclient: Please contribute if you find this software useful.
Nov 5 00:40:31 firewall dhclient: For info, please visit http://www.isc.org/dhcp-contrib.html
Nov 5 00:40:31 firewall dhclient:
Nov 5 00:40:33 firewall dhclient: Listening on LPF/eth0/00:20:78:14:5a:e3
Nov 5 00:40:33 firewall dhclient: Sending on LPF/eth0/00:20:78:14:5a:e3
Nov 5 00:40:33 firewall dhclient: Sending on Socket/fallback/fallback-net
Nov 5 00:40:33 firewall dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
dhclient started and our system asked for a DHCP server
Nov 5 00:40:34 firewall dhclient: ip length 328 disagrees with bytes received 332.And got an offer from your ISP's DHCP server. The 4 byte length difference between the actual size of the packet (332 bytes) and the length indicated by the IP header (332 bytes) is a known bug with specific DHCP servers (I don't recall which off-hand...a quick google search should find the culprit).
Nov 5 00:40:34 firewall dhclient: accepting packet with data after udp payload.
Nov 5 00:40:34 firewall dhclient: DHCPOFFER from 66.235.63.242
Nov 5 00:40:37 firewall dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Your system now requests an IP from the dhcp server...
Nov 5 00:40:37 firewall dhclient: ip length 328 disagrees with bytes received 332.
Nov 5 00:40:37 firewall dhclient: accepting packet with data after udp payload.
Nov 5 00:40:37 firewall dhclient: DHCPACK from 66.235.63.242
Nov 5 00:40:43 firewall dhclient: bound to 66.235.41.189 -- renewal in 43200 seconds.
...and gets it, again with the 4 byte packet length mis-match.
Nov 5 00:40:47 firewall dhclient: ip length 328 disagrees with bytes received 332.The rest of these errors are due to other DHCP traffic on your cable-modem segment (ie your neighbors DHCP traffic), which you are recieving since DHCP uses broadcast packet to communicate.
Nov 5 00:40:47 firewall dhclient: accepting packet with data after udp payload.
Nov 5 00:40:47 firewall dhclient: ip length 328 disagrees with bytes received 332.
Nov 5 00:40:47 firewall dhclient: accepting packet with data after udp payload.
Nov 5 00:40:56 firewall dhclient: ip length 328 disagrees with bytes received 332.
Nov 5 00:40:56 firewall dhclient: accepting packet with data after udp payload.
Nov 5 00:40:56 firewall dhclient: ip length 328 disagrees with bytes received 332.
Nov 5 00:40:56 firewall dhclient: accepting packet with data after udp payload.
So...you will continue to see the length errors until your ISP upgrades their DHCP server to a non-buggy version.
--
Charles Steinkuehler
[EMAIL PROTECTED]
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
