DHCP oddity

Brian Candler B.Candler at pobox.com
Tue Dec 27 05:06:19 PST 2005


On Mon, Dec 26, 2005 at 12:15:14PM -0600, Skylar Thompson wrote:
> While doing some network stress-tests from a dual-CPU x86 FreeBSD 5.4 
> server, I noticed that a "ping -f" drives dhcpd's CPU usage way up. I 
> put dhcpd into debug mode and didn't  get any error messages. I then ran 
> dhcpd with strace, and saw loads of these messages when I started the 
> ping flood:
> 
> select(8, [?], [?], [?], NULL)          = 1 ()
> gettimeofday({...}, NULL)               = 0
> recvfrom(4, 0xbfbfe090, 1500, 0, {...}, [?]) = 84
> select(8, [?], [?], [?], NULL)          = 1 ()
> gettimeofday({...}, NULL)               = 0
> recvfrom(4, 0xbfbfe090, 1500, 0, {...}, [?]) = 84
> 
> Does anyone know why this would happen?

Were you running tcpdump or similar at the same time, such that the
interface was put into promiscuous mode?

Check using ifconfig that it is not (i.e. there is no PROMISC flag shown)


More information about the freebsd-net mailing list