From owner-freebsd-net@FreeBSD.ORG Mon Mar 23 20:40:55 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E2EA1065670; Mon, 23 Mar 2009 20:40:55 +0000 (UTC) (envelope-from jhay@meraka.csir.co.za) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [IPv6:2001:4200:7000:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 5A0EC8FC19; Mon, 23 Mar 2009 20:40:54 +0000 (UTC) (envelope-from jhay@meraka.csir.co.za) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id C9FC133CB6; Mon, 23 Mar 2009 22:40:50 +0200 (SAST) Date: Mon, 23 Mar 2009 22:40:50 +0200 From: John Hay To: Bruce M Simpson Message-ID: <20090323204050.GA5477@zibbi.meraka.csir.co.za> References: <20090317103650.GA6156@rebelion.Sisis.de> <49BF7DE4.4010804@incunabulum.net> <20090317104548.GB6182@rebelion.Sisis.de> <49BFF258.4020207@freebsd.org> <20090323182310.GA1825@rebelion.Sisis.de> <49C7D89A.6070502@incunabulum.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49C7D89A.6070502@incunabulum.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org, Sam Leffler , Matthias Apitz , bug-followup@freebsd.org, "Sean C. Farley" Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2009 20:40:55 -0000 On Mon, Mar 23, 2009 at 06:44:42PM +0000, Bruce M Simpson wrote: > Matthias Apitz wrote: > >I went today evening with my EeePC and CURRENT on USB key > >to that Greek restaurant; DHCP does not get IP in CURRENT either; > >this is somehow good news, isn't it :-) > > > > This may be orthogonal, but: > A lab colleague and I have been seeing a sporadic problem where the > ath0 exhibits the symptoms of being disassociated from its AP. We are > running RELENG_7 on the EeePC 701 since the open source HAL merge. > In the behaviour we're seeing, we don't see any problem with the > initial dhclient run, the ath0 just seems to get disassociated within > 5-10 minutes of associating. > > If we leave 'ping ' running in the background, we don't > see this problem. > I found doing a -bgscan before it happens, make it not happen. I now have -bgscan in my rc.conf. John -- John Hay -- John.Hay@meraka.csir.co.za / jhay@FreeBSD.org