Release Asuswrt-Merlin 3006.102.4 is now available

[dave14305]

I hope this helps!

I took the values from Asus’ own list.

https://nw-dlcdnet.asus.com/plugin/js/dot-servers.json

 

[dave14305]

Shouldn't be necessary for now tho, Asus hasn't implemented IPv6 support yet to SDN (AFAIK).

I only mention it because I saw enable-ra here. Whether it works in practice, I have not checked.

asuswrt-merlin.ng/release/src/router/rc/sdn.c at 835d092ab03b79e61ac5b7101d215e75412a3dbb · RMerl/asuswrt-merlin.ng

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

github.com

 

[toffy]

upgraded my ax86_pro from 388.8_4 to 3006.102.4. Connection to the internet fails on all devices with same symptom: DNS requests fail.
example: nslookup www.google.com
;; communications error to 192.168.0.1#53: connection refused
(192.168.0.1. is the ax86pro itselfs).
connections via ip-address do work internally & externally.

If I ssh to the ax86pro and try nslookup from there it does work nicely: it looks like only DNS-requests from clients in the internal network get blocked...
Pretty vanilla settings, no custom scripts.
Any thoughts?
Thank you!

PS Downgraded to 3004 for now --> everything's working again.

 

[dave14305]

Any thoughts?

dnsmasq likely failed to startup due to some customizations you had on the older version that are now duplicated in the newer firmware as part of the firmware. The system log entries with “dnsmasq” will give you clues.

 

[toffy]

dnsmasq likely failed to startup due to some customizations you had on the older version that are now duplicated in the newer firmware as part of the firmware. The system log entries with “dnsmasq” will give you clues.

I added a few hosts to dnsmasq.conf.add (fixed IP for a few old machines that die not fit the reservation page)
...and even these do work with ssh on the router and trying nslookup from there.
nothing unusual in the logs. To be sure I'll remove the dnsmasq.conf.add file tomorrow and give it a try. Thanks for the hint!

 

[mellifluous]

On a RT-BE92U, should I be worried about GPL 102_37526 vs GPL 102-37548?

Thanks,

 

[RMerlin]

On a RT-BE92U, should I be worried about GPL 102_37526 vs GPL 102-37548?

No.

 

[prp2]

Upgraded my GT-BE98 Pro to 3006.102.4 from the beta3 and noticed the wireless driver downgrade?

System Info now shows Nov 22 2024 19:05:11 version 17.10.369.39012 (r839077) BSPv1W13 for all the wireless drivers, but on beta3 and prior it was something from Feb 2025? Haven't noticed any difference in performance on the clients, though, but just something I observed as a change.

 

[shabbs]

Let's GO!!!

EDIT: Filthy upgrade from Beta 3 on my GT-AX6000 Router. No issues off the hop. 2nd reboot done. Time to let it settle... so far so good. As always... thank you @RMerlin and team!

 

[junior120872]

Upgraded my GT-BE98 Pro to 3006.102.4 from the beta3 and noticed the wireless driver downgrade?

System Info now shows Nov 22 2024 19:05:11 version 17.10.369.39012 (r839077) BSPv1W13 for all the wireless drivers, but on beta3 and prior it was something from Feb 2025? Haven't noticed any difference in performance on the clients, though, but just something I observed as a change.

Merlin reverted back. https://github.com/RMerl/asuswrt-merlin.ng/commit/00a3f70623d72bc4b344cee2d1e5efff521bd6b8. I'm actually seeing better connectivity with my IoT devices on this released version than the newer one he had in the beta3. It could all be in my head as well though.

 

[bbunge]

upgraded my ax86_pro from 388.8_4 to 3006.102.4. Connection to the internet fails on all devices with same symptom: DNS requests fail.
example: nslookup www.google.com
;; communications error to 192.168.0.1#53: connection refused
(192.168.0.1. is the ax86pro itselfs).
connections via ip-address do work internally & externally.

If I ssh to the ax86pro and try nslookup from there it does work nicely: it looks like only DNS-requests from clients in the internal network get blocked...
Pretty vanilla settings, no custom scripts.
Any thoughts?
Thank you!

PS Downgraded to 3004 for now --> everything's working again.

You may want to do a factory reset and reconfigure. If you were running DNS Director there were some changes that could shut you down. Also, some of the AMTM scripts have changed. My AX86U Pro is humming along on the new firmware!

 

[AlbumMan]

It's been awhile since doing a factory reset but did one today after the long-awaited release flash. Started a manual config and after getting to the LAN IP, I changed it from the default 192.168.50.1 back back to 192.168.1.1 which changed the DHCP pools as expected. The logon page appears but keep getting "invalid username or password" now and both are correct. I remember this occurring when resetting a long time ago but forgot how I fixed it. Yep, I've searched the forum but could not find an answer. Can anyone help? Many thanks.

 

[JoeHz]

Any significant changes since 3006.102.4 beta3? It generally worked well but I found it in need of a one or twice daily reboot when all of nothing DNS lookups would all fail. Not using DNS Director.

 

[mavortium]

Merlin, did something change that affects the Pixel disconnecting the radio? I haven't noticed it yet on the release version.

 

[Stefan1578]

Hi, sorry for the English (translated)... I had already reported the problem with the second beta. I no longer have access to the modem connected to the WAN. With the 3004 there were no problems.
ASUS ROG GT-AX6000

 

[RMerlin]

Merlin, did something change that affects the Pixel disconnecting the radio? I haven't noticed it yet on the release version.

I reverted a driver update on the RT-BE96U and GT-BE98_PRO. Sounds odd that this would be causing you an issue, as these are drivers used in Asus released firmwares. But due to lack of time to gather more feedback for it I decided to revert it just in case.

 

[octopus]

Hi, sorry for the English (translated)... I had already reported the problem with the second beta. I no longer have access to the modem connected to the WAN. With the 3004 there were no problems.
ASUS ROG GT-AX6000

If you use ROG theme then you don't use latest RMerlin software.

 

[RMerlin]

Any significant changes since 3006.102.4 beta3? It generally worked well but I found it in need of a one or twice daily reboot when all of nothing DNS lookups would all fail. Not using DNS Director.

$ git log --oneline 3006.102.4-beta3..3006.102.4
0c35adea7e (tag: 3006.102.4) Fix changelog
ae6247a24b Bumped revision to 3006.102.4 final
1615369218 Updated documentation
610bd976b3 rc: add quiet-ra when quieting dnsmasq's DHCP chatter
00a3f70623 Revert "Update RT-BE96U and GT-BE98_PRO wireless dongle driver to 102_37812 builds"
23bc753f62 webui: fix Control-D DoT IPv4 addresses
c3f1d427e6 Updated documentation
5d5c70a2ac webui: fix headers of the split Tools pages

 

[ExtremeFiretop]

Merlin, did something change that affects the Pixel disconnecting the radio? I haven't noticed it yet on the release version.

Was mentioned 4 posts above yours.

Sounds odd that this would be causing you an issue, as these are drivers used in Asus released firmwares. But due to lack of time to gather more feedback for it I decided to revert it just in case.

To me it sounds like since you reverted, he hasn't had the issue: "I haven't noticed it yet on the release version."

If you use ROG theme then you don't use latest RMerlin software.

His model is ROG model (GT-AX6000), he didn't mention using the ROG theme.

 

[octopus]

His model is ROG model (GT-AX6000), he didn't mention using the ROG theme.

Ops. early morning here....