Guest Network Pro Issues With AiMesh Node

[Jack_D]

Like a lot of others on this forum I am having issues with the Guest Network Pro when using an AiMesh Node:

RT-AX88U Pro Main Router running Merlin 3006.102.5
RT-AX86U Pro Mesh node running Merlin 3006.102.5
Connected via Ethernet Backhaul on the 2.5G ports between both routers. No switches in between.

My issue seems a little different than any others I have seen on the forum so far. I set up a custom Guest network for my IoT devices to use to segregate them from my main network (Did not use the IoT Network option). The Mesh node is broadcasting the IoT network SSIDs and clients can connect just fine. Access to main intranet is disabled, VLAN ID is set to 100, and DHCP server is set for 192.168.100.1. Clients that connect through the main router to this IoT SSID are getting correct IP's (192.168.100.X). But any clients connecting to the mesh nodes IoT SSID are getting IP's from the main LAN (192.168.1.X).

I am not super familiar with configuring and setting up VLANs so maybe there is some setting that I am missing but it seems like VLAN tagging over the backhaul is not working correctly.

 

[jksmurf]

Quick reply as short on time but have a look at this post. It’s for wired VLANs but essentially unless you have a node on that list it won’t serve up VLANs to the nodes in a wired config. You Fong mention your router, nodes or config?

Similarly for wireless nodes there are limitations on how many wireless interfaces get propagated to the nodes unless you have specific nodes on ASUS list. There’s a separate thread on that too. @visortgw and @Seth Harman will be able to add a lot more to the explanation.

The entire linked thread is long but interesting.

 

[visortgw]

Like a lot of others on this forum I am having issues with the Guest Network Pro when using an AiMesh Node:

RT-AX88U Pro Main Router running Merlin 3006.102.5
RT-AX86U Pro Mesh node running Merlin 3006.102.5
Connected via Ethernet Backhaul on the 2.5G ports between both routers. No switches in between.

My issue seems a little different than any others I have seen on the forum so far. I set up a custom Guest network for my IoT devices to use to segregate them from my main network (Did not use the IoT Network option). The Mesh node is broadcasting the IoT network SSIDs and clients can connect just fine. Access to main intranet is disabled, VLAN ID is set to 100, and DHCP server is set for 192.168.100.1. Clients that connect through the main router to this IoT SSID are getting correct IP's (192.168.100.X). But any clients connecting to the mesh nodes IoT SSID are getting IP's from the main LAN (192.168.1.X).

I am not super familiar with configuring and setting up VLANs so maybe there is some setting that I am missing but it seems like VLAN tagging over the backhaul is not working correctly.

What hardware and firmware for primary router and nodes? Are you referring to wireless or wired clients? What do you mean by "but it seems like VLAN tagging over the backhaul is not working correctly"?

 

[Jack_D]

Thanks! I'll take a look at the thread. Just a quick look at it though, my routers are both on the list: RT-AX88U Pro main router. RT-AX86U Pro mesh node Both are running the latest Merlin firmware (v3006.102.5).

The clients are all wireless IoT devices. I'll be honest I'm not entirely sure what I mean by "but it seems like VLAN tagging over the backhaul is not working correctly" This is really my first dive into using VLANs so I'm not 100% on all the terminology yet. I was doing some searching on why these clients are not getting IPs in the IoT VLAN. From what I understand, a client that connects to that SSID should get tagged to VLAN 100. It seems like the mesh node is not properly passing those tags to the main router. So the main router is seeing the client come in "untagged" and just assigning it an IP from the main LAN.

 

[visortgw]

Thanks! I'll take a look at the thread. Just a quick look at it though, my routers are both on the list: RT-AX88U Pro main router. RT-AX86U Pro mesh node Both are running the latest Merlin firmware (v3006.102.5).

The clients are all wireless IoT devices. I'll be honest I'm not entirely sure what I mean by "but it seems like VLAN tagging over the backhaul is not working correctly" This is really my first dive into using VLANs so I'm not 100% on all the terminology yet. I was doing some searching on why these clients are not getting IPs in the IoT VLAN. From what I understand, a client that connects to that SSID should get tagged to VLAN 100. It seems like the mesh node is not properly passing those tags to the main router. So the main router is seeing the client come in "untagged" and just assigning it an IP from the main LAN.

VLANs for wireless devices on AiMesh nodes are handled automatically. For your IoT network, have you enabled AiMesh connections? Go to Network tab (or Guest Network Pro, depending on primary router model), select guest network using the wrench icon, click on AiMesh (bottom of right column), select AiMesh nodes to push guest network to, and click Apply — otherwise, AiMesh nodes do not accept guest network connections.

 

[Jack_D]

VLANs for wireless devices on AiMesh nodes are handled automatically. For your IoT network, have you enabled AiMesh connections? Go to Network tab (or Guest Network Pro, depending on primary router model), select guest network using the wrench icon, click on AiMesh (bottom of right column), select AiMesh nodes to push guest network to, and click Apply — otherwise, AiMesh nodes do not accept guest network connections.

Yes, both main router and mesh node are enabled for the guest network. The mesh node is broadcasting the IoT network SSID and clients are connecting to it fine. They are just getting the wrong IP when connected to the mesh node. I attached a couple screenshots. In the client list for the guest network, the clients circled in red are connected to the guest network through the AiMesh node. You can see they have 192.168.1.X IP addresses. The other clients are connected to the main router and getting IPs assigned properly (192.168.100.X).

 

[visortgw]

Yes, both main router and mesh node are enabled for the guest network. The mesh node is broadcasting the IoT network SSID and clients are connecting to it fine. They are just getting the wrong IP when connected to the mesh node. I attached a couple screenshots. In the client list for the guest network, the clients circled in red are connected to the guest network through the AiMesh node. You can see they have 192.168.1.X IP addresses. The other clients are connected to the main router and getting IPs assigned properly (192.168.100.X).

Try removing and re-adding nodes. Something is dorked up.

 

[Jack_D]

Try removing and re-adding nodes. Something is dorked up.

Okay I removed the Mesh node from the configuration and re-added it. Things appear better so far. Only two devices have connected to the IoT network through the mesh node, but they are getting the correct IPs now. I'll keep an eye on it as other devices connect to it.

Thanks for the help!

 

[visortgw]

Okay I removed the Mesh node from the configuration and re-added it. Things appear better so far. Only two devices have connected to the IoT network through the mesh node, but they are getting the correct IPs now. I'll keep an eye on it as other devices connect to it.

Thanks for the help!

90+% of the time (from personal experience), "unexplained flakiness" in AiMesh nodes can be resolved by removing and re-adding the nodes.

 

[visortgw]

Okay I removed the Mesh node from the configuration and re-added it. Things appear better so far. Only two devices have connected to the IoT network through the mesh node, but they are getting the correct IPs now. I'll keep an eye on it as other devices connect to it.

Thanks for the help!

Nodes tend to move over time to optimize connections. And remember, the closest node to device is not always the optimal node.

 

[Jack_D]

90+% of the time (from personal experience), "unexplained flakiness" in AiMesh nodes can be resolved by removing and re-adding the nodes

When this kind of "weirdness" happens I tend to just blame solar flares...

 

[bbunge]

Try switching to a 1GB LAN port. I've had issues with the 2.5 GB port losing connection even though I have CAT 6 cable and patch cords. Same issue on Merlin or Asus firmware. FYI the AiMesh node should be on Asus firmware.

 

[Jack_D]

Try switching to a 1GB LAN port. I've had issues with the 2.5 GB port losing connection even though I have CAT 6 cable and patch cords. Same issue on Merlin or Asus firmware. FYI the AiMesh node should be on Asus firmware.

Really? So main router can be on Merlin but AiMesh should always be Asus? I had no idea.

I did try moving over to the 1 GB port for backhaul but it didn't change anything. I'm guessing it would work now that I have removed and re-added the mesh node.

 

[visortgw]

Really? So main router can be on Merlin but AiMesh should always be Asus? I had no idea.

Not necessarily true. It's more of a) personal preference and b) assessment of GPL versions that firmware is based on -- Merlin uses AiMesh code asis from Asus.

 

[visortgw]

Try switching to a 1GB LAN port. I've had issues with the 2.5 GB port losing connection even though I have CAT 6 cable and patch cords. Same issue on Merlin or Asus firmware. FYI the AiMesh node should be on Asus firmware.

Interesting... I am able to maintain stable 2.5 Gbps and 10 Gbps connections.