#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]):
The problem isn't the AP, it's either the card or the driver. I verified
this by comparing the packets captured by another card with the packets
madwifi logged to kern.log. The madwifi version of the packet has 4 extra
bytes tacked on the end.
While figuring that out, I noticed some other strange behavior.
Occasionally the message "ath_rx_tasklet: short packet 14"
On tests when the association works immediately, a madwifi monitor mode
vap is able to capture packets.
On tests when the association fails at first, a madwifi monitor mode vap
fails to capture any packets.
I'll attach my test script in a minute.
--
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
