Frequent Disconnections in Network Using Deco X95 in AP Mode
Operating the main Deco X95 in AP mode, connected via wired LAN under the router, in a network with 9 other Deco units, the main Deco disconnects from the network about once or twice every few days. When this happens, a red light is displayed. After a few minutes, the light turns green, and the network connection is restored.
Logs:
Thu May 9 13:59:53 2024 daemon.err mcsd: ENTER mcManagerMCReadBufCB
Thu May 9 13:59:53 2024 daemon.err mcsd: Get netlink MSG 100 size 52 from br-lan
Thu May 9 13:59:53 2024 daemon.err mcsd: mcManagerMCReadBufCB: Receive mdb updated event from br-lan
Thu May 9 13:59:53 2024 daemon.err mcsd: ENTER mcManagerMCReadBufCB
Thu May 9 13:59:53 2024 daemon.err mcsd: ENTER mcManagerMCReadBufCB
Thu May 9 13:59:53 2024 daemon.err mcsd: Get netlink MSG 17 size 6708 from br-lan
Thu May 9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 0 - F4:39:09:1B:A9:FB, add it to flood table
Thu May 9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 0, update forwarding table
Thu May 9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 1 - E4:54:E8:DA:90:FF, add it to flood table
Thu May 9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 1, update forwarding table
Thu May 9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 2 - B0:22:7A:23:93:EC, add it to flood table
Thu May 9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 2, update forwarding table
Thu May 9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 3 - 20:C1:9B:03:F2:D2, add it to flood table
Thu May 9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 3, update forwarding table
Thu May 9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 4 - B0:7D:64:5E:91:33, add it to flood table
Thu May 9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 4, update forwarding table
Thu May 9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Interface eth2's forwarding table is changed
Thu May 9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Updated interface eth2 forwarding table successfully
Thu May 9 13:59:53 2024 daemon.err mcsd: ENTER mcManagerMCReadBufCB
Thu May 9 13:59:54 2024 daemon.err nrd[19095]: bcm_get_fdb_dst failed
Thu May 9 13:59:54 2024 daemon.err nrd[19095]: bcm_get_fdb_dst failed
Thu May 9 13:59:58 2024 daemon.err nrd[19095]: triggerMonSteering: Failed to get uplink rssi for 52:67:D3:0E:2F:0E
Thu May 9 13:59:58 2024 daemon.err nrd[19095]: triggerMonSteering: Failed to get uplink rssi for 9E:5D:82:9D:48:66
Thu May 9 14:00:06 2024 daemon.err client_mgmt: can not parse json_obj
Thu May 9 14:00:06 2024 daemon.err client_mgmt: update_history_wire_type:exit failed.
Thu May 9 14:00:06 2024 daemon.err client_mgmt: update /tmp/client_mgmt/history_wire_type failed, offline client type recognization of link priority will be influenced.
Thu May 9 14:00:10 2024 daemon.err nrd[19095]: _bcm_wlanifBSteerEventsHandleRRMReportInd: 11k handle regclass=128 channel=36, channelId=(36)24
Thu May 9 14:00:10 2024 daemon.err nrd[19095]: _bcm_wlanifBSteerEventsHandleRRMReportInd: 11k handle regclass=129 channel=36, channelId=(36)24
Thu May 9 14:00:10 2024 daemon.err nrd[19095]: _bcm_wlanifBSteerEventsHandleRRMReportInd: 11k handle regclass=129 channel=36, channelId=(36)24
Thu May 9 14:00:10 2024 daemon.err nrd[19095]: _bcm_wlanifBSteerEventsHandleRRMReportInd: 11k handle regclass=129 channel=36, channelId=(36)24
Thu May 9 14:00:10 2024 daemon.err nrd[19095]: _bcm_wlanifBSteerEventsHandleRRMReportInd: Beacon report too much
Thu May 9 14:00:10 2024 daemon.err nrd[19095]: steeralgFindBestAPCallback: iterate BSS APId 9 ChanId 2 ESSId 0 targetBand(0) != measuredBss->band(1)
Thu May 9 14:00:11 2024 user.err smartip: [lan] !!ip addr del!! ip addr del 192.168.0.81 dev br-lan
Thu May 9 14:00:11 2024 daemon.err udhcpc[9160]: Received SIGTERM
Thu May 9 14:00:12 2024 daemon.err udhcpc[23820]: udhcpc (v1.22.1) started
Thu May 9 14:00:12 2024 daemon.err udhcpc[23820]: Sending discover...
Thu May 9 14:00:12 2024 daemon.err udhcpc[23820]: Sending select for 192.168.0.81...
Thu May 9 14:00:13 2024 user.emerg logx: tp217,505[23909]:
Thu May 9 14:00:14 2024 daemon.err nrd[19095]: bcm_get_fdb_dst failed
Thu May 9 14:00:14 2024 daemon.err nrd[19095]: bcm_get_fdb_dst failed
Thu May 9 14:00:16 2024 daemon.err nrd[19095]: triggerMonSteering: Failed to get uplink rssi for 52:67:D3:0E:2F:0E
Thu May 9 14:00:24 2024 daemon.err client_mgmt: can not parse json_obj
Thu May 9 14:00:24 2024 daemon.err client_mgmt: update_history_wire_type:exit failed.
Thu May 9 14:00:24 2024 daemon.err client_mgmt: update /tmp/client_mgmt/history_wire_type failed, offline client type recognization of link priority will be influenced.
Thu May 9 14:00:39 2024 daemon.err nrd[19095]: _bcm_wlanifBSteerEventsHandleRRMReportInd: error mode: 4
Thu May 9 14:00:39 2024 daemon.err nrd[19095]: estimatorCmnHandleBeaconReportEvent: Invalid beacon report for 52:67:D3:0E:2F:0E
Thu May 9 14:00:42 2024 daemon.err client_mgmt: can not parse json_obj
Thu May 9 14:00:42 2024 daemon.err client_mgmt: update_history_wire_type:exit failed.
Thu May 9 14:00:42 2024 daemon.err client_mgmt: update /tmp/client_mgmt/history_wire_type failed, offline client type recognization of link priority will be influenced.
Thu May 9 14:00:45 2024 daemon.err nrd[19095]: triggerMonSteering: Failed to get uplink rssi for 52:67:D3:0E:2F:0E
Thu May 9 14:00:45 2024 daemon.err mcsd: ENTER mcManagerMCReadBufCB
Thu May 9 14:00:45 2024 daemon.err mcsd: Get netlink MSG 100 size 52 from br-lan
I suspect there might be an issue with the log at 14:00:11.