Date: Mon, 23 Mar 2009 18:44:42 +0000 From: Bruce M Simpson <bms@incunabulum.net> To: Matthias Apitz <guru@unixarea.de> Cc: freebsd-net@freebsd.org, Sam Leffler <sam@freebsd.org>, "Sean C. Farley" <scf@freebsd.org>, bug-followup@freebsd.org Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Message-ID: <49C7D89A.6070502@incunabulum.net> In-Reply-To: <20090323182310.GA1825@rebelion.Sisis.de> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
We have yet to produce a tcpdump to catch it 'in the act' and
observe the DLT_IEEE80211 traffic when it actually happens, I have only
seen the symptoms. The AP does not show the EeePC units as being
associated any more at this point, but ath0 still shows 'status:
associated'. The AP involved is a Netgear WG602 V2, and is running the
vendor's firmware.
I'll try to get set up with 'tcpdump -y ieee802_11' from initial boot
(including dhcp and anything we bump into).
cheers
BMS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49C7D89A.6070502>