Release Asuswrt-Merlin 3006.102.6 is now available

[NoLight]

Same here.
Installed 102.6 and did a factory reset (WPS reset or Administration - Restore). Manually config all the settings I use and UPnP is enabled. Xbox Series X shows NAT Type: Moderate.
View attachment 69414

Reinstalled 102.5, factory reset (WPS reset or Administration - Restore) and Manually config all the settings I use with UPnP enabled and my Xbox Series X shows NAT Type: Open.
View attachment 69415

Sorry for going a little off topic here:
It doesn't look like a Asuswrt-Merlin issue because it happens with the factory firmware on the ASUS GT-AX6000 too.
Also done with factory reset (WPS reset or Administration - Restore) and manually config all the settings with UPnP enabled.
ASUS GT-AX6000 Firmware version 3.0.0.6.102_34825, UPNP enabled works.
ASUS GT-AX6000 Firmware version 3.0.0.6.102_34860 and 3.0.0.6.102_34876, UPnP enabled doesn't work correctly on the Xbox.

Somewhat off topic, but if your only using UPnP for an Xbox, you just need to open TCP/UDP for ports 3074 and 9002.

 

[RMerlin]

Maybe, just maybe - what's broken is the test, not the firmware?

Because there has been zero change to UPnP these past few releases.

 

[ColinTaylor]

Maybe, just maybe - what's broken is the test, not the firmware?

^ this.

The Windows and XBox tests for port forwarding have always been broken in this way. People should just ignore it.

 

[Paliv]

Maybe, just maybe - what's broken is the test, not the firmware?

Because there has been zero change to UPnP these past few releases.

I was thinking the same as there is zero difference in the experience when these test report moderate or open. Also, I just noticed Call of Duty was showing open earlier today on my lunch break, but now shows moderate. So…who cares as long as it’s working, since the ports are being forwarded.

 

[AlexHK]

Sorry I am late to the party.
Does ASUS now force https? Guess it's time for me to finally enter the modern age

I am greeted with this on port 80

 

[lgkahn]

in my case if you set the plulldown to http instread of both you dont get that.. it just works in http/80. but i guess it may depend on what router you have.

 

[Jeffrey Young]

GT-AX6000 using http to connect to the router, this is painfully slow and laggy, anyone else?

Try a different browser. My AX86U Pro (running on 388 firmware) is experiencing the same issue as you - very sluggish and slow to respond on Chrome. Using Brave, the GUI is its normal snappy self.

 

[Aiadi]

Because there has been zero change to UPnP these past few releases.

I’ve also noticed that remote access to my Plex server has been intermittently failing ever since doing a clean install of the latest AsusMerlin firmware. It used to work consistently on previous versions with no issues.

Disabling UPnP and switching to manual port forwarding fixes the problem, but something in the latest firmware is definitely causing these intermittent disconnects. The fact that UPnP now defaults to “off” also suggests that there has been some change of some sort.

 

[ColinTaylor]

The fact that UPnP now defaults to “off” also suggests that there has been some change of some sort.

It's just being consistent with the new Asus default setting. It's as simple as that. No need to read more into that change than there is. And no suggestion, as you imply, that it is disabled because of a functional problem.

 

[visortgw]

It's just being consistent with the new Asus default setting. It's as simple as that. No need to read more into that change than there is. And no suggestion, as you imply, that it is disabled because of a functional problem.

Correct, Asus has been enforcing stricter security related settings.

 

[bennor]

Disabling UPnP and switching to manual port forwarding fixes the problem

Its a YMMV, but with Plex when I've use the Plex remote access feature; I've always had to use manual router port forwarding for Plex remote access to work consistently even before the 3006.102.6 firmware. Had to do this going back to even when using a RT-AC68U and 3004.386.x firmware. I have UPnP disabled always anyway with the 3006.102.x firmware prior to the change in this firmware release.

 

[TheLostSwede]

GT-AX6000 using http to connect to the router, this is painfully slow and laggy, anyone else?

Nope, no issues.

 

[outlaw78]

Yes, that’s a new,y enforced limit. But those priorities don’t do anything anyway unless you’re using Traditional QoS.

asuswrt-merlin.ng/release/src/router/www/AdaptiveQoS_Bandwidth_Monitor.asp at 976a38e5ef9b275c6ded33f4acae2d1204e1dae7 · RMerl/asuswrt-merlin.ng

Third party firmware for Asus routers (newer codebase) - RMerl/asuswrt-merlin.ng

github.com

But I don't have any where close to 32 set.

 

[dave14305]

But I don't have any where close to 32 set.

See what you have:

nvram get qos_rulelist | tr '<' '\n'

 

[GuardYaGrill]

Just updated my router, don't know how to explain it but it killed WAN access for my devices, however my VPN clients are still able to establish connections and devices routed through the VPN tunnels work fine. My router is still able to curl/ping websites, i can't explain why my devices over WAN fail to connect to any site/server.

admin@RT-AX86U_Pro:/tmp/home/root# ping dnsleaktest.com
PING dnsleaktest.com (23.239.16.110): 56 data bytes
64 bytes from 23.239.16.110: seq=0 ttl=48 time=71.992 ms
64 bytes from 23.239.16.110: seq=1 ttl=48 time=88.942 ms
64 bytes from 23.239.16.110: seq=2 ttl=48 time=71.802 ms
64 bytes from 23.239.16.110: seq=3 ttl=48 time=72.228 ms
^C
--- dnsleaktest.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 71.802/76.241/88.942 ms

admin@RT-AX86U_Pro:/tmp/home/root# curl https://dnsleaktest.com

    <!DOCTYPE html>
    <html lang="en" dir="ltr">
    <head>
        <title>DNS leak test</title>
...
...
...

user@raspberrypi:~/compose $ ping dnsleaktest.com
PING dnsleaktest.com (23.239.16.110) 56(84) bytes of data.
^C
--- dnsleaktest.com ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 5121ms

user@raspberrypi:~/compose $ curl https://dnsleaktest.com
curl: (28) Failed to connect to dnsleaktest.com port 443 after 134028 ms: Couldn't connect to server

If i can't get this going within the next few hours i am rolling back to the previous update in hopes everything kicks back in.

 

[CJ-V300]

I would like to report a cosmetic issue I'm observing on my ASUS BE92U (running the latest Merlin firmware).

My OnePlus 15, which connects via the 6 GHz band (WiFi 7), is frequently misidentified in the "Client List" and "Network Map" as a wired Ethernet connection.

It displays the Ethernet (cable) icon. The Tx/Rx rates are shown as hyphens ("-") instead of actual values. The interface column usually shows a generic LAN icon instead of the 6GHz badge.

The connection is perfect. The device performs at full speed with no stability issues.

If I toggle the WiFi off and on again on the phone, the router briefly identifies it correctly as a 6 GHz client and displays the correct Tx/Rx rates. However, after some time or a refresh, it reverts to the "Wired" status.

It seems like the web UI is having trouble mapping the 6 GHz interface for this specific WiFi 7 client to the correct visual indicator.

Thanks for your work!

 

[Poul Bak]

I would like to report a cosmetic issue I'm observing on my ASUS BE92U (running the latest Merlin firmware).

My OnePlus 15, which connects via the 6 GHz band (WiFi 7), is frequently misidentified in the "Client List" and "Network Map" as a wired Ethernet connection.

It displays the Ethernet (cable) icon. The Tx/Rx rates are shown as hyphens ("-") instead of actual values. The interface column usually shows a generic LAN icon instead of the 6GHz badge.

The connection is perfect. The device performs at full speed with no stability issues.

If I toggle the WiFi off and on again on the phone, the router briefly identifies it correctly as a 6 GHz client and displays the correct Tx/Rx rates. However, after some time or a refresh, it reverts to the "Wired" status.

It seems like the web UI is having trouble mapping the 6 GHz interface for this specific WiFi 7 client to the correct visual indicator.

Thanks for your work!

Seems wifi 7 devices have this weird bug. You can try my post here to see if it works for you:
https://www.snbforums.com/threads/asuswrt-merlin-3006-102-6-is-now-available.96254/post-977478

 

[CJ-V300]

Seems wifi 7 devices have this weird bug. You can try my post here to see if it works for you:
https://www.snbforums.com/threads/asuswrt-merlin-3006-102-6-is-now-available.96254/post-977478

Thanks a lot! That was spot on.

I just enabled MLO globally (under Wireless > MLO) while keeping it disabled on my specific SSIDs/Networks, and boom: the OnePlus 15 is now correctly identified with the WiFi 7 icon. It seems the firmware needs that global switch 'On' to properly parse the WiFi 7 signaling/icons, even if we don't use the feature on the actual bands.

My only concern now is stability. The main reason I had MLO completely disabled was that it caused buffering and stuttering on my TV (Sony 85X90L) when playing heavy high-bitrate Remux files (60GB+).

Logic dictates that since MLO is still disabled on the specific SSID the TV uses, it should remain stable and solid. I’m going to perform a stress test with a heavy Remux tonight to confirm that this "Hybrid" configuration (Global ON / SSID OFF) doesn't reintroduce the lag.

I will report back with the results. Thanks again for the tip!

 

[Poul Bak]

Logic dictates that since MLO is still disabled on the specific SSID the TV uses, it should remain stable and solid.

I will report back with the results. Thanks again for the tip!

I think that logic is correct. It's just some silly display issue when MLO is off globally.

 

[CJ-V300]

I think that logic is correct. It's just some silly display issue when MLO is off globally.

Well, I have an update, and it's quite surreal.

ASUS BE92U Global MLO = ON / SSID MLO = OFF.

The Good: The OnePlus 15 (WiFi 7) finally displayed the correct WiFi 7 icon in the client list.
The Bad: (and deal-breaker): My TV (Sony 85X90L) completely stopped seeing the 5GHz&6GHz SSID.

It wasn't just a connection error; the network literally vanished from the TV's available networks list. The TV could see the 2.4GHz band, but the Pro (5GHz/6GHz) network became invisible to it. I tried disabling/enabling WiFi on the TV, but it made no difference.

It seems that enabling MLO globally changes something in the broadcast/beacon frames that makes the SSID invisible or incompatible with the TV's WiFi chipset, even if MLO is technically disabled for that specific network.

Conclusion:I reverted to MLO Globally Disabled. As soon as I did that, the TV found the 5GHz network again immediately.

I prefer a rock-solid network stability (no buffering on 60GB Remuxes) over a correct client list. I'll just live with the current bug where the phone either appears as "wired" or often doesn't appear in the client list at all.

Thanks anyway for the help!