Daniel Schmitt wrote:
> hostapd doesn't continue to work after controller is restarted.
> I also have the problem that the wlan0-interface shall not be upped with
> "ifconfig wlan0 0.0.0.0 up" before starting hostapd, otherwise no beacons
> will be send. The interface must be down before starting hostapd.
> If I terminate a not daemonized hostapd with CTRL+C and restart if without
> rmmod+modprobe b43legacy, no beacons are sent, too. And I cannot connect
> the AP.
> This happens with the bleeding-edge wireless drivers 2009-11-13.
I noticed the same on MN700 hardware running OpenWrt bleeding edge. The init scripts enable and
disable wlan0 once before starting hostapd. Here, beacons are still being sent, but hostapd is
unable to transmit any packet. When reloading b43legacy and starting hostapd manually it works, but
only once.
The attached patch resolves the problem for me.
Thanks,
Jochen
On 01/15/2010 06:12 AM, Jochen Friedrich wrote:
> Daniel Schmitt wrote:
>
>> hostapd doesn't continue to work after controller is restarted.
>> I also have the problem that the wlan0-interface shall not be upped with
>> "ifconfig wlan0 0.0.0.0 up" before starting hostapd, otherwise no beacons
>> will be send. The interface must be down before starting hostapd.
>> If I terminate a not daemonized hostapd with CTRL+C and restart if
>> without
>> rmmod+modprobe b43legacy, no beacons are sent, too. And I cannot connect
>> the AP.
>> This happens with the bleeding-edge wireless drivers 2009-11-13.
>
> I noticed the same on MN700 hardware running OpenWrt bleeding edge. The
> init scripts enable and disable wlan0 once before starting hostapd.
> Here, beacons are still being sent, but hostapd is unable to transmit
> any packet. When reloading b43legacy and starting hostapd manually it
> works, but only once.
>
> The attached patch resolves the problem for me.
Daniel: Does this patch fix your problem as well?
Has this problem been reported in the kernel bugzilla? If so, what is the number?
How far back does this problem go? From the date of your compat-wireless
package, it seems that 2.6.32 would be affected. How about 2.6.31?
I have tested the patch on my system where it does no harm. I do not run that
system as an AP and had not seen the problem.
As soon as I have the answers to these questions, I will push the patch to
wireless testing.
Thanks for resolving this issue.
Larry