Firmware: Merlin 386.11
Equipment: RT-AC88U, RT-AC68U, RTAC66U B1 (daisy chained, aimesh w ethernet backhaul)
Forgive me if this is the wrong topic to post in! I'm very new to home networking, despite having created a complicated setup.
I've been using GPT-4 to help me troubleshoot this issue.
I live in a 2 floor apartment and have 3 diasy-chained hardwired asus routers.
Wired to the ONT is a router with IP 192.168.1.1 that I'll call .1/Bedroom/88U
That leads to router 192.168.1.68, which I'll call .68/Basement/68U.
Then back upstairs to a guest room which needs its own router because of the materials of the walls (Guestroom/686U, not part of this question).
They're set up as aimesh nodes but I tether most of my devices to each router because most are stationary, and because I experience a lot of stability issues.
I run a lot of smarthome devices (total. of about 80 wireless clients connected at a given time), so I set it up this way. Most of them use 2.4ghz.
I often experience authentication issues with the basement router, #2 in the chain.
Devices tethered to that router drop off. My smartphone becomes unable to authenticate on the 2.4ghz SSID (even with correct password) and it takes a reboot of the router to fix this. I imagine this is also happening with the smart devices drooping off.
At the advice of GPT4, I ssh'd into the router and read the logs.
This error keeps coming up:
I understand this to mean that the .68/Basement/68U Router can't get its hostname (RT-AC68U-E938) because it's already assigned to .1/Bedroom/88U in that router's /hosts file.
The router claiming this hostname is an 88U and should not be claiming it!
I've used ssh to edit /etc/hosts on .1/Bedroom/88U to remove that line and it seems to add itself back.
at GPT4's suggestion I used JFFS on .1/Bedroom/88U to create a new host file and redirect it, but the log still shows this error, which makes sense because /etc/hosts is still regenerating the line.
Is this something I can intervene with? Is this a product of aimesh/merlin?
Is there a script I can use to rewrite /etc/hosts regularly instead of just redirecting?
Finally (not totally urgent), I also get a lot of log messages beginning with this:
(and then some action)
Any advice (even if i'm just meant to most this somewhere else) would be deeply appreciated. I really want to improve my stability, and I'm hoping I don't have to switch them all to APs (although I'm open to it).
Equipment: RT-AC88U, RT-AC68U, RTAC66U B1 (daisy chained, aimesh w ethernet backhaul)
Forgive me if this is the wrong topic to post in! I'm very new to home networking, despite having created a complicated setup.
I've been using GPT-4 to help me troubleshoot this issue.
I live in a 2 floor apartment and have 3 diasy-chained hardwired asus routers.
Wired to the ONT is a router with IP 192.168.1.1 that I'll call .1/Bedroom/88U
That leads to router 192.168.1.68, which I'll call .68/Basement/68U.
Then back upstairs to a guest room which needs its own router because of the materials of the walls (Guestroom/686U, not part of this question).
They're set up as aimesh nodes but I tether most of my devices to each router because most are stationary, and because I experience a lot of stability issues.
I run a lot of smarthome devices (total. of about 80 wireless clients connected at a given time), so I set it up this way. Most of them use 2.4ghz.
I often experience authentication issues with the basement router, #2 in the chain.
Devices tethered to that router drop off. My smartphone becomes unable to authenticate on the 2.4ghz SSID (even with correct password) and it takes a reboot of the router to fix this. I imagine this is also happening with the smart devices drooping off.
At the advice of GPT4, I ssh'd into the router and read the logs.
This error keeps coming up:
Code:
dnsmasq-dhcp[1447]: not giving name RT-AC68U-E938 to the DHCP lease of 192.168.1.68 because the name exists in /etc/hosts with address 192.168.1.1
I understand this to mean that the .68/Basement/68U Router can't get its hostname (RT-AC68U-E938) because it's already assigned to .1/Bedroom/88U in that router's /hosts file.
The router claiming this hostname is an 88U and should not be claiming it!
I've used ssh to edit /etc/hosts on .1/Bedroom/88U to remove that line and it seems to add itself back.
at GPT4's suggestion I used JFFS on .1/Bedroom/88U to create a new host file and redirect it, but the log still shows this error, which makes sense because /etc/hosts is still regenerating the line.
Is this something I can intervene with? Is this a product of aimesh/merlin?
Is there a script I can use to rewrite /etc/hosts regularly instead of just redirecting?
Finally (not totally urgent), I also get a lot of log messages beginning with this:
Code:
kernel: 24:F5:A2:98:FC:EF not mesh client, can't
Any advice (even if i'm just meant to most this somewhere else) would be deeply appreciated. I really want to improve my stability, and I'm hoping I don't have to switch them all to APs (although I'm open to it).