#698: madwifi-ng not associating with some access-points
-----------------------------------------------+----------------------------
Reporter: wollenberg _at_ web _dot_ de | Owner:
Type: defect | Status: new
Priority: major | Milestone: version 0.9.x -
progressive release candidate phase
Component: madwifi: driver | Version: trunk
Resolution: | Keywords: roamabout
associate
Patch_attached: 1 |
-----------------------------------------------+----------------------------
Comment (by [EMAIL PROTECTED]):
A few people here at Pepper ran into this bug over the past week. In one
case, the access point was an original Apple Airport and the other was a
more recent 'WiFlyer' access point.
The patch when applied to 0.9.1 allows connection to both problem access
points.
I understand the reluctance to add device-specific work-arounds to the
driver, but asking an end-user to decide whether or not to enable such
work-arounds also doesn't seem to the right solution either.
If I get a chance, I'll take a look at the HostAP driver and see how it
handles bad IEs and report back.
--
Ticket URL: <http://madwifi.org/ticket/698>
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
