Please, see the wiki at <wireless.kernel.org>, especially [1] and [2]. - Sedat - [1] http://wireless.kernel.org/en/users/Support [2] http://wireless.kernel.org/en/developers/MailingLists On Thu, Feb 10, 2011 at 3:55 PM, Chaoxing Lin <CLin@xxxxxxxx> wrote: > Sorry if this message is duplicate. > > I am confused which email address to send. > linux-wireless@xxxxxxxxxxxxxxx or linux-wireless-owner@xxxxxxxxxxxxxxx > > > > -----Original Message----- > From: Chaoxing Lin > Sent: Wednesday, February 09, 2011 5:23 PM > To: 'linux-wireless-owner@xxxxxxxxxxxxxxx' > Subject: hostapd problem on reconfig (SIGHUP) > > > Hello Experts, > > I see a problem while testing the latest hostapd/kernel/wpa_supplicant. I believe the problem in on hostapd side. > It is easy to recreate the problem. So it can be an easy fix for hostapd maintainer. > > Thanks > > > Problem: hostapd not working after SIGHUP signal > > Symptoms > > 1. If there's a client associated, a SIGHUP signal to hostapd can cause problem that no clients can associate (almost 100% reproducible) > > 2. "segmentation fault" happens a few times(not all the time) Âto hostapd by repeating SIGHUP and SIGUSR1 to hostapd. > > 3. Another minor thing. Actually a suggestion, hostapd does not need to re-config if configuration file is not changed. This is preferred because when hostapd controls multiple radios (e.g hostapd radio1.conf radio2.conf), itâs desirable that service on other radio is not disrupted when one of the conf is changed. > > > Some facts: > ÂÂÂ a. The already associated client still thinks itself associated. This is verified by "iw wlan0 link" on client side. > It timed out later on and can no longer associate. > > ÂÂÂ b. driver (ath9k in kernel 2.6.38-rc4, operate over ar9380) says it has already deauthenticated the clients per > ÂÂÂÂÂÂÂÂÂÂ hostapd flush instruction. This is verified by "iw wlan0 station dump" on ap side. > ÂÂÂ ÂÂÂ I sniffed the air. Deauthentication packets (as broadcast) were sent out by driver. The associated client does not > deauthenticate and re-associate (bug in wpa_supplicant?). > > ÂÂÂ c. hostapd still thinks the associated client is associated, which is wrong. This is verified by "killall -SIGUSR1 hostapd" > ÂÂÂ ÂÂ followed by "cat /tmp/hostapd.dump" > > ÂÂÂ d. Tried to use new client to associate. No success. > ÂÂÂÂÂÂ Both old and clients stuck > > Workaround: > > ÂÂÂÂÂÂÂÂ Do NOT use SIGHUP. User has to kill hostapd and restart hostapd. > > Software version info: > 1. hostapd-0.7.3 and the latest unofficial snapshot release 0.8-snapshot > 2. Tried both kernel 2.6.38-rc3 and 2.6.38-rc4. > 3. ath9k operates over AR9380 chipset > 4. wpa_supplicant-0.7.3 is used for client test. > > -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
