Guest WiFi Pro on GT-AX11000 Pro & RT-AX88U Mesh System

[rush_ad]

My home network consists of the following under let's call it SSID "MAIN"
1) Primary Router GT-AX111000 Pro (latest firmware 3.0.0.6.102.34735)
2) Second RT-AX88U (original, not Pro on firmware 3.0.0.4.388_24221)... this is setup as AIMesh Node
3) Distant MOCA access point using Verizon FiOS Quantum Gateway... this is very old but still functional

My Goal is to create the following using Guest Network Pro setting area
1) Guest WiFi SSID for home... let's call it "Home"
2) VPN WiFi SSID... let's call it "VPN"

I am able to create both of the Guest SSID profiles without any errors... but it appears that my Mesh system does not broadcast the new guest SSID "Home" and "VPN." However everything works as intended under "MAIN" SSID.
I've tried searching for the SSID on several phones, computers, but no luck.

My suspicion is that I am mixing AIMesh with different firmware 3.0.0.6 and 3.0.0.4... but can't say for sure.

Any thought or help to figure out how to achieve desired results?

 

[junior120872]

I ran into this problem with my be96u router with 3 ET12 aimesh nodes as well. The guest network vlans will NOT propogate from asuswrt 5 to asuswrt 4. I ended up having to put the beta version of 9.0.0.6.102 on my ET12's until the asuswrt 5 comes out for them.

 

[bbunge]

My home network consists of the following under let's call it SSID "MAIN"
1) Primary Router GT-AX111000 Pro (latest firmware 3.0.0.6.102.34735)
2) Second RT-AX88U (original, not Pro on firmware 3.0.0.4.388_24221)... this is setup as AIMesh Node
3) Distant MOCA access point using Verizon FiOS Quantum Gateway... this is very old but still functional

My Goal is to create the following using Guest Network Pro setting area
1) Guest WiFi SSID for home... let's call it "Home"
2) VPN WiFi SSID... let's call it "VPN"

I am able to create both of the Guest SSID profiles without any errors... but it appears that my Mesh system does not broadcast the new guest SSID "Home" and "VPN." However everything works as intended under "MAIN" SSID.
I've tried searching for the SSID on several phones, computers, but no luck.

My suspicion is that I am mixing AIMesh with different firmware 3.0.0.6 and 3.0.0.4... but can't say for sure.

Any thought or help to figure out how to achieve desired results?

Did you enable the AiMesh under the Guest Network Pro/(profile Name)?

 

[jksmurf]

I ran into this problem with my be96u router with 3 ET12 aimesh nodes as well. The guest network vlans will NOT propogate from asuswrt 5 to asuswrt 4. I ended up having to put the beta version of 9.0.0.6.102 on my ET12's until the asuswrt 5 comes out for them.

Apologies for reposting my response from another thread but on reading this my sentiments onAIMesh remain the same i.e.

You really have to wonder if Asus have lost the plot with the implementation of the AIMesh system, first it only propagated one Guest Network (GN1) to nodes (in addition to the main network), then with the GN Pro FW it made VLANs but it was never formally clear if this version worked with non-Pro nodes, although there were reports from a number of folks (including senior forum members, refer posts in this thread post #15, post #19 and post #35) who confirmed it was, and now they are making (baking?) a whole new FW system (yes I’ve seen RMerlin’s note in another thread)… hmmm .

 

[rush_ad]

Did you enable the AiMesh under the Guest Network Pro/(profile Name)?

Yes it is enabled.

It's weird that all setting and setup steps go without any issues.

Guess Wi-Fi even looks enabled within the settings.

But actual wifi broadcast isn't on...meaning no signals with guest wifi SSID.

 

[rush_ad]

I ran into this problem with my be96u router with 3 ET12 aimesh nodes as well. The guest network vlans will NOT propogate from asuswrt 5 to asuswrt 4. I ended up having to put the beta version of 9.0.0.6.102 on my ET12's until the asuswrt 5 comes out for them.

Ahhh I see. Similar to what I suspected earlier.

I don't believe beta firmware is available on AX88U, so this suggestion won't work for me

 

[Tech9]

I'm highly in doubt we'll ever see an official AiMesh features compatibility list from Asus. The marketing is okay with AiMesh Compatible on everything. This is called "False or Misleading Representations and Deceptive Marketing Practices", unfortunately wide spread and no actions are taken against it even though it's illegal in many countries.

According to Asus here:

What is AiMesh and AiMesh Router | ASUS

AiMesh lets you mix different routers to create whole home mesh WiFi system for for fast and stable WiFi. Learn more about AiMesh vs mesh, and how to set up AiMesh.

www.asus.com

"All devices in an AiMesh network enjoy access to all the features of the main router..."

@rush_ad - ""Running an AiMesh network is truly hassle-free."

 

[rush_ad]

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.

 

[junior120872]

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.

Does your guest network and main network use the same DHCP scheme? I was seeing guest network connecting to the right SSID, but not pulling the assigned IP address for the guest network.

 

[rush_ad]

Does your guest network and main network use the same DHCP scheme? I was seeing guest network connecting to the right SSID, but not pulling the assigned IP address for the guest network.

I'm not sure what you mean by same DHCP scheme

But I can say that Guest network picked up a local IP that I was able to recognize

 

[junior120872]

I'm not sure what you mean by same DHCP scheme

But I can say that Guest network picked up a local IP that I was able to recognize

If it was on the same DHCP scope as the main network. I wasn't able to use a different DHCP scope on my guest network.

 

[bennor]

I'm not sure what you mean by same DHCP scheme

Does your Guest Network Pro entry have the option Use same subnet as main network enabled? If that option is enabled, the Guest Network Pro client on that preset will use an IP address from the main network's DHCP IP address pool. See attached example.

 

[junior120872]

Okay. If you're use case shares the subnet I see that working fine. I segregate my IoT and guest networks for security reasons etc. Glad it's working for you the way you want it!!! Cheers!

 

[routerq]

Q) What is the advantage / disadvantage of using the setting "Use same subnet as main network"?

 

[bennor]

@routerq As explained above; when you enable Use same subnet as main network, the Guest Network Pro clients (on that GNP preset entry) will receive an IP address from the main LAN IP address pool. This means the Guest Network Pro client should be able to pull a manual IP address defined in the LAN > DHCP Server page.

As others have found out, the Guest Network Pro feature has some issues. For example when you enable Use same subnet as main network, the Access Intranet Guest Network Pro feature seems to be broken. Meaning the feature doesn't block Guest Network Pro clients from the main network if you disable the Access Intranet setting while Use same subnet as main network is enabled (at least it doesn't work on my RT-AX86U Pro).

Edit to add: This is what Asus says about the Use same subnet as main network option.

[Guest Network Pro] How to set up IoT Network? | Official Support | ASUS USA

3. When setting up your IoT Network, the [Use same subnet as main network] option is enabled by default for seamless connectivity and easy device control. For enhanced security, disable this feature to create a dedicated IoT Network. This adds a layer of protection, ensuring your devices operate securely, providing peace of mind and robust network integrity.

*Enabling [Use same subnet as main network] restricts configuring DHCP server, LAN IP, subnet mask, VLAN ID, and DNS server.

 

[routerq]

@routerq As explained above; when you enable Use same subnet as main network, the Guest Network Pro clients (on that GNP preset entry) will receive an IP address from the main LAN IP address pool. This means the Guest Network Pro client should be able to pull a manual IP address defined in the LAN > DHCP Server page.

As others have found out, the Guest Network Pro feature has some issues. For example when you enable Use same subnet as main network, the Access Intranet Guest Network Pro feature seems to be broken. Meaning the feature doesn't block Guest Network Pro clients from the main network if you disable the Access Intranet setting while Use same subnet as main network is enabled (at least it doesn't work on my RT-AX86U Pro).

Edit to add: This is what Asus says about the Use same subnet as main network option.

[Guest Network Pro] How to set up IoT Network? | Official Support | ASUS USA

Thanks, @bennor. With my own experimentation and frustration, I know that the Guest SDN is a very broken / half baked feature and it should not have been released in this state. When I raised a ticket with Asu, they ha dno answer only info was, we may get a FW update in March, so you wait and watch.

I just found out that when you use a Guest SDN with "Use same subnet as main network" enabled, the block internet feature from the App works. Web GUI still no way to block.

Ref: https://www.snbforums.com/threads/q...settings-for-access-control.93187/post-944558

But my question was more from a general perspective. If the IP range of devices of SDN is same as main network, what it he purpose.

Suppose I set up my Guest SDN with the setting enabled and Access Intranet & AP Isolated enabled, what could be the purpose of such network? For all practical purpose I see this Guest SDN as isolated with only the devices having same IP range as Main network?