Client List on RT-AX88U Pro incorrectly showing a VLAN Device on the Primary Network; incorrectly showing Static device as DHCP

[jksmurf]

I appreciate this has been discussed many, many times before, I am aware of the prior posts, so to be clear this is not a request for fixing it.

RMerlin has repeatedly stated this Client List is closed source and he cannot fix it (I am running Merlin FW 3006.102.4_alpha2), hence posting in this forum and not Asus-Merlin. I believe it is also a generic issue and not just Wifi 5/6/7 related.

Pre-empting @Tech9 's response I have already sent the issue to ASUS Support with the same screenshots (I do not expect much to happen there), but was hoping to see if others were similarly affllicted with the same issues I am seeing i.e. with similar configurations of AIMesh Nodes, for example.

The two issues I am seeing are these:

1. Referring to the client list accessible from 'Network Map', 'View List', I am seeing devices I have assigned to VLAN 53 'SmurfIoT' (Manually Assigned addresses e.g. 192.168.53.109) AND that have attached themselves to a mesh node, show up (incorrectly) in the client list of the Primary LAN (SmurfNET) which is my 192.168.9.x subnet. Conversely, VLAN Clients that latch on to the Primary Router Wi-Fi appear to list themselves correctly. I also see that any time a device on the IoT Subnet (VLAN 53) moves from being attached the Primary to the AIMesh Node, it moves from SmurfIoT to the incorrect SmurfNET list, hence it appears to be a Node or AIMesh related issue.
2. A second issue with that list is that some (mainly wired) clients show up as DHCP, however these have ALSO been Manually Assigned a Static IP Address, so I consider this behaviour to also be incorrect. See example for AppleTV4KEth on 192.168.53.16 (note I have a separate entry for the Wireless MAC).

k.

 

[Tech9]

I am running Merlin FW 3006.102.4_alpha2

Pre-empting @Tech9 's response I have already sent the issue to ASUS Support

Asus Support has nothing to do with your Asuswrt-Merlin alpha firmware. Closed source component involvement doesn't exactly mean the observed behavior is the same in Asuswrt and Asuswrt-Merlin.

 

[jksmurf]

Asus Support has nothing to do with your Asuswrt-Merlin alpha firmware. Closed source component involvement doesn't exactly mean the observed behavior is the same in Asuswrt and Asuswrt-Merlin.

And that's why I have asked if anyone else is seeing this, with either firmware; hence posting in this general forum as clearly stated above.
The previous complaints about the client list are not limited to Asusrt-Merlin firmware. Only ASUS can fix it.

 

[Tech9]

Have patience. You are running unsupported Asuswrt-Merlin firmware intended for testing purposes only based on a some work-in-progress GPL upstream that may or may not be used for an official Asuswrt release. Fixing things is at the beginning of the process.

 

[jksmurf]

Have patience. You are running unsupported Asuswrt-Merlin firmware intended for testing purposes only based on a some work-in-progress GPL upstream that may or may not be used for an official Asuswrt release. Fixing things is at the beginning of the process.

Lol, I am sure that the folks who have been waiting for the issue that has been "...known about and discussed for years" as Colin so succintly put it in May 2021 and has still not been addresed in the interim, have been very, very patient.

I am pretty sure if I downloaded the official firmware for my Router and configured GNP the exact same way and DHCP (Primary and VLANs) Manual Assignments the exact same way (and I am not going to test it out to prove a point) the same issue would be evident. I might be wrong. who knows, maybe one day when I get time (and I can load both Primary and Guest VLAN DHCPs back more easily) I will test it out.

 

[Tech9]

Client List indeed had issues forever in flat network design. With the addition of VLANs running separate DHCP servers the challenge is even bigger. This GNP you are seeing now is going away after 3006 37xxx update, in case AX-class devices get there. Whatever you are testing may be just temporary transitional situation. You have a lot more testing, reboots and resets ahead of you...

 

[junior120872]

GNP only works on 3.0.0.6.102_x firmware. I’m sure the fact you’re running 3.0.0.4 on your ax3000 is causing some issues.

 

[jksmurf]

GNP only works on 3.0.0.6.102_x firmware. I’m sure the fact you’re running 3.0.0.4 on your ax3000 is causing some issues.

Possibly, but in my view ASUS permitting Nodes with 3004 Codebase, just with a message that there are limitations on Wifi interfaces for that node, suggest older Architecture should be supported and should work.

 

[bennor]

Possibly, but in my view ASUS permitting Nodes with 3004 Codebase, just with a message that there are limitations on Wifi interfaces for that node, suggest older Architecture should be supported and should work.

Asus support apparently indicates the following (in bold).

[Wireless Router] How to set up Guest Network features to Sync to AiMesh node? | Official Support | ASUS Global

2. This feature can only be configured on the AiMesh router. Guest network is currently designed to allow the first set of each band (2.4G, 5G, 5G-1) available to the AiMesh node. Only one set is available for each band.

If I remember right there was an other lengthy discussion in this same subforum a while back on trying to get 3006 Guest Network Pro features on the main router to flow down stream to AiMesh 3004.x firmware non Guest Network Pro routers and the results were mixed.

 

[bennor]

From a earlier discussion on 3006 main router and 3004 aimesh node. The OP of that thread indicated the following:
https://www.snbforums.com/threads/g...0-pro-rt-ax88u-mesh-system.93781/#post-944457

Well I seem to have solved the problem...sharing in case someone might find it helpful.

• Removed all Guest/IoT networks, only kept the MAIN SSID
• Removed AX88U from the mesh
• Added back in a Guest network
  • This worked... I was able to see new Guest SSID broadcast and connect to it
• Added back AX88U as a Mesh node

Basically, it seems like mixing firmware somehowe doesn't allow adding Guest networks AFTER setting up all Mesh nodes.
It's better to setup main router with all necessary settings... and then add the mesh nodes.

 

[jksmurf]

If I remember right there was an other lengthy discussion in this same subforum a while back

Yes I think I saw that one, from Feb 2024 I think. It’s certainly designed to work 3006 Main/3004 Nodes and is doable with the limited “WiFi Interfaces” they refer to.

For me there’s just some odd results in the Client List. Will try to run that issue to ground sometime with the stock FW.

Ultimately 3006 nodes will be the solution but I’m happy with one one band each on a 3004 node so I’m in no rush to add a 3006 node.

 

[bennor]

For me there’s just some odd results in the Client List. Will try to run that issue to ground sometime with the stock FW.

The Network Map Client List weirdness has long been a bane to Asus router users. For what ever reason it just doesn't properly list clients some times. Users are finding that sometimes the need to use the Asus router app to configure thing rather than the router GUI to get certain things to work properly in the 3006 firmware.

 

[junior120872]

Possibly, but in my view ASUS permitting Nodes with 3004 Codebase, just with a message that there are limitations on Wifi interfaces for that node, suggest older Architecture should be supported and should work.

I was unable to get my clients to work properly on my ET12s until I reverted to the 9.0.0.6 beta on them. I don’t share the same subnet as I prefer to have a different ip scheme and separation in my IoT.

 

[bbunge]

 

[Tech9]

I was unable to get my clients to work properly on my ET12s

As per Asus official FAQ (updated Feb 2025) both products ZenWiFi Pro ET12/XT12 don't have user configurable VLAN support.

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

I also see this:

We have liftoff

Will branch 3006 arrive on it? Chances are slim to none...

www.snbforums.com

The functionality you expect to have with new firmware may actually never come to your model.

 

[junior120872]

As per Asus official FAQ (updated Feb 2025) both products ZenWiFi Pro ET12/XT12 don't have user configurable VLAN support.

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

I also see this:

We have liftoff

Will branch 3006 arrive on it? Chances are slim to none...

www.snbforums.com

The functionality you expect to have with new firmware may actually never come to your model.

It won’t in the 3.0.0.6 version, but it is in the 9.0.0.6 beta which works fine. I’m less concerned since they are all Amish nodes behind my be96u main router. I can assign vlans to ports etc now, so I may just stay with the beta till I replace the nodes down the road.

 

[Tech9]

Somewhat disappointing for such expensive hardware, but sounds like a plan. Hopefully your nodes continue working with the main router firmware updates because if they stop - this is the end of the road. Not sure why Asus marketed this hardware as Pro...

 

[junior120872]

Somewhat disappointing for such expensive hardware, but sounds like a plan. Hopefully your nodes continue working with the main router firmware updates because if they stop - this is the end of the road. Not sure why Asus marketed this hardware as Pro...

Yes. Super frustrating. Especially since I have 3 of them. I purchased the ET12’s because Asus marketed them as supporting VLANs then they pulled it at a later date. I’ve had many “words” with them to no avail. . I’ll just continue to install Merlin’s updates for the be96u till Asus breaks that compatibility then deal with it at that point.

 

[Tech9]

Ethernet infrastructure in place? Call me when you have enough...

 

[junior120872]

I don’t complain too much. My network, after a lot of reading these forums and tweaking, is super solid even with beta software on the ET12’s. 5gig fiber, 2.5g backhaul. WiFi 6e everywhere. Solid mesh with great roaming, IoT network supporting 80+ devices. It’s taken a lot of trial and error but once you get there the Asus hardware does its job! With the addition of Merlin and all the addons, diversion and Skynet etc I feel I’m in a great situation! Aside from the growing pains to get here.