From owner-freebsd-stable@FreeBSD.ORG Mon Aug 4 10:29:44 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF79F1065684 for ; Mon, 4 Aug 2008 10:29:44 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by mx1.freebsd.org (Postfix) with ESMTP id 7B6938FC41 for ; Mon, 4 Aug 2008 10:29:44 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: by yw-out-2324.google.com with SMTP id 9so931775ywe.13 for ; Mon, 04 Aug 2008 03:29:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=S7pGihmoYa2WTx/8gIjWqXI12mxM+MzYmMUsUMB1+XU=; b=KOaHGPtpnLkX0ZuWL+DLpnQ/6SZgGoSUpewCK480nnNpr5MnXKDBQqq9HQTl45h8O0 XJubLluQ1sRTqZNBGj7wQRRTepESRhbcecteBOTS569nrRW9LjOnj+MwnIf8xAWcrDx7 CnbZ2hM2OhjJgbu2kTaGen3KpUw2AZt+EBlUo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=S0tdFWTZM+h+NsVk7hFe70AyqisnRUjLduAOKswYwBnGsql5Zhdtm6vmmbMk6SwK5r G1zvW5+/JJtNMdWYxFfdZrMR180u6r21E7vqLboNiAw1TM1pyIoHMNB2+NzyFnHFrV2z hweauosx/+soYV+VoducE1NU008Dx/6i44Hds= Received: by 10.151.27.15 with SMTP id e15mr7998922ybj.33.1217845783834; Mon, 04 Aug 2008 03:29:43 -0700 (PDT) Received: by 10.150.229.11 with HTTP; Mon, 4 Aug 2008 03:29:43 -0700 (PDT) Message-ID: Date: Mon, 4 Aug 2008 11:29:43 +0100 From: "Chris Rees" To: "Jeremy Chadwick" In-Reply-To: <20080804102419.GB28928@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080804102419.GB28928@eos.sc1.parodius.com> Cc: Torfinn Ingolfsen , freebsd-stable@freebsd.org, Martin Subject: Re: em(4) on FreeBSD is sometimes annoying X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2008 10:29:44 -0000 2008/8/4 Jeremy Chadwick : > On Mon, Aug 04, 2008 at 11:00:16AM +0100, Chris Rees wrote: >> Martin wrote: >> >> > On Sat, 02 Aug 2008 12:55:53 +0200 >> > Torfinn Ingolfsen wrote: >> > >> >> Just to be sure: also if the first command you try on the interface is >> >> 'ifconfig up'? >> > >> > Hello Torfinn, >> > >> > good point, no. The problem appears when the first thing called on this >> > interface is dhclient (caused by ifconfig_em0="DHCP"). I could also >> > provoke this behavior after the interface was once up had an IP and was >> > working (ping). All I need to do is to disconnect the NIC from the >> > switch when I type "/etc/rc.d/netif restart". >> > >> > I have noticed further strange effects here. The behavior seems to >> > be even more complex. >> > >> > After I typed "/etc/rc.d/netif restart", I waited until I get "giving >> > up" message. Then I plugged the cable in. After about 30 seconds the >> > link LED was on. I noticed that at this point I couldn't get an address >> > using DHCP. >> > >> > So I disconnected physically the NIC (no cable) and link LED was >> > still on! ifconfig showed me "state: active" with no cable plugged in. >> > After further 30 seconds the LED went off. >> > >> > I attached the NIC again to the switch again and after 30 seconds >> > again I got some other effect. The link LED went on (status: active) >> > and the data LED was permanently blinking (about 2,5 times a second). I >> > pulled the cable again and now the link LED is still on and the data >> > LED still blinking (since about 10 minutes already). >> > >> > By the way... >> > Now I'm typing this E-Mail without an ethernet cable plugged in and the >> > link status LED is still on and the other data LED is blinking. >> > >> > -- >> > Martin >> > >> I may have misunderstood the purpose of this, but do you have the bpf >> compiled into your kernel? If you're having DHCP troubles, this could >> be a problem. > > I have never seen "device bpf" cause any sort of DHCP-related problems > on FreeBSD. > > Can you expand on this, and provide reference material confirming such? > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > Sorry, I was referring to the possible absence of it. Ref: http://www.freebsd.org/doc/en/books/handbook/network-dhcp.html , section 27.5.4: "Make sure that the bpf device is compiled into your kernel. To do this, add device bpf to your kernel configuration file, and rebuild the kernel." Chris -- R< $&h ! > $- ! $+ $@ $2 < @ $1 .UUCP. >