Date: Mon, 23 Jan 2006 10:06:56 +0100 From: Krzysztof Kowalik <kkowalik@uci.agh.edu.pl> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: freebsd-stable@freebsd.org Subject: Re: dhclient wedged Message-ID: <20060123090656.GA22255@uci.agh.edu.pl> In-Reply-To: <20060122221828.GA7703@odin.ac.hmc.edu> References: <43D339CC.3020204@forrie.com> <20060122155131.GA823@the-grills.com> <20060122221828.GA7703@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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. [...] 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 ;) -- Krzysztof Kowalik | () ASCII Ribbon Campaign Computer Center, AGH UST | /\ Support plain text e-mail
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060123090656.GA22255>