So recently I started using AiMesh, and having a few weird issues.
1. Logs like this,
Feb 17 11:57:08 kernel: 192.168.1.1 already exist in UDB, can't add it
Feb 17 11:57:08 kernel: 192.168.1.119 already exist in UDB, can't add it
Feb 17 11:57:08 kernel: 192.168.1.1 already exist in UDB, can't add it
Feb 17 11:57:11 kernel: 192.168.1.119 already exist in UDB, can't add it
Feb 17 11:57:11 kernel: 192.168.1.1 already exist in UDB, can't add it
192.168.1.1 is my routers main IP...... so thats extra confusing. And 192.168.1.119 is not even connected...
Now I have a few clients which for some reason constantly spam the log and then I notice they're connecting to the GT-AC5300 main router, which is on another floor than the device which is sitting RIGHT next to the AX55 AiMesh node! Seems to be only 3 devices out of the 40 thankfully. I do bind the clients to an AP when I can.
And a issue that can only be reproduced after about a week is packet loss on the AiMesh node which is fixed by a reboot annoying. The mesh node is wired.
1. Logs like this,
Feb 17 11:57:08 kernel: 192.168.1.1 already exist in UDB, can't add it
Feb 17 11:57:08 kernel: 192.168.1.119 already exist in UDB, can't add it
Feb 17 11:57:08 kernel: 192.168.1.1 already exist in UDB, can't add it
Feb 17 11:57:11 kernel: 192.168.1.119 already exist in UDB, can't add it
Feb 17 11:57:11 kernel: 192.168.1.1 already exist in UDB, can't add it
192.168.1.1 is my routers main IP...... so thats extra confusing. And 192.168.1.119 is not even connected...
Now I have a few clients which for some reason constantly spam the log and then I notice they're connecting to the GT-AC5300 main router, which is on another floor than the device which is sitting RIGHT next to the AX55 AiMesh node! Seems to be only 3 devices out of the 40 thankfully. I do bind the clients to an AP when I can.
And a issue that can only be reproduced after about a week is packet loss on the AiMesh node which is fixed by a reboot annoying. The mesh node is wired.
