Guest User!

You are not Sophos Staff.

[8.165][BUG][OPEN] Wireless shows as inactive

Hi All

After the Update the AP10 shows as inactive. However, it up and clients are connected. Pleasee see log and image

2011:05:31-17:20:18 ap-10 hostapd: wlan0: STA 00:1f:c6:e2:c5:1d WPA: received EAPOL-Key frame (4/4 Pairwise)

2011:05:31-17:20:18 ap-10 awelogger[1561]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="****** " ssid_id="WLAN0" bssid="00:1a:8c:06:13:50" sta="00:1f:c6:e2:c5:1d"
2011:05:31-17:20:18 ap-10 hostapd: wlan0: STA 00:1f:c6:e2:c5:1d IEEE 802.1X: authorizing port
2011:05:31-17:20:18 ap-10 hostapd: wlan0: STA 00:1f:c6:e2:c5:1d RADIUS: starting accounting session 4DE40254-00000015
2011:05:31-17:20:18 ap-10 hostapd: wlan0: STA 00:1f:c6:e2:c5:1d WPA: pairwise key handshake completed (RSN)
2011:05:31-17:27:17 ap-10 hostapd: wlan0: WPA rekeying GTK
2011:05:31-17:27:17 ap-10 hostapd: wlan0: STA 00:1f:c6:e2:c5:1d WPA: sending 1/2 msg of Group Key Handshake
2011:05:31-17:27:17 ap-10 hostapd: wlan0: STA 00:1f:c6:e2:c5:1d WPA: received EAPOL-Key frame (2/2 Group)
2011:05:31-17:27:17 ap-10 hostapd: wlan0: STA 00:1f:c6:e2:c5:1d WPA: group key handshake completed (RSN)
2011:05:31-17:27:17 ap-10 hostapd: wlan1: WPA rekeying GTK 



Thanks
Parents Reply
  • Could someone experiencing this issue run awed in debug mode and provide me with the wireless.log afterwards?


    /var/mdw/scripts/awed stop
    awed.plx --debug


    This should add some useful information to the wireless.log a and hopefully provides us a hint why this strange issue appears.

    To get awed into normal state again run this:

    /var/mdw/scripts/awed restart


    Thanks,
    Helmut
Children
No Data