#1957: beacon miss causes client to reassociate
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: driver | Version: trunk
Resolution: | Keywords: beacon miss disconnect
Patch_attached: 0 |
-----------------------------------+----------------------------------------
Comment (by [EMAIL PROTECTED]):
I am experiencing something similar. The network consists of multiple APs,
non-encrypted with a VPN on top of it. When a beacon is missed, a
disconnect, and reauthentication follows. The state changes are beacon
miss triggers the state transitions run -> scan -> auth -> run. All this
takes only a couple of sec. and the VPN connection stays intact.
But whenever a beacon is received while authenticating, there is an
additional auth -> scan transition and and a new scan is triggered. Beacon
miss triggers the state transitions run -> scan -> auth (here a beacon is
received)-> scan ...
So the reathentication is delayed by several seconds and the VPN
connection is gone.
Is there anything I can do about it?
(I am using a T40p with a 5211 chip)
--
Ticket URL: <http://madwifi.org/ticket/1957#comment:3>
madwifi.org <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
