AX86uPRO- updated to 3006.102.4_0 disaster on 2025-05-16

[newb]

RT-AX86uPRO from v.3004.388.8_4 to 3006.102.4_0 result - every device on LAN has connectivity. The router alone has access to the internet.
I did not have: a guest network, wireless scheduler, DNS director.
Figured it still must be a DNS problem. Played with DNS settings that are now scattered through many tabs. Some devices started to work until they stopped. Eg: TV, Roku, mesh APs, laptops, telephones, OOma. I guess devices that could reach WiFi back to the main router could work - but did not go to internet. But even a desktop hardwired to AX86uPRO failed to reach the internet.
Reloaded the 3006... firmware - some devices started having connection after some playing with entering DNS 8.8.8.8 in various places, but still reported no internet, although Roku miraculously was pulling YouTube.
But AX88u and AC68 (both set as a mesh AP) could not reconnect to the AX86uPRO the main router. Reloaded 3004.388.8_4 the previous firmware to AX86uPRO - all works without any intervention, or maybe most work until I discover what does not.
I am sure I did something wrong but still - the smooth sailing it was not.
I will wait for the new and improved v.3006 for my AX86uPRO.

 

[Ripshod]

I will wait for the new and improved v.3006 for my AX86uPRO.

Did you try a factory reset and manual setup? You've moved from 3004 to 3006 firmwares and expect everything to work fine?
Waiting for the next release won't help as you'll just face the same problem - there's no problem with this firmware, other than IoT niggles inherited from Asus firmware.

 

[Analog-1]

I have the AX86U Pro running this new firmware and it's rock solid. What ever issue your having is on your end.

 

[bbunge]

I tested the 3.0.0.6.102.4 firmware on my AX86U Pro. Always do a factory restore when switching firmware. I, too, had some connection issues which were probably related to my locking things down too tightly and several large blocking lists on Diversion. Ultimately decided that the Asus firmware was enough for my needs with the use of a filtering DNS (DoT) service. Results: Happy network and happy family!

 

[bennor]

I am sure I did something wrong but still - the smooth sailing it was not.

Did you perform a hard factory reset (or any kind of a reset) when you flashed from 3004.388.8_4 to 3006.102.4?
When flashing to 3006.102.x firmware from the 3004.388.8_x firmware I performed a hard factory reset on a RT-AX86U Pro. Did so because the 3006 firmware is a significant change from 3004 firmware.

3006.102.4 has been working well on the RT-AX86U Pro once I understood the quirks and issues with Guest Network Pro.

 

[newb]

Did you try a factory reset and manual setup? You've moved from 3004 to 3006 firmwares and expect everything to work fine?
Waiting for the next release won't help as you'll just face the same problem - there's no problem with this firmware, other than IoT niggles inherited from Asus firmware.

Yes - I did expect everything to work. I did not expect a DNS total failure. What do you mean by "manual setup" - in my system the only lengthy setup is DHCP manual assignment.
Yes - I am spoiled by decades of Merlin's wonderful work.
It helps to know that you-all did not have any problems - I shall try again. Thank you.

 

[bbunge]

Yes - I did expect everything to work. I did not expect a DNS total failure. What do you mean by "manual setup" - in my system the only lengthy setup is DHCP manual assignment.
Yes - I am spoiled by decades of Merlin's wonderful work.
It helps to know that you-all did not have any problems - I shall try again. Thank you.

You can avoid the manual assignment if you assign a static IP address to those clients and reserve a pool of addresses in the DHCP range. Then when you have to do a firmware reset all your addresses are already assigned.

 

[JoeHz]

log files? Surely RMerlin would love to see what went wrong. The rest of us are merely curious.

 

[bennor]

... in my system the only lengthy setup is DHCP manual assignment.

No issues using YazDHCP ("develop" version - v1.0.7) to import main LAN client DHCP server manual IP address assignments previously saved from Asus-Merlin 3004.388.x firmware into Asus-Merlin 3006.102.x firmware. Only manual assignments I had to do manually were the Guest Network Pro clients on their respective Profiles, under Advanced Settings -> Manually Assign IP around the DHCP list, because I had the Guest Network Pro Profile setup option Use same subnet as main network set to disable.

 

[RMerlin]

after some playing with entering DNS 8.8.8.8 in various places,

You need to understand what you are doing if you are to ever get things working properly. Settings aren't "scattered", they each have a very specific role in their specific location. Randomly entering "8.8.8.8" in anything that has the word "DNS" next to it is not the way to do it...