Date: Mon, 23 Mar 2009 22:40:50 +0200 From: John Hay <jhay@meraka.org.za> To: Bruce M Simpson <bms@incunabulum.net> Cc: freebsd-net@freebsd.org, Sam Leffler <sam@freebsd.org>, Matthias Apitz <guru@unixarea.de>, bug-followup@freebsd.org, "Sean C. Farley" <scf@freebsd.org> Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Message-ID: <20090323204050.GA5477@zibbi.meraka.csir.co.za> In-Reply-To: <49C7D89A.6070502@incunabulum.net> References: <20090317103650.GA6156@rebelion.Sisis.de> <49BF7DE4.4010804@incunabulum.net> <20090317104548.GB6182@rebelion.Sisis.de> <alpine.BSF.2.00.0903171148250.51892@thor.farley.org> <49BFF258.4020207@freebsd.org> <20090323182310.GA1825@rebelion.Sisis.de> <49C7D89A.6070502@incunabulum.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <ap-ip-address>' 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090323204050.GA5477>