Release Asuswrt-Merlin 3006.102.4 is now available

[cc666]

Technically yes it is a bug. One that has been there for a while with the Network Map. The Network Map just gets wonky from time to time. As others already indicated, the Network Map may fix itself after a period of time or if you kill and restart the Network Map process. I've found that when making a change to a Guest Network Pro profile, sometimes the profile number of client indicator (indicated by the yellow highlight box in the image below) doesn't refresh properly for a period of time. Likely gets refreshed when the Guest Network Pro profile's client lease time is renewed.
View attachment 65889

This does not happen on the latest stock firmware.

Also another dilema, i decided to reset and input all my settings manually. For some reason the router would not connect to the internet after the reset, saying DHCP server error. I tried everthing and nothing fixed the problem. I then reflashed the stock firmware, uoloaded a config file and everthing was back to normal. Why did that happen? any idea

CC

 

[bennor]

This does not happen on the latest stock firmware.

May not have happened for you, but I've experienced the Network Map not properly updating and the Guest Network Pro profile client list and client tab not updating correctly on pretty much all the iterations of the stock Asus 3006.102.x firmware for the RT-AX86U Pro. I normally just ignore it when it happens as it usually corrects itself (in both locations) after a short period of time. YMMV and all that.

 

[CaptainSTX]

I was using only AES. Besides i think it would not connect in that case completely.

One way to test is setup a guest network that is open with no encryption and see if the problematic clients will connect. If they will then the problem is probably the encryption. Not recommending you run long term with no encryption and what I did was install an old travel router as an AP just for this device with AES-TKIP encryption.

 

[cc666]

May not have happened for you, but I've experienced the Network Map not properly updating and the Guest Network Pro profile client list and client tab not updating correctly on pretty much all the iterations of the stock Asus 3006.102.x firmware for the RT-AX86U Pro. I normally just ignore it when it happens as it usually corrects itself (in both locations) after a short period of time. YMMV and all that.

OK, any ideas on not connecting to internet? I had to go back to stock. I tried everything.

CC

 

[bennor]

OK, any ideas on not connecting to internet? I had to go back to stock. I tried everything.

No idea without more information. Where were you seeing the "DHCP server error"? Did you check the router log to see what it indicated for the internet loss?

 

[128bit]

May not have happened for you, but I've experienced the Network Map not properly updating and the Guest Network Pro profile client list and client tab not updating correctly on pretty much all the iterations of the stock Asus 3006.102.x firmware for the RT-AX86U Pro.

. . . which segues nicely to this question: what's the latest guidance on having the mesh node on merlinware as opposed to stockware?

 

[bbunge]

I "tested" 3006.102.4 on my AX86U Pro again yesterday. Enabled DoT, DNS Director (Router) and installed AMTM, Entware and Diversion. Everything seemed to be working but out of curiosity I opened a terminal and ran "stubby -l" to check the DoT operation. Normally I should see the connections going to the upstream resolvers. But, there was no results shown. I removed Diversion and turned off DNS Director and tried "stubby -l" again. Nothing. Sorry but I did not check the router log before I went back to Asus firmware. Am reporting this as a possible issue.

Update: Back to 3006.102.4. Set up the AX86U Pro with pretty basic settings. To test DoT I set up Cloudflare (1.1.1.1, 1.0.0.1) in the DoT area. I then went to "https://one.one.one.one/help/" to check if the router was connected to Cloudflare and if it was using DoT. It was. Back to the command prompt where "stubby -l" just showed that Stubby had started. Web research showed that "stubby -v 7" should show the connections. It didn't but as I felt convinced that the DoT was working I moved on to finish configuring the router.

 

[cc666]

No idea without more information. Where were you seeing the "DHCP server error"? Did you check the router log to see what it indicated for the internet loss?

The WAN port was not being recognized.

CC

 

[joegreat]

I "tested" 3006.102.4 on my AX86U Pro again yesterday. Enabled DoT, DNS Director (Router) and installed AMTM, Entware and Diversion. Everything seemed to be working but out of curiosity I opened a terminal and ran "stubby -l" to check the DoT operation. Normally I should see the connections going to the upstream resolvers. But, there was no results shown. I removed Diversion and turned off DNS Director and tried "stubby -l" again. Nothing. Sorry but I did not check the router log before I went back to Asus firmware. Am reporting this as a possible issue.

Same behavior here - but stubby seems to work - as you can verify with https://ipleak.net/ - it shows the configured (local) Cloudflare DNS servers.

 

[przemekwawa]

One way to test is setup a guest network that is open with no encryption and see if the problematic clients will connect. If they will then the problem is probably the encryption. Not recommending you run long term with no encryption and what I did was install an old travel router as an AP just for this device with AES-TKIP encryption.

To be honest, I don’t understand why it stopped working. I created a guest Wi-Fi network with Open System, and it was stable. I couldn’t get the MusicCast app to work, but I might have to reinstall it. I was able to run network radio. However, when I switched back to the default network, it stopped working.

I’ve been installing the newest firmware for a long time, and the whole time, WPA2 - AES encryption was set. The manual says that my device is capable of “WEP, WPA2-PSK (AES), Mixed Mode,” so what happened?
I will have to check later with tcpdump, but now I could use workaround with micro router in bridge mode.

 

[Dedel66]

To be honest, I don’t understand why it stopped working. I created a guest Wi-Fi network with Open System, and it was stable. I couldn’t get the MusicCast app to work, but I might have to reinstall it. I was able to run network radio. However, when I switched back to the default network, it stopped working.

I’ve been installing the newest firmware for a long time, and the whole time, WPA2 - AES encryption was set. The manual says that my device is capable of “WEP, WPA2-PSK (AES), Mixed Mode,” so what happened?
I will have to check later with tcpdump, but now I could use workaround with micro router in bridge mode.

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.

 

[bennor]

The WAN port was not being recognized.

Was that an error from the router log? If so what was the exact error message? What were the messages before and after that specific error message?

How was the WAN settings configured? What is the router's WAN port connected to upstream? Are the WAN settings under Merlin the exact same as under stock Asus firmware? Sounds stupid, but did you try replacing the WAN cable as a troubleshooting step?

Are any addon scripts installed under Asus-Merlin?

You indicated you reset the router, what type of reset did you do? Did you perform a hard factory reset? If not, as a troubleshooting step perform a hard factory reset. Sometimes it fixes weird issues the other reset doesn't fix.

In short, provide more information and context to your WAN issue under Asus-Merlin firmware including what troubleshooting steps other than installing stock Asus firmware, how the WAN is configured (readable screen shots help) and if possible post actual router logs for others to review.

 

[pdc]

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?

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.

 

[Pocah.H]

Whats this new privacy agreement?
Honestly, I am a bit annoyed that the router now forces us to agree, without a warning that this has been included in the latest version of the software.

 

[brill]

Some will print/save each GUI page where they've made changes to PDF so they can copy and paste the changes later. There are various methods and or scripts (YazDHCP for example) one can use to export and import manual DHCP reservations which can save some time. But in the end, a reset and manual configuration is going to take a little bit of time.

I used this method which I 'believe' captures all the config:

ssh to AP
PWD = /tmp/home/root
nvram show > 88u-pro-conf.txt
exit
ssh admin@x.x.x.x "cat /tmp/home/root/88u-pro-conf.txt" > 88u-pro-conf.txt
ssh back in and delete temp file if needed

*UPDATE
This may not show all settings. I had to adjust beacon intervals and the live value doesn't appear. So it would seem only some parts of the config are captured.

 

[Pocah.H]

Yeah, actually, I am really furious that there is a new agreement with this release and there was no real warning before I downloaded it.
I really do not agree with the what seems to be the router is now able to download stuff for itself even if I tell it not to.
It also won't go back to an older release.
This really is annoying.

 

[Makaveli]

Yeah, actually, I am really furious that there is a new agreement with this release and there was no real warning before I downloaded it.
I really do not agree with the what seems to be the router is now able to download stuff for itself even if I tell it not to.
It also won't go back to an older release.
This really is annoying.

This is your second post about the same thing.

Totally out of merlin's control and a requirement from asus.

 

[Ripshod]

..... and also a requirement of your government.

 

[bennor]

It also won't go back to an older release.

Why cannot you roll back to earlier firmware, versions before Asus implemented the new EULA agreements and updates sometime last year? Does changing the nvram downgrade check pass value not work? (ETA: Assuming one has a router running firmware 3006.102_37000 or greater.)

Per the 3006 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.

 

[Alexander Savkin]

Hello everyone.
If I upgrade from version 3004.388.8_4 to 3006.102.4, if something goes wrong, will I be able to go back to version 3004.388.8_4 or will it be impossible?