Re: [leaf-user] DHCLIENT errors filling up my log...eigerstein.
On Friday 14 June 2002 10:02, Charles Steinkuehler wrote: 1) How do I install udhcp-0.9.6-compiled.tar.gz if I want to use it? Do I just copy it onto the LEAF and uncompress/untar it in some directory, then backup? Or is it something else. This is the non-packaged binary Charles' made available for someone to package. You can find the LEAF package of udhcp at: http://leaf.sourceforge.net/devel/guitarlynn I hope this helps, -- ~Lynn Avants aka Guitarlynn guitarlynn at users.sourceforge.net http://leaf.sourceforge.net If linux isn't the answer, you've probably got the wrong question! ___ Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ 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
Re: [leaf-user] DHCLIENT errors filling up my log...eigerstein.
Resend as plain text Michael McClure wrote: 3 questions: 1) How do I install udhcp-0.9.6-compiled.tar.gz if I want to use it? Do I just copy it onto the LEAF and uncompress/untar it in some directory, then backup? Or is it something else. 2) I did download the dhclient.lrp which is version 2.0pl5: # lrpkg -l NameVersionDescription ===-==-== root 3.1.0 etc 3.1.0 log 3.1.0 local 3.1.0 Local package. This package does not contain a modules 3.1.0 Modules package. Contains kernel modules and u dhcpd 2.0.1 dhcpd - Autoconfigure client machines dnscache1.00 dnscache - Provide a local DNS cache sshd 1.2.26-1 dhclient2.0pl5 dhclient - Dynamically configure an interface and yet I still get the cannot load error. 3) What do I have to change to not log the error? Jun 13 00:03:34 mikerouter dhclient: ip length 328 disagrees with bytes received 332. This thing is filling up my ramdisk. 4)Bonus question -- should I upgrade to dachstein? Are there any compelling reasons to do so (i.e. security holes that are cleaned up, less space, less bugs, etc) over Eigerstein? The functionality of eigerstein suits me fine, and I don't want to have to learn iptables -- ipchains makes sense to me, iptables doesn't. thanks, charles. mike. Charles Steinkuehler wrote: Jun 13 00:03:34 mikerouter dhclient: ip length 328 disagrees with bytes received 332. IIRC, this is a known bug in a widly released non-linux based DHCP server (BSD or Solaris, if memory serves). Nothing to do about this but ignore (or not log) the errors...or get your ISP to update their DHCP server (good luck there :). Jun 13 00:03:34 mikerouter dhcpd: receive_packet failed on eth1: Network is down This is the classic symptom of a bug in all dhclient packages from me except the latest (caused by an error in translating the dhclient scripts from ifconfig/route to iproute2). Replace your dhclient.lrp with the lastest one from my website (or the udhcp package recently made available, if you want extra space!), and you should be able to correctly re-start. Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cf m?source=osdntextlink 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 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink 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
Re: [leaf-user] DHCLIENT errors filling up my log...eigerstein.
1) How do I install udhcp-0.9.6-compiled.tar.gz if I want to use it? Do I just copy it onto the LEAF and uncompress/untar it in some directory, then backup? Or is it something else. Copy the package file to your floppy and add the package to the LRP= part of your syslinux.cfg file. 2) I did download the dhclient.lrp which is version 2.0pl5: # lrpkg -l NameVersionDescription dhclient2.0pl5 dhclient - Dynamically configure an interface and yet I still get the cannot load error. Hmm...there could be something else wrong. Please provide the exact circumstances involved, and the exact error(s) generated. 3) What do I have to change to not log the error? Jun 13 00:03:34 mikerouter dhclient: ip length 328 disagrees with bytes received 332. This thing is filling up my ramdisk. You'll probably have to stop *ALL* logging from dhclient. You control this with the /etc/syslog.conf file. I don't off-hand remember how you'd do this, but a quick google search should turn up man pages and/or helpful info. 4)Bonus question -- should I upgrade to dachstein? Are there any compelling reasons to do so (i.e. security holes that are cleaned up, less space, less bugs, etc) over Eigerstein? The functionality of eigerstein suits me fine, and I don't want to have to learn iptables -- ipchains makes sense to me, iptables doesn't. You should upgrade. Dachstein is still based on a 2.2 kernel (ipchains), and is a direct decendant of EigerStein. Basically, Dachstein is EigerStein with several updated binaries, a newer kernel, and enhanced firewall scripts, so you should feel right at home coming from any of the other mountain based releases (ie Eiger/Materhorn). Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink 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
Re: [leaf-user] DHCLIENT errors filling up my log...eigerstein.
More info from the logs: Jun 13 00:03:34 mikerouter dhclient: ip length 328 disagrees with bytes received 332. Jun 13 00:03:34 mikerouter dhclient: accepting packet with data after udp payload. Jun 13 00:03:34 mikerouter dhclient: ip length 328 disagrees with bytes received 332. Jun 13 00:03:34 mikerouter dhclient: accepting packet with data after udp payload. Jun 13 00:03:34 mikerouter dhcpd: receive_packet failed on eth1: Network is down Jun 13 00:03:48 mikerouter dhclient: ip length 328 disagrees with bytes received 332. Jun 13 00:03:48 mikerouter dhclient: accepting packet with data after udp payload. Jun 13 00:03:48 mikerouter dhclient: ip length 328 disagrees with bytes received 332. Jun 13 00:03:48 mikerouter dhclient: accepting packet with data after udp payload. Jun 13 00:04:04 mikerouter dhclient: ip length 328 disagrees with bytes received 332. Any help would be greatly appreciated. TIA. mike. Michael McClure wrote: I was recently forced to switch from dedicated to dhclient ip by my cable modem company. It worked fine, but I'm getting the following messages in my log (which are shown in a manual startup: # svi dhclient start Starting dhclient... Internet Software Consortium DHCP Client 2.0pl5 Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium. All rights reserved. Please contribute if you find this software useful. For info, please visit http://www.isc.org/dhcp-contrib.html IP filters: [IP Forwarding: DISABLED] flushed Listening on LPF/eth0/00:80:29:68:a1:4f Sending on LPF/eth0/00:80:29:68:a1:4f Sending on Socket/fallback/fallback-net IP filters: [IP Forwarding: DISABLED] flushed IP filters: [IP Forwarding: DISABLED] flushed DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20 ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPOFFER from 64.255.221.4 ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPOFFER from 64.255.221.4 DHCPOFFER already seen. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPOFFER from 64.255.221.4 DHCPOFFER already seen. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPOFFER from 64.255.221.4 DHCPOFFER already seen. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPOFFER from 64.255.221.4 DHCPOFFER already seen. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPOFFER from 64.255.221.4 DHCPOFFER already seen. DHCPREQUEST on eth0 to 255.255.255.255 port 67 ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPACK from 64.255.221.4 IP filters: firewall [IP Forwarding: ENABLED] Would send signal 15 to 1904. Stopped /usr/sbin/dnscache (pid 1904). Starting /usr/sbin/dnscache... bound to 66.235.3.59 -- renewal in 43200 seconds. In addition, when I tried a restart, I got some errors in the script: # svi dhclient restart Starting dhclient... Internet Software Consortium DHCP Client 2.0pl5 Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium. All rights reserved. Please contribute if you find this software useful. For info, please visit http://www.isc.org/dhcp-contrib.html
Re: [leaf-user] DHCLIENT errors filling up my log...eigerstein.
I have seen mention of a nic driver bug awhile back that got fixed. http://www.scyld.com/pipermail/realtek/2000-October/000659.html On Wed, 12 Jun 2002, Michael McClure wrote: More info from the logs: Jun 13 00:03:34 mikerouter dhclient: ip length 328 disagrees with bytes received 332. Jun 13 00:03:34 mikerouter dhclient: accepting packet with data after udp payload. Jun 13 00:03:34 mikerouter dhclient: ip length 328 disagrees with bytes received 332. Jun 13 00:03:34 mikerouter dhclient: accepting packet with data after udp payload. Jun 13 00:03:34 mikerouter dhcpd: receive_packet failed on eth1: Network is down Jun 13 00:03:48 mikerouter dhclient: ip length 328 disagrees with bytes received 332. Jun 13 00:03:48 mikerouter dhclient: accepting packet with data after udp payload. Jun 13 00:03:48 mikerouter dhclient: ip length 328 disagrees with bytes received 332. Jun 13 00:03:48 mikerouter dhclient: accepting packet with data after udp payload. Jun 13 00:04:04 mikerouter dhclient: ip length 328 disagrees with bytes received 332. Any help would be greatly appreciated. TIA. mike. Michael McClure wrote: I was recently forced to switch from dedicated to dhclient ip by my cable modem company. It worked fine, but I'm getting the following messages in my log (which are shown in a manual startup: # svi dhclient start Starting dhclient... Internet Software Consortium DHCP Client 2.0pl5 Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium. All rights reserved. Please contribute if you find this software useful. For info, please visit http://www.isc.org/dhcp-contrib.html IP filters: [IP Forwarding: DISABLED] flushed Listening on LPF/eth0/00:80:29:68:a1:4f Sending on LPF/eth0/00:80:29:68:a1:4f Sending on Socket/fallback/fallback-net IP filters: [IP Forwarding: DISABLED] flushed IP filters: [IP Forwarding: DISABLED] flushed DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20 ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPOFFER from 64.255.221.4 ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPOFFER from 64.255.221.4 DHCPOFFER already seen. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPOFFER from 64.255.221.4 DHCPOFFER already seen. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPOFFER from 64.255.221.4 DHCPOFFER already seen. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPOFFER from 64.255.221.4 DHCPOFFER already seen. ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPOFFER from 64.255.221.4 DHCPOFFER already seen. DHCPREQUEST on eth0 to 255.255.255.255 port 67 ip length 328 disagrees with bytes received 332. accepting packet with data after udp payload. DHCPACK from 64.255.221.4 IP filters: firewall [IP Forwarding: ENABLED] Would send signal 15 to 1904. Stopped /usr/sbin/dnscache (pid 1904). Starting /usr/sbin/dnscache... bound to 66.235.3.59 -- renewal in 43200 seconds. In addition, when I tried a restart, I got some errors in the script: # svi
Re: [leaf-user] DHCLIENT errors filling up my log...eigerstein.
Jun 13 00:03:34 mikerouter dhclient: ip length 328 disagrees with bytes received 332. IIRC, this is a known bug in a widly released non-linux based DHCP server (BSD or Solaris, if memory serves). Nothing to do about this but ignore (or not log) the errors...or get your ISP to update their DHCP server (good luck there :). Jun 13 00:03:34 mikerouter dhcpd: receive_packet failed on eth1: Network is down This is the classic symptom of a bug in all dhclient packages from me except the latest (caused by an error in translating the dhclient scripts from ifconfig/route to iproute2). Replace your dhclient.lrp with the lastest one from my website (or the udhcp package recently made available, if you want extra space!), and you should be able to correctly re-start. Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink 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
[leaf-user] DHCLIENT errors filling up my log...eigerstein.
I was recently forced to switch from dedicated to dhclient ip by my
cable modem company. It worked fine, but I'm getting the following
messages in my log (which are shown in a manual startup:
# svi dhclient start
Starting dhclient...
Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.
Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html
IP filters: [IP Forwarding: DISABLED] flushed
Listening on LPF/eth0/00:80:29:68:a1:4f
Sending on LPF/eth0/00:80:29:68:a1:4f
Sending on Socket/fallback/fallback-net
IP filters: [IP Forwarding: DISABLED] flushed
IP filters: [IP Forwarding: DISABLED] flushed
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPOFFER from 64.255.221.4
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPOFFER from 64.255.221.4
DHCPOFFER already seen.
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPOFFER from 64.255.221.4
DHCPOFFER already seen.
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPOFFER from 64.255.221.4
DHCPOFFER already seen.
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPOFFER from 64.255.221.4
DHCPOFFER already seen.
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPOFFER from 64.255.221.4
DHCPOFFER already seen.
DHCPREQUEST on eth0 to 255.255.255.255 port 67
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPACK from 64.255.221.4
IP filters: firewall [IP Forwarding: ENABLED]
Would send signal 15 to 1904.
Stopped /usr/sbin/dnscache (pid 1904).
Starting /usr/sbin/dnscache...
bound to 66.235.3.59 -- renewal in 43200 seconds.
In addition, when I tried a restart, I got some errors in the script:
# svi dhclient restart
Starting dhclient...
Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.
Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html
/var/state/dhcp/dhclient.leases line 36: no option named dhlease
option dhlease {
^
/var/state/dhcp/dhclient.leases line 50: expecting lease declaration.
lease
^
/var/state/dhcp/dhclient.leases line 64: expecting semicolon.
lease
^
/var/state/dhcp/dhclient.leases line 78: expecting lease declaration.
lease
^
/var/state/dhcp/dhclient.leases line 92: expecting semicolon.
lease
^
/var/state/dhcp/dhclient.leases line 106: expecting lease declaration.
lease
^
/var/state/dhcp/dhclient.leases line 120: expecting semicolon.
lease
^
/var/state/dhcp/dhclient.leases line 133: unterminated lease declaration.
lease {
^
IP filters: [IP Forwarding: DISABLED] flushed
Listening on LPF/eth0/00:80:29:68:a1:4f
Sending on LPF/eth0/00:80:29:68:a1:4f
Sending on Socket/fallback/fallback-net
IP filters: [IP Forwarding: DISABLED] flushed
IP filters: [IP Forwarding: DISABLED] flushed
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to
