#698: madwifi-ng not associating with some access-points
-----------------------------------------------+----------------------------
Reporter: wollenberg _at_ web _dot_ de | Owner: mrenzmann
Type: defect | Status: closed
Priority: major | Milestone: version 0.9.3
Component: madwifi: driver | Version: trunk
Resolution: fixed | Keywords: roamabout
associate
Patch_attached: 1 |
-----------------------------------------------+----------------------------
Comment (by ):
Hi I am trying to associate atheros based clients with prism2 based
firware AP (linux-wlan-ng-0.2.5 driver). But everytime this is what i see
in iwconfig output
ath0 IEEE 802.11g ESSID:"xthru2"
Mode:Managed Frequency:2.417 GHz Access Point:
00:00:00:00:00:00
Bit Rate:1 Mb/s Tx-Power:16 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=63/94 Signal level=-32 dBm Noise level=-95 dBm
Rx invalid nwid:3343 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
The client is able to see the AP in its scan list, but is unable to
associate...The problem exists only with firware AP, works fine for all
other APs.
Any clues?
Thanks in Advance..
--
Ticket URL: <http://madwifi.org/ticket/698>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
