AP client mode
Fri Apr 11 21:06:15 PDT 2003
On Fri, Apr 11, 2003 at 10:37:47AM -0300, JuanJo Ciarlante wrote:
> hostapd.conf has correct assoc_ap_addr=<uplink_AP_MAC>
> wds_type: WDS type bitfield
> 2 = use AP client mode in 'Managed mode'
> ... SEEMS that wlan card should in "managed" mode.
Yes, indeed. These are two completely separate features. assoc_ap_addr
with hostapd is a very experimental code for associating to another AP
while operating as a station. wds_type 2 is a "AP client mode" in which
the Host AP driver operates in Managed mode, associates to another AP,
and is using WDS frames to allow bridging. However, "AP client" is _not_
operating as an AP at the same time. This mode does not use hostapd.
> Starting in managed mode
> + iwpriv wlan0 wds_type 2 associates even before launching hostapd;
> launching hostapd has no effect (after all I'm _not_ in master mode).
Yes, that is the expected behavior of wds_type 2.
> Doing the other way, master mode + wds_type + hostapd correctly setups my
> "local" AP (local STA gets associated Ok) _but_ I lose my association with
> "uplink" AP, hostapd -dd shows some errors regarding auth ACKs (which
> suggests that hostapd is trying to auth with uplink AP, which is in open
Unfortunately, assoc_ap_addr seems to work with only limited set of
Prism2 firmware versions, namely 0.7.6 and 0.8.0.
Jouni Malinen PGP id EFC895FA
More information about the Hostap