[ath9k-devel] ath9k: Virtual interface as AP

[jean-pierre cartal <jean-pierre.cartal@plugnsurf.fr>]

  Le 27/10/2010 18:32, "Lorna Gonz?lez" a ?crit :
> Hallo Jouni,
>
>
>>> Configuration file: hostapd.conf
>>> ioctl[SIOCGIFFLAGS]: No such device
>>> Could not read interface flags (wlan1)
>>> nl80211 driver initialization failed.
>> That sounds like you did not have wlan1 when starting hostapd..
>>
>>> interface=wlan1
>>> bss=wlan1
>> This is not a valid configuration. interface defines the main AP
>> interface and bss is a virtual, secondary interface that will be
>> created. As such, it must have a different interface name. I was
>> assuming that you are trying to use multiple AP interfaces, but that may
>> not be the case.
>>
>>> If I don?t add a new interface using iw, I wonder how the hostapd
>> creates it. And, in order to function as an AP I also need to configurate the
>> following a priori :
>>
>> hostapd does not create the main interface; it only configures the
>> secondary ones (bss=). What you seem to be trying to do (station + AP)
>> is not really supported that well currently. In theory, you would need
>> to create a new vif manually (e.g., with iw) and then run hostapd on one
>> of the interfaces. However, I would not give any guarantees on that
>> working correctly in all (or well, even most) cases.
>>
>> - Jouni
>>
> Your last comment explains exactly what I am trying to do:  STA + AP interfaces on the same radio. That?s why I was setting first a second interface in master mode using iw, which works ok. But after initiated hostapd, other stations are not able to sense this virtual AP. I will try again, otherwise I will keep testing using wiphys.
>
> thanks again!!
>
> Lorna
>
>
Hi Lorna,

Try starting hostapd before the client side i.e. wpa_supplicant.

Regards.