kern/132722: [ath] Wifi ath0 associates fine with AP,
but DHCP or IP does not work
John Hay
jhay at meraka.org.za
Mon Mar 23 13:40:55 PDT 2009
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
More information about the freebsd-net
mailing list