On Mon, Jan 23, 2006 at 10:06:56AM +0100, Krzysztof Kowalik wrote: > Brooks Davis <[EMAIL PROTECTED]> 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. [...] > > It happens to me quite often, too. The only thing related in the > non-debug messages is: > > 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 > > ... 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. > > I was looking at those packets with tcpdump once and didn't see anything > obvious/bad there. > > 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 -- 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
pgprpjH6da2ZF.pgp
Description: PGP signature
