Beta Asuswrt-Merlin 3006.102.4 Beta is now available

[zenmota]

Please collect some screenshots:
1. Login to the router UI.
2. Press F12 in Edge to open the developer tools.
3. Switch to the Network tab of the tools window.
4. Go to the VPN Status page in the router UI.
5. Watch all the requests go by in the Network tab.
6. When the activity slows down, scroll up in that Network tab and look for any red errors for "ajax". Most should be successful status 200. Filter the network list (search bar above the scrolling list) for ajax_vpn and click the result like in the screenshot below. View the Response tab on the right side.
7. In the developer tools, switch from the Network tab to the Console tab and look for any errors there.

Here is what it looks like in Firefox on a Linux PC, just to understand what I'm trying to describe.
View attachment 65159

I saw no errors (I think). Screen Shots"

The only red I saw was a "disable_hover.svg as you see in this scrrenshot:

Next is a filter ajax_vpn. Only one item showed. This is with VPN enabled but Status page not showing it unless I clear cache and refresh page:

Next is Console tab. No errors:

Thanks

 

[dineshgyl]

Asuswrt-Merlin 3006.102.4 Beta 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. Note that the GPL used for this initial support suffers from some CPU-related issues, so support for this model at this time should be considered EXPERIMENTAL. If you lose the ability to access the router, then power cycle it, that usually solves it. Beta 2 updated that device's GPL to 102_37526, which should be stable.

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.

Update (19-Apr): 3006.102.4 Beta 2 is now available. Changelogs for all three branches:

Wifi 6:

fe104c9774 (3006.102) webui: updated DNS Director notes
dcef132c02 Update RT-BE96U and GT-BE98_PRO wireless dongle driver to 102_37812 builds
1cc4127a8d miniupnpd: fix building (missing header file)
85c9d353af miniupnpd: update to 2.3.8
198e89a5e8 rc: move service-event-end back within again: loop
170d2e48b5 rc: Have DNS Director "Router" mode use REDIRECT target instead of DNAT to LAN IP in iptables.
8d40fbd7f2 Bumped revision to beta 2
879ad023d4 webui: fix missing button to remove Offline Client List entries
c77742afb1 webui: cleanup sysdep Wireless pages that are no longer existant

Wifi 7:

fe104c9774 (3006.102) webui: updated DNS Director notes
dcef132c02 Update RT-BE96U and GT-BE98_PRO wireless dongle driver to 102_37812 builds
1cc4127a8d miniupnpd: fix building (missing header file)
85c9d353af miniupnpd: update to 2.3.8
170d2e48b5 rc: Have DNS Director "Router" mode use REDIRECT target instead of DNAT to LAN IP in iptables.
8d40fbd7f2 Bumped revision to beta 2
879ad023d4 webui: fix missing button to remove Offline Client List entries
c77742afb1 webui: cleanup sysdep Wireless pages that are no longer existant

RT-BE92U:

fe104c9774 (3006.102) webui: updated DNS Director notes
dcef132c02 Update RT-BE96U and GT-BE98_PRO wireless dongle driver to 102_37812 builds
1cc4127a8d miniupnpd: fix building (missing header file)
85c9d353af miniupnpd: update to 2.3.8
170d2e48b5 rc: Have DNS Director "Router" mode use REDIRECT target instead of DNAT to LAN IP in iptables.
8d40fbd7f2 Bumped revision to beta 2
9fe89ff9b6 httpd: fix CPU temperature report on BCM4916
cb50c47eff Merge RT-BE92U binary blobs from 37526
789a111d63 Merge with GPL 102_37526 (RT-BE92U)
879ad023d4 webui: fix missing button to remove Offline Client List entries
c77742afb1 webui: cleanup sysdep Wireless pages that are no longer existant

Changelog:

3006.102.x (xx-xxx-xxxx)
  - 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.

  - 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_37435.  This GPL
         seems to have some stability issues, so consider support
         for this model to remain Beta, until a fix is provided
         for it.

  - UPDATED: Merged GPL 3006.102_36521 for Wifi 6 models (Wifi 7
             GPL codebase is unchanged from 3006.102.3).
  - UPDATED: OpenVPN to 2.6.14.
  - UPDATED: miniupnpd to 2.3.7 (20250207 snapshot)
  - UPDATED: amtm to 5.2 (decoderman)
  - UPDATED: dnsmasq to 2.91.
  - UPDATED: dropbear to 2025.87.
  - 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 DNSDirector set
           to "Router" would fail to do any name resolution.
  - FIXED: Wrong tab selected when clicking on "Profile" on the VLAN
           page (dave14305)

Make sure you do read the changelog, especially if migrating from 3004 to 3006. I documented the known recommendations from Asus' own changelog, but there might be further compatibility issues arising when upgrading from 3004. In particular, I would recommend disconnecting and reconnecting any AiMesh node. Also, double check Wireless settings.

For this beta release I need test feedback for:

• The models that were migrated from 3004
• General RT-BE92U performance
• The Wireless Log page should be more accurate on Wifi 7 devices, the root problem of missing/incorrect hostnames having been resolved

Please keep discussions on this specific beta release.


Downloads are here.
Changelog is here.

I see that RT AX86U pro has been included for 3.0.0.6.102 version however i dont see source code for the same is available on asus website. Just curious so how its possible to release 3.0.0.6.102 for RT AX86U Pro when asus has not released source code?

 

[JWoo]

Using Beta 2 on RT-BE92U. The 6 GHz signal is amazingly weak. About 5 to 8 dBm weaker than 6 GHz my other triband router (different manufacturer). Main functions work (IPv6, DoT, guest network, main network). Yes, I agree that 6 GHz would be weaker than 5 GHz in theory as higher frequencies do not propagate as well as lower frequencies. But the difference on my other router is 1 to 2 dBM. The Asus 6 GHz is well weaker than that.

Wireguard client works on main Asus release 3.0.0.6.102_37526 but does not work on 3006.102.4 Beta 2. I can configure it and activate it but when I check my IP address and DNS resolvers chosen using DNS Check, the IP address for the Wireguard Client is not being used by the router. I tried turning off DoT and IPv6 but that made no difference. The Wireguard Client is active on 3006.102.4 Beta 2 but does not actually connect..

 

[dave14305]

Next is a filter ajax_vpn. Only one item showed. This is with VPN enabled but Status page not showing it unless I clear cache and refresh page:

Please select the ajax_vpn_status line and check the “Response” tab on the right-hand side. Does the output look correct?

 

[zenmota]

Please select the ajax_vpn_status line and check the “Response” tab on the right-hand side. Does the output look correct?

Looks ok to me. I covered the ip addresses in response tab, but they were correct.

 

[rickysuperdog]

Using Beta 2 on RT-BE92U. The 6 GHz signal is amazingly weak. About 5 to 8 dBm weaker than 6 GHz my other triband router (different manufacturer). Main functions work (IPv6, DoT, guest network, main network). Yes, I agree that 6 GHz would be weaker than 5 GHz in theory as higher frequencies do not propagate as well as lower frequencies. But the difference on my other router is 1 to 2 dBM. The Asus 6 GHz is well weaker than that.

Wireguard client works on main Asus release 3.0.0.6.102_37526 but does not work on 3006.102.4 Beta 2. I can configure it and activate it but when I check my IP address and DNS resolvers chosen using DNS Check, the IP address for the Wireguard Client is not being used by the router. I tried turning off DoT and IPv6 but that made no difference. The Wireguard Client is active on 3006.102.4 Beta 2 but does not actually connect..

I also using BE92u running Merlin beta2. I had tested the speed of 6GHz is just almost the same as original Asus firmware, speed is around 2xxxMbps to 3xxxMbps. I am using 3.5G broadband.

 

[dave14305]

Looks ok to me.

The last idea I have is to open the F12 tools and “Console” tab again, and type wireguard_support then press enter. You should get a number 1 back.

 

[zenmota]

The last idea I have is to open the F12 tools and “Console” tab again, and type wireguard_support then press enter. You should get a number 1 back.

I guess if it gets a 1 back that means it supports wireguard? The wireguard works fine. It is just once I enable or disable it I have to clear the cache for it show correctly on the status page, etc... Maybe I just need to do a "hard reset" and start over. Just that it is time consuming.

Thanks

 

[dave14305]

I guess if it gets a 1 back that means it supports wireguard?

Yes, it was just to check that the page always loads that information correctly since the display of the VPN wireguard clients depends on that initial check. I’d be more inclined to reset your Edge profile than the router settings.

 

[zenmota]

Yes, it was just to check that the page always loads that information correctly since the display of the VPN wireguard clients depends on that initial check. I’d be more inclined to reset your Edge profile than the router settings.

Yeah, I thought about that too. But I tried on a Windows 10 computer I have on this same home network and I had the same problem. It uses Edge also.

Thanks

 

[RMerlin]

I see that RT AX86U pro has been included for 3.0.0.6.102 version however i dont see source code for the same is available on asus website. Just curious so how its possible to release 3.0.0.6.102 for RT AX86U Pro when asus has not released source code?

Due to my specific needs (like having GPL of the same version for all devices), I get the source code directly from Asus.

Wireguard client works on main Asus release 3.0.0.6.102_37526 but does not work on 3006.102.4 Beta 2. I can configure it and activate it but when I check my IP address and DNS resolvers chosen using DNS Check, the IP address for the Wireguard Client is not being used by the router.

Did you configure any rules on VPN Director? By default, nothing gets routed through a WireGuard client.

 

[MDM]

Using Beta 2 on RT-BE92U. The 6 GHz signal is amazingly weak. About 5 to 8 dBm weaker than 6 GHz my other triband router (different manufacturer). Main functions work (IPv6, DoT, guest network, main network). Yes, I agree that 6 GHz would be weaker than 5 GHz in theory as higher frequencies do not propagate as well as lower frequencies. But the difference on my other router is 1 to 2 dBM. The Asus 6 GHz is well weaker than that.

And again missing the crucial info - WiFi setting are on Auto or Manual (charnel, bandwidth...)?

 

[GWTechTalk]

Using Beta 2 on RT-BE92U. The 6 GHz signal is amazingly weak. About 5 to 8 dBm weaker than 6 GHz my other triband router (different manufacturer). Main functions work (IPv6, DoT, guest network, main network). Yes, I agree that 6 GHz would be weaker than 5 GHz in theory as higher frequencies do not propagate as well as lower frequencies. But the difference on my other router is 1 to 2 dBM. The Asus 6 GHz is well weaker than that.

Wireguard client works on main Asus release 3.0.0.6.102_37526 but does not work on 3006.102.4 Beta 2. I can configure it and activate it but when I check my IP address and DNS resolvers chosen using DNS Check, the IP address for the Wireguard Client is not being used by the router. I tried turning off DoT and IPv6 but that made no difference. The Wireguard Client is active on 3006.102.4 Beta 2 but does not actually connect..

I have not seen any degradation of wifi signal strength even when comparing to stock ASUS. Interestingly enough when I disabled BSD my signal stability actually increased but was only noticeable on my 6Ghz clients. Merlin used to have a way to put the devices into "Global" mode so that you could have max transmitter power settings, which legally a grey area for residential devices, but with the new firmware the same tricks don't seem to work anymore. Haven't put much work into figuring it out because all my devices seem very happy with the current firmware.

I personally use Auto everything for channel selection and such. So like @MDM said likely some sort of setting issue. Hopefully everyone realizes that since Merlin is in active development and that there are going to be times where you might see issues if you are dirty flashing devices. If you have an issue first step should always be to factory reset and then MANUALLY set it back up, don't use a backup image. Personally I made start up scripts so that when I wipe my device I can drop the script back onto the router and reboot.

Also, 6Ghz is very wiki washy, its not a very wide service area and ANY obstacle between the device and the router is going to really kick down the strength and resulting bandwidth. 6Ghz is very different than 2.4 and 5 not to mention 160+ widths and MLO capability. I still have not went though all the new features to see how they are accomplishing all of the data segmenting and such for MLO.

 

[JWoo]

Due to my specific needs (like having GPL of the same version for all devices), I get the source code directly from Asus.


Did you configure any rules on VPN Director? By default, nothing gets routed through a WireGuard client.

Yes. And I can see it is active.

 

[JWoo]

I also using BE92u running Merlin beta2. I had tested the speed of 6GHz is just almost the same as original Asus firmware, speed is around 2xxxMbps to 3xxxMbps. I am using 3.5G broadband.

The connection speed is the same as stock firmware 5.7 GHz between the device and the router at about 12 meters with few obstructions. The signal strength especially on 6GHz is really poor compared to my other triband router. I am using channel 5 on 6 GHz.

 

[MDM]

The connection speed is the same as stock firmware 5.7 GHz between the device and the router at about 12 meters with few obstructions. The signal strength especially on 6GHz is really poor compared to my other triband router. I am using channel 5 on 6 GHz.

Depends on country setting a lot, if not the same on both devices, even on same channel big différences are possible. (thus why I set my router to country code #a, and yes I know it disables DFS but for where I live not important...)

 

[JWoo]

Doe

Depends on country setting a lot, if not the same on both devices, even on same channel big différences are possible. (thus why I set my router to country code #a, and yes I know it disables DFS but for where I live not important...)

I do agree with you. The other router is running OpenWRT and has a global setting. So I think what you are saying is correct. Back in the day, with Tomato you would pick #a in the wireless menu or set an NVRAM variable. Which NVRAM variable are you setting, and does it survive reboot or require a startup entry in a script?

 

[zenmota]

Yes, it was just to check that the page always loads that information correctly since the display of the VPN wireguard clients depends on that initial check. I’d be more inclined to reset your Edge profile than the router settings.

I reset the Edge profile to defaults, didn't fix the problem. Think I will wait till release version then when I get time do a "hard reset" on router. Thanks for help though.

 

[aurizn]

Is ASUS' Adaptive QoS implementation still broken ? Any ways to verify if Adaptive QoS is working

 

[dave14305]

Any ways to verify if Adaptive QoS is working

Set your bandwidth to an extremely low bandwidth (e.g. 10 Mbit down, 1 Mbit up) and then run a speed test from a machine on your network (not the router speed test). If the throughput is close to what you entered, it works. If it’s near the advertised ISP speed, it doesn’t work.