#682: WEP encryption does not work
----------------------------------------+-----------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: closed
Priority: major | Milestone:
Component: madwifi: other | Version:
Resolution: invalid | Keywords: wep
Patch_attached: 0 |
----------------------------------------+-----------------------------------
Changes (by brian):
* resolution: => invalid
* status: reopened => closed
Comment:
Your symptoms are different, and the resolution of the problem is
different. There is no way your problem is the same as jarviskin's. If
anything, this is a new defect, but this actually sounds more like a
configuration problem to me. The select_bss failure means that madwifi
scanned for APs, but didn't find a suitable access point. If you send me
([EMAIL PROTECTED]) your debug output I'll have a look to see what APs
were found and why madwifi didn't select any of them. Otherwise I suggest
you take this up on IRC or the madwifi-users mailing list.
(Now that you mention it, Jarviskin's logs were a little odd... that
error message from madwifi means that the AP was sending an authentication
frame with the authentication algorithm set to "open", and that failure
code. Maybe the AP responds that way if there is a conflict between the
station auth algorithm and the AP auth algorithm?)
--
Ticket URL: <http://madwifi.org/ticket/682>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
