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

AP50 - losing all 2.4GHz connections

Hi, My AP50 on UTM 9 (latest firmware) has been losing the 2.4GHz channels (the 2.4GHz SSIDs completely disappear from all my devices) until I make any change (such as disabling one SSID) at which point they work again.

This has been happening at least once a week... it happened a few minutes ago, the wireless.log entries are below.

 

2017:05:01-18:27:18 192.168.211.211 hostapd: wlan2: STA 00:14:d1:f1:c5:ba WPA: pairwise key handshake completed (RSN)
2017:05:01-18:28:29 192.168.211.211 hostapd: wlan1: STA 10:1c:0c:2a:f0:9f WPA: group key handshake completed (RSN)
2017:05:01-18:28:29 192.168.211.211 hostapd: wlan1: STA 0c:d7:46:ab:84:00 WPA: group key handshake completed (RSN)
2017:05:01-18:28:29 192.168.211.211 hostapd: wlan1: STA 1c:5c:f2:9b:34:79 WPA: group key handshake completed (RSN)
2017:05:01-18:28:30 192.168.211.211 hostapd: wlan2: STA 68:54:fd:6b:96:fa WPA: group key handshake completed (RSN)
2017:05:01-18:28:30 192.168.211.211 hostapd: wlan2: STA 00:14:d1:f1:c5:ba WPA: group key handshake completed (RSN)
2017:05:01-18:28:30 192.168.211.211 hostapd: wlan2: STA 00:d0:2d:26:37:2c WPA: group key handshake completed (RSN)
2017:05:01-18:28:30 192.168.211.211 hostapd: wlan2: STA 34:97:f6:77:27:f4 WPA: group key handshake completed (RSN)
2017:05:01-18:28:30 192.168.211.211 hostapd: wlan2: STA 74:da:38:1e:8b:fb WPA: group key handshake completed (RSN)
2017:05:01-18:28:31 192.168.211.211 hostapd: wlan2: STA f0:27:65:ea:69:40 WPA: group key handshake completed (RSN)
2017:05:01-18:38:29 192.168.211.211 hostapd: wlan1: STA 10:1c:0c:2a:f0:9f WPA: group key handshake completed (RSN)
2017:05:01-18:38:29 192.168.211.211 hostapd: wlan1: STA 0c:d7:46:ab:84:00 WPA: group key handshake completed (RSN)
2017:05:01-18:38:30 192.168.211.211 hostapd: wlan2: STA 00:14:d1:f1:c5:ba WPA: group key handshake completed (RSN)
2017:05:01-18:38:30 192.168.211.211 hostapd: wlan2: STA 68:54:fd:6b:96:fa WPA: group key handshake completed (RSN)
2017:05:01-18:38:30 192.168.211.211 hostapd: wlan1: STA 1c:5c:f2:9b:34:79 WPA: group key handshake completed (RSN)
2017:05:01-18:38:30 192.168.211.211 hostapd: wlan2: STA 00:d0:2d:26:37:2c WPA: group key handshake completed (RSN)
2017:05:01-18:38:30 192.168.211.211 hostapd: wlan2: STA f0:27:65:ea:69:40 WPA: group key handshake completed (RSN)
2017:05:01-18:38:30 192.168.211.211 hostapd: wlan2: STA 74:da:38:1e:8b:fb WPA: group key handshake completed (RSN)
2017:05:01-18:38:30 192.168.211.211 hostapd: wlan2: STA 34:97:f6:77:27:f4 WPA: group key handshake completed (RSN)
2017:05:01-18:41:27 192.168.211.211 aweclient[757]: aweclient.c (2050) No reply get from last message, close socket.
2017:05:01-18:41:42 192.168.211.211 aweclient[757]: aweclient.c (2050) No reply get from last message, close socket.
2017:05:01-18:41:57 192.168.211.211 aweclient[757]: aweclient.c (2050) No reply get from last message, close socket.
2017:05:01-18:42:12 192.168.211.211 aweclient[757]: aweclient.c (2050) No reply get from last message, close socket.
2017:05:01-18:42:30 fw awed[4785]: [MASTER] new connection from 192.168.211.211:38644
2017:05:01-18:42:30 fw awed[4785]: [MASTER] new connection from 192.168.211.211:38645
2017:05:01-18:42:30 fw awed[4785]: [MASTER] new connection from 192.168.211.211:38646
2017:05:01-18:42:30 fw awed[4785]: [MASTER] new connection from 192.168.211.211:38647
2017:05:01-18:42:28 192.168.211.211 aweclient[757]: aweclient.c (2050) No reply get from last message, close socket.
2017:05:01-18:42:41 fw awed[20268]: [A40018A30FC2D14] ll_read: dead socket: Resource temporarily unavailable
2017:05:01-18:42:41 fw awed[20268]: [A40018A30FC2D14] disconnected. Close socket and kill process.
2017:05:01-18:42:46 fw awed[12065]: [A40018A30FC2D14] AP50 from 192.168.211.211:38645 identified as A40018A30FC2D14
2017:05:01-18:42:46 fw awed[12066]: [A40018A30FC2D14] AP50 from 192.168.211.211:38646 identified as A40018A30FC2D14
2017:05:01-18:42:46 fw awed[12067]: [A40018A30FC2D14] AP50 from 192.168.211.211:38647 identified as A40018A30FC2D14
2017:05:01-18:42:46 fw awed[12064]: [A40018A30FC2D14] AP50 from 192.168.211.211:38644 identified as A40018A30FC2D14
2017:05:01-18:42:43 192.168.211.211 aweclient[757]: aweclient.c (2050) No reply get from last message, close socket.
2017:05:01-18:42:58 192.168.211.211 aweclient[757]: aweclient.c (2050) No reply get from last message, close socket.
2017:05:01-18:43:05 fw awed[12064]: [A40018A30FC2D14] (Re-)loaded identity and/or configuration
2017:05:01-18:43:05 fw awed[12065]: [A40018A30FC2D14] (Re-)loaded identity and/or configuration
2017:05:01-18:43:05 fw awed[12066]: [A40018A30FC2D14] (Re-)loaded identity and/or configuration
2017:05:01-18:43:13 fw awed[12067]: [A40018A30FC2D14] (Re-)loaded identity and/or configuration
2017:05:01-18:43:13 192.168.211.211 aweclient[757]: aweclient.c (2050) No reply get from last message, close socket.
2017:05:01-18:43:19 fw awed[4785]: [MASTER] new connection from 192.168.211.211:38648
2017:05:01-18:43:21 fw awed[4785]: [MASTER] new connection from 192.168.211.211:38649
2017:05:01-18:43:23 fw awed[4785]: [MASTER] new connection from 192.168.211.211:38650
2017:05:01-18:43:23 fw awed[4785]: [MASTER] new connection from 192.168.211.211:38651
2017:05:01-18:43:26 fw awed[12090]: [A40018A30FC2D14] AP50 from 192.168.211.211:38649 identified as A40018A30FC2D14
2017:05:01-18:43:26 fw awed[12092]: [A40018A30FC2D14] AP50 from 192.168.211.211:38651 identified as A40018A30FC2D14
2017:05:01-18:43:26 fw awed[12091]: [A40018A30FC2D14] AP50 from 192.168.211.211:38650 identified as A40018A30FC2D14
2017:05:01-18:43:26 fw awed[12089]: [A40018A30FC2D14] AP50 from 192.168.211.211:38648 identified as A40018A30FC2D14
2017:05:01-18:43:28 192.168.211.211 aweclient[757]: aweclient.c (2050) No reply get from last message, close socket.
2017:05:01-18:43:33 fw awed[12090]: [A40018A30FC2D14] (Re-)loaded identity and/or configuration
2017:05:01-18:43:33 fw awed[12092]: [A40018A30FC2D14] (Re-)loaded identity and/or configuration
2017:05:01-18:43:34 fw awed[12089]: [A40018A30FC2D14] (Re-)loaded identity and/or configuration
2017:05:01-18:43:34 fw awed[12091]: [A40018A30FC2D14] (Re-)loaded identity and/or configuration
2017:05:01-18:43:36 fw awed[12064]: [A40018A30FC2D14]The connection is closed.
2017:05:01-18:43:36 fw awed[12066]: [A40018A30FC2D14]The connection is closed.
2017:05:01-18:43:36 fw awed[12064]: [A40018A30FC2D14] error while writing to socket, dropping.
2017:05:01-18:43:36 fw awed[12065]: [A40018A30FC2D14]The connection is closed.
2017:05:01-18:43:36 fw awed[12065]: [A40018A30FC2D14] error while writing to socket, dropping.
2017:05:01-18:43:36 fw awed[12066]: [A40018A30FC2D14] error while writing to socket, dropping.
2017:05:01-18:43:36 fw awed[12089]: [A40018A30FC2D14]The connection is closed.
2017:05:01-18:43:36 fw awed[12089]: [A40018A30FC2D14] error while writing to socket, dropping.
2017:05:01-18:43:36 fw awed[12090]: [A40018A30FC2D14]The connection is closed.
2017:05:01-18:43:36 fw awed[12090]: [A40018A30FC2D14] error while writing to socket, dropping.
2017:05:01-18:43:46 fw awed[12091]: [A40018A30FC2D14]The connection is closed.
2017:05:01-18:43:46 fw awed[12091]: [A40018A30FC2D14] error while writing to socket, dropping.
2017:05:01-18:43:44 192.168.211.211 aweclient[757]: aweclient.c (2050) No reply get from last message, close socket.
2017:05:01-18:43:50 fw awed[12092]: [A40018A30FC2D14]The connection is closed.
2017:05:01-18:43:50 fw awed[12092]: [A40018A30FC2D14] error while writing to socket, dropping.
2017:05:01-18:43:52 fw awed[4785]: [MASTER] new connection from 192.168.211.211:38652
2017:05:01-18:43:52 fw awed[4785]: [MASTER] new connection from 192.168.211.211:38653
2017:05:01-18:43:52 fw awed[12125]: [A40018A30FC2D14] AP50 from 192.168.211.211:38652 identified as A40018A30FC2D14
2017:05:01-18:43:52 fw awed[12126]: [A40018A30FC2D14] AP50 from 192.168.211.211:38653 identified as A40018A30FC2D14
2017:05:01-18:43:54 fw awed[12125]: [A40018A30FC2D14] (Re-)loaded identity and/or configuration
2017:05:01-18:44:01 fw awed[12125]: [A40018A30FC2D14]The connection is closed.
2017:05:01-18:44:01 fw awed[12125]: [A40018A30FC2D14] error while writing to socket, dropping.
2017:05:01-18:44:01 fw awed[12126]: [A40018A30FC2D14] (Re-)loaded identity and/or configuration
2017:05:01-18:44:04 fw awed[12126]: [A40018A30FC2D14]The connection is closed.
2017:05:01-18:44:04 fw awed[12126]: [A40018A30FC2D14] error while writing to socket, dropping.
2017:05:01-18:43:59 192.168.211.211 aweclient[757]: aweclient.c (2050) No reply get from last message, close socket.
2017:05:01-18:44:18 fw awed[4785]: [MASTER] new connection from 192.168.211.211:38654
2017:05:01-18:44:18 fw awed[12139]: [A40018A30FC2D14] AP50 from 192.168.211.211:38654 identified as A40018A30FC2D14
2017:05:01-18:44:18 fw awed[12139]: [A40018A30FC2D14] (Re-)loaded identity and/or configuration
2017:05:01-18:44:14 192.168.211.211 aweclient[757]: aweclient.c (2462) Exit from main loop with no error. Get new configuration.
2017:05:01-18:44:16 192.168.211.211 aweclient[757]: Cloudclient not found on ubus.
2017:05:01-18:44:17 192.168.211.211 netifd: Network device 'wlan2' link is down
2017:05:01-18:44:17 192.168.211.211 kernel: [815354.040000] br-lan: port 2(wlan2) entered disabled state
2017:05:01-18:44:17 192.168.211.211 kernel: [815354.050000] device wlan2 left promiscuous mode
2017:05:01-18:44:17 192.168.211.211 kernel: [815354.050000] br-lan: port 2(wlan2) entered disabled state
2017:05:01-18:44:17 192.168.211.211 kernel: [815354.110000] br-lan: port 4(wlan11) entered disabled state
2017:05:01-18:44:17 192.168.211.211 netifd: Network device 'wlan11' link is down
2017:05:01-18:44:17 192.168.211.211 kernel: [815354.120000] device wlan11 left promiscuous mode
2017:05:01-18:44:17 192.168.211.211 kernel: [815354.130000] br-lan: port 4(wlan11) entered disabled state
2017:05:01-18:44:17 192.168.211.211 netifd: Network device 'wlan1' link is down
2017:05:01-18:44:17 192.168.211.211 kernel: [815354.190000] br-vxlan102: port 2(wlan1) entered disabled state
2017:05:01-18:44:17 192.168.211.211 kernel: [815354.190000] device wlan1 left promiscuous mode
2017:05:01-18:44:17 192.168.211.211 kernel: [815354.200000] br-vxlan102: port 2(wlan1) entered disabled state
2017:05:01-18:44:17 192.168.211.211 netifd: lan (872): Performing a DHCP renew
2017:05:01-18:44:17 192.168.211.211 netifd: lan (872): Sending renew...
2017:05:01-18:44:17 192.168.211.211 kernel: [815354.300000] br-vxlan102: port 3(wlan10) entered disabled state
2017:05:01-18:44:17 192.168.211.211 kernel: [815354.300000] device wlan10 left promiscuous mode
2017:05:01-18:44:17 192.168.211.211 kernel: [815354.310000] br-vxlan102: port 3(wlan10) entered disabled state
2017:05:01-18:44:17 192.168.211.211 netifd: Network device 'wlan10' link is down
2017:05:01-18:44:17 192.168.211.211 kernel: [815354.540000] br-lan: port 3(wlan9) entered disabled state
2017:05:01-18:44:17 192.168.211.211 kernel: [815354.540000] device wlan9 left promiscuous mode
2017:05:01-18:44:17 192.168.211.211 kernel: [815354.550000] br-lan: port 3(wlan9) entered disabled state
2017:05:01-18:44:17 192.168.211.211 netifd: Network device 'wlan9' link is down
2017:05:01-18:44:17 192.168.211.211 kernel: [815354.620000] device wlan0 left promiscuous mode
2017:05:01-18:44:17 192.168.211.211 kernel: [815354.620000] br-vxlan100: port 2(wlan0) entered disabled state
2017:05:01-18:44:18 192.168.211.211 kernel: [815354.780000] device wlan8 left promiscuous mode
2017:05:01-18:44:18 192.168.211.211 kernel: [815354.780000] br-vxlan100: port 3(wlan8) entered disabled state
2017:05:01-18:44:18 192.168.211.211 netifd: Network device 'wlan0' link is down
2017:05:01-18:44:18 192.168.211.211 netifd: lan (872): Lease of 192.168.211.211 obtained, lease time 86400
2017:05:01-18:44:18 192.168.211.211 netifd: Network device 'wlan8' link is down
2017:05:01-18:44:18 192.168.211.211 add_radio_mapping.sh: AP50 detected: Using on-the-fly ACS procedure
2017:05:01-18:44:20 192.168.211.211 root: Enable remote 802.11 capturing ...
2017:05:01-18:44:21 192.168.211.211 kernel: [815358.120000] device mon0 entered promiscuous mode
2017:05:01-18:44:21 192.168.211.211 kernel: [815358.150000] device mon1 entered promiscuous mode
2017:05:01-18:44:22 192.168.211.211 netifd: radio0 (20043): Configuration file: /var/run/hostapd-phy0.conf
2017:05:01-18:44:22 192.168.211.211 netifd: radio0 (20043): eapol_version=1
2017:05:01-18:44:22 192.168.211.211 netifd: radio0 (20043): eapol_version=1
2017:05:01-18:44:22 192.168.211.211 netifd: radio0 (20043): Duplicate BSSID 00:1a:8c:73:91:70 on interface 'wlan2' and 'wlan0'.
2017:05:01-18:44:22 192.168.211.211 netifd: radio0 (20043): 1 errors found in configuration file '/var/run/hostapd-phy0.conf'
2017:05:01-18:44:22 192.168.211.211 netifd: radio0 (20043): Failed to set up interface with /var/run/hostapd-phy0.conf
2017:05:01-18:44:22 192.168.211.211 netifd: radio0 (20043): hostapd_init: free iface 0x6db0d8
2017:05:01-18:44:22 192.168.211.211 netifd: radio0 (20043): Failed to initialize interface
2017:05:01-18:44:22 192.168.211.211 netifd: radio0 (20043): cat: can't open '/var/run/wifi-phy0.pid': No such file or directory
2017:05:01-18:44:22 192.168.211.211 netifd: radio0 (20043): Command failed: Invalid argument
2017:05:01-18:44:22 192.168.211.211 netifd: radio0 (20043): Device setup failed: HOSTAPD_START_FAILED
2017:05:01-18:44:27 192.168.211.211 kernel: [815364.720000] device wlan8 entered promiscuous mode
2017:05:01-18:44:27 192.168.211.211 netifd: radio1 (20268): Configuration file: /var/run/hostapd-phy1.conf
2017:05:01-18:44:27 192.168.211.211 netifd: radio1 (20268): eapol_version=1
2017:05:01-18:44:27 192.168.211.211 netifd: radio1 (20268): eapol_version=1
2017:05:01-18:44:27 192.168.211.211 netifd: radio1 (20268): eapol_version=1
2017:05:01-18:44:27 192.168.211.211 netifd: radio1 (20268): nl80211: TDLS supported
2017:05:01-18:44:27 192.168.211.211 netifd: radio1 (20268): nl80211: TDLS external setup
2017:05:01-18:44:27 192.168.211.211 netifd: radio1 (20268): nl80211: Supported cipher 00-0f-ac:1
2017:05:01-18:44:27 192.168.211.211 netifd: radio1 (20268): nl80211: Supported cipher 00-0f-ac:5
2017:05:01-18:44:27 192.168.211.211 netifd: radio1 (20268): nl80211: Supported cipher 00-0f-ac:2
2017:05:01-18:44:27 192.168.211.211 netifd: radio1 (20268): nl80211: Supported cipher 00-0f-ac:4
2017:05:01-18:44:27 192.168.211.211 netifd: radio1 (20268): nl80211: Supported cipher 00-0f-ac:6
2017:05:01-18:44:27 192.168.211.211 netifd: radio1 (20268): nl80211: Using driver-based off-channel TX
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: Use separate P2P group interface (driver advertised support)
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: interface wlan8 in phy phy1
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: Set mode ifindex 179 iftype 3 (AP)
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: Setup AP(wlan8) - device_ap_sme=0 use_monitor=0
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: Subscribe to mgmt frames with AP handle 0x5fcce8
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: Register frame type=0xb0 nl_handle=0x5fcce8 match=
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: Register frame type=0x0 nl_handle=0x5fcce8 match=
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: Register frame type=0x20 nl_handle=0x5fcce8 match=
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: Register frame type=0xa0 nl_handle=0x5fcce8 match=
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: Register frame type=0xc0 nl_handle=0x5fcce8 match=
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: Register frame type=0xd0 nl_handle=0x5fcce8 match=
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: Register frame type=0x40 nl_handle=0x5fcce8 match=
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: Add own interface ifindex 5
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: if_indices[16]: 5
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: Add own interface ifindex 3
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: if_indices[16]: 5 3
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: Add own interface ifindex 7
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: if_indices[16]: 5 3 7
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: Add own interface ifindex 179
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: if_indices[16]: 5 3 7 179
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: Adding interface wlan8 into bridge br-vxlan100
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): phy: phy1
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): BSS count 3, BSSID mask 00:00:00:00:00:03 (2 bits)
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Using existing control interface directory.
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Using existing control interface directory.
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): wlan8: interface state UNINITIALIZED->COUNTRY_UPDATE
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Previous country code US, new country code US
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: Regulatory information - country=US (DFS-FCC)
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: 2402-2472 @ 40 MHz 30 mBm
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: 5170-5250 @ 80 MHz 17 mBm
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: 5250-5330 @ 80 MHz 23 mBm (DFS)
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: 5490-5590 @ 80 MHz 24 mBm (DFS)
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: 5650-5710 @ 40 MHz 24 mBm (DFS)
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: 5735-5835 @ 80 MHz 30 mBm
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): nl80211: 57240-63720 @ 2160 MHz 40 mBm
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Allowed channel: mode=2 chan=36 freq=5180 MHz max_tx_power=17 dBm
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Allowed channel: mode=2 chan=40 freq=5200 MHz max_tx_power=17 dBm
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Allowed channel: mode=2 chan=44 freq=5220 MHz max_tx_power=17 dBm
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Allowed channel: mode=2 chan=48 freq=5240 MHz max_tx_power=17 dBm
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Channel 52 (5260)is disabled!!
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Channel 56 (5280)is disabled!!
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Channel 60 (5300)is disabled!!
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Channel 64 (5320)is disabled!!
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Channel 100 (5500)is disabled!!
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Channel 104 (5520)is disabled!!
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Channel 108 (5540)is disabled!!
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Channel 112 (5560)is disabled!!
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Channel 116 (5580)is disabled!!
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Channel 120 (5600)is disabled!!
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Channel 124 (5620)is disabled!!
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Channel 128 (5640)is disabled!!
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Channel 132 (5660)is disabled!!
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Channel 136 (5680)is disabled!!
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Channel 140 (5700)is disabled!!
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Allowed channel: mode=2 chan=149 freq=5745 MHz max_tx_power=30 dBm
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Allowed channel: mode=2 chan=153 freq=5765 MHz max_tx_power=30 dBm
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Allowed channel: mode=2 chan=157 freq=5785 MHz max_tx_power=30 dBm
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Allowed channel: mode=2 chan=161 freq=5805 MHz max_tx_power=30 dBm
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): Interface initialization will be completed in a callback (ACS)command failed: No such device (-19)
2017:05:01-18:44:28 192.168.211.211 netifd: radio1 (20268): command failed: No such device (-19)
2017:05:01-18:44:33 192.168.211.211 kernel: [815370.110000] br-vxlan100: port 2(wlan8) entered forwarding state
2017:05:01-18:44:33 192.168.211.211 kernel: [815370.120000] br-vxlan100: port 2(wlan8) entered forwarding state
2017:05:01-18:44:33 192.168.211.211 netifd: Network device 'wlan8' link is up
2017:05:01-18:44:33 192.168.211.211 kernel: [815370.150000] device wlan9 entered promiscuous mode
2017:05:01-18:44:33 192.168.211.211 kernel: [815370.150000] br-lan: port 2(wlan9) entered forwarding state
2017:05:01-18:44:33 192.168.211.211 kernel: [815370.160000] br-lan: port 2(wlan9) entered forwarding state
2017:05:01-18:44:33 192.168.211.211 netifd: Network device 'wlan9' link is up
2017:05:01-18:44:33 192.168.211.211 kernel: [815370.580000] device wlan10 entered promiscuous mode
2017:05:01-18:44:33 192.168.211.211 kernel: [815370.590000] br-vxlan102: port 2(wlan10) entered forwarding state
2017:05:01-18:44:33 192.168.211.211 kernel: [815370.590000] br-vxlan102: port 2(wlan10) entered forwarding state
2017:05:01-18:44:34 192.168.211.211 netifd: Network device 'wlan10' link is up
2017:05:01-18:44:35 192.168.211.211 kernel: [815372.120000] br-vxlan100: port 2(wlan8) entered forwarding state
2017:05:01-18:44:35 192.168.211.211 kernel: [815372.160000] br-lan: port 2(wlan9) entered forwarding state
2017:05:01-18:44:35 192.168.211.211 kernel: [815372.590000] br-vxlan102: port 2(wlan10) entered forwarding state
2017:05:01-18:44:36 192.168.211.211 hostapd: wlan10: STA 10:1c:0c:2a:f0:9f IEEE 802.11: authenticated
2017:05:01-18:44:36 192.168.211.211 hostapd: wlan10: STA 10:1c:0c:2a:f0:9f IEEE 802.11: associated (aid 1)
2017:05:01-18:44:36 192.168.211.211 hostapd: wlan10: STA 10:1c:0c:2a:f0:9f WPA: pairwise key handshake completed (RSN)
2017:05:01-18:44:36 192.168.211.211 awelogger[20378]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="WIFIWIFI2" ssid_id="WLAN2.1" bssid="00:1a:8c:73:91:7a" sta="10:1c:0c:2a:f0:9f" status_code="0"
2017:05:01-18:44:36 192.168.211.211 awelogger[20378]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="WIFIWIFI2" ssid_id="WLAN2.1" bssid="00:1a:8c:73:91:7a" sta="10:1c:0c:2a:f0:9f" status_code="0"
2017:05:01-18:44:36 192.168.211.211 awelogger[20378]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="WIFIWIFI2" ssid_id="WLAN2.1" bssid="00:1a:8c:73:91:7a" sta="10:1c:0c:2a:f0:9f"
2017:05:01-18:44:36 192.168.211.211 hostapd: wlan10: STA 0c:d7:46:ab:84:00 IEEE 802.11: authenticated
2017:05:01-18:44:36 192.168.211.211 hostapd: wlan10: STA 0c:d7:46:ab:84:00 IEEE 802.11: associated (aid 2)
2017:05:01-18:44:36 192.168.211.211 hostapd: wlan10: STA 0c:d7:46:ab:84:00 WPA: pairwise key handshake completed (RSN)
2017:05:01-18:44:36 192.168.211.211 awelogger[20378]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="WIFIWIFI2" ssid_id="WLAN2.1" bssid="00:1a:8c:73:91:7a" sta="0c:d7:46:ab:84:00" status_code="0"
2017:05:01-18:44:36 192.168.211.211 awelogger[20378]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="WIFIWIFI2" ssid_id="WLAN2.1" bssid="00:1a:8c:73:91:7a" sta="0c:d7:46:ab:84:00" status_code="0"
2017:05:01-18:45:07 fw awed[4785]: [MASTER] updating confd object for AP A40018A30FC2D14 with new channels (11,165 -> 165)
2017:05:01-18:45:32 fw awed[4785]: [MASTER] start processing configuration change
2017:05:01-18:45:34 fw awed[4785]: [MASTER] end processing configuration change
2017:05:01-18:49:36 192.168.211.211 hostapd: wlan9: STA f0:27:65:ea:69:40 IEEE 802.11: disassociated
2017:05:01-18:49:36 192.168.211.211 awelogger[20376]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="Westerberg5" ssid_id="WLAN1.1" bssid="00:1a:8c:73:91:79" sta="f0:27:65:ea:69:40"
2017:05:01-18:49:37 192.168.211.211 hostapd: wlan9: STA f0:27:65:ea:69:40 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
2017:05:01-18:49:40 192.168.211.211 hostapd: wlan9: STA f0:27:65:ea:69:40 IEEE 802.11: authenticated
2017:05:01-18:49:40 192.168.211.211 hostapd: wlan9: STA f0:27:65:ea:69:40 IEEE 802.11: associated (aid 1)
2017:05:01-18:49:40 192.168.211.211 hostapd: wlan9: STA f0:27:65:ea:69:40 WPA: pairwise key handshake completed (RSN)
2017:05:01-18:49:40 192.168.211.211 awelogger[20376]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="Westerberg5" ssid_id="WLAN1.1" bssid="00:1a:8c:73:91:79" sta="f0:27:65:ea:69:40" status_code="0"
2017:05:01-18:49:40 192.168.211.211 awelogger[20376]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="Westerberg5" ssid_id="WLAN1.1" bssid="00:1a:8c:73:91:79" sta="f0:27:65:ea:69:40" status_code="0"
2017:05:01-18:49:40 192.168.211.211 awelogger[20376]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="Westerberg5" ssid_id="WLAN1.1" bssid="00:1a:8c:73:91:79" sta="f0:27:65:ea:69:40"
2017:05:01-18:54:38 192.168.211.211 hostapd: wlan9: STA f0:27:65:ea:69:40 WPA: group key handshake completed (RSN)
2017:05:01-18:54:39 192.168.211.211 hostapd: wlan10: STA 0c:d7:46:ab:84:00 WPA: group key handshake completed (RSN)
2017:05:01-18:54:39 192.168.211.211 hostapd: wlan10: STA 10:1c:0c:2a:f0:9f WPA: group key handshake completed (RSN)
2017:05:01-18:54:39 192.168.211.211 hostapd: wlan10: STA 1c:5c:f2:9b:34:79 WPA: group key handshake completed (RSN)



This thread was automatically locked due to age.
Parents Reply
  • Channel selection can be one of the options to try. Where multiple APs are being used, they should be configured to use different channels if their signals will overlap; and these channels should be as far apart as possible. For example, you may have two APs configured as:

    • AP1: channel 3
    • AP2: channel 9

    Thanks

    Sachin Gurung
    Team Lead | Sophos Technical Support
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

Children