HostAP Digest, Vol 2, Issue 21

[David Gurevich]

Thanks,
Does this mean that it is not possible to configure the wlan0wds0 interface differently from the main wlan0 interface?
I would like to set it with its own ESSID. I also do not want to send 4 address frames over it. What I'm trying to do is
run HostAP in Managed mode as a station connecting to some standard AP while also talking to other HostAP nodes via the
WDS interfaces. I do not want to bridge (therefore no 4 address frames). I'll just route across the interfaces. I would
think that this would be a neat feature that enables one to extend the range of a standard AP infrastructure.

> 
> > How come iwconfig wlan0wds essid "test" produces an error:
> > 
> > Error for wireless request "Set ESSID" (8B1A) :
> >     SET failed on device wlan0wds ; No such device.
> > 
> > Why can't I configure a WDS interface with iwconfig?
> 
> Because you are using incorrect interface name. The full name is
> wlan0wds0 for the first WDS link. iwconfig is apparenlty 
> truncating it.
> In addition, Host AP driver does not store separate data for WDS
> interfaces. That iwconfig command would still be configuring the "main
> interface".
> 
> -- 
> Jouni Malinen                                            PGP 
> id EFC895FA
> 
>