Release Asuswrt-Merlin 3006.102.4 is now available

[roundaway]

RT-AX-86U Pro 3006.102.4

The ShieldsUP scan of Common Ports says FAILED because a a Ping (IMCP Echo) reply was received. The Firewall setting, Respond IMCP Echo (ping) Request from WAN, is NO. Any issue with this behavior?

The test did pass a couple of hours later. The first ShieldsUP test showed my computer with a 193.x.x.x IP address. The second test showed the correct public address. Thanks to all for helpful replies.

----------------------------------------------------------------------

GRC Port Authority Report created on UTC: 2025-06-02 at 02:52:12

Results from scan of ports: 0, 21-23, 25, 79, 80, 110, 113,
119, 135, 139, 143, 389, 443, 445,
1002, 1024-1030, 1720, 5000

0 Ports Open
0 Ports Closed
26 Ports Stealth
---------------------
26 Ports Tested

ALL PORTS tested were found to be: STEALTH.

TruStealth: PASSED - ALL tested ports were STEALTH,
- NO unsolicited packets were received,
- NO Ping reply (ICMP Echo) was received.

----------------------------------------------------------------------

 

[przemekwawa]

After checking an open sytem I suggest to check with short password. Maybe you have been using some "weired" characters in your strong password that were not supported by new Merlin WRT?
Remember: for MusicCast app to work your smartphone and receiver must be in same network.

For what it's worth, I had a similar problem where a thermostat that used to connect under 3004 could not connect under 3006, showing authentication errors when it tried to connect.

It took a lot of troubleshooting, but eventually I tried changing the password to something with just letters and numbers and it worked. Now that said, my phone was able to connect using the long password, so there is something more subtle about 3006 than just special characters in the password, but there is something different going on.

Nope. I added new IoT network with 8 letters/digits, and situation is the same. What is funny, I completely forgot that years ago my clothes dryer (LG) started to have some issues with network, but after upgrade it automatically reconnected to IoT network (I did not change password for my original IoT network). So, Yamaha connected to empty password wifi, but cannot reconnect after upgrade to any other guest network.

 

[ScottsoMuni]

Was curious if non-pro models will be supported (i.e. RT-AX88u) in the future?

 

[visortgw]

Was curious if non-pro models will be supported (i.e. RT-AX88u) in the future?

If you are asking about 3006.102 firmware for the RT-AX88U and other "non-pro" models, the question has been asked and answered many times — the answer is still "NO!". Asus has not (and has no plans to) developed or released the GPLs necessary to do this. These devices continue to be supported on the 3004.388 firmware baseline.

 

[chA]

Mesh Nodes - Range Extenders

I'm running a BE96U with Merlin 3006.102.4 final. I recently tried to link a new RP-BE58 Wifi 7 extender and could only get it to link up with my main router using the wired option. Then, selecting 5G preferred link in the node management menu, restarting without wire, the node would not link up. I tried to go back to 102.4_Beta3 and was able to link with wire, then move away and link via wireless, but it was very iffy. I did not try Asus 3006.102 release because I didn't want to go through the hassle of wipe and manual reinstall.
For kicks, I pulled out a RP-AX58 Wifi 6 extender and it readily linked with the BE96U wirelessly on Merlin 3006.102.4 final. I'll try this exercise again once the BE58 has a firmware update. I'm guessing there's a firmware catch up needed for the BE58.

Can't offer a solution / reason behind your experience, but can state that I also have a BE96U on 3006.102.4, and I have thus far had zero issues with a BE7200 (BE88U) connecting via 5GHz backhaul also on 3006.102.4. Rated performance of the AIMesh connection is similar to running 3006.102.4b2 and 3006.102.3 as well

 

[Wisiwyg]

Can't offer a solution / reason behind your experience, but can state that I also have a BE96U on 3006.102.4, and I have thus far had zero issues with a BE7200 (BE88U) connecting via 5GHz backhaul also on 3006.102.4. Rated performance of the AIMesh connection is similar to running 3006.102.4b2 and 3006.102.3 as well

The RP-BE58 is on the initial release firmware 3006_102_37604 fwiw.

 

[tresnugget]

102.4 (BE98-Pro) broke streaming in certain apps but only on my LG OLED TV. I've spent most of the day troubleshooting.

It was all very weird. As soon as I updated the firmware I got logged out of most of my streaming apps on the TV.

Then I noticed Hulu and Disney+ would take forever to load episodes and a lot of times wouldn't load at all or the TV rating icon in the corner would be a missing image icon.

Then I noticed the Apple TV app wouldn't load at all.

I tried factory resetting both the TV and router while restoring settings from a settings backup file. No luck. Tried factory resetting and manually setting everything up again. No luck.

If would all work no problem on my phones hotspot though.

Finally I rolled back to 102.3 and everything is working again.

One curious thing is I haven't been able to play Paramount+ from the LG app for a long time and all of a sudden that worked no problem on 102.4. Back on 102.3 and it won't play again. But it works on my phones hotspot so I'm guessing it's the firmware and I've just been blaming the Paramount+ app for being terrible this whole time.

Any idea if there's a setting I can check to fix this?

Edit: apparently it has something to do with DNS. I got off my ISP's DNS and now Paramount+ works on the TV and Hulu, Disney+, and Apple TV all work as well. I'm still on 102.3. I was also on my ISP's DNS on 102.4 and Paramount+ worked (whereas it hasn't on previous firmware revisions) but the other 3 apps wouldn't so I'm assuming 102.4 was forcing another DNS despite my ISPs static DNS servers entered and not enabling DNS Director.

 

[ArashT]

I have GT-AX6000 with asuswrt-merlin GT-AX6000_3006_102.4_0 firmware
Sometimes (randomly) the router become unresponsive, web panel won't work, ssh won't work, even I loose internet access
In this case I can't do anything except a hard reboot by turn the router off and on
I have no idea how can I debug this issue, How can I check the logs after boot ?

 

[paul0363]

Edit: apparently it has something to do with DNS. I got off my ISP's DNS and now Paramount+ works on the TV and Hulu, Disney+, and Apple TV all work as well. I'm still on 102.3. I was also on my ISP's DNS on 102.4 and Paramount+ worked (whereas it hasn't on previous firmware revisions) but the other 3 apps wouldn't so I'm assuming 102.4 was forcing another DNS despite my ISPs static DNS servers entered and not enabling DNS Director.

It's more likely the apps forcing another DNS (likely Google's). A lot of apps are hard coded with Google's DNS (apparently to "enforce" geolocation).

I also have an LG OLED and am running 102.4 on a RT-BE92U with no issues with any of the apps you mentioned. However, DNS director is enabled and forces the use of ISP DNS for the TV.

 

[Paliv]

My FireTV 4k max sticks all show google DNS in leak tests no matter what I put in DNS Director. I have it set to Router (which is set to us my ISP in the WAN page). It’ll occasionally show my ISP DNS, it then shows about 100 different google IPs. I haven’t bothered figuring it out yet. I can’t stand that they force google DNS when it pulls less than ideal IPs for streaming services when the ISP handles sending me to the peering services inside their network better.

 

[bennor]

My FireTV 4k max sticks all show google DNS in leak tests no matter what I put in DNS Director. I have it set to Router (which is set to us my ISP in the WAN page). It’ll occasionally show my ISP DNS, it then shows about 100 different google IPs. I haven’t bothered figuring it out yet. I can’t stand that they force google DNS when it pulls less than ideal IPs for streaming services when the ISP handles sending me to the peering services inside their network better.

The Google DNS may be hard coded into the FireTV. If so you may need to block the Google DNS using the LAN > Router page in the GUI. Example (the Gateway IP address is the router's address):

 

[MDM]

which is set to us my ISP in the WAN page

Not sure, but if in auto I think it might not work. So try to assign it manually (even to your ISP)...
Also try setting Prevent client auto DoH to Yes.

 

[tresnugget]

It's more likely the apps forcing another DNS (likely Google's). A lot of apps are hard coded with Google's DNS (apparently to "enforce" geolocation).

I also have an LG OLED and am running 102.4 on a RT-BE92U with no issues with any of the apps you mentioned. However, DNS director is enabled and forces the use of ISP DNS for the TV.

I'd think if the app was forcing DNS the results would be the same across 102.3 and 102.4. I know the Paramount app is using what's set as changing the DNS from the ISP to Google fixed my issues on 102.3. I ended up setting everything to use my ISP's DNS globally as it was slightly lower latency than Google's then forcing Google's to the TV using DNS director and all apps are working on 102.3. When I have some free time I'll do the save thing on 102.4 and see how it goes.

 

[paul0363]

The Google DNS may be hard coded into the FireTV. If so you may need to block the Google DNS using the LAN > Router page in the GUI. Example (the Gateway IP address is the router's address):
View attachment 66089

..or add the following to a NAT-START script:

#!/bin/sh

iptables -t nat -A PREROUTING -p udp -d 8.8.8.8 --dport 53 -j DNAT --to `nvram get lan_ipaddr`

iptables -t nat -A PREROUTING -p tcp -d 8.8.8.8 --dport 53 -j DNAT --to `nvram get lan_ipaddr`

iptables -t nat -A PREROUTING -p udp -d 8.8.4.4 --dport 53 -j DNAT --to `nvram get lan_ipaddr`

iptables -t nat -A PREROUTING -p tcp -d 8.8.4.4 --dport 53 -j DNAT --to `nvram get lan_ipaddr`

iptables -t nat -A POSTROUTING -j MASQUERADE

 

[Jerky_san]

Is anyone else's speed test broken on this version? AXE16000 is the router I'm running.

 

[ExtremeFiretop]

Is anyone else's speed test broken on this version? AXE16000 is the router I'm running.

All good here... Have you configured a VPN by chance?
WAN Test:

WireGuard VPN Test:

 

[Jerky_san]

All good here... Have you configured a VPN by chance?
WAN Test:
View attachment 66127

WireGuard VPN Test:
View attachment 66128

Mine just shows this

 

[ExtremeFiretop]

Mine just shows this

View attachment 66130

Can you provide your F12 debug output please on that page?? (Not for me, but for reference)
On the page hit F12 key, and go to "Console" and look for any errors, maybe send a screenshot of the results.

 

[Jerky_san]

Can you provide your F12 debug output please on that page?? (Not for me, but for reference)
On the page hit F12 key, and go to "Console" and look for any errors, maybe send a screenshot of the results.

Appears to be a missing CSS

Edit

Should of said a missing picture referenced by the css

 

[rickysuperdog]

Mine just shows this

View attachment 66130

Me also! even with original Asus firmware since a couple of updates before. Asus support said it's normal......
Now I cannot do the WAN test using Asus WebUI.