#651: unable to associate to AP using WEP with madwifi-ng
-------------------------------------------+--------------------------------
Reporter: [EMAIL PROTECTED] | Owner: mentor
Type: defect | Status: assigned
Priority: major | Milestone:
Component: madwifi: other | Version:
Resolution: | Keywords: associating fails
Patch_attached: 0 |
-------------------------------------------+--------------------------------
Comment (by [EMAIL PROTECTED]):
Interesting that this still doesn't work. I can't reproduce what you are
seeing. There are a few odd things you could investigate.
Your scan appears to show two APs with the same address but different
SSIDs. That's a little strange.
The madwifi debug output logs an assoc_resp packet from the AP that seems
bad. The packet looks reasonable up through 82 84 0b 16, which indicates
supported rates of 1, 2, 5.5 and 11 Mbit/sec, then the remaining 20 bytes
don't look like anything ethereal recognizes as normal. If you add
'+elemid' to your 80211debug command, I think madwifi will spit out errors
saying the packet is too short. Actually, the packet is too long. It's
like it had garbage tacked on the end.
If you can capture traffic of another driver successfully associating with
this AP, I'd like to see it.
--
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
