Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 18 Aug 2006 14:00:39 GMT
From:      Brooks Davis <brooks@one-eyed-alien.net>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: bin/102226: dhclient stops working, 100% cpu and logs at ~4000 lines/sec
Message-ID:  <200608181400.k7IE0dUl048539@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: Brooks Davis <brooks@one-eyed-alien.net>
To: Joost Bekkers <joost@jodocus.org>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: bin/102226: dhclient stops working, 100% cpu and logs at ~4000 lines/sec
Date: Fri, 18 Aug 2006 08:56:44 -0500

 > >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.
 
 -- Brooks



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