This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

AP15 Locks up when Samsung S8 connects

VM UTM v9.412-2
2@ AP15

When my new Samsung S8 phone connects to AP, the AP locks up solid and requires extended an power cycle to recover.

Nothing obvious in the Wireless active logs:

2017:05:01-14:15:19 A4002458AE3B628 hostapd: wlan0: STA a0:cc:2b:91:0a:f0 IEEE 802.11: authenticated
2017:05:01-14:15:19 A4002458AE3B628 hostapd: wlan0: STA a0:cc:2b:91:0a:f0 IEEE 802.11: associated (aid 1)
2017:05:01-14:15:19 A4002458AE3B628 awelogger[1480]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="Rest" ssid_id="WLAN0.0" bssid="00:1a:8c:7f:3e:f2" sta="a0:cc:2b:91:0a:f0" status_code="0"
2017:05:01-14:15:19 A4002458AE3B628 awelogger[1480]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="Rest" ssid_id="WLAN0.0" bssid="00:1a:8c:7f:3e:f2" sta="a0:cc:2b:91:0a:f0" status_code="0"
2017:05:01-14:15:19 A4002458AE3B628 hostapd: wlan0: STA a0:cc:2b:91:0a:f0 WPA: pairwise key handshake completed (RSN)
2017:05:01-14:15:19 A4002458AE3B628 awelogger[1480]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="Rest" ssid_id="WLAN0.0" bssid="00:1a:8c:7f:3e:f2" sta="a0:cc:2b:91:0a:f0"
2017:05:01-14:16:12 utm1 awed[8797]: [A4002458AE3B628] ll_read: dead socket: Resource temporarily unavailable
2017:05:01-14:16:12 utm1 awed[8797]: [A4002458AE3B628] disconnected. Close socket and kill process.

..is there a way for me to enable deeper AP logging?



This thread was automatically locked due to age.
  • Hi JimmyJoeBob,

    do you already know about "awetool"? Just run awetool on the UTM, connect to the AP, and do a "logread -f" to follow what's happening on the console when the S8 connects. Please post here if you see something interesting, and we can decide about further steps.

    Thank you for reporting this issue!

    Best regards,

    Andreas