Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 19 Aug 2006 11:20:16 GMT
From:      Joost Bekkers <joost@jodocus.org>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: bin/102226: dhclient stops working, 100% cpu and logs at ~4000 lines/sec
Message-ID:  <200608191120.k7JBKGtP009094@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/102226; it has been noted by GNATS.

From: Joost Bekkers <joost@jodocus.org>
To: Brooks Davis <brooks@one-eyed-alien.net>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: bin/102226: dhclient stops working, 100% cpu and logs at ~4000 lines/sec
Date: Sat, 19 Aug 2006 13:17:41 +0200

 On Fri, Aug 18, 2006 at 08:56:44AM -0500, Brooks Davis wrote:
 > > >How-To-Repeat:
 > > 
 > > 	/sbin/dhclient <interface>
 > > 
 > > 	and wait.
 > 
 > Since this happends to virtually no one else (your's sounds a lot more
 > repeatable than any cases I've heard previously), we'll need more
 > information to have any chance of reproducing this.  Realistically it's
 > not going to be possible for me to do it since it's probably hardware
 > dependent (quite possible a NIC + switch/modem combination).  What I'd
 > like you to do is is capture all dhcp traffic on the interface until
 > this happens so I can look at the packet stream and see what's coming in
 > and how we're mishandling it.  I think the following should do it:
 > 
 > tcpdump -i <interface> -s 0 -w dhcp.pcap port 67 
 > 
 > Once you've got that, compress it and put it somewhere I can download
 > it.  Feel free to send the trace in private e-mail if you don't want the
 > information to be public.
 > 
 
 We're in luck, it already happend again. Aug 19 10:26:25 local time
 
 Capture and log are available at the site mentioned in private mail.
 
 -- 
 greetz Joost
 joost@jodocus.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200608191120.k7JBKGtP009094>