kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work

[John Hay]

The following reply was made to PR kern/132722; it has been noted by GNATS.

From: John Hay <jhay at meraka.org.za>
To: Bruce M Simpson <bms at incunabulum.net>
Cc: Matthias Apitz <guru at unixarea.de>, freebsd-net at freebsd.org,
	Sam Leffler <sam at freebsd.org>, "Sean C. Farley" <scf at freebsd.org>,
	bug-followup at freebsd.org
Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
Date: Mon, 23 Mar 2009 22:40:50 +0200

 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 at meraka.csir.co.za / jhay at FreeBSD.org