BUG: weird behaviour after killing hostapd in latest CVS.

Jouni Malinen jkmaline at cc.hut.fi
Mon Aug 4 22:27:49 EDT 2003

On Mon, Aug 04, 2003 at 02:21:08PM -0300, JuanJo Ciarlante wrote:

> While testing hostapd I could "reproduceable" get this behaviour: after
> killing hostapd (run hostapd from cmdline and do ^C, ie kill -2) 
> my Linux console gets stuck: no response to keys,  no Alt-Fn switching
> _but_ I can do the magic sysrq S-U-B with expected results (no fsck in next
> boot).
> This does not happen with 0.0.4.

I did change wlan0ap and wlan0sta interface unregistering, so that might
have caused some issues. I tested this only with Linux 2.6.0-test2..
Which kernel version are you using?

> Attached hostapd.conf, the only "rare" thing is that I'm using
> "assoc_ap_addr" to a working AP; and I _do_ get expected behaviour:
> association  Ok and "local" AP via hostapd.

Which station firmware version are you using?

Did you have wlan0sta interface UP when killing hostapd? If yes, what
happens if you first set it down and only after that kill hostapd?

Jouni Malinen                                            PGP id EFC895FA

More information about the HostAP mailing list