It may also be the different 802.11 layer; it doesn't have to be ath5k specific.
I know there's an outstanding bug with FreeBSD (which uses net80211,
like madwifi does) with power save queue management timers being
off-whack and that appears like this, also I found this comment in the
source:
/*
* NB: We used to deauth the station but it turns out
* the Blackberry Curve 8230 (and perhaps other devices)
* sometimes send the wrong AID when WME is negotiated.
* Being more lenient here seems ok as we already check
* the station is associated and we only return frames
* queued for the station (i.e. we don't use the AID).
*/
That's in hostap_recv_pspoll(), which is handling the power-save polling stuff.
Good luck!
Adrian
On 12 May 2011 05:14, Piotr Kaczorek <piotrkaczo...@bluetrace.eu> wrote:
> W dniu 11.05.2011 06:05, Bob Copeland pisze:
>> On Tue, May 10, 2011 at 9:42 AM, Piotr Kaczorek
>> <piotrkaczo...@bluetrace.eu> wrote:
>>> Is there any known problem with BlackBerry phones?
>>> I've set up hotspot (ath5k + hostapd). Any device can connect to it and
>>> use it (SE P1i, few laptops, iPhone) except BlackBerry (Curve 8520)
>>> phone. It connects to Wifi but i cannot access any website (it displays
>>> can't find server message).
>>> Maybe it's an issue with power management
>> My guess is this. Probably blackberry is going to sleep and missing
>> (or ath5k is not sending) the beacons along with all of the buffered
>> traffic.
>>
>>> (http://thread.gmane.org/gmane.os.freebsd.current/110707)?
>>> A timeout?
>>> I have no idea where to look further for a solution.
>> Try to get a packet capture with a second device, and see if the AP
>> is sending when the station is in power save mode.
>>
> Thanks for your suggestions, i'll probably try that if i will stay with
> ath5k.
> Confirmed this is definately a matter of ath5k driver. I tried madwifi
> and BlackBerry worked.
> Of course i've got the Stuck beacon problem on madwifi.
> Now I'll have to make a decision - try to fix ath5k, try to find working
> madwifi or leave atheros at all and try different wifi card/chipset.
> _______________________________________________
> ath5k-devel mailing list
> ath5k-devel@lists.ath5k.org
> https://lists.ath5k.org/mailman/listinfo/ath5k-devel
>
_______________________________________________
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel
