Switch capabilities of AIMesh Nodes?

[Tech9]

Most likely the connection type in GUI is for Asus devices with MoCA or PLA integrated options. I've seen some sold in other countries. In your case MoCA is a transparent bridge with Ethernet end points. I would be surprised if Asuswrt is actually seeing it. Link up/down monitoring is indeed software feature, but for some unknown to me reason Asus faces challenges for years even with Dual WAN when two Ethernet links are used. Report the issue to Asus and hope for the best.

 

[Swistheater]

Does AiMesh recognize your MoCA connection at all?

View attachment 65477

Agree the backhaul has to be connection monitoring based.

moca 2.5 enabled nodes are required to see moca Aimesh setup.

 

[Tech9]

Okay... this is Asus device with built-in MoCA. Makes sense. Thanks for sharing.

 

[Swistheater]

Okay... this is Asus device with built-in MoCA. Makes sense. Thanks for sharing.

It works really well. But I caution in pairing the ASUS MoCA nodes, ensuring the right band range is essential otherwise pairing can be a daunting task even for the most technical savvy.

 

[Tech9]

This confirms MoCA icon for connection in GUI works with integrated adapters only, but the real issue experienced by @OzarkEdge is Asuswrt failing to detect wired backhaul issues when external MoCA adapter is used with Ethernet connection to the router. This has to be fixed upstream by Asus.

 

[jksmurf]

If you haven't already seen the following Asus Support document, it may (or may not) have some information that is relevant to your questions or desires:

[Wireless Router] How to setup Guest Network Pro (SDN) across AiMesh and managed switch? | Official Support | ASUS USA

While I do have a older managed switch (Netgear GS908E), I haven't experimented with it's VLAN features or how it's VLAN feature would work with a RT-AX86U Pro's Guest Network Pro/VLAN/SDN at all. Nor have I tried playing with AiMesh nodes and VLAN, only have a couple of RT-AC68U's currently sitting around unused that could be used as AiMesh nodes.

Well I finally got around to testing my new TP-Link TL-SG105E "Easy Smart" Managed Switch with a Merlin 3006.102.4 FW Router (RT-AX88U) and a 3004.388.9_2 FW Mesh Node (RT-AX3000). It's been a bit of a nightmare day of testing, because (along with very dubious suggestions from ChatGPT, Gemini and Deepseek, all of whom I had to keep correcting as to what the FAQ actually says), I kept losing access to the Switch and to the Mesh Node.

I attach my Switch VLAN AND PVID Settings and my RT-AX88U ROUTER VLAN Settings below:

The TP-Link TL-SG105E Switch requires that VLAN 1 be assigned to all ports. Whilst the ASUS FAQ says to set Ports 3, 4 and 5 as Untagged, it does not explicitly say to set Ports 1,2 as Untagged. I tried, but could not set them as non-members; it does not allow a "Not Member" setting for any ports. They MUST either be set as be "Tagged" or "Untagged", so I set them all as Untagged, which I think is correct here (and makes no difference as they do not connect to anything anyway). Without that, the AIMesh Node connected, but kept disconnecting.

• Router Port 1 → Guest VLAN 52 (192.168.52.x) Access
• Router Port 2 → IoT VLAN 53 (192.168.53.x) Access
• Router Port 3 → ALL 3 x VLANS. Default. Cable goes to Port 5 of Switch.
• Cable from Port 4 of Switch to WAN of Node.

So, the Node works fine through a Switch, which is what the FAQ is suggesting, although note that it does refer to "selected models with Guest network pro feature", meaning BOTH the Router and the Node. Absent a 3006 Codebase (VLAN-capable) Node, the AIMesh part still works OK, however not surprisingly, devices connected to the Nodes’ LAN Ports still get assigned the VLAN 1 subnet (192.168.9.x) and not the 192.168.53.x subnet as I wanted. Assigning a MAC-bound Static IP in the main Router does nothing to change this. Any attempt to set PVID 53 simply borks the AIMesh connectivity as it (apparently) relies on the VLAN 1 backhaul for ‘Management’.

So whilst I was hoping for some hidden magic in the Node where it tagged VLAN XX Devices based on the VLAN Port Assignments in the Main Router (and I DID try the ESP32 device in each of the 4 LAN Ports of the Node), it pretty much confirms my expectation that if you want the Mesh Nodes LAN ports to Tag Devices with a specific VLAN ID:

1. If your Nodes are 3004 Codebase, you simply can not; you need to attach a managed switch to the LAN Port of the Node, configure the Switch for VLAN 53 and attach your devices to the SWITCH; and
2. [EDIT] If your Nodes are on the list of ASUS Routers that support VLANs (which are on the 3006 Codebase), you can set VLAN IDs per Port ON the Node, in the MAIN Router's VLAN Page as shown in the Screencaps above by @visortgw.** So far, it is only confirmed to work on a GT-BE98U Pro.

I started this thread thinking of the various ways 5# 3004 Codebase Mesh Nodes in 5 separate rooms could each assign an ESP32 (for Home Assistant) attached to their LAN Port, an IoT Address in my 192.168.53.x subnet. The only ways are (1) and (2) above, to the best of my knowledge.

For me (1) requires 5# (Easy) Managed Switches like the one I bought for testing, which gets kind of ugly with cables and lights everywhere (although that model does have an option to disable LEDs). I will just have to wait until I can get some small, unobtrusive (preferably internal antenna) and cheap, 3006 Codebase Nodes ** that support VLANs!

References:

• [Wireless Router] How to setup Guest Network Pro (SDN) across AiMesh and managed switch? | Official Support | ASUS USA
• [Wireless Router] What is VLAN and how to setup in ASUS Wireless Router? | Official Support | ASUS Global
• [Wireless Router] What is VLAN and how to setup in ASUS Wireless Router? | Official Support | ASUS USA

 

[visortgw]

Well I finally got around to testing my new TP-Link TL-SG105E "Easy Smart" Managed Switch with a Merlin 3006.102.4 FW Router (RT-AX88U) and a 3004.388.9_2 FW Mesh Node (RT-AX3000). It's been a bit of a nightmare day of testing, because (along with very dubious suggestions from ChatGPT, Geimini and Deepseek, all of whom I had to keep correcting as to what the FAQ actually says), I kept losing access to the Switch and to the Mesh Node.

I attach my Switch VLAN AND PVID Settings and my RT-AX88U ROUTER VLAN Settings below:

View attachment 65687View attachment 65689
View attachment 65690

Note the TP-Link Switch does not accept The TP-Link TL-SG105E requires that VLAN 1 be assigned to all ports. Whilst the ASUS FAQ says to set Ports 3, 4 and 5 as Untagged, it does not explicitly say to set Ports 1,2 as Untagged. I tried, but could not set them as non-members; it does not allow a "Not Member" setting for any ports. They MUST either be set as be "Tagged" or "Untagged", so I set them all as Untagged, which I think is correct here (and makes no difference as they do not connect to anything anyway). Without that, the AIMesh Node connected, but kept disconnecting.

• Router Port 1 → Guest VLAN 52 (192.168.52.x) Access
• Router Port 2 → IoT VLAN 53 (192.168.53.x) Access
• Router Port 3 → ALL 3 x VLANS. Default. Cable goes to Port 5 of Switch.
• Cable from Port 4 of Switch to WAN of Node.

So, the Node works fine through a Switch, which is what the FAQ is suggesting (although note that it does refer to "selected models with Guest network pro feature", meaning BOTH the Router and the Node. Absent a 3006 Codebase Node, teh AIMesh Part still works OK, however not surprisingly, devices connected to the Nodes LAN Ports still get assigned the VLAN1 Subnet (192.168.9.x) and not the 192.168.53.x subnet as I wanted. Assigning a MAC-bound Static IP in the main Router does nothing to change this. Any attempt to set PVID 53 simply borks the AIMesh connectivity as it relies on the VLAN 1 Backhaul for Management.

So whilst I was hoping for some hidden magic in the Node where it tagged VLAN XX Devices based on the VLAN Port Assignments in the Main Router (and I DID try the ESP32 device in each of the 4 LAN Ports of the Node, it pretty much confirms my expectation that if you want the Mesh Nodes LAN ports to Tag Devices with a specific VLAN ID

1. If your Nodes are 3004 Codebase, you simply can not; you need to attach a managed switch to the LAN Port of the Node, configure the Switch for VLAN 53 and attach your devices to the SWITCH; and
2. If your Nodes are 3006 Codebase, you can set VLAN IDs per Port ON the Node, in the MAIN Router's VLAN Page as shown in the Screencaps above by @visortgw.

I started this thread thinking of the various ways 5# 3004 Codebase Mesh Nodes in 5 separate rooms could each assign an ESP32 (for Home Assistant) attached to their LAN Port, an IoT Address in my 192.168.53.x subnet. The only ways are (1) and (2) above, to the best of my knowledge. For me (1) requires 5# (Easy) Managed Switches like the one I bought for Testing, which gets kind of ugly with cables and lights everywhere (although that model does have an option to disable LEDs). I will just have to wait until I can get some cheaper 3006 Codebase Nodes .

References:

[Wireless Router] How to setup Guest Network Pro (SDN) across AiMesh and managed switch? | Official Support | ASUS USA

[Wireless Router] What is VLAN and how to setup in ASUS Wireless Router? | Official Support | ASUS Global

Based upon a quick read, the first thing that I'd do is to connect router to port one of switch with all VLANs enabled as tagged, allowing all traffic to enter switch with proper tags. Use your other ports to connect to nodes with the appropriate VLAN tags as desired.

 

[jksmurf]

Based upon a quick read, the first thing that I'd do is to connect router to port one of switch with all VLANs enabled as tagged, allowing all traffic to enter switch with proper tags. Use your other ports to connect to nodes with the appropriate VLAN tags as desired.

Hmm, I'm not sure I 100% follow but I had a heck of a time keeping the Node connected just as a mesh, so your suggestion might work for an AP, but I am not sure about a Node.

EDIT: Referring to this note, I did try at one stage in my trials to plug the cable that was configured as Trunk (I’m assuming this is what you mean by all enabled and tagged) to “Port 1” (actually port 5 in ASUS FAQ example) of the Switch but then AIMesh simply refused to work.

If this is what you meant the reason could be in this statement on the VLAN Page of the Router?

 

[Seth Harman]

So whilst I was hoping for some hidden magic in the Node where it tagged VLAN XX Devices based on the VLAN Port Assignments in the Main Router (and I DID try the ESP32 device in each of the 4 LAN Ports of the Node, it pretty much confirms my expectation that if you want the Mesh Nodes LAN ports to Tag Devices with a specific VLAN ID

1. If your Nodes are 3004 Codebase, you simply can not; you need to attach a managed switch to the LAN Port of the Node, configure the Switch for VLAN 53 and attach your devices to the SWITCH; and
2. If your Nodes are 3006 Codebase, you can set VLAN IDs per Port ON the Node, in the MAIN Router's VLAN Page as shown in the Screencaps above by @visortgw.

Both my nodes are 3006 codebase and I've found no way to configure the nodes to assign VLAN IDs to devices connected to the node's physical ports; the VLAN page on the main router only shows the ports on the main router.

 

[visortgw]

Both my nodes are 3006 codebase and I've found no way to configure the nodes to assign VLAN IDs to devices connected to the node's physical ports; the VLAN page on the main router only shows the ports on the main router.

What firmware versions are currently installed on RT-AX88U Pro primary router and RT-BE58U nodes?

 

[Seth Harman]

What firmware versions are currently installed on RT-AX88U Pro primary router and RT-BE58U nodes?

RT-AX88U Pro is running Merlin 3006.102.4, both nodes are running official Asus firmware 3.0.0.6.102_37073-g3124d2d_968-gc6148_BB0B.

Edit: Not sure if it matters, but both nodes are using Ethernet backhauls.

 

[jksmurf]

Both my nodes are 3006 codebase and I've found no way to configure the nodes to assign VLAN IDs to devices connected to the node's physical ports; the VLAN page on the main router only shows the ports on the main router.

Oh; that’s a worry. Now we have to start guessing whether it’s down to the model used as the Primary Router or some other setting. Ethernet backhaul, as you stated you have, should be fine and you should have those options. I don’t have a 3006 codebase Node so we’re going to have to rely on someone that does (and can see the screens that @visortgw can, see this post earlier in the thread.

 

[visortgw]

RT-AX88U Pro is running Merlin 3006.102.4, both nodes are running official Asus firmware 3.0.0.6.102_37073-g3124d2d_968-gc6148_BB0B.

Edit: Not sure if it matters, but both nodes are using Ethernet backhauls.

Ethernet backhaul preferred. Works for me on GT-BE98 Pro..Might you try factory reset of nodes and re-pairing to primary router?

 

[Seth Harman]

Ethernet backhaul preferred. Works for me on GT-BE98 Pro..Might you try factory reset of nodes and re-pairing to primary router?

I'll give that a try when I get a chance, but both of those nodes were purchased and paired AFTER the main router was updated to 3006, so even if re-pairing fixes the problem I'd suspect there's an issue anyway since we're talking two out of two with the same issue.

Edit: Ok, factory resetting one of the nodes and re-pairing it didn't change anything.

 

[jksmurf]

I'll give that a try when I get a chance, but both of those nodes were purchased and paired AFTER the main router was updated to 3006, so even if re-pairing fixes the problem I'd suspect there's an issue anyway since we're talking two out of two with the same issue.

Edit: Ok, factory resetting one of the nodes and re-pairing it didn't change anything.

Probably not the result you wanted, but thanks for trying that all the same. I was wondering if the Wifi 7 (BE) devices had some sort of additional function over AX ones but the Merlin 3006.102.4 FW is universal for BE and AX devices so should not make any difference?

I was on the verge of looking for a cheap used RT-AX86U Pro to pair with my (local) RT-AX88U Pro but I will definitely hold off until this is ironed out. Strange one, hopefully just a VLAN setting, but we will need more VLAN/GNP details from @visortgw than is shown on his screencaps to work out if it is that.

If anyone else has a 3006-codebase Router/Mesh pair and can confirm whether or not they see the Port settings for each Node, ON the Router VLAN page, that would be very much appreciated; along with any VLAN/GNP settings that might influence that.

 

[Seth Harman]

Probably not the result you wanted, but thanks for trying that all the same. I was wondering if the Wifi 7 (BE) devices had some sort of additional function over AX ones but the Merlin 3006.102.4 FW is universal for BE and AX devices so should not make any difference?

I was on the verge of looking for a cheap used RT-AX86U Pro to pair with my (local) RT-AX88U Pro but I will definitely hold off until this is ironed out. Strange one, hopefully just a VLAN setting, but we will need more VLAN/GNP details from @visortgw than is shown on his screencaps to work out if it is that.

If anyone else has a 3006-codebase Router / Mesh pair and can confirm whether or not they see the Port settings for each Node, ON the Router VLAN page, that would be very much appreciated.

Always happy to help troubleshoot. Frankly, I didn't even know the nodes were supposed to show up on that VLAN page until I saw this thread. I've got a managed switch plugged into the node where I need VLAN tagging so I don't really miss the functionality but it's curious that it apparently isn't working as intended.

 

[visortgw]

Probably not the result you wanted, but thanks for trying that all the same. I was wondering if the Wifi 7 (BE) devices had some sort of additional function over AX ones but the Merlin 3006.102.4 FW is universal for BE and AX devices so should not make any difference?

I was on the verge of looking for a cheap used RT-AX86U Pro to pair with my (local) RT-AX88U Pro but I will definitely hold off until this is ironed out. Strange one, hopefully just a VLAN setting, but we will need more VLAN/GNP details from @visortgw than is shown on his screencaps to work out if it is that.

If anyone else has a 3006-codebase Router/Mesh pair and can confirm whether or not they see the Port settings for each Node, ON the Router VLAN page, that would be very much appreciated; along with any VLAN/GNP settings that might influence that.

Merlin 3006.102.4 is NOT completely "universal" between all devices — it is based upon at least three (3) different GPLs: originally supported WIFi 7 devices (102_37346), WiFi 6 devices (102_36521), and the most recently added GT-BE92U (102_37526).

 

[jksmurf]

Merlin 3006.102.4 is NOT completely "universal" between all devices — it is based upon at least three (3) different GPLs: originally supported WIFi 7 devices (102_37346), WiFi 6 devices (102_36521), and the most recently added GT-BE92U (102_37526).

I see, OK, thank you for clarifying that, mea culpa. So one possibility the reason you're seeing these additional VLAN screens is because the GPL for your main (BE) Router GT-BE98 Pro has that capability?

I wonder what GPL @Seth Harman has on his RT-BE58U and whether if one of them was configured as the Primary Router, whether he would then automagically see VLAN Port Screens on his AIMesh Nodes (his other two devices, if configured as Nodes), like you see on yours.

 

[visortgw]

I see, OK, thank you for clarifying that, mea culpa. So one possibility the reason you're seeing these additional VLAN screens is because the GPL for your main (BE) Router GT-BE98 Pro has that capability?

I wonder what GPL @Seth Harman has on his RT-BE58U and whether if one of them was configured as the Primary Router, whether he would then automagically see VLAN Port Screens on his AIMesh Nodes (his other two devices, if configured as Nodes), like you see on yours.

@Seth Harman's RT-BE58U nodes are running Asus baseline 3.0.0.6.102_37073-g3124d2d_968-gc6148_BB0B (from a few posts back).

 

[Seth Harman]

@Seth Harman's RT-BE58U nodes are running Asus baseline 3.0.0.6.102_37073-g3124d2d_968-gc6148_BB0B (from a few posts back).

It appears from your signature that you're running Merlin on your AiMesh nodes. I wonder if installing it on one my nodes would yield a different result.