#698: madwifi-ng not associating with some access-points
------------------------------------+---------------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: driver | Version:
Resolution: | Keywords: roamabout associate
Patch_attached: 0 |
------------------------------------+---------------------------------------
Comment (by Till Wollenberg (wollenberg _at_ web _dot_ de)):
After some investigation I found out that the most probable reason for
this bug is the chipset used in RoamAbout access-points. It's an Agere
/Orinoco-chipset which sends out malformed management frames. The madwifi-
ng-driver introduced checks for those malformed frames in r1409. The
malformed frames are discarded shortly after reception (in
net80211/ieee80211_input.c) and so the 802.11 state-machine does not "see"
the positive answer of the access-point in the association-phase.
Disabling those checks is not really an option since without them
malformed (probably "prepared"...) frames would cause illegal memory-
access on kernel-level. The only way out seems to be some special checks
for Agere/Orinoco-tags to handle the illegal length-parameters.
This bug is also discussed in tickets #353 and #428 (the latter one is
more recent but does not provide a soloution, too).
--
Ticket URL: <http://madwifi.org/ticket/698>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
