#428: Only old madwifi-driver package will connect to AirPort router
---------------------------------+------------------------------------------
Reporter: anonymous | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: other | Version: trunk
Resolution: | Keywords:
Patch_attached: 0 |
---------------------------------+------------------------------------------
Comment (by [EMAIL PROTECTED]):
I think the problem is the r1409/r1410 frame element length checks.
Maybe a lot (?) of the commercial AP routers send out bad element frames ?
Can someone provide a capture of the probe response/request associate
response/request of
their routers ?
To do this: set your madwifi-ng to use a monitor vap (i.e wlanconfig ath0
create wlandev wifi0 wlanmode monitor)
Turn it on,
and run ethereal to capture off ath0.
Then use another laptop/computer to try to associate to the AP.
Turn off ethereal, and save the capture for us to look at (attach to the
ticket).
This might help me take a closer look at the problem.
--
Ticket URL: <http://madwifi.org/ticket/428>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
