It has been a rather frustrating time, <%-). In case it was a NIC, I stopped at the local surplus store and bought 2 ISA NICs, a SMC and a 3c509. They didn't work, long story. I also downloaded the Dachstein .bin file instead of the .exe file and used WinImage to generate a new floppy. The firewall was using two 3c509 NICs with eth0 connected to a Motorola surfboard cablemodem. Using the new floppy, I made the changes necessary for the NIC modules to load. My ISP is using dynamic IP addresses. I did not change ipfilter.conf in order to keep things simple.
With the original two NICs and the new floppy, I got the same results where dhclient is reporting "ip length 328 disagrees with bytes received 332". I then removed the eth0 NIC and rebooted with the remaininng NIC (yes only one NIC in the system) as eth0 with the same results. Finally I cannibilized a Linksys PCI card from another computer and rebooted with the Linksys as eth0 and a 3c509 as eth1 (connected to another computer for dchpd). The same dhclient message was being logged. Also, since I was not seeing the DHCPDISCOVER type messages in the syslog, I found this message
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?
In searching for more answers, I discovered three other reports of the same issue.
http://www.mail-archive.com/leaf-devel@;lists.sourceforge.net/msg05593.html
http://www.mail-archive.com/leaf-user@;lists.sourceforge.net/msg09397.html
http://www.isc.org/ml-archives/dhcp-client/2000/06/msg00051.html
The last message to me implies that there may be something with using cablemodems. I could not find what the resolution was for the two messages posted by Erich Titl and what kind of connection he is/was using. I am beginning to think that this is not necessarily a network driver issue, even though there have been posts stating such, as most of the posts have been in the last two years and multiple drivers have been used. I have not been able to talk to my ISP to find out what they are sending in response to the DHCPDISCOVER messages and what they expect in return.
Syslog, with the 'new' dhclient, with 1 Linksys PCI NIC connected to the cablemodem and 1 3c509 NIC connected to another computer:
Nov 5 00:40:29 firewall syslogd 1.3-3#31.slink1: restart.
Nov 5 00:40:30 firewall kernel: klogd 1.3-3#31.slink1, log source = /proc/kmsg started.
Nov 5 00:40:30 firewall kernel: Cannot find map file.
Nov 5 00:40:30 firewall kernel: Loaded 14 symbols from 14 modules.
Nov 5 00:40:30 firewall kernel: Linux version 2.2.19-3-LEAF (root@debian) (gcc version 2.7.2.3) #1 Sat Dec 1 12:15:05 CST 2001
Nov 5 00:40:30 firewall kernel: BIOS-provided physical RAM map:
Nov 5 00:40:30 firewall kernel: BIOS-e820: 0009f000 @ 00000000 (usable)
Nov 5 00:40:30 firewall kernel: BIOS-e820: 01f00000 @ 00100000 (usable)
Nov 5 00:40:30 firewall kernel: Console: colour VGA+ 80x25
Nov 5 00:40:30 firewall kernel: Calibrating delay loop... 33.28 BogoMIPS
Nov 5 00:40:30 firewall kernel: Memory: 30264k/32768k available (732k kernel code, 416k reserved, 612k data, 44k init)
Nov 5 00:40:30 firewall kernel: Checking if this processor honours the WP bit even in supervisor mode... Ok.
Nov 5 00:40:30 firewall kernel: Dentry hash table entries: 4096 (order 3, 32k)
Nov 5 00:40:30 firewall kernel: Buffer cache hash table entries: 32768 (order 5, 128k)
Nov 5 00:40:30 firewall kernel: Page cache hash table entries: 8192 (order 3, 32k)
Nov 5 00:40:30 firewall kernel: CPU: Intel 486 DX/2 stepping 05
Nov 5 00:40:30 firewall kernel: Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Nov 5 00:40:30 firewall kernel: Checking 'hlt' instruction... OK.
Nov 5 00:40:30 firewall kernel: POSIX conformance testing by UNIFIX
Nov 5 00:40:30 firewall kernel: PCI: PCI BIOS revision 2.10 entry at 0xf6f41
Nov 5 00:40:30 firewall kernel: PCI: Using configuration type 1
Nov 5 00:40:30 firewall kernel: PCI: Probing PCI hardware
Nov 5 00:40:30 firewall kernel: PCI: 00:91 [1060/673a]: Working around UM8886BF bugs
Nov 5 00:40:30 firewall kernel: Linux NET4.0 for Linux 2.2
Nov 5 00:40:30 firewall kernel: Based upon Swansea University Computer Society NET3.039
Nov 5 00:40:30 firewall kernel: NET4: Unix domain sockets 1.0 for Linux NET4.0.
Nov 5 00:40:30 firewall kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Nov 5 00:40:30 firewall kernel: IP Protocols: ICMP, UDP, TCP
Nov 5 00:40:30 firewall kernel: TCP: Hash tables configured (ehash 32768 bhash 32768)
Nov 5 00:40:30 firewall kernel: Initializing RT netlink socket
Nov 5 00:40:30 firewall kernel: Starting kswapd v 1.5
Nov 5 00:40:30 firewall kernel: Software Watchdog Timer: 0.05, timer margin: 60 sec
Nov 5 00:40:30 firewall kernel: Real Time Clock Driver v1.09
Nov 5 00:40:30 firewall kernel: RAM disk driver initialized: 16 RAM disks of 6144K size
Nov 5 00:40:30 firewall kernel: Floppy drive(s): fd0 is 1.44M
Nov 5 00:40:30 firewall kernel: FDC 0 is an 8272A
Nov 5 00:40:30 firewall kernel: RAMDISK: Compressed image found at block 0
Nov 5 00:40:30 firewall kernel: RAMDISK: Uncompressing root archive: done.
Nov 5 00:40:30 firewall kernel: RAMDISK: Auto Filesystem - minix: 2048i 6144bk 68fdz(68) 1024zs 2147483647ms
Nov 5 00:40:30 firewall kernel: VFS: Mounted root (minix filesystem).
Nov 5 00:40:30 firewall kernel: RAMDISK: Extracting root archive: done.
Nov 5 00:40:30 firewall kernel: VFS: Disk change detected on device fd(2,44)
Nov 5 00:40:30 firewall kernel: Freeing unused kernel memory: 44k freed
Nov 5 00:40:30 firewall kernel: ne2k-pci.c:v1.01a 10/4/2000 D. Becker/P. Gortmaker
Nov 5 00:40:30 firewall kernel: http://www.scyld.com/network/ne2k-pci.html
Nov 5 00:40:30 firewall kernel: eth0: Winbond 89C940 found at 0xff80, IRQ 12, 00:20:78:14:5A:E3.
Nov 5 00:40:30 firewall kernel: eth1: 3c509 at 0x300 tag 1, 10baseT port, address 00 a0 24 98 81 3f, IRQ 10.
Nov 5 00:40:30 firewall kernel: 3c509.c:1.16 (2.2) 2/3/98 [EMAIL PROTECTED]
Nov 5 00:40:30 firewall kernel: eth1: Setting Rx mode to 1 addresses.
Nov 5 00:40:30 firewall /usr/sbin/cron[790]: (CRON) INFO (pidfile fd = 3)
Nov 5 00:40:30 firewall /usr/sbin/cron[791]: (CRON) STARTUP (fork ok)
Nov 5 00:40:30 firewall dhcpd: Internet Software Consortium DHCP Server 2.0pl5
Nov 5 00:40:30 firewall dhcpd: Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
Nov 5 00:40:30 firewall dhcpd: All rights reserved.
Nov 5 00:40:30 firewall dhcpd:
Nov 5 00:40:30 firewall dhcpd: Please contribute if you find this software useful.
Nov 5 00:40:30 firewall dhcpd: For info, please visit http://www.isc.org/dhcp-contrib.html
Nov 5 00:40:30 firewall dhcpd:
Nov 5 00:40:30 firewall dhcpd: Listening on LPF/eth1/00:a0:24:98:81:3f/192.168.1.0
Nov 5 00:40:30 firewall dhcpd: Sending on LPF/eth1/00:a0:24:98:81:3f/192.168.1.0
Nov 5 00:40:30 firewall dhcpd: Sending on Socket/fallback/fallback-net
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:32 firewall dhcpd: DHCPREQUEST for 66.235.19.223 from 00:50:da:c7:26:87 via eth1
Nov 5 00:40:32 firewall dhcpd: DHCPNAK on 66.235.19.223 to 00:50:da:c7:26:87 via eth1
Nov 5 00:40:33 firewall dhcpd: DHCPDISCOVER from 00:50:da:c7:26:87 via eth1
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
Nov 5 00:40:34 firewall dhcpd: DHCPOFFER on 192.168.1.1 to 00:50:da:c7:26:87 via eth1
Nov 5 00:40:34 firewall dhcpd: DHCPREQUEST for 192.168.1.1 from 00:50:da:c7:26:87 via eth1
Nov 5 00:40:34 firewall dhcpd: DHCPACK on 192.168.1.1 to 00:50:da:c7:26:87 via eth1
Nov 5 00:40:34 firewall dhclient: ip length 328 disagrees with bytes received 332.
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
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.
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: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.
Nov 5 00:41:15 firewall kernel: Packet log: input DENY eth0 PROTO=17 172.23.0.5:164 255.255.255.255:164 L=127 S=0x00 I=60658 F=0x0000 T=128 (#9)
Nov 5 00:41:15 firewall kernel: Packet log: input DENY eth0 PROTO=2 0.0.0.0:65535 224.0.0.1:65535 L=28 S=0x00 I=18716 F=0x0000 T=1 (#4)
Nov 5 00:41:17 firewall dhclient: ip length 328 disagrees with bytes received 332.
Nov 5 00:41:17 firewall dhclient: accepting packet with data after udp payload.
Nov 5 00:41:17 firewall dhclient: ip length 328 disagrees with bytes received 332.
Nov 5 00:41:17 firewall dhclient: accepting packet with data after udp payload.
Sorry for such a long post. I guess I'm loooking for the "smoking gun". Thanks for your time and effort.
John Wittenberg
From: Greg Morgan <[EMAIL PROTECTED]>
To: Greg Morgan <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED], John Wittenberg <[EMAIL PROTECTED]>
Subject: Re: [leaf-user] dhclient to dchp server handshaking
Date: Thu, 31 Oct 2002 23:02:27 -0700
John,
Based on these links that google coughed up, I'd try creating a new diskette and reconfiguring your router. Please look at the last link especially. Part of the reply message is quoted below. When a person questions the software integrity on a LEAF diskette distributing, it could be a failing floppy. The other option as noted below is that the network card is bad.
I hope this angle helps,
Greg Morgan
dhrelay
http://www.isc.org/ml-archives/dhcp-server/2000/11/msg00175.html
http://www.isc.org/ml-archives/dhcp-server/2000/11/msg00225.html
dhclient
http://www.isc.org/ml-archives/dhcp-server/2000/05/msg00275.html
http://www.isc.org/ml-archives/dhcp-server/2000/05/msg00276.html
This means that the client mentioned afterwards is sending more bytes
than it says it's sending, which indicates a bug in its IP stack. So
I'd be very suspicious of the software running on that client,
although this particular problem doesn't actually do any harm.
> if it does not work, then i have a message like this:
> May 13 19:11:46 grey dhcpd: ip length 328 disagrees with bytes received
> 332.
> May 13 19:11:46 grey dhcpd: accepting packet with data after udp
> payload.
> May 13 19:11:46 grey dhcpd: Client option option-100 (47) larger than
> buffer.
This means that the packet's corrupt for some reason. Maybe the
network card in the device is bad, or maybe the software running on it
is.
_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail
-------------------------------------------------------
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
