#1188: Can connect to the AP, but network doensn't work.
------------------------------------------+---------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: other | Version: v0.9.2.1
Resolution: | Keywords:
Patch_attached: 0 |
------------------------------------------+---------------------------------
Comment (by Bas):
Hi,
I experienced the same problems when connecting a non-atheros/madwifi
based client (Intel/WinXP) to a madwifi based AP.
Turning off Fast Frames (FF) resolved the problem for me. So I took a look
in the code, and it seems that on association of a client, the Atheros
specific capabilities of the AP are copied to the client, but never
cleared. This results in the AP sending FastFrames to the client, which
the client obviously does not understand. In this case, ping will work
because the ping packets are small, but full sized packets will be
concatenated by the FF code.
I have made some changes to the code to reset the capabilities on
association.
Please see attached ni_state patch.
This fix might apply to some more tickets with vague connection problems
as well.
Best regards,
Bas
--
Ticket URL: <http://madwifi.org/ticket/1188#comment:4>
madwifi.org <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
