Release ASUS ROG Rapture GT-AXE16000 Firmware version 3.0.0.6.102_36382 (2025/03/12)

[RMerlin]

Hello,
I am new to this community and came to ask a question. I upgraded the firmware on my GT-AXE16000 to this new update (3.0.0.6.102_36382). After the update finished the router rebooted and when it came back online all of my mesh nodes were not taking any clients. I have 3 ZenWiFi XD4 Plus nodes for my mesh. All the clients were connecting on the main router causing some to have extremely weak connection. Has anyone had this problem or could indicate what a possible solution would be. Calling Asus they told me to expect a call from an engineer that would research this problem but I have not heard back and I doubt I will because they said it would take at most 2 days.
Any help would be appreciated.
Thanks

If you just upgraded from a 3.0.0.4.388_* firmware, it's probably best to disconnect all AiMesh nodes, and reconnect them as new nodes.

 

[SeRf]

Thanks for the reply. Unfortunately I have already tried that. I would rather not try a factory reset if possible.

 

[mmjlmjl]

I tried this 3.0.0.6 fimrware but the cat feeder which we use showed wifi randomly disconnects and stays offline.I installed the 9.0.6 beta again, let's se if that resolves my issue.

 

[af82]

5.To enhance software functionality, we have implemented architectural changes. As a result, some settings will require manual reconfiguration:

One of the big 'architectural changes' that prevents me from upgrading is they always used tagged vlans 501+ for guest networks. I have these configured in my managed switches to get over to the AI mesh node(s). I also use these VLANs as wired guest not wireless guest access. ASUS randomly decided to renumber these without the 0 (51,52,53, etc..) These VLAN numbers conflict with existing VLANs on my network. WTF ASUS! I'll have to spend a lot of time reconfiguring switch ports to make this change !!!

In addition, I use the OpenVPN service to route my browser / DNS from my phone back to my home location with the option of blocking all other DNS. DNS doesn't work anymore when you upgrade to this version. The DNS pushed by the router is the LAN interface, not the router's VPN interface IP which is normal but fails. The best I can tell is that the iptables rules are different and not allowing, but I had to get my network back online so I reverted the firmware for now and didn't troubleshoot further.

 

[visortgw]

One of the big 'architectural changes' that prevents me from upgrading is they always used tagged vlans 501+ for guest networks. I have these configured in my managed switches to get over to the AI mesh node(s). I also use these VLANs as wired guest not wireless guest access. ASUS randomly decided to renumber these without the 0 (51,52,53, etc..) These VLAN numbers conflict with existing VLANs on my network. WTF ASUS! I'll have to spend a lot of time reconfiguring switch ports to make this change !!!

In addition, I use the OpenVPN service to route my browser / DNS from my phone back to my home location with the option of blocking all other DNS. DNS doesn't work anymore when you upgrade to this version. The DNS pushed by the router is the LAN interface, not the router's VPN interface IP which is normal but fails. The best I can tell is that the iptables rules are different and not allowing, but I had to get my network back online so I reverted the firmware for now and didn't troubleshoot further.

For your first issue, simply change the VLAN IDs in Guest Network Pro settings — It's configurable. @RMerlin has a change in the works for DNS Director that may address your second issue.

 

[af82]

For your first issue, simply change the VLAN IDs in Guest Network Pro settings — It's configurable. @RMerlin has a change in the works for DNS Director that may address your second issue.

Are these pro settings in the regular ASUS firmware or only Merlin?

 

[visortgw]

For your first issue, simply change the VLAN IDs in Guest Network Pro settings — It's configurable. @RMerlin has a change in the works for DNS Director that may address your second issue.

VLAN ID settable in either via Guest Network Pro or Network tab (tab name changed in a recent firmware revision) in both stock and Merlin firmware. DNS Director is specific to Merlin firmware — I was confused as to which thread I was responding to as I follow both.

 

[af82]

VLAN ID settable in either via Guest Network Pro or Network tab (tab name changed in a recent firmware revision) in both stock and Merlin firmware. DNS Director is specific to Merlin firmware — I was confused as to which thread I was responding to as I follow both.

I found some posts about Guest Network Pro and Network tabs and the rename, but the firmware just before this upgrade didn't seem to have those. I'm on 3.0.0.4.388_24403 which does not have those options at all. I don't run Merlin on this router although I may have to. I usually don't switch until ASUS breaks something like they did with my AX11000... Remote management ACLs make it stay in a reboot loop, support doesn't care, of course that Wizard's firmware doesn't do that.

Anyway, regarding my DNS problem. ASUS' new firmware pushes the LAN interface for the DNS server instead of the VPN interface and then firewalls it off, and with the block-outside-dns custom option added, this isn't good because it cuts off DNS for the client completely. (The reason is to force All DNS through the VPN for filtering with a piHole). The router forwards it to a DMZ pihole (yes, I know I could just hand-out the pihole address with the DHCP option, but this doesn't work really for the VPN settings) As long as DNS Director can forward back internally, I could move it back into the network vs just outside it.

I like to be complicated

 

[visortgw]

I found some posts about Guest Network Pro and Network tabs and the rename, but the firmware just before this upgrade didn't seem to have those. I'm on 3.0.0.4.388_24403 which does not have those options at all. I don't run Merlin on this router although I may have to. I usually don't switch until ASUS breaks something like they did with my AX11000... Remote management ACLs make it stay in a reboot loop, support doesn't care, of course that Wizard's firmware doesn't do that.

Anyway, regarding my DNS problem. ASUS' new firmware pushes the LAN interface for the DNS server instead of the VPN interface and then firewalls it off, and with the block-outside-dns custom option added, this isn't good because it cuts off DNS for the client completely. (The reason is to force All DNS through the VPN for filtering with a piHole). The router forwards it to a DMZ pihole (yes, I know I could just hand-out the pihole address with the DHCP option, but this doesn't work really for the VPN settings) As long as DNS Director can forward back internally, I could move it back into the network vs just outside it.

I like to be complicated

Guest Network Pro or Network tabs came with 3006.x firmware (i.e., like the title of this thread). Migrating from 3004 to 3006 is a major upgrade, so you should anticipate some hiccoughs. You may want to consider moving forward as neither Asus nor Merlin will continue to support the 3004 codebase for a device once it moves to 3006.

 

[af82]

Guest Network Pro or Network tabs came with 3006.x firmware (i.e., like the title of this thread). Migrating from 3004 to 3006 is a major upgrade, so you should anticipate some hiccoughs. You may want to consider moving forward as neither Asus nor Merlin will continue to support the 3004 codebase for a device once it moves to 3006.

I upgraded again and found the VLAN settings. Thank you.

For DNS I had to just add a push "dhcp-option DNS **DMZ IP**" to route the DNS directly to my server. internal and VPN interfaces wont respond over the VPN.

 

[opq]

Also having issues with my OpenVPN server after upgrading to 3.0.0.6. Clients VPN'ing in can no longer access anything on the local network.

Also, is anyone else noticing poorer 2.4GHz performance on a "Guest Network Pro" IOT 2.4GHz network? I have a device that shows up like this in the Log but never shows up in Clients and never "connects" anymore.

Apr 9 17:17:26 wlceventd: wlceventd_proc_event(722): eth10: Assoc [MAC], status: Successful (0), rssi:-87
Apr 9 17:17:47 wlceventd: wlceventd_proc_event(645): eth10: Deauth_ind [MAC], status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Apr 9 17:17:47 wlceventd: wlceventd_proc_event(662): eth10: Disassoc [MAC], status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0