Date: Mon, 23 Jan 2006 13:42:26 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: Krzysztof Kowalik <kkowalik@uci.agh.edu.pl> Cc: freebsd-stable@freebsd.org Subject: Re: dhclient wedged Message-ID: <20060123214226.GA11995@odin.ac.hmc.edu> In-Reply-To: <20060123090656.GA22255@uci.agh.edu.pl> References: <43D339CC.3020204@forrie.com> <20060122155131.GA823@the-grills.com> <20060122221828.GA7703@odin.ac.hmc.edu> <20060123090656.GA22255@uci.agh.edu.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
--9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 23, 2006 at 10:06:56AM +0100, Krzysztof Kowalik wrote: > Brooks Davis <brooks@one-eyed-alien.net> wrote: > > This definitly sounds like something particular to your dhcp servers. > > It would be nice if we could fix it, but without some debugging help > > that's going to be pretty much impossible. [...] >=20 > It happens to me quite often, too. The only thing related in the > non-debug messages is: >=20 > Jan 8 12:02:19 moneypenny dhclient[68091]: 5 bad IP checksums seen in 5 = packets > Jan 8 12:02:49 moneypenny last message repeated 743054 times > Jan 8 12:04:50 moneypenny last message repeated 2951866 times > Jan 8 12:14:51 moneypenny last message repeated 14457921 times > Jan 8 12:24:52 moneypenny last message repeated 14812032 times > Jan 8 12:34:53 moneypenny last message repeated 14770327 times > Jan 8 12:44:55 moneypenny last message repeated 14748300 times > Jan 8 12:51:44 moneypenny last message repeated 10037074 times >=20 > ... which accounts for the CPU usage, I guess. I killed the "bad IP > checksums" messages, so it doesn't annoy my syslog anymore, but it of > course didn't fix the underlaying issue.=20 >=20 > I was looking at those packets with tcpdump once and didn't see anything > obvious/bad there. >=20 > And yes, I didn't have this problem with ISC client. And I surely use > different cable provider, than the original poster ;) What NIC are you using? This particular issue sounds like a NIC returning corrupt packets for some reason. Alternatively, the sending server could be producing corrupt packets. Some tcpdump traces (preferably raw dumps) could be useful. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --9jxsPFA5p3P2qPhR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFD1U3CXY6L6fI4GtQRAtvvAJ9OT5rNrfjES1ehZRh8ZW5ok2ET2wCfXq52 inlkFcP2RbSiIHiszJecr3Y= =mxNG -----END PGP SIGNATURE----- --9jxsPFA5p3P2qPhR--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060123214226.GA11995>