>>> Removing wlan0 from /etc/conf.d/hostapd is not what you would want, as you
>>> wish hostapd to use wlan0.
>>> The init scripts are not able to set up master mode correctly and bring up
>>> an error or set up wlan0 interface in a false mode so hostapd can not set it
>>> up any more.
>>> So i set up my init to completely ignore wlan0 till hostapd handles it.
>>> Somehow hot- or coldplug initialized the net.wlan0 script anyway, so i
>>> removed it completely.
>>>
>>
>> Can you be more specific about what you did? Did you just remove the
>> wlan0 initscript, or did you also make an initscript modification? If
>> so, could you share your modification?
>>
>>
> Sure.
> I removed the net.wlan0 script, or better, i never created it.
> I modified the init.d/hostapd script, not to depend on all interfaces
> but on only those, which i need:
>
> /etc/init.d/hostapd
> depend() {
> need net.br0
> need net.eth0
> use logger
> }
>
> As i said earlier, this is kind of redundant as it is possible, that
> without the script, hostapd would not start that interface. But i can
> not tell, i never tested it.
>
>>> Basicly it is moving over the handling of wlan0 from rc-scripts to hostapd.
>>>
>>
>> That's why I thought removing wlan0 from /etc/conf.d/hostapd would be
>> appropriate.
>>
>> - Grant
>>
> Damnit, you are right, i should have read the text.
>
> After looking over this setting with a little distance for this thread,
> 10 days after setting this up and with yout hint, i feel this could be
> smoothed up significantly ;-). So thanks for that. I think i will put
> some energy in it tomorrow.
>
> Norman
Still no luck for me with master mode, even after editing
wireless-testing/drivers/net/wireless/ath5k/base.c. 2.6.28 is
supposed to work but I'm wondering if it's not in 2.6.28-hardened or
something. I still get "Failed to set interface ath0 to master mode"
from hostapd.
- Grant
