3006.102.5 Guest Network Pro issues in Aimesh nodes after reboot

[Southmad1977]

Im running 3006.102.5 in my RT-AX88U Pro along with 4 Aimesh node. My nodes are a combination of 3 RT-AC66U B1 (3004.386.14_2) and 1 RT-AX58U V2 (3004.388.9_2gnuton2) that had no issues with my prior version of Merlin (3006.102.4).

Since the last update (actually the following day, which then became relevant) I noticed that none of my clients were able to connect to either of my guest networs (IoT and Guest) as invalid IP configuration showed up.

As i have seen this in the past I deleted all the networks and set it again in specific nodes. All seemed to work just fine for that day, problem was again noticeable the following day, since I have a daily reboot of all my nodes @4.30AM and my router @4.31, all my system reboots in sequence.

Once the sequence happened I noticed that only the router seems to connect with the clients in the guest network (I dont have any issues in the main), but the nodes which continues to reject connection with an Invalid IP configuration (I see this in my phone). To fix this I made a dummy refresh in the Guest Network Pro (removed a node, added again) and everything was up again.

My though at this point is that the Guest Pro configuration its not been refreshed after reboot and probably some old configuration remained in the NVRAM of the nodes (Probably some VLAN changed when I reset the original configuration on the first step). This also happened after I reboot any node,

Any ideas (rather than not rebooting daily will be appreciated!)

 

[AlbumMan]

Im running 3006.102.5 in my RT-AX88U Pro along with 4 Aimesh node. My nodes are a combination of 3 RT-AC66U B1 (3004.386.14_2) and 1 RT-AX58U V2 (3004.388.9_2gnuton2) that had no issues with my prior version of Merlin (3006.102.4).

Same issue here. I did not notice it until a day after updating to 102.5. First thing I tried was rebooting the node (RT-AX3000) as that was not done when updating the main router (RT-AX86U Pro). After that did not work, I removed the node and waited awhile to add it back. Still nothing. All of my IoT devices are connected to the main router while the node is in the bedroom with lamps in the same room and other devices nearby. I can force a bind on the node but that is not a solution. The node is running 388.9_2 and did not have an issue before.

 

[Southmad1977]

Same issue here. I did not notice it until a day after updating to 102.5. First thing I tried was rebooting the node (RT-AX3000) as that was not done when updating the main router (RT-AX86U Pro). After that did not work, I removed the node and waited awhile to add it back. Still nothing. All of my IoT devices are connected to the main router while the node is in the bedroom with lamps in the same room and other devices nearby. I can force a bind on the node but that is not a solution. The node is running 388.9_2 and did not have an issue before.

Yeah.. annoying. At this point I was only able to do it with a dummy refresh. Perhaps someone knowledgeable can do a script with a cron job to refresh after each reboot cycle until get solved.

 

[bbunge]

It has been recommended time and again to run Asus firmware on the nodes. It is also noted that mismatch of firmware versions between router and AiMesh nodes can cause issues. Although the AC66U B1 is or was a super router (I have one on the shelf in reserve), using those as AiMesh nodes will reduce the capabilities of newer routers (limit bandwidth and channels of the 5 GHz). Best to use the older devices as Access Pionts.

And yes, a daily reboot is not necessary in most instances.

 

[Southmad1977]

It has been recommended time and again to run Asus firmware on the nodes. It is also noted that mismatch of firmware versions between router and AiMesh nodes can cause issues. Although the AC66U B1 is or was a super router (I have one on the shelf in reserve), using those as AiMesh nodes will reduce the capabilities of newer routers (limit bandwidth and channels of the 5 GHz). Best to use the older devices as Access Pionts.

And yes, a daily reboot is not necessary in most instances.

I don't disagree but the AX58 which is newer behaves in the same manner. Before doing that will move to the prior version of Merlin. That doesn't seemed to be an issue.

Also, rebooting or not, if I lose power Router and access point will reboot and will lost connection in all the IoT devices so definitely not a viable solution.

 

[glrush]

I am having a similar problem. I have a BE-88U as my main router with another BE-88U as a node and a AC-88U as another. With the previous Merlin build, I was able to connect the BE-88U's via MLO by simply enabling it via the GUI.
But when I updated to the latest build this week, the BE-88U node went stupid. It showed up as a node, but no clients would connect. I tried a factory reset on both BE-88U's and tried again same result: turning on MLO would make the BE-88U node go stupid; turning off MLO would not help only a factory reset of the node would work. The old warhorse AC-88U had no issues.
Currently the network is stable but with MLO turned off, but I am curious if there was a change to the firmware that could have caused this.

 

[Southmad1977]

I am having a similar problem. I have a BE-88U as my main router with another BE-88U as a node and a AC-88U as another. With the previous Merlin build, I was able to connect the BE-88U's via MLO by simply enabling it via the GUI.
But when I updated to the latest build this week, the BE-88U node went stupid. It showed up as a node, but no clients would connect. I tried a factory reset on both BE-88U's and tried again same result: turning on MLO would make the BE-88U node go stupid; turning off MLO would not help only a factory reset of the node would work. The old warhorse AC-88U had no issues.
Currently the network is stable but with MLO turned off, but I am curious if there was a change to the firmware that could have caused this.

Would recommend to downgrade for the moment. That is what made my whole network stable again.