Guest User!

You are not Sophos Staff.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 26 subscribers
  • Views 631 views
  • Users 0 members are here
Options
Suggested
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

AP55c rebooting, netifd: radio0: "result": "FAILURE"

LHerzog

XG 18.5 MR2 managed AP55c are in VLAN and broadcast multiple SSID, some with hotspot, one with RADIUS, and multiple with WPA2 PSK.
AP Firmware: 11.0.018

We first noticed problems on an AP where the users had mutiple disconnects over the day. this AP was also showing up with multiple disconnects logged in awed.log.

Today we put in a spare AP55c for that one and it is also having issues and mostly I find these FAILURE messages problematic:

<29>Mar 28 09:15:11 A4003478DE4AE30 netifd: radio0 (2018):      "result": "FAILURE"
<29>Mar 28 09:15:12 A4003478DE4AE30 netifd: radio1 (2021):      "result": "FAILURE"
<29>Mar 28 09:19:51 A4003478DE4AE30 netifd: radio1 (2019):      "result": "FAILURE"
<29>Mar 28 09:19:51 A4003478DE4AE30 netifd: radio0 (2018):      "result": "FAILURE"
<29>Mar 28 09:31:05 A4003478DE4AE30 netifd: radio1 (2028):      "result": "FAILURE"
<29>Mar 28 09:31:06 A4003478DE4AE30 netifd: radio0 (2026):      "result": "FAILURE"
<29>Mar 28 09:54:15 A4003478DE4AE30 netifd: radio0 (2018):      "result": "FAILURE"
<29>Mar 28 09:54:16 A4003478DE4AE30 netifd: radio1 (2021):      "result": "FAILURE"
<29>Mar 28 10:04:47 A4003478DE4AE30 netifd: radio0 (2017):      "result": "FAILURE"
<29>Mar 28 10:04:48 A4003478DE4AE30 netifd: radio1 (2018):      "result": "FAILURE"
<29>Dec 23 08:34:50 A4003478DE4AE30 netifd: radio0 (2028):      "result": "FAILURE"
<29>Dec 23 08:34:51 A4003478DE4AE30 netifd: radio1 (2029):      "result": "FAILURE"
<29>Dec 23 08:34:51 A4003478DE4AE30 netifd: radio0 (2024):      "result": "FAILURE"
<29>Dec 23 08:34:51 A4003478DE4AE30 netifd: radio1 (2025):      "result": "FAILURE"
<29>Mar 28 10:32:23 A4003478DE4AE30 netifd: radio0 (2017):      "result": "FAILURE"
<29>Mar 28 10:32:23 A4003478DE4AE30 netifd: radio1 (2018):      "result": "FAILURE"
<29>Mar 28 10:40:08 A4003478DE4AE30 netifd: radio0 (2025):      "result": "FAILURE"
<29>Mar 28 10:40:09 A4003478DE4AE30 netifd: radio1 (2029):      "result": "FAILURE"
<29>Mar 28 10:48:26 A4003478DE4AE30 netifd: radio0 (2028):      "result": "FAILURE"
<29>Mar 28 10:48:26 A4003478DE4AE30 netifd: radio1 (2029):      "result": "FAILURE"
<29>Mar 28 10:58:49 A4003478DE4AE30 netifd: radio0 (2020):      "result": "FAILURE"
<29>Mar 28 10:58:49 A4003478DE4AE30 netifd: radio1 (2021):      "result": "FAILURE"
<29>Mar 28 11:08:51 A4003478DE4AE30 netifd: radio0 (2022):      "result": "FAILURE"
<29>Mar 28 11:08:51 A4003478DE4AE30 netifd: radio1 (2023):      "result": "FAILURE"
<29>Mar 28 11:16:07 A4003478DE4AE30 netifd: radio1 (2027):      "result": "FAILURE"
<29>Mar 28 11:16:07 A4003478DE4AE30 netifd: radio0 (2025):      "result": "FAILURE"
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio0 (2016):      "result": "FAILURE"
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio1 (2017):      "result": "FAILURE"

This reminds me about the issue described here: https://community.sophos.com/xg-firewall/f/discussions/120686/wlan-disconnects-after-applying-new-ap-firmware-11-0-012

This is a full log block, you can see at the end, the AP probably rebooted and reconnected

<29>Mar 28 11:27:26 A4003478DE4AE30 aweclient[1057]: aweclient.c (2559) Exit from main loop with no error. Get new configuration.
<30>Mar 28 11:29:04 A4003478DE4AE30 pdog[871]: src/process.c:249/timer_timeout_cb: process aweclient is dead for 100 seconds
<27>Mar 28 11:29:35 A4003478DE4AE30 pdog[871]: src/process.c:325/unregister_process: process with name aweclient is not registered before
<30>Mar 28 11:29:36 A4003478DE4AE30 procd: - shutdown -
<24>Mar 28 11:29:36 A4003478DE4AE30 procd:
<27>Mar 28 11:29:36 A4003478DE4AE30 pdog[871]: src/process.c:325/unregister_process: process with name aweclient is not registered before
<29>Mar 28 11:29:36 A4003478DE4AE30 aweclient[3749]: Opening log...
<28>Mar 28 11:29:36 A4003478DE4AE30 aweclient[3749]: aweclient.c (295) Failed to connect to 0.0.0.0.
<24>Mar 28 11:29:36 A4003478DE4AE30 procd:
<86>Mar 28 11:29:37 A4003478DE4AE30 dropbear[2582]: Early exit: Terminated by signal
<30>Dec 23 08:34:35 A4003478DE4AE30 logread[1245]: Logread connected to 172.16.xxx.200:415

<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio0 (2016): nl80211: Scan frequency 2442 MHz
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio0 (2016): nl80211: Scan frequency 2447 MHz
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio0 (2016): nl80211: Scan frequency 2452 MHz
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio0 (2016): nl80211: Scan frequency 2457 MHz
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio0 (2016): nl80211: Scan frequency 2462 MHz
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio0 (2016): nl80211: Scan frequency 2467 MHz
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio0 (2016): nl80211: Scan frequency 2472 MHz
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio0 (2016): Scan requested (ret=0) - scan timeout 10 seconds
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio0 (2016): wlan0: interface state COUNTRY_UPDATE->ACS
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio0 (2016): wlan0: ACS-STARTED
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio0 (2016): Interface initialization will be completed in a callback (ACS)
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio0 (2016): ctrl_iface not configured!
<3>Mar 28 11:22:35 A4003478DE4AE30 kernel: [   60.500000] ath: phy2: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02100020 DMADBG_7=0x00006300
<27>Mar 28 11:22:35 A4003478DE4AE30 pdog[871]: src/process.c:325/unregister_process: process with name hostapd-phy3 is not registered before
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio1 (2017): {
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio1 (2017):      "result": "FAILURE"
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio1 (2017): }
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio1 (2017): Configuration file: /var/run/hostapd-phy3.conf
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio1 (2017): eapol_version=1
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio1 (2017): eapol_version=1
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio1 (2017): eapol_version=1
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio1 (2017): eapol_version=1
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Supported cipher 00-0f-ac:1
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Supported cipher 00-0f-ac:5
<29>Mar 28 11:22:35 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Supported cipher 00-0f-ac:2
<29>Mar 28 11:22:36 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Supported cipher 00-0f-ac:4
<29>Mar 28 11:22:36 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Supported cipher 00-0f-ac:6
<29>Mar 28 11:22:36 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Supported cipher 00-0f-ac:13
<29>Mar 28 11:22:36 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Supported cipher 00-0f-ac:11
<29>Mar 28 11:22:36 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Supported cipher 00-0f-ac:12
<29>Mar 28 11:22:36 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Using driver-based off-channel TX
<29>Mar 28 11:22:36 A4003478DE4AE30 netifd: radio1 (2017): nl80211: interface wlan8 in phy phy3
<29>Mar 28 11:22:36 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Set mode ifindex 16 iftype 3 (AP)
<29>Mar 28 11:22:36 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Setup AP(wlan8) - device_ap_sme=0 use_monitor=0
<29>Mar 28 11:22:36 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Subscribe to mgmt frames with AP handle 0xb80960
<29>Mar 28 11:22:36 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Register frame type=0xb0 (WLAN_FC_STYPE_AUTH) nl_handle=0xb80960 match=
<29>Mar 28 11:22:36 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Register frame type=0x0 (WLAN_FC_STYPE_ASSOC_REQ) nl_handle=0xb80960 match=
<29>Mar 28 11:22:36 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Register frame type=0x20 (WLAN_FC_STYPE_REASSOC_REQ) nl_handle=0xb80960 match=
<29>Mar 28 11:22:36 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Register frame type=0xa0 (WLAN_FC_STYPE_DISASSOC) nl_handle=0xb80960 match=
<29>Mar 28 11:22:36 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Register frame type=0xc0 (WLAN_FC_STYPE_DEAUTH) nl_handle=0xb80960 match=
<29>Mar 28 11:22:36 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xb80960 match=
<29>Mar 28 11:22:36 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Register frame type=0x40 (WLAN_FC_STYPE_PROBE_REQ) nl_handle=0xb80960 match=
<3>Mar 28 11:22:36 A4003478DE4AE30 kernel: [   61.970000] ath: phy2: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006300
<4>Mar 28 11:22:37 A4003478DE4AE30 kernel: [   62.960000] ath10k_pci 0000:00:00.0: pdev param 0 not supported by firmware
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Add own interface ifindex 13
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: if_indices[16]: 13
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Add own interface ifindex 11
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: if_indices[16]: 13 11
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Add own interface ifindex 11
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: ifindex 11 already in the list
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Add own interface ifindex 9
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: if_indices[16]: 13 11 9
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Add own interface ifindex 16
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: if_indices[16]: 13 11 9 16
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Adding interface wlan8 into bridge br-lan3006
<6>Mar 28 11:22:38 A4003478DE4AE30 kernel: [   63.070000] device wlan8 entered promiscuous mode
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): phy: phy3
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): BSS count 4, BSSID mask 00:00:00:00:00:03 (2 bits)
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Using existing control interface directory.
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Using existing control interface directory.
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Using existing control interface directory.
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Using existing control interface directory.
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): wlan8: interface state UNINITIALIZED->COUNTRY_UPDATE
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Previous country code DE, new country code DE
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Regulatory information - country=DE (DFS-ETSI)
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: 2400-2483 @ 40 MHz 20 mBm
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: 5150-5250 @ 80 MHz 20 mBm (no outdoor)
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: 5250-5350 @ 80 MHz 20 mBm (no outdoor) (DFS)
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: 5470-5725 @ 160 MHz 26 mBm (DFS)
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: 57000-66000 @ 2160 MHz 40 mBm
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Allowed channel: mode=2 chan=36 freq=5180 MHz max_tx_power=20 dBm
<3>Mar 28 11:22:38 A4003478DE4AE30 kernel: [   63.150000] ath: phy2: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02100020 DMADBG_7=0x00006300
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Allowed channel: mode=2 chan=40 freq=5200 MHz max_tx_power=20 dBm
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Allowed channel: mode=2 chan=44 freq=5220 MHz max_tx_power=20 dBm
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Allowed channel: mode=2 chan=48 freq=5240 MHz max_tx_power=20 dBm
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Allowed channel: mode=2 chan=52 freq=5260 MHz max_tx_power=20 dBm (DFS state = usable)
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Allowed channel: mode=2 chan=56 freq=5280 MHz max_tx_power=20 dBm (DFS state = usable)
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Allowed channel: mode=2 chan=60 freq=5300 MHz max_tx_power=20 dBm (DFS state = usable)
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Allowed channel: mode=2 chan=64 freq=5320 MHz max_tx_power=20 dBm (DFS state = usable)
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Allowed channel: mode=2 chan=100 freq=5500 MHz max_tx_power=26 dBm (DFS state = usable)
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Allowed channel: mode=2 chan=104 freq=5520 MHz max_tx_power=26 dBm (DFS state = usable)
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Allowed channel: mode=2 chan=108 freq=5540 MHz max_tx_power=26 dBm (DFS state = usable)
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Allowed channel: mode=2 chan=112 freq=5560 MHz max_tx_power=26 dBm (DFS state = usable)
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): ACS: skipping channel 157 (5785)
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): ACS: skipping channel 161 (5805)
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): ACS: skipping channel 165 (5825)
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): ACS: Scanning 1 / 5
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): wlan8: nl80211: scan request
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Scan frequency 5180 MHz
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Scan frequency 5200 MHz
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Scan frequency 5220 MHz
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Scan frequency 5240 MHz
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Scan frequency 5660 MHz
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Scan frequency 5680 MHz
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): nl80211: Scan frequency 5700 MHz
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Scan requested (ret=0) - scan timeout 10 seconds
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): wlan8: interface state COUNTRY_UPDATE->ACS
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): wlan8: ACS-STARTED
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): Interface initialization will be completed in a callback (ACS)
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio1 (2017): ctrl_iface not configured!
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio0 (2016): command failed: No such device (-19)
<29>Mar 28 11:22:38 A4003478DE4AE30 netifd: radio0 (2016): command failed: No such device (-19)
<29>Mar 28 11:22:39 A4003478DE4AE30 netifd: radio0 (2016): command failed: No such device (-19)
<3>Mar 28 11:22:39 A4003478DE4AE30 kernel: [   64.560000] ath: phy2: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02100020 DMADBG_7=0x00006300
<3>Mar 28 11:22:39 A4003478DE4AE30 kernel: [   64.720000] ath: phy2: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02100020 DMADBG_7=0x00006300
<29>Mar 28 11:22:40 A4003478DE4AE30 netifd: radio1 (2017): command failed: No such device (-19)
<29>Mar 28 11:22:40 A4003478DE4AE30 netifd: radio1 (2017): command failed: No such device (-19)
<29>Mar 28 11:22:40 A4003478DE4AE30 netifd: radio1 (2017): command failed: No such device (-19)
<3>Mar 28 11:22:41 A4003478DE4AE30 kernel: [   66.090000] ath: phy2: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02100020 DMADBG_7=0x00006300
<3>Mar 28 11:22:41 A4003478DE4AE30 kernel: [   66.240000] ath: phy2: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02100020 DMADBG_7=0x00006300
<3>Mar 28 11:22:42 A4003478DE4AE30 kernel: [   67.620000] ath: phy2: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02100020 DMADBG_7=0x00006300
<3>Mar 28 11:22:43 A4003478DE4AE30 kernel: [   68.220000] ath: phy2: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02100020 DMADBG_7=0x00006300
<29>Mar 28 11:22:43 A4003478DE4AE30 aweclient[1057]: aweclient.c (1882) A signal received during select.
<86>Mar 28 11:22:43 A4003478DE4AE30 dropbear[2582]: Not backgrounding
<3>Mar 28 11:22:44 A4003478DE4AE30 kernel: [   69.850000] ath: phy2: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x00006300
<30>Mar 28 11:22:44 A4003478DE4AE30 hostapd: wlan0: RADIUS Authentication server 172.16.xxx.200:414
<30>Mar 28 11:22:44 A4003478DE4AE30 hostapd: wlan0: RADIUS Accounting server 172.16.xxx.200:417
<6>Mar 28 11:22:44 A4003478DE4AE30 kernel: [   69.910000] br-lan3006: port 2(wlan0) entered forwarding state
<6>Mar 28 11:22:44 A4003478DE4AE30 kernel: [   69.920000] br-lan3006: port 2(wlan0) entered forwarding state
<29>Mar 28 11:22:44 A4003478DE4AE30 netifd: Network device 'wlan0' link is up
<6>Mar 28 11:22:44 A4003478DE4AE30 kernel: [   69.950000] device wlan1 entered promiscuous mode
<6>Mar 28 11:22:44 A4003478DE4AE30 kernel: [   69.980000] br-lan254: port 2(wlan1) entered forwarding state
<6>Mar 28 11:22:44 A4003478DE4AE30 kernel: [   69.980000] br-lan254: port 2(wlan1) entered forwarding state
<6>Mar 28 11:22:45 A4003478DE4AE30 kernel: [   70.910000] br-lan254: port 2(wlan1) entered disabled state
<6>Mar 28 11:22:46 A4003478DE4AE30 kernel: [   71.360000] br-lan254: port 2(wlan1) entered forwarding state
<6>Mar 28 11:22:46 A4003478DE4AE30 kernel: [   71.370000] br-lan254: port 2(wlan1) entered forwarding state
<29>Mar 28 11:22:46 A4003478DE4AE30 netifd: Network device 'wlan1' link is up
<6>Mar 28 11:22:46 A4003478DE4AE30 kernel: [   71.410000] device wlan2 entered promiscuous mode
<6>Mar 28 11:22:46 A4003478DE4AE30 kernel: [   71.430000] br-lan254: port 3(wlan2) entered forwarding state
<6>Mar 28 11:22:46 A4003478DE4AE30 kernel: [   71.430000] br-lan254: port 3(wlan2) entered forwarding state
<30>Mar 28 11:22:46 A4003478DE4AE30 hostapd: wlan2: RADIUS Authentication server 172.16.xxx.200:414
<30>Mar 28 11:22:46 A4003478DE4AE30 hostapd: wlan2: RADIUS Accounting server 172.16.xxx.200:417
<29>Mar 28 11:22:46 A4003478DE4AE30 netifd: Network device 'wlan2' link is up
<6>Mar 28 11:22:46 A4003478DE4AE30 kernel: [   71.530000] device wlan3 entered promiscuous mode
<6>Mar 28 11:22:46 A4003478DE4AE30 kernel: [   71.550000] br-lan15: port 2(wlan3) entered forwarding state
<6>Mar 28 11:22:46 A4003478DE4AE30 kernel: [   71.550000] br-lan15: port 2(wlan3) entered forwarding state
<6>Mar 28 11:22:46 A4003478DE4AE30 kernel: [   71.910000] br-lan15: port 2(wlan3) entered disabled state
<6>Mar 28 11:22:46 A4003478DE4AE30 kernel: [   71.920000] br-lan3006: port 2(wlan0) entered forwarding state
<6>Mar 28 11:22:48 A4003478DE4AE30 kernel: [   73.050000] br-lan15: port 2(wlan3) entered forwarding state
<6>Mar 28 11:22:48 A4003478DE4AE30 kernel: [   73.060000] br-lan15: port 2(wlan3) entered forwarding state
<29>Mar 28 11:22:48 A4003478DE4AE30 netifd: Network device 'wlan3' link is up
<6>Mar 28 11:22:48 A4003478DE4AE30 kernel: [   73.370000] br-lan254: port 2(wlan1) entered forwarding state
<6>Mar 28 11:22:48 A4003478DE4AE30 kernel: [   73.430000] br-lan254: port 3(wlan2) entered forwarding state
<6>Mar 28 11:22:50 A4003478DE4AE30 kernel: [   75.060000] br-lan15: port 2(wlan3) entered forwarding state
<30>Mar 28 11:22:50 A4003478DE4AE30 hostapd: wlan8: RADIUS Authentication server 172.16.xxx.200:414
<30>Mar 28 11:22:50 A4003478DE4AE30 hostapd: wlan8: RADIUS Accounting server 172.16.xxx.200:417
<6>Mar 28 11:22:50 A4003478DE4AE30 kernel: [   75.750000] br-lan3006: port 3(wlan8) entered forwarding state
<6>Mar 28 11:22:50 A4003478DE4AE30 kernel: [   75.760000] br-lan3006: port 3(wlan8) entered forwarding state
<29>Mar 28 11:22:50 A4003478DE4AE30 netifd: Network device 'wlan8' link is up
<6>Mar 28 11:22:50 A4003478DE4AE30 kernel: [   75.810000] device wlan9 entered promiscuous mode
<6>Mar 28 11:22:50 A4003478DE4AE30 kernel: [   75.820000] br-lan254: port 4(wlan9) entered forwarding state
<6>Mar 28 11:22:50 A4003478DE4AE30 kernel: [   75.830000] br-lan254: port 4(wlan9) entered forwarding state
<6>Mar 28 11:22:51 A4003478DE4AE30 kernel: [   76.750000] br-lan254: port 4(wlan9) entered disabled state
<6>Mar 28 11:22:52 A4003478DE4AE30 kernel: [   77.070000] br-lan254: port 4(wlan9) entered forwarding state
<6>Mar 28 11:22:52 A4003478DE4AE30 kernel: [   77.080000] br-lan254: port 4(wlan9) entered forwarding state
<29>Mar 28 11:22:52 A4003478DE4AE30 netifd: Network device 'wlan9' link is up
<6>Mar 28 11:22:52 A4003478DE4AE30 kernel: [   77.120000] device wlan10 entered promiscuous mode
<6>Mar 28 11:22:52 A4003478DE4AE30 kernel: [   77.140000] br-lan254: port 5(wlan10) entered forwarding state
<6>Mar 28 11:22:52 A4003478DE4AE30 kernel: [   77.140000] br-lan254: port 5(wlan10) entered forwarding state
<30>Mar 28 11:22:52 A4003478DE4AE30 hostapd: wlan10: RADIUS Authentication server 172.16.xxx.200:414
<30>Mar 28 11:22:52 A4003478DE4AE30 hostapd: wlan10: RADIUS Accounting server 172.16.xxx.200:417
<29>Mar 28 11:22:52 A4003478DE4AE30 netifd: Network device 'wlan10' link is up
<6>Mar 28 11:22:52 A4003478DE4AE30 kernel: [   77.330000] device wlan11 entered promiscuous mode
<6>Mar 28 11:22:52 A4003478DE4AE30 kernel: [   77.350000] br-lan15: port 3(wlan11) entered forwarding state
<6>Mar 28 11:22:52 A4003478DE4AE30 kernel: [   77.360000] br-lan15: port 3(wlan11) entered forwarding state
<6>Mar 28 11:22:52 A4003478DE4AE30 kernel: [   77.750000] br-lan15: port 3(wlan11) entered disabled state
<6>Mar 28 11:22:52 A4003478DE4AE30 kernel: [   77.760000] br-lan3006: port 3(wlan8) entered forwarding state
<6>Mar 28 11:22:53 A4003478DE4AE30 kernel: [   78.790000] br-lan15: port 3(wlan11) entered forwarding state
<6>Mar 28 11:22:53 A4003478DE4AE30 kernel: [   78.800000] br-lan15: port 3(wlan11) entered forwarding state
<29>Mar 28 11:22:53 A4003478DE4AE30 netifd: Network device 'wlan11' link is up
<6>Mar 28 11:22:54 A4003478DE4AE30 kernel: [   79.080000] br-lan254: port 4(wlan9) entered forwarding state
<6>Mar 28 11:22:54 A4003478DE4AE30 kernel: [   79.140000] br-lan254: port 5(wlan10) entered forwarding state
<6>Mar 28 11:22:55 A4003478DE4AE30 kernel: [   80.800000] br-lan15: port 3(wlan11) entered forwarding state
<27>Mar 28 11:27:21 A4003478DE4AE30 aweclient[1057]: aweclient.c (2122) No reply get from last message, close socket.
<28>Mar 28 11:27:21 A4003478DE4AE30 aweclient[1057]: aweclient.c (295) Failed to connect to 0.0.0.0.
<29>Mar 28 11:27:26 A4003478DE4AE30 aweclient[1057]: aweclient.c (2107) Reconfiguration required. need_reconf = 1
<29>Mar 28 11:27:26 A4003478DE4AE30 aweclient[1057]: aweclient.c (2559) Exit from main loop with no error. Get new configuration.
<30>Mar 28 11:29:04 A4003478DE4AE30 pdog[871]: src/process.c:249/timer_timeout_cb: process aweclient is dead for 100 seconds
<27>Mar 28 11:29:35 A4003478DE4AE30 pdog[871]: src/process.c:325/unregister_process: process with name aweclient is not registered before
<30>Mar 28 11:29:36 A4003478DE4AE30 procd: - shutdown -
<24>Mar 28 11:29:36 A4003478DE4AE30 procd:
<27>Mar 28 11:29:36 A4003478DE4AE30 pdog[871]: src/process.c:325/unregister_process: process with name aweclient is not registered before
<29>Mar 28 11:29:36 A4003478DE4AE30 aweclient[3749]: Opening log...
<28>Mar 28 11:29:36 A4003478DE4AE30 aweclient[3749]: aweclient.c (295) Failed to connect to 0.0.0.0.
<24>Mar 28 11:29:36 A4003478DE4AE30 procd:
<86>Mar 28 11:29:37 A4003478DE4AE30 dropbear[2582]: Early exit: Terminated by signal
<30>Dec 23 08:34:35 A4003478DE4AE30 logread[1245]: Logread connected to 172.16.xxx.200:415
<29>Dec 23 08:34:38 A4003478DE4AE30 netifd: Interface 'vxlan' is enabled
<29>Dec 23 08:34:38 A4003478DE4AE30 netifd: Network device 'vxlan' link is up
<29>Dec 23 08:34:38 A4003478DE4AE30 netifd: Interface 'vxlan' has link connectivity
<29>Dec 23 08:34:38 A4003478DE4AE30 netifd: Interface 'vxlan' is setting up now
<29>Dec 23 08:34:38 A4003478DE4AE30 netifd: Interface 'vxlan' is now up
<29>Dec 23 08:34:38 A4003478DE4AE30 netifd: VLAN 'br-lan.15' link is up

Also I noticed some ping loss when pinging the AP while it was able to ping me without loss.



This thread was automatically locked due to age.
Parents
  • 0

    an other AP55c: a user connects to RADIUS WiFi SSID, then the AP reboots.

    <30>Mar 28 12:08:04 A40034C39287DD6 hostapd: wlan2: STA e8:78:29:c0:b5:15 IEEE 802.11: authenticated
<13>Mar 28 12:08:04 A40034C39287DD6 awelogger[2657]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="our_ssid-name" ssid_id="WLAN4.0" bssid="00:1a:8c:a1:98:f8" sta="e8:78:29:c0:b5:15" status_code="0"
<13>Mar 28 12:08:04 A40034C39287DD6 awelogger[2657]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="our_ssid-name" ssid_id="WLAN4.0" bssid="00:1a:8c:a1:98:f8" sta="e8:78:29:c0:b5:15" status_code="0"
<30>Mar 28 12:08:04 A40034C39287DD6 hostapd: wlan2: STA e8:78:29:c0:b5:15 IEEE 802.11: associated (aid 1)
<30>Mar 28 12:08:05 A40034C39287DD6 hostapd: wlan2: STA e8:78:29:c0:b5:15 IEEE 802.1X: STA identity 'username'
<27>Mar 28 12:08:14 A40034C39287DD6 pdog[869]: src/process.c:325/unregister_process: process with name aweclient is not registered before
<30>Mar 28 12:08:14 A40034C39287DD6 procd: - shutdown -
<24>Mar 28 12:08:15 A40034C39287DD6 procd:
<27>Mar 28 12:08:15 A40034C39287DD6 pdog[869]: src/process.c:325/unregister_process: process with name aweclient is not registered before
<29>Mar 28 12:08:15 A40034C39287DD6 aweclient[3198]: Opening log...
<28>Mar 28 12:08:16 A40034C39287DD6 aweclient[3198]: aweclient.c (295) Failed to connect to 0.0.0.0.
<24>Mar 28 12:08:16 A40034C39287DD6 procd:
<86>Mar 28 12:08:16 A40034C39287DD6 dropbear[2736]: Early exit: Terminated by signal
<30>Dec 23 08:34:34 A40034C39287DD6 logread[1244]: Logread connected to 172.16.xxx.200:415
<29>Dec 23 08:34:38 A40034C39287DD6 netifd: Interface 'vxlan' is enabled
<29>Dec 23 08:34:38 A40034C39287DD6 netifd: Network device 'vxlan' link is up
<29>Dec 23 08:34:38 A40034C39287DD6 netifd: Interface 'vxlan' has link connectivity
<29>Dec 23 08:34:38 A40034C39287DD6 netifd: Interface 'vxlan' is setting up now
<29>Dec 23 08:34:38 A40034C39287DD6 netifd: Interface 'vxlan' is now up
<29>Dec 23 08:34:38 A40034C39287DD6 netifd: VLAN 'br-lan.15' link is up

    then it came up again, enabled it's radios and just rebooted again

    <29>Mar 28 12:16:35 A40034C39287DD6 netifd: Network device 'wlan10' link is up
<6>Mar 28 12:16:35 A40034C39287DD6 kernel: [  125.680000] device wlan11 entered promiscuous mode
<6>Mar 28 12:16:35 A40034C39287DD6 kernel: [  125.690000] br-lan15: port 3(wlan11) entered forwarding state
<6>Mar 28 12:16:35 A40034C39287DD6 kernel: [  125.690000] br-lan15: port 3(wlan11) entered forwarding state
<6>Mar 28 12:16:35 A40034C39287DD6 kernel: [  126.030000] br-lan15: port 3(wlan11) entered disabled state
<6>Mar 28 12:16:35 A40034C39287DD6 kernel: [  126.040000] br-lan3006: port 2(wlan8) entered forwarding state
<6>Mar 28 12:16:36 A40034C39287DD6 kernel: [  127.200000] br-lan15: port 3(wlan11) entered forwarding state
<6>Mar 28 12:16:36 A40034C39287DD6 kernel: [  127.200000] br-lan15: port 3(wlan11) entered forwarding state
<29>Mar 28 12:16:36 A40034C39287DD6 netifd: Network device 'wlan11' link is up
<6>Mar 28 12:16:37 A40034C39287DD6 kernel: [  127.430000] br-lan254: port 4(wlan9) entered forwarding state
<6>Mar 28 12:16:37 A40034C39287DD6 kernel: [  127.500000] br-lan254: port 5(wlan10) entered forwarding state
<6>Mar 28 12:16:38 A40034C39287DD6 kernel: [  129.200000] br-lan15: port 3(wlan11) entered forwarding state
<27>Mar 28 12:16:46 A40034C39287DD6 aweclient[1057]: aweclient.c (2122) No reply get from last message, close socket.
<28>Mar 28 12:16:46 A40034C39287DD6 aweclient[1057]: aweclient.c (295) Failed to connect to 0.0.0.0.
<27>Mar 28 12:17:03 A40034C39287DD6 aweclient[1057]: aweclient.c (2122) No reply get from last message, close socket.
<28>Mar 28 12:17:03 A40034C39287DD6 aweclient[1057]: aweclient.c (295) Failed to connect to 0.0.0.0.
<29>Mar 28 12:17:06 A40034C39287DD6 aweclient[1057]: aweclient.c (2107) Reconfiguration required. need_reconf = 1
<29>Mar 28 12:17:06 A40034C39287DD6 aweclient[1057]: aweclient.c (2559) Exit from main loop with no error. Get new configuration.
<30>Mar 28 12:18:45 A40034C39287DD6 pdog[870]: src/process.c:249/timer_timeout_cb: process aweclient is dead for 100 seconds
<27>Mar 28 12:19:16 A40034C39287DD6 pdog[870]: src/process.c:325/unregister_process: process with name aweclient is not registered before
<30>Mar 28 12:19:16 A40034C39287DD6 procd: - shutdown -
<24>Mar 28 12:19:17 A40034C39287DD6 procd:
<27>Mar 28 12:19:17 A40034C39287DD6 pdog[870]: src/process.c:325/unregister_process: process with name aweclient is not registered before
<29>Mar 28 12:19:17 A40034C39287DD6 aweclient[3184]: Opening log...
<28>Mar 28 12:19:17 A40034C39287DD6 aweclient[3184]: aweclient.c (295) Failed to connect to 0.0.0.0.
<24>Mar 28 12:19:17 A40034C39287DD6 procd:
<86>Mar 28 12:19:17 A40034C39287DD6 dropbear[2740]: Early exit: Terminated by signal
<30>Dec 23 08:34:34 A40034C39287DD6 logread[1246]: Logread connected to 172.16.xxx.200:415
<29>Dec 23 08:34:38 A40034C39287DD6 netifd: Interface 'vxlan' is enabled
<29>Dec 23 08:34:38 A40034C39287DD6 netifd: Network device 'vxlan' link is up
<29>Dec 23 08:34:38 A40034C39287DD6 netifd: Interface 'vxlan' has link connectivity
<29>Dec 23 08:34:38 A40034C39287DD6 netifd: Interface 'vxlan' is setting up now
<29>Dec 23 08:34:38 A40034C39287DD6 netifd: Interface 'vxlan' is now up
<29>Dec 23 08:34:38 A40034C39287DD6 netifd: VLAN 'br-lan.15' link is up
<6>Dec 23 08:34:38 A40034C39287DD6 kernel: [   47.900000] device br-lan.15 entered promiscuous mode
<6>Dec 23 08:34:38 A40034C39287DD6 kernel: [   47.930000] br-lan15: port 1(br-lan.15) entered forwarding state
<6>Dec 23 08:34:38 A40034C39287DD6 kernel: [   47.930000] br-lan15: port 1(br-lan.15) entered forwarding state
<29>Dec 23 08:34:38 A40034C39287DD6 netifd: Interface 'lan15' is enabled


    <29>Mar 28 12:04:11 A40034C39287DD6 netifd: radio0 (2015):      "result": "FAILURE"
    <29>Mar 28 12:04:11 A40034C39287DD6 netifd: radio1 (2016):      "result": "FAILURE"
    <29>Dec 23 08:34:51 A40034C39287DD6 netifd: radio1 (2021):      "result": "FAILURE"
    <29>Dec 23 08:34:51 A40034C39287DD6 netifd: radio0 (2020):      "result": "FAILURE"
    <29>Mar 28 12:15:31 A40034C39287DD6 netifd: radio1 (2017):      "result": "FAILURE"
    <29>Mar 28 12:15:31 A40034C39287DD6 netifd: radio0 (2016):      "result": "FAILURE"
    <29>Dec 23 08:34:51 A40034C39287DD6 netifd: radio0 (2024):      "result": "FAILURE"
    <29>Dec 23 08:34:51 A40034C39287DD6 netifd: radio0 (2017):      "result": "FAILURE"
    <29>Dec 23 08:34:53 A40034C39287DD6 netifd: radio1 (2018):      "result": "FAILURE"

    <29>Dec 23 08:34:49 A40034C39287DD6 netifd: radio1 (2018): ./mac80211.sh: eval: line 1: 1: not found
<29>Mar 28 13:02:07 A40034C39287DD6 netifd: radio0 (2017): ./mac80211.sh: eval: line 1: 1: not found
<29>Mar 28 13:02:07 A40034C39287DD6 netifd: radio1 (2018): ./mac80211.sh: eval: line 1: 1: not found
<27>Mar 28 13:02:08 A40034C39287DD6 pdog[870]: src/process.c:325/unregister_process: process with name hostapd-phy2 is not registered before
<29>Mar 28 13:02:08 A40034C39287DD6 netifd: radio0 (2017): {
<29>Mar 28 13:02:08 A40034C39287DD6 netifd: radio0 (2017):      "result": "FAILURE"
<29>Mar 28 13:02:08 A40034C39287DD6 netifd: radio0 (2017): }
<29>Mar 28 13:02:08 A40034C39287DD6 netifd: radio0 (2017): Configuration file: /var/run/hostapd-phy2.conf

    Someone actively working on EoL enforcement? New WiFi hardware orders have no delivery date, probably out of stock.

  • 0 in reply to LHerzog

    Hello LHerzog,

    Thank you for contacting the Sophos Community.

    I checked internally and could find  NC-78214 that sort of matches the logs you shared, but not entirely as  they differ on 

    <29>Mar 28 11:29:36 A4003478DE4AE30 aweclient[3749]: Opening log...
    <28>Mar 28 11:29:36 A4003478DE4AE30 aweclient[3749]: aweclient.c (295) Failed to connect to 0.0.0.0.
    <24>Mar 28 11:29:36 A4003478DE4AE30 procd:
    <86>Mar 28 11:29:37 A4003478DE4AE30 dropbear[2582]: Early exit: Terminated by signal
    <30>Dec 23 08:34:35 A4003478DE4AE30 logread[1245]: Logread connected to 172.16.xxx.200:415

    Can you try to set a static entry in the DHCP for the MAC address of the unit, as well as disable Fast Roaming if it is turned on.

    If the issue persists, enable CSC in debug mode, wait for the issue to happen stop the service and submit the csc.log, syslog.log, awed.log,  wc_remote.log and the output of  cat /content/apfw/AP55C.devinfo (ran from the advanced shell) 

    Note: To enable and disable CSC log run the following command from the advanced shell

    # csc custom debug

    Regards,

     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support Videos | Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
Reply
  • 0 in reply to LHerzog

    Hello LHerzog,

    Thank you for contacting the Sophos Community.

    I checked internally and could find  NC-78214 that sort of matches the logs you shared, but not entirely as  they differ on 

    <29>Mar 28 11:29:36 A4003478DE4AE30 aweclient[3749]: Opening log...
    <28>Mar 28 11:29:36 A4003478DE4AE30 aweclient[3749]: aweclient.c (295) Failed to connect to 0.0.0.0.
    <24>Mar 28 11:29:36 A4003478DE4AE30 procd:
    <86>Mar 28 11:29:37 A4003478DE4AE30 dropbear[2582]: Early exit: Terminated by signal
    <30>Dec 23 08:34:35 A4003478DE4AE30 logread[1245]: Logread connected to 172.16.xxx.200:415

    Can you try to set a static entry in the DHCP for the MAC address of the unit, as well as disable Fast Roaming if it is turned on.

    If the issue persists, enable CSC in debug mode, wait for the issue to happen stop the service and submit the csc.log, syslog.log, awed.log,  wc_remote.log and the output of  cat /content/apfw/AP55C.devinfo (ran from the advanced shell) 

    Note: To enable and disable CSC log run the following command from the advanced shell

    # csc custom debug

    Regards,

     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support Videos | Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
Children
  • 0 in reply to emmosophos

    Thank you ,

    yesterday we noticed a strange fact:

    when we put the switch port into a different VLAN, it gets a dynamic IP and the AP is pingable continously and the reboots stop.

    if we switch the AP back to the management VLAN, where we have DHCP MAC reservation, the issue begins again immediately.

    Both VLANs are routed by the XG.

    I connected a machine with wireshark to the Mgmt VLAN to see if there is some packet flood or something strange, but is not.

    Will continue to work on this with the network guys and if all does not help, will collect the logs you mentioned.

  • 0 in reply to LHerzog

    I could narrow the issue down to happen, when a specific SSID is bound to that AP. As soon as that config is applied by the AP, it starts losing network connectivity.

    I have 3 other RADIUS SSID applied to the AP successfully without a problem.

    The AP is getting problems regardless of the following SSID is applied as the only (single) SSID or in combination with other SSID. As soon as it is applied, the AP is getting problems.

    This is the problematic SSID:

    The VLAN 15 is applied to the Switchport.

    <29>Mar 29 11:34:43 A40034C39287DD6 netifd: Interface 'lan15' is now up
    <6>Mar 29 11:34:45 A40034C39287DD6 kernel: [ 3850.330000] br-lan15: port 1(br-lan.15) entered forwarding state
    #-> here the first ping timeout occoured <-#

    So as soon as br-lan15 is enabled, it has no stable connect to the firewall anymore.

    FAIL:
<29>Mar 29 11:34:39 A40034C39287DD6 add_radio_mapping.sh: AP55C detected: Using on-the-fly ACS procedure
<6>Mar 29 11:34:39 A40034C39287DD6 kernel: [ 3844.360000] device wlan8 left promiscuous mode
<6>Mar 29 11:34:39 A40034C39287DD6 kernel: [ 3844.360000] br-lan3006: port 2(wlan8) entered disabled state
<29>Mar 29 11:34:40 A40034C39287DD6 netifd: Network device 'wlan8' link is down
<29>Mar 29 11:34:43 A40034C39287DD6 netifd: VLAN 'br-lan.15' link is up
<6>Mar 29 11:34:43 A40034C39287DD6 kernel: [ 3848.320000] device br-lan.15 entered promiscuous mode
<6>Mar 29 11:34:43 A40034C39287DD6 kernel: [ 3848.320000] br-lan15: port 1(br-lan.15) entered forwarding state
<6>Mar 29 11:34:43 A40034C39287DD6 kernel: [ 3848.330000] br-lan15: port 1(br-lan.15) entered forwarding state
<29>Mar 29 11:34:43 A40034C39287DD6 netifd: Interface 'lan15' is enabled
<29>Mar 29 11:34:43 A40034C39287DD6 netifd: Bridge 'br-lan15' link is up
<29>Mar 29 11:34:43 A40034C39287DD6 netifd: Interface 'lan15' has link connectivity
<29>Mar 29 11:34:43 A40034C39287DD6 netifd: Interface 'lan15' is setting up now
<29>Mar 29 11:34:43 A40034C39287DD6 netifd: Interface 'lan15' is now up
<6>Mar 29 11:34:45 A40034C39287DD6 kernel: [ 3850.330000] br-lan15: port 1(br-lan.15) entered forwarding state
#-> here the first ping timeout occoured <-#
<29>Mar 29 11:34:55 A40034C39287DD6 netifd: radio0 (8994): ./mac80211.sh: eval: line 1: 1: not found
<29>Mar 29 11:34:56 A40034C39287DD6 netifd: radio1 (9013): ./mac80211.sh: eval: line 1: 1: not found
...
<29>Mar 29 11:35:17 A40034C39287DD6 netifd: Network device 'wlan11' link is up
<6>Mar 29 11:35:18 A40034C39287DD6 kernel: [ 3881.930000] br-lan254: port 4(wlan9) entered forwarding state
<6>Mar 29 11:35:18 A40034C39287DD6 kernel: [ 3882.000000] br-lan254: port 5(wlan10) entered forwarding state
<6>Mar 29 11:35:19 A40034C39287DD6 kernel: [ 3883.750000] br-lan15: port 3(wlan11) entered forwarding state
<27>Mar 29 11:35:45 A40034C39287DD6 aweclient[1198]: aweclient.c (2122) No reply get from last message, close socket.
<28>Mar 29 11:35:45 A40034C39287DD6 aweclient[1198]: aweclient.c (295) Failed to connect to 0.0.0.0.
<27>Mar 29 11:36:03 A40034C39287DD6 aweclient[1198]: aweclient.c (2122) No reply get from last message, close socket.
<28>Mar 29 11:36:03 A40034C39287DD6 aweclient[1198]: aweclient.c (295) Failed to connect to 0.0.0.0.
<29>Mar 29 11:36:07 A40034C39287DD6 aweclient[1198]: aweclient.c (2107) Reconfiguration required. need_reconf = 1
<29>Mar 29 11:36:07 A40034C39287DD6 aweclient[1198]: aweclient.c (2559) Exit from main loop with no error. Get new configuration.





OK:
<29>Mar 29 11:32:56 A40034C39287DD6 add_radio_mapping.sh: AP55C detected: Using on-the-fly ACS procedure
<29>Mar 29 11:32:59 A40034C39287DD6 netifd: VLAN 'br-lan.3006' link is up
<6>Mar 29 11:32:59 A40034C39287DD6 kernel: [ 3743.100000] device br-lan.3006 entered promiscuous mode
<6>Mar 29 11:32:59 A40034C39287DD6 kernel: [ 3743.100000] br-lan3006: port 1(br-lan.3006) entered forwarding state
<6>Mar 29 11:32:59 A40034C39287DD6 kernel: [ 3743.110000] br-lan3006: port 1(br-lan.3006) entered forwarding state
<29>Mar 29 11:32:59 A40034C39287DD6 netifd: Interface 'lan3006' is enabled
<29>Mar 29 11:32:59 A40034C39287DD6 netifd: Bridge 'br-lan3006' link is up
<29>Mar 29 11:32:59 A40034C39287DD6 netifd: Interface 'lan3006' has link connectivity
<29>Mar 29 11:32:59 A40034C39287DD6 netifd: Interface 'lan3006' is setting up now
<29>Mar 29 11:32:59 A40034C39287DD6 netifd: Interface 'lan3006' is now up
<6>Mar 29 11:33:01 A40034C39287DD6 kernel: [ 3745.110000] br-lan3006: port 1(br-lan.3006) entered forwarding state
<29>Mar 29 11:33:06 A40034C39287DD6 netifd: radio0 (7309): ./mac80211.sh: eval: line 1: 1: not found
<29>Mar 29 11:33:06 A40034C39287DD6 netifd: radio1 (7326): ./mac80211.sh: eval: line 1: 1: not found

    Support Case: 05085796

Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?