Release Asuswrt-Merlin 3006.102.4 is now available

[JoeHz]

For me and my setup, the Asus app still works great... So you can't generalize.
Of course, there's no guarantee that the interaction will work.

Incompatible sounds like an overbid.
Not supported sounds more accurate.

I've had no problems with it. There was a time where I found rebooting the router through it was more reliable than via the http gui

 

[bennor]

Possibly this, if it was associated with mDNS?

That might have been it. There have been so many separate discussions on issues with Guest Network Pro, and the use of iptables to perform certain things with Guest Network Pro, I might be confusing things.

 

[inakaya]

That might have been it. There have been so many separate discussions on issues with Guest Network Pro, and the use of iptables to perform certain things with Guest Network Pro, I might be confusing things.

And me!

 

[CaptainSTX]

Asuswrt-Merlin 3006.102.4 is now available. There are a number of significant things to note with this release:

1) BCM4912 models are now migrated to this 3006 code base. This includes the following device list:

• GT-AX6000
• zenWifi Pro XT12
• GT-AX11000 Pro
• GT-AXE16000
• RT-AX86U Pro
• RT-AX88U Pro

2) New addition - the RT-BE92U is now supported.

3) Beside the addition of new models, the focus of this release is the merge of GPL code (I currently need to manage three separate GPL versions for this release.....), updated components, and a number of fixes.

Please make sure you read the Changelog.

3006.102.x (10-May-2025)
  - NOTE: If migrating from a 3004 firmware, only the first Guest
          Network will be migrated - any additionnal GN must be
          manually reconfigured.
  - NOTE: If migrating from a 3004 firmware, the Wireless Scheduler
          will need to be manually reconfigured if you were using
          it.
  - NOTE: As a reminder, the ROG variant of the webui is not
          supported in the 3006 firmware series, as maintaining
          two separate interfaces is too much extra work.
  - NOTE: Due to numerous webui changes, it's recommended to
          force refresh the page after first login, or clear
          your browser cache.

  - NEW: Moved RT-AX86U_PRO, RT-AX88U_PRO, ZenWifi Pro XT12,
         GT-AX6000, GT-AXE16000 and GT-AX11000_PRO to the
         3006 firmware series.
  - NEW: Added RT-BE92U support, based on GPL 102_37526.
  - NEW: Added Control-D servers to DNS-over-TLS
         presets (dave14305)
  - UPDATED: Merged GPL 3006.102_36521 for Wifi 6 models (Wifi 7
             devices other than the RT-BE92U are still on
             102_37346).
  - UPDATED: OpenVPN to 2.6.14.
  - UPDATED: miniupnpd to 2.3.8.
  - UPDATED: amtm to 5.2 (decoderman)
  - UPDATED: dnsmasq to 2.91.
  - UPDATED: dropbear to 2025.87.
  - CHANGED: Setting DNS Director to "Router" will now always
             redirect to the router's own IP.  Previously it
             would redirect to the first DNS server configured
             on the DHCP page (which defaults to the router
             itself).
             If you need DNS Director to redirect to an IP
             configured in your DHCP settings, use a Custom DNS
             entry in DNS Director.  This makes it more consistant
             with what the name implies, and was also necessary
             for improved Guest Network support.
  - CHANGED: Tools category renamed System Info.
  - CHANGED: Tools -> Other Settings were moved to new tabs
             (Administration -> Tweaks, and
             Traffic Analyzer -> Settings).
  - CHANGED: Moved "Redirect to asusrouter.com " to the new
             Tweaks tab, and moved "Enable JFFS Custom Scripts"
             to the Basic Config section on the System page.
  - FIXED: Missing hostname on Wireless Log for MLO-capable Wifi 7
           clients.
  - FIXED: CVE-2024-9143 in OpenSSL (Debian backport by RSDNTWK)
  - FIXED: CVE-2024-13176 in OpenSSL (Ubuntu backport by RSDNTWK)
  - FIXED: Guest Networks on an isolated VLAN with DNS Director set
           to "Router" would fail to do any name resolution (both
           for whole network and for specific clients).
  - FIXED: Wrong tab selected when clicking on "Profile" on the
           VLAN page (dave14305)
  - FIXED: Missing button to remove entries in the Offline Client
           List (dave14305)
  - FIXED: CVE-2025-2492 in AiCloud (backport from upstream)
  - FIXED: DoT access wasn't properly blocked when appropriate
           for Guest Networks.
  - FIXED: DNS-over-TLS presets overwritten by Asus' own (dave14305)
  - FIXED: Networkmap system status frame failing to load when
           accessing the router with some particular hostnames.
  - FIXED: Missing option to disable logging of DHCP/RA queries.

Discussions in this thread should be limited to this specific release. This thread may get locked once the release discussion has quieted down.


Downloads are here.
Changelog is here.

After going through the alpha and beta releases I have been working to maximize the benefits of using Guest Network Pro on the release version. One limitation I have run into is that for devices connecting by WiFI to a guest network on a node I haven't been able to force the device to connect using an assigned static IP.

Also has anyone experimented with the 802.1Q option under WAN and which ASUS classifies as multi-service WAN?

 

[Natty]

@CaptainSTX in the Advanced Settings of a Customized Network in Guest Network Pro, , does the 'Manually Assigned IP around the DHCP list' allow you to assign static IP? I havent tried this but it looks editable

 

[bennor]

.... does the 'Manually Assigned IP around the DHCP list' allow you to assign static IP? I havent tried this but it looks editable

Yes ,you can use the Guest Network Pro profile's "Manually Assign IP around DHCP list" option to assign; IP address, DNS Server and Host Name to Guest Network Pro profile clients. Example attached.

 

[Seth Harman]

@CaptainSTX in the Advanced Settings of a Customized Network in Guest Network Pro, , does the 'Manually Assigned IP around the DHCP list' allow you to assign static IP? I havent tried this but it looks editable

That's exactly where you do it, I have a whole mess of WiFi clients with manual DHCP assignments on my IoT VLAN.

 

[pdc]

I have two issues I see with the new firmware on GT-AX6000.

The first is that the 2.4 GHz section only shows the first 10 characters of the wi-fi password. I confirmed the full 63(?) character password is there, since my phone can still connect using the full password. This truncation shows in both the system status (home screen) and the wireless settings in Advanced Settings.

The 5 GHz section shows the full password correctly.

The second problem is that something appears to be different about how clients connect. I have a thermostat that was connected using the previous version (3004.388.8_4) but was no longer able to connect with the new version. I ultimately changed the password to something smaller and less complex, and now it can connect, but it took all morning to figure that out!

The old password was a very long random password, so it's possible that a special character is being escaped or hashed differently. I mention this just in case someone else is scratching their head over IOT devices not being able to connect on 3006. My phone could connect, so I know the password was correct, but the thermostat kept getting authentication errors.

All seems to be working well with the shorter password.

 

[heysoundude]

Hmm... reading here https://www.snbforums.com/threads/is-roaming-assistant-a-myth.60660/ it sounds like never worked well, and @RMerlin says it is outside of his control. But I do not understand why Android 15 would hold on to a crappy Wi-Fi signal from the router miles away when it has the credentials to connect to a much better faster signal from an AP 4m away. The router is AX but the AP is AC. Could that be the reason? Badly programmed client firmware?

EDIT: after further research (other threads on this forum) I believe the feature is working correctly. I had misunderstood how roaming assistant works. It is up to the client if it takes the advice from the router to disconnect and look for a better connection. My choices at this point are either ignore/accept and live with it as-is, or turn the roaming assistant off.

AiMesh is supposed to make this easy, but I think you're making it more difficult for yourself by mixing wifi standards, @Natty

I'd leave RA just as you have it now and go into the config of each router's Advanced>Wireless>Professional section and turn all bands Tx power (slider at the bottom of the page) down by one notch to "good" from "performance", and then perhaps down again in the 2.4 band from "good" to "balance" and see if that helps. The transmitters don't always have to be on full power death star energy beam mode, right? If you see an improvement, then you start tweaking RA or moving the APs physical locations to get the performance/coverage you expect.

"miles away" is subjective. I'd offer that you've too many Stations too close together at too high power output for the client devices to not get confused and prevent locking onto what it knows works...or the Roaming Assistant config needs some work, but more probably some of both.

I relocated my AX88Pro and was shocked/surprised to still have a good connection driving out of my neighbourhood, 40-ish meters from its location. If my wifi radiates equally in all directions, I'm a problem for a good number of my neighbours, as I suspect a fair number of folks on SNBForums are. I'm going to work on making my wifi bubble/coverage/attack surface extend as far as the property lines and no further, as cool as it is to have the invisible tether able to be functional at surprising distance - "Functional" and "enough" rather than "MORE! FARTHER! FASTER!!!"

 

[routerq]

From the Change Log:
3006.102.3 (11-Jan-2025)
- NOTE: If flashing on top of Asus stock firmware 3006.102_37000
or greater, then you first need to enable downgrade
capabilities before flashing Asuswrt-Merlin on top
of it. Connect Over SSH, and run the following command:

nvram set DOWNGRADE_CHECK_PASS=1

After that, you can upload Asuswrt-Merlin through
the webui like any regular firmware upgrade.

This is only required when flashing Asuswrt-Merlin
for the first time.

My RT-AX86U Pro is on FW 3.0.0.6.102_34349, and I am guessing no harm for this FW too.

SO I ran the command "nvram set DOWNGRADE_CHECK_PASS=1"

Is there a way to check that it was implemented?

TIA
Sunny

 

[jksmurf]

That's exactly where you do it, I have a whole mess of WiFi clients with manual DHCP assignments on my IoT VLAN.

There is however a limit…so it depends on how you count a ‘whole mess’. I ended up using the dnsmasq-x.conf.add approach to get past that limitation for Guest Network clients.

I even had some fun writing a custom_client list generator in Excel for both the YazDHCP and dnsmasq-x.conf.add custom client names and icons.

 

[bennor]

SO I ran the command "nvram set DOWNGRADE_CHECK_PASS=1"

Is there a way to check that it was implemented?

You can probably issue the following to see if a value has been set.
nvram get DOWNGRADE_CHECK_PASS

 

[routerq]

You can probably issue the following to see if a value has been set.
nvram get DOWNGRADE_CHECK_PASS

perfect , got a 1 .. thanks for helping out a noob

 

[airwalker2662]

RMerlin, can you comment about the issue regarding the 2.5gbps port on routers like the RT-AX86U Pro maxxing out at 1gbps? I've tried both official Asus and your firmwares and still cannot get wireless speeds over 1gbps over the wireless.

Yes, I am connected on the 2.5 port and my switch shows it a full speed. Currently in AP mode, and I also tested router mode - openspeed test results are always near 1gpbs. Nothing else is connected to the router. Even a couple crappy Windstream DSL modems I have with 2.5 ports will transfer at full 2.5gpbs over wifi.

 

[fotingo]

Glad this discussion post is still open. Some of the lingering question I had were answered on here, like where to assign static IPs. I was wondering about that and I see it's in the Advanced settings.
One question I still have that I haven't found a discussion on is..

does it matter which Network to choose from when adding a new one?
What I mean is, is there a benefit and or limitation when using one vs the others?
I get that IoTs would go into the IoT Network, but why?.. why not the Customized or Guest Network?

**EDIT
Also, is it better to set static IPs in the router or at the device level?

 

[Natty]

AiMesh is supposed to make this easy, but I think you're making it more difficult for yourself by mixing wifi standards, @Natty

I'd leave RA just as you have it now and go into the config of each router's Advanced>Wireless>Professional section and turn all bands Tx power (slider at the bottom of the page) down by one notch to "good" from "performance", and then perhaps down again in the 2.4 band from "good" to "balance" and see if that helps. The transmitters don't always have to be on full power death star energy beam mode, right? If you see an improvement, then you start tweaking RA or moving the APs physical locations to get the performance/coverage you expect.

"miles away" is subjective. I'd offer that you've too many Stations too close together at too high power output for the client devices to not get confused and prevent locking onto what it knows works...or the Roaming Assistant config needs some work, but more probably some of both.

I relocated my AX88Pro and was shocked/surprised to still have a good connection driving out of my neighbourhood, 40-ish meters from its location. If my wifi radiates equally in all directions, I'm a problem for a good number of my neighbours, as I suspect a fair number of folks on SNBForums are. I'm going to work on making my wifi bubble/coverage/attack surface extend as far as the property lines and no further, as cool as it is to have the invisible tether able to be functional at surprising distance - "Functional" and "enough" rather than "MORE! FARTHER! FASTER!!!"

Thanks. I tried turning off RA. Clients clung on to bad signals even more with it turned off, so I turned it back on again. Clients then at least have the option to take the hint that the signal is not so good. I won't be dimming the power because, due to attenuation between rooms, some of my guests need all the signal they can get. GT-AX6000 with AX 4x4 2.4GHz does a great job in that department. I have doubts that upgrading the wired AP from 3x3 AC to ?x? AX would make much difference, and it's not that big an issue.

I think "Disconnect clients with RSSI lower than ... dBm" led me to expect something along the lines provided by a previous DD-WRT router and AP, where (if memory serves) the connect and disconnect dBm thresholds can be set independently, and if a client does not provide a high enough signal, the router disconnects the client. That helps prevent wardriving or whatever it's called, and forces legitimate clients to re-connect elsewhere, i.e. to another AP on the network. But that is a feature of Atheros wireless and DD-WRT. With Broadcom chipset (ASUS), my understanding is that such nice-to-have router functionality is not possible. So, I'm accepting it as it is.

 

[GaselK]

For everyone having wireless scheduler functionality problems and scheduling for the SDN clients with GPL 3006.102_36521 for Wifi 6 models (Asuswrt-Merlin 3006.102.4) as described
here https://www.snbforums.com/threads/a...ta-is-now-available.94366/page-31#post-954093
and here https://www.snbforums.com/threads/asuswrt-merlin-3006-102-4-beta-is-now-available.94366/post-954401
it seems there was indeed a GPL bug which seems fixed by ASUS
Version 3.0.0.6.102_37073 (RT-BE58U) changelog
- Fixed an anomaly in the wireless scheduler functionality.
- Fixed an issue preventing the configuration of time scheduling for the SDN client.
So next release (or next beta) probably will fix this for Wifi 6 (BCM4912) models.

 

[bbunge]

Glad this discussion post is still open. Some of the lingering question I had were answered on here, like where to assign static IPs. I was wondering about that and I see it's in the Advanced settings.
One question I still have that I haven't found a discussion on is..

does it matter which Network to choose from when adding a new one?
What I mean is, is there a benefit and or limitation when using one vs the others?
I get that IoTs would go into the IoT Network, but why?.. why not the Customized or Guest Network?

**EDIT
Also, is it better to set static IPs in the router or at the device level?

View attachment 65777

I feel it is better to set static addresses at the client level. Then when the router is reset you do not have to stand on your head to manually reserve addresses.

 

[Natty]

Question about syslog when booting. This writes over 1200 lines, of which several hundred look like progress counting:

Jan  1 00:00:29 kernel: Loading firmware into detected PHYs: map=0x20000 count=1
Jan  1 00:00:29 kernel: Halt the PHYs processors operation
Jan  1 00:00:29 kernel: Upload the firmware into the on-chip memory: file=/rom/etc/fw/longfin_a0_firmware.bin size=294708
Jan  1 00:00:29 kernel: 0%^[[1A
Jan  1 00:00:29 kernel: 0%^[[1A
Jan  1 00:00:29 kernel: 1%^[[1A
Jan  1 00:00:29 kernel: 1%^[[1A
Jan  1 00:00:29 kernel: 1%^[[1A
Jan  1 00:00:29 kernel: 2%^[[1A
Jan  1 00:00:29 kernel: 2%^[[1A
Jan  1 00:00:29 kernel: 2%^[[1A
Jan  1 00:00:29 kernel: 3%^[[1A
Jan  1 00:00:29 kernel: 3%^[[1A
Jan  1 00:00:29 kernel: 3%^[[1A
Jan  1 00:00:29 kernel: 4%^[[1A
Jan  1 00:00:29 kernel: 4%^[[1A

and so on up to 100%.
This happens twice, at 0x20000 and 0x80000. Are these progress percentages useful to the developers in the release version? Could their number be significantly reduced on the next release?

 

[CaptainSTX]

Yes ,you can use the Guest Network Pro profile's "Manually Assign IP around DHCP list" option to assign; IP address, DNS Server and Host Name to Guest Network Pro profile clients. Example attached.

I have been able to assign IPs to devices on my guest network and it works fine if the device is connecting to the primary router either by WiFi or Ethernet. What I have not been able to accomplish so far is to get devices connecting to my AX86S node running the latest ASUS firmware to connect and accept the IP I have assigned them.

Also the language suggesting that you assign the IPs outside DHCP pool doesn't seem to be possible. First I haven't seen a place where you can set the range for the default 192.168.52.0/24 pool in the GUI. I then tried using a 192.168.52.0/27 pool and then assigning static IPs outside the pool. That was a no go as even though I had assigned the devices IPs above the upper limit of the /27 pool the router now ignored those assignments and assigned the devices IPs within the 27 pool. Since that didn't work I just reverted to using a /24 pool and everything works fine, and the devices get the IP I have assigned.