Thread Info
  • State Not Answered
  • Replies 6 replies
  • Subscribers 3 subscribers
  • Views 17452 views
  • Users 0 members are here
Options
Suggested

[9.470-14] [Bug] - Wireless / All Clients are unable to work

dirkkotte 
Hi there,
after upgrading my UTM (Home license/software appliance) to 9.470-14 three times (nearly one per week) all wireless clients are unable to work.
Restarting wireless clients don't work. They shows as connected/connecting.
After restarting AP (AP15) all clients are able to work again. 
Can't see anything within wireless log.  

wireless-log:
2017:04:26-11:24:44 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: authenticated
2017:04:26-11:24:44 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: associated (aid 1)
2017:04:26-11:24:44 A4002346BE2EXXX awelogger[1740]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:24:44 A4002346BE2EXXX awelogger[1740]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:24:44 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 WPA: pairwise key handshake completed (RSN)
2017:04:26-11:24:44 A4002346BE2EXXX awelogger[1740]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:24:46 A4002346BE2EXXX awelogger[1740]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:24:50 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: authenticated
2017:04:26-11:24:50 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: associated (aid 1)
2017:04:26-11:24:50 A4002346BE2EXXX awelogger[1740]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:24:50 A4002346BE2EXXX awelogger[1740]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:24:51 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 WPA: pairwise key handshake completed (RSN)
2017:04:26-11:24:51 A4002346BE2EXXX awelogger[1740]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:24:52 A4002346BE2EXXX awelogger[1740]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:24:56 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: authenticated
2017:04:26-11:24:56 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: associated (aid 1)
2017:04:26-11:24:56 A4002346BE2EXXX awelogger[1740]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:24:56 A4002346BE2EXXX awelogger[1740]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:24:56 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 WPA: pairwise key handshake completed (RSN)
2017:04:26-11:24:56 A4002346BE2EXXX awelogger[1740]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:24:57 A4002346BE2EXXX awelogger[1740]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:24:58 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: authenticated
2017:04:26-11:24:58 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: associated (aid 1)
2017:04:26-11:24:58 A4002346BE2EXXX awelogger[1740]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:24:58 A4002346BE2EXXX awelogger[1740]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:24:58 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 WPA: pairwise key handshake completed (RSN)
2017:04:26-11:24:58 A4002346BE2EXXX awelogger[1740]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:00 A4002346BE2EXXX awelogger[1740]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:01 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: authenticated
2017:04:26-11:25:01 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: associated (aid 1)
2017:04:26-11:25:01 A4002346BE2EXXX awelogger[1740]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:01 A4002346BE2EXXX awelogger[1740]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:01 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 WPA: pairwise key handshake completed (RSN)
2017:04:26-11:25:01 A4002346BE2EXXX awelogger[1740]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:04 A4002346BE2EXXX awelogger[1740]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:08 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: authenticated
2017:04:26-11:25:08 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: associated (aid 1)
2017:04:26-11:25:08 A4002346BE2EXXX awelogger[1740]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:08 A4002346BE2EXXX awelogger[1740]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:09 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 WPA: pairwise key handshake completed (RSN)
2017:04:26-11:25:09 A4002346BE2EXXX awelogger[1740]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:11 A4002346BE2EXXX awelogger[1740]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:12 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: authenticated
2017:04:26-11:25:12 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: associated (aid 1)
2017:04:26-11:25:12 A4002346BE2EXXX awelogger[1740]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:12 A4002346BE2EXXX awelogger[1740]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:12 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 WPA: pairwise key handshake completed (RSN)
2017:04:26-11:25:12 A4002346BE2EXXX awelogger[1740]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:13 A4002346BE2EXXX awelogger[1740]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:18 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: authenticated
2017:04:26-11:25:18 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: associated (aid 1)
2017:04:26-11:25:18 A4002346BE2EXXX awelogger[1740]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:18 A4002346BE2EXXX awelogger[1740]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:18 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 WPA: pairwise key handshake completed (RSN)
2017:04:26-11:25:18 A4002346BE2EXXX awelogger[1740]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:19 A4002346BE2EXXX awelogger[1740]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:24 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: authenticated
2017:04:26-11:25:24 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: associated (aid 1)
2017:04:26-11:25:24 A4002346BE2EXXX awelogger[1740]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:24 A4002346BE2EXXX awelogger[1740]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:24 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 WPA: pairwise key handshake completed (RSN)
2017:04:26-11:25:24 A4002346BE2EXXX awelogger[1740]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:26 A4002346BE2EXXX awelogger[1740]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:26 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: authenticated
2017:04:26-11:25:26 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: associated (aid 1)
2017:04:26-11:25:26 A4002346BE2EXXX awelogger[1740]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:26 A4002346BE2EXXX awelogger[1740]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:26 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 WPA: pairwise key handshake completed (RSN)
2017:04:26-11:25:26 A4002346BE2EXXX awelogger[1740]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:28 A4002346BE2EXXX awelogger[1740]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:29 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: authenticated
2017:04:26-11:25:29 A4002346BE2EXXX awelogger[1740]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:29 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: associated (aid 1)
2017:04:26-11:25:29 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 WPA: pairwise key handshake completed (RSN)
2017:04:26-11:25:29 A4002346BE2EXXX awelogger[1740]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:29 A4002346BE2EXXX awelogger[1740]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:31 A4002346BE2EXXX awelogger[1740]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:34 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: authenticated
2017:04:26-11:25:34 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: associated (aid 1)
2017:04:26-11:25:34 A4002346BE2EXXX awelogger[1740]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:34 A4002346BE2EXXX awelogger[1740]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:35 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 WPA: pairwise key handshake completed (RSN)
2017:04:26-11:25:35 A4002346BE2EXXX awelogger[1740]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:35 A4002346BE2EXXX awelogger[1740]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:36 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: authenticated
2017:04:26-11:25:36 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: associated (aid 1)
2017:04:26-11:25:36 A4002346BE2EXXX awelogger[1740]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:36 A4002346BE2EXXX awelogger[1740]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:36 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 WPA: pairwise key handshake completed (RSN)
2017:04:26-11:25:36 A4002346BE2EXXX awelogger[1740]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:38 A4002346BE2EXXX awelogger[1740]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:39 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: authenticated
2017:04:26-11:25:39 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: associated (aid 1)
2017:04:26-11:25:39 A4002346BE2EXXX awelogger[1740]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:39 A4002346BE2EXXX awelogger[1740]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
2017:04:26-11:25:40 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 WPA: pairwise key handshake completed (RSN)
2017:04:26-11:25:40 A4002346BE2EXXX awelogger[1740]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:42 A4002346BE2EXXX awelogger[1740]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35"
2017:04:26-11:25:42 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: authenticated
2017:04:26-11:25:42 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 IEEE 802.11: associated (aid 1)
2017:04:26-11:25:42 A4002346BE2EXXX hostapd: wlan0: STA 44:d4:e0:d9:7e:35 WPA: pairwise key handshake completed (RSN)
2017:04:26-11:25:42 A4002346BE2EXXX awelogger[1740]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="SophosGuest" ssid_id="WLAN0.0" bssid="00:1a:8c:7e:19:09" sta="44:d4:e0:d9:7e:35" status_code="0"
Parents
  • 0

    Hi Dirk,

    Can you please tell us more about what you observed?

    • You mentioned you updated your UTM three times? Or did your wireless stop working three times? Which version of UTM are you coming from?
    • Did you do anything that could have caused Wireless to stop working (e.g. changing configuration)?
    • Did a restart of the AP fix the problem permanently, or is it re-appearing?
    • How many clients do you have, and what type of clients do you have?
    • How many Access Points do you have, and what types? 

     

    Thanks for reporting the issue!

    Best regards,

    Andreas

  • 0 in reply to AndreasGrosse

    Hi Andreas,

    thanks for your answer...

    You mentioned you updated your UTM three times? Or did your wireless stop working three times?
    - wireless stop working three times

    Which version of UTM are you coming from?
    - i go from 9.411-3 to 9.470-14

    Did you do anything that could have caused Wireless to stop working (e.g. changing configuration)?
    - no

    Did a restart of the AP fix the problem permanently, or is it re-appearing?
    - restarting the AP fix the problem for some time only

    How many clients do you have, and what type of clients do you have?
    - Clinets:  4*Windows(XP, Win7,Win10), 3*Android phone, 2IPad -- no one is able to work if error occurs

    How many Access Points do you have, and what types?
    - only one AP AP15


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

Reply
  • 0 in reply to AndreasGrosse

    Hi Andreas,

    thanks for your answer...

    You mentioned you updated your UTM three times? Or did your wireless stop working three times?
    - wireless stop working three times

    Which version of UTM are you coming from?
    - i go from 9.411-3 to 9.470-14

    Did you do anything that could have caused Wireless to stop working (e.g. changing configuration)?
    - no

    Did a restart of the AP fix the problem permanently, or is it re-appearing?
    - restarting the AP fix the problem for some time only

    How many clients do you have, and what type of clients do you have?
    - Clinets:  4*Windows(XP, Win7,Win10), 3*Android phone, 2IPad -- no one is able to work if error occurs

    How many Access Points do you have, and what types?
    - only one AP AP15


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

Children
  • 0 in reply to dirkkotte

    Hi Dirk,

    with your observation that the log does not look fishy you are partly right. Actually what we can see in this log line: "...pairwise key handshake completed..." is that the wireless part of the connection worked out. But 2 seconds later we see that the client disconnects. This is most often happening when the client is not getting an IP over DHCP, can you check the dhcpd.log of this time frame if we see the request coming in, and a reply being prepared?

    From the name "SophosGuest" I assume it is a "seperate zone" ssid, right?

    Regards,
    Emanuel

  • 0 in reply to etaube

    Hi Emanuel,

    yes, separate zone.

    here are the DHCP-LOG:

    2017:04:26-11:25:25 astaro dhcpd: DHCPREQUEST for 172.16.28.108 from 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:25 astaro dhcpd: DHCPACK on 172.16.28.108 to 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:27 astaro dhcpd: Dynamic and static leases present for 172.16.28.108.
    2017:04:26-11:25:27 astaro dhcpd: Remove host declaration REF_NetHosHandyxxxxs_2 or remove 172.16.28.108
    2017:04:26-11:25:27 astaro dhcpd: from the dynamic address pool for 172.16.28.0/24
    2017:04:26-11:25:27 astaro dhcpd: DHCPREQUEST for 172.16.28.108 from 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:27 astaro dhcpd: DHCPACK on 172.16.28.108 to 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:29 astaro dhcpd: Dynamic and static leases present for 172.16.28.108.
    2017:04:26-11:25:29 astaro dhcpd: Remove host declaration REF_NetHosHandyxxxxs_2 or remove 172.16.28.108
    2017:04:26-11:25:29 astaro dhcpd: from the dynamic address pool for 172.16.28.0/24
    2017:04:26-11:25:29 astaro dhcpd: DHCPREQUEST for 172.16.28.108 from 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:29 astaro dhcpd: DHCPACK on 172.16.28.108 to 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:35 astaro dhcpd: Dynamic and static leases present for 172.16.28.108.
    2017:04:26-11:25:35 astaro dhcpd: Remove host declaration REF_NetHosHandyxxxxs_2 or remove 172.16.28.108
    2017:04:26-11:25:35 astaro dhcpd: from the dynamic address pool for 172.16.28.0/24
    2017:04:26-11:25:35 astaro dhcpd: DHCPREQUEST for 172.16.28.108 from 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:35 astaro dhcpd: DHCPACK on 172.16.28.108 to 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:37 astaro dhcpd: Dynamic and static leases present for 172.16.28.108.
    2017:04:26-11:25:37 astaro dhcpd: Remove host declaration REF_NetHosHandyxxxxs_2 or remove 172.16.28.108
    2017:04:26-11:25:37 astaro dhcpd: from the dynamic address pool for 172.16.28.0/24
    2017:04:26-11:25:37 astaro dhcpd: DHCPREQUEST for 172.16.28.108 from 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:37 astaro dhcpd: DHCPACK on 172.16.28.108 to 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:40 astaro dhcpd: Dynamic and static leases present for 172.16.28.108.
    2017:04:26-11:25:40 astaro dhcpd: Remove host declaration REF_NetHosHandyxxxxs_2 or remove 172.16.28.108
    2017:04:26-11:25:40 astaro dhcpd: from the dynamic address pool for 172.16.28.0/24
    2017:04:26-11:25:40 astaro dhcpd: DHCPREQUEST for 172.16.28.108 from 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:40 astaro dhcpd: DHCPACK on 172.16.28.108 to 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:43 astaro dhcpd: Dynamic and static leases present for 172.16.28.108.
    2017:04:26-11:25:43 astaro dhcpd: Remove host declaration REF_NetHosHandyxxxxs_2 or remove 172.16.28.108
    2017:04:26-11:25:43 astaro dhcpd: from the dynamic address pool for 172.16.28.0/24
    2017:04:26-11:25:43 astaro dhcpd: DHCPREQUEST for 172.16.28.108 from 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:43 astaro dhcpd: DHCPACK on 172.16.28.108 to 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:44 astaro dhcpd: Dynamic and static leases present for 172.16.28.108.
    2017:04:26-11:25:44 astaro dhcpd: Remove host declaration REF_NetHosHandyxxxxs_2 or remove 172.16.28.108
    2017:04:26-11:25:44 astaro dhcpd: from the dynamic address pool for 172.16.28.0/24
    2017:04:26-11:25:44 astaro dhcpd: DHCPREQUEST for 172.16.28.108 from 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:44 astaro dhcpd: DHCPACK on 172.16.28.108 to 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:47 astaro dhcpd: Dynamic and static leases present for 172.16.28.108.
    2017:04:26-11:25:47 astaro dhcpd: Remove host declaration REF_NetHosHandyxxxxs_2 or remove 172.16.28.108
    2017:04:26-11:25:47 astaro dhcpd: from the dynamic address pool for 172.16.28.0/24
    2017:04:26-11:25:47 astaro dhcpd: DHCPREQUEST for 172.16.28.108 from 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:47 astaro dhcpd: DHCPACK on 172.16.28.108 to 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:49 astaro dhcpd: Dynamic and static leases present for 172.16.28.108.
    2017:04:26-11:25:49 astaro dhcpd: Remove host declaration REF_NetHosHandyxxxxs_2 or remove 172.16.28.108
    2017:04:26-11:25:49 astaro dhcpd: from the dynamic address pool for 172.16.28.0/24
    2017:04:26-11:25:49 astaro dhcpd: DHCPREQUEST for 172.16.28.108 from 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:25:49 astaro dhcpd: DHCPACK on 172.16.28.108 to 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-11:30:44 astaro dhcpd: Dynamic and static leases present for 172.16.28.118.
    2017:04:26-11:30:44 astaro dhcpd: Remove host declaration REF_NetHosNbtil or remove 172.16.28.118
    2017:04:26-11:30:44 astaro dhcpd: from the dynamic address pool for 172.16.28.0/24
    2017:04:26-11:30:44 astaro dhcpd: DHCPREQUEST for 172.16.28.118 from 00:23:14:65:4a:c8 via wlan0
    2017:04:26-11:30:44 astaro dhcpd: DHCPACK on 172.16.28.118 to 00:23:14:65:4a:c8 via wlan0
    2017:04:26-12:07:00 astaro dhcpd: Dynamic and static leases present for 172.16.28.113.
    2017:04:26-12:07:00 astaro dhcpd: Remove host declaration REF_NetHosxxxx06 or remove 172.16.28.113
    2017:04:26-12:07:00 astaro dhcpd: from the dynamic address pool for 172.16.28.0/24
    2017:04:26-12:07:00 astaro dhcpd: DHCPREQUEST for 172.16.28.113 from a4:34:d9:67:6b:5f via wlan0
    2017:04:26-12:07:00 astaro dhcpd: DHCPACK on 172.16.28.113 to a4:34:d9:67:6b:5f via wlan0
    2017:04:26-12:07:40 astaro dhcpd: Dynamic and static leases present for 172.16.28.108.
    2017:04:26-12:07:40 astaro dhcpd: Remove host declaration REF_NetHosHandyxxxxs_2 or remove 172.16.28.108
    2017:04:26-12:07:40 astaro dhcpd: from the dynamic address pool for 172.16.28.0/24
    2017:04:26-12:07:40 astaro dhcpd: DHCPREQUEST for 172.16.28.108 from 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-12:07:40 astaro dhcpd: DHCPACK on 172.16.28.108 to 44:d4:e0:d9:7e:35 via wlan0
    2017:04:26-12:58:28 astaro dhcpd: Dynamic and static leases present for 172.16.28.118.
    2017:04:26-12:58:28 astaro dhcpd: Remove host declaration REF_NetHosNbtil or remove 172.16.28.118
    2017:04:26-12:58:28 astaro dhcpd: from the dynamic address pool for 172.16.28.0/24
    2017:04:26-12:58:28 astaro dhcpd: DHCPREQUEST for 172.16.28.118 from 00:23:14:65:4a:c8 via wlan0
    2017:04:26-12:58:28 astaro dhcpd: DHCPACK on 172.16.28.118 to 00:23:14:65:4a:c8 via wlan0
    2017:04:26-13:20:20 astaro dhcpd: Dynamic and static leases present for 172.16.28.118.
    2017:04:26-13:20:20 astaro dhcpd: Remove host declaration REF_NetHosNbtil or remove 172.16.28.118


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

  • 0 in reply to dirkkotte

    Hi Dirk,

    it would be interesting if the client is able to receive this DHCP ACK. Can you do a scan (tcpdump, wireshark,...) on any client device the next time this issue occurs. If the DHCP Ack is not seen on the client the next step would be to make this tcpdump on the UTM to see on which interface this ACK is going out. Would it be possible to get access to this UTM during the issue, to limit the back and forth cycles?

    Regards,
    Emanuel

  • 0 in reply to etaube

    hi Emanuel,

    i'll capture DHCP traffic next time the problem occurs.

    But i run these UTM at home, so i mostly see the problem in the evening or at weekend.

     

     


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

Unfiltered HTML