#848: Beacon misses cause client to reassociate
----------------------------------------+-----------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: 802.11 stack | Version:
Resolution: | Keywords:
Patch_attached: 0 |
----------------------------------------+-----------------------------------
Comment (by [EMAIL PROTECTED]):
Even with a good professional grade access point (Proxim AP-700) I am
still seeing approximately 5 beacon misses per day. These are all from the
hardware interrupt (the software timer does not appear to be running).
At the same time, I am running an ipw3945 in monitor mode directly next to
the system with the atheros card (AR5005G). The ipw3945 system sees 9 or
10 beacons per second during the time when madwifi receives the bmiss
interrupt.
The patches in #511 don't help a huge amount (beacon interval is 100) but
they do improve the situation a little - I have seen it ignore one or two
bmiss interrupts due to them occurring soon after the last beacon timer
configuration.
I am finding that increasing beacon interval to 20 makes it slightly more
reliable. I also tried increasing it to 50 and it *still* generated bmiss
interrupts. That means the device went deaf for more than 5 seconds!
--
Ticket URL: <http://madwifi.org/ticket/848>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
