DECO M9PLUSV2 loss of network problem
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
There is something strange going on with my network setup and I am wondering if any of you can help figure it out.
There's currently 9 deco units, all m9 plus v2, in use. Set up in AP mode with some connected via ethernet, and others via a wireless link.
Sometimes, the main deco loses internet connectivity. Unplugging the network cable and plugging it back in restores it.
the messages in the log haven't pointed me towards a cause, but they do report an error.
Sun May 14 13:03:56 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:03:56 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:03:56 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:03:56 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:03:57 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:03:57 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath1] in eth_ifname
Sun May 14 13:03:58 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:03:58 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:03:58 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:03:58 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:03:58 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:03:58 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:03:59 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:03:59 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:00 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:00 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:00 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:00 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:00 2023 user.err csrMeshGw[5373]:
CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff
Sun May 14 13:04:00 2023 user.err csrMeshGw[5373]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2
Sun May 14 13:04:00 2023 user.err csrMeshGw[5373]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30
Sun May 14 13:04:00 2023 user.err csrMeshGw[5373]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30
Sun May 14 13:04:00 2023 user.err csrMeshGw[5373]:
CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!
Sun May 14 13:04:00 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:01 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:01 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:01 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:01 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:02 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:02 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:02 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:03 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath1] in eth_ifname
Sun May 14 13:04:03 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:03 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:03 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:03 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:04 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath1] in eth_ifname
Sun May 14 13:04:04 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:05 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:05 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:05 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath1] in eth_ifname
Sun May 14 13:04:06 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:06 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:07 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath1] in eth_ifname
Sun May 14 13:04:08 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:08 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:08 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:10 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Sun May 14 13:04:10 2023 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1424: Error: can't find ifname[ath22.1] in eth_ifname
Does this make sense to anyone ?
Hi, is your current network layout like this；
I think there might be too many Decos and recently, due to the previous troubleshooting experience, it is suggested to have no more than 6 Decos especially when most of them are on wireless Backhaul: How many Deco units can I add to my Deco mesh network? Maybe you could try to reduce the numbers of wireless Backhaul Deco M9 nodes.
And when the main Deco turned red, could you please try to unplug powerline adapters from the network to see whether the main Deco could turn back to green?
Thank you very much.
Best regards.
@David-TP Yes, the way you depicted it was how I described it.
That setup was unstable somehow with the main deco losing internet access.
Now the setup has changed.
Now it is
bbox
- main deco - zyxel
on the zyxel the powerline is connected and some other house hold computers and one sattelite deco
on the other end of the powerline, the setup has remained the same with two decos connected to the powerline and one computer and one wireless deco.
to the main deco 4 more satellite decos are wirelessly connected.
This setup has been stable for several days now, ie no long term intermittent loss of internet access to the deco.
