#651: unable to associate to AP using WEP with madwifi-ng
-------------------------------------------+--------------------------------
Reporter: [EMAIL PROTECTED] | Owner: mentor
Type: defect | Status: assigned
Priority: major | Milestone: version 0.9.x -
progressive release candidate phase
Component: madwifi: other | Version: trunk
Resolution: | Keywords: associating fails
Patch_attached: 0 |
-------------------------------------------+--------------------------------
Comment (by [EMAIL PROTECTED]):
I can sometimes, sort of, nearly reproduce this.
Sometimes my card is slower to associate with the AP than it should be.
If I look in the logs produced from 80211debug +recv +recv_desc, I can see
what looks like broken packets being received from the AP. When this
happens, the driver ignores the packet, and eventually the association or
the authentication times out.
Then the driver rescans, finds the same AP, and the process repeats. The
timeout appears to be five seconds. Sometimes several attempts are
necessary before the association succeeds.
Leo - what happens if you wait for 60 seconds after you run your
association script? Does it work then? If so, maybe I am seeing the same
problem you are seeing.
I'm going to do some more tests to try to pin down whether my AP is
actually sending broken packets, or if madwifi is damaging the packets
after reception.
--
Ticket URL: <http://madwifi.org/ticket/651>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
