logo       

[madwifi-tickets] [MadWifi] #708: Frames routing mechanism does not allow t: msg#00357

linux.drivers.madwifi.tickets

Subject: [madwifi-tickets] [MadWifi] #708: Frames routing mechanism does not allow to switch easy from one VAP to another for some devices

#708: Frames routing mechanism does not allow to switch easy from one VAP to
another for some devices
-------------------------------------------------+--------------------------
Reporter: "Ivan S. Dubrov" <wfragg@xxxxxxxxx> | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: driver | Version:
Keywords: | Patch_attached: 0
-------------------------------------------------+--------------------------
The code in the ath_rx_tasklet() function (if_ath.c:5550) contains a code
that routes the incoming frame to one of the VAP (or spams all VAPs). If
the device is already connected (let's say, to the ath0), then all
messages that come from this device are routed to the ath0 VAP only.

So if this device sends "PROBE REQ" then only one VAP answers. This makes
some Pocket PC's unhappy since they think that other VAP is unavailable.
The same with other frames (like auth), I suppose.

--
Ticket URL: <http://madwifi.org/ticket/708>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity _______________________________________________
Madwifi-tickets mailing list
Madwifi-tickets@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise