WDS associates with AP instead of specified MAC

David Gurevich dgurevich at packethop.com
Tue Jun 17 17:03:07 EDT 2003


I am running in AP client (Managed mode).

I do:

prism2_param wlan0 wds_type 2
iwpriv wlan0 wds_add 00:02:6F:03:FD:85

then

iwconfig

. . .


wlan0     IEEE 802.11b  ESSID:"test"  
          Mode:Managed  Frequency:2.462GHz  Access Point: 00:03:2F:06:8A:55  
          Bit Rate:11Mb/s   Tx-Power:-12 dBm   Sensitivity=1/3  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality:92/92  Signal level:-40 dBm  Noise level:-100 dBm
          Rx invalid nwid:0  Rx invalid crypt:2  Rx invalid frag:0
          Tx excessive retries:5  Invalid misc:486765   Missed beacon:0

wlan0wds  IEEE 802.11b  ESSID:"test"  
          Mode:Managed  Frequency:2.462GHz  Access Point: 00:03:2F:06:8A:55  
          Bit Rate:11Mb/s   Tx-Power:-12 dBm   Sensitivity=1/3  
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Power Management:off

The question is why does the wlan0wds0 link associate with the AP and not the MAC I specified?



More information about the HostAP mailing list