Release Asuswrt-Merlin 3004.388.10 is now available

[John Fitzgerald]

Can someone please tell me what the new password requirements are, and if they are enforced immediately or only when the pw is next changed? I will wait to update if they are enforced immediately -- too many devices and users teach the new pw.

Thanks!

One capital, one special character, one number, length 10 or better. RMerlin relaxed no consecutive character repeat (example, DD).

EDIT: not sure how the enforcement part is going to work. (I changed mine prior to flashing)

 

[zOi-br]

One capital, one special character, length 10 or better. RMerlin relaxed no consecutive character repeat (example, DD).

EDIT: not sure how the enforcement part is going to work. (I changed mine prior to flashing)

Unfortunately it was not found, even with the node turned off. I don't know what else to do. I've tried almost everything, but this router doesn't update anymore. Version 388.9_2 is stuck.

Thank you for your dedication in trying to help me

 

[davidwford]

I agree. Especially for a third party developer working on a free independent solo project. I find it rude that so many make demands with the Me Me Me attitude.

Didn’t realise anyone was making demands or was being rude on this thread? I for one was only reporting an issue that wasn’t there previously. I don’t think anyone has blamed Merlin for the problem, if the problem is in this build, rather than the app, then it could easily be in the GPL or any other closed code than Merlin does have access too. If the post was directed at me, then sorry for how you have interpreted it, but that wasn’t my intention.

 

[John Fitzgerald]

Unfortunately it was not found, even with the node turned off. I don't know what else to do. I've tried almost everything, but this router doesn't update anymore. Version 388.9_2 is stuck.

Thank you for your dedication in trying to help me

What happens if you attempt a GUI reset with the box checked next to it to clear JFFS. Again no nodes should be powered on during any of this.
Have you backed up settings and JFFS, just in case.
I'm guessing this needs a complete wipe and reset and you will need to load all settings from scratch once you can get it going.
Try also, WPS reset like 3 or 4 times in a row then flash. (not flashing between WPS) That works for some.

EDIT: Also re-circle around to using merlinAU to update, now that the nodes are powered off.

EDIT: Also try Restoration tool with the most recent stock Asus firmware, or just keep trying different ways over again but with stock firmware.

 

[ExtremeFiretop]

Got notified last night that my node auto-updated successfully. Quickly logged in by SSH and all appears functional as expected.

As always much appreciate the time and effort RMerlin.

 

[dave14305]

For all the broken HA users, is your integration setup to use HTTPS already?

 

[bartj12]

For all the broken HA users, is your integration setup to use HTTPS already?

Yes, maybe I try to change it to http or ssh prior to updating again

 

[NXIL]

AX-3000 (AX58) dirty upgrade with zero problems or issues.

I did update my router's password before the update to make sure it complied with new requirements.

ASUS Router Password Rules & Recommendations

• Length: Passwords should be at least 10 characters long.
  

• Complexity: Include a combination of uppercase letters, lowercase letters, numbers, and special characters (e.g., !, @, #, $).
  
  
• Uniqueness: Use a different password for your Wi-Fi network and for accessing the router's admin settings.
  
  
• No Consecutive Identical Characters: Avoid passwords with repeating characters, such as "1111" or "aaaa".
  
  
• Avoid Default Passwords: Do not use default credentials like "admin" for your administrator password; set a strong, unique password during the initial setup.

"Admin": in Cliff Stoll's 1989 book "The Cuckoo's Egg", an early book about hacking connected computers, a lot of Unix administrators kept "Admin" and "Admin" as the username/password for their system, including nuclear labs, military systems, Reagan's "Star Wars" contractors, and so on. Book would have been a lot shorter without the sloppy password usage.

In one incident Stoll watched hackers (from overseas, no spoilers) log into Los Angeles Air Force Base's Unix system. He called the duty officer, said "there are foreign intel agents logged into your system".

Duty officer said "That's impossible, it has a password."

Stoll replied "the password is Admin."

The duty officer said "stand by", checked, and then proceeded to unplug the system from wall power as fast as he could.

 

[dbell]

If you don't run Home Assistant, than the integration isn't causing your issues (because the integration runs inside Home Assistant, not on the router.) But, as the integration also logs in on the router, as does the app, maybe there is a problem with the login process?

I for one had never seen the https asus login screen and instructions to install a certificate before installing this version.

I saw the instability with browser login and mobile app with beta 1 - had better success when I switched the access from allow "both" to https only and made sure that the HA integration was configured for https / 8443 as well. Suddenly all started working properly again. I had brought it up in the beta thread: https://www.snbforums.com/threads/asuswrt-merlin-3004-388-10-beta-is-now-available.95740/post-970225

 

[rung]

Tried and failed upgrade the node with the released version. Even with unpair, WPS reset, re-pair procedure. Clients were not happy. Reverted back to beta 2, and all working again. I'll monitor the thread to see if there are similar issues/suggestions or if (more likely) this is PEBKAC. I do know my main router is NOT compliant with the new password rules. Try this next?

 

[DrTurk]

Dirty upgrade on my RT-AX86U from 3004_388.9_2 with no issues so far. Thanks for all you do RMerlin!

 

[AlbumMan]

Dirty update from Alpha 1 directly to Release (skipping betas this time) a few hours ago on the RT-AX3000 node and all is quiet. Nice job @RMerlin !

Being relatively new to having a node, I did as others have recommended and unchecked the node from the GN Pro tab which made all of the IoT's connect to the Main Router across the house which is expected. My reason for having a node was a few of the outdoor smart flood lights right outside the room where the node is, needed a closer / stronger connection. Even after checking (adding) the node back in, the nearby IoT's fail to connect to the node unless they are powered off so they are released by the Main (makes sense again) briefly and powered on. This has been needing done on every update so I'm assuming this is typical behavior having a 3004 node and a 3006 Main.

 

[Stephen Harrington]

For all the broken HA users, is your integration setup to use HTTPS already?

I’m assuming no in my case, as my AX86U only has http access and has never had https enabled. Been so long I can’t quite remember where to check in HA …

 

[aex.perez]

The default HTTPS port is 8443, not 443.

I had the same issue with both Alpha's, Beta and Release, 80 or 8443 no dice, neither worked, deleted and reinstalled it, even linked to my Google account, nothing fixed it.

Left it alone and forgot about it since it's not supported on Merlin FW. Even changed the Router password to meet the new requirements. Then after a few days, launched the app on the iPhone and after deleting it, reinstalling and starting clean and linking to my Google account again with the now current password, the connected device count on the router and nodes came up and were correct like it did in previous FW releases.

Just sharing what I did to get it to start up without erroring out.

Have no idea what I did to fix it, or have it start working (using the term loosely since it's not supported on Merlin FW) even as the Router is set to accept both...

 

[Khadanja]

RT-AX86U

Same issue with Home Assistent Asus Router Integration (https://www.home-assistant.io/integrations/asuswrt/). - understanding that this integration is not supported by Merlin, but a lot of my automations are depending on it. I was not able to access GUI after updating.

After turning off the HA integration i was able to connect to the GUI using HTTPS, with HTTP i got a (I think standard Asus screen) with the message that HTTPS was safer. Even after confirming to connect through HTTP is did not work. Tried to enable/disable HTTP and HTTPS via SSH (nvram set https_enable=1, nvram set http_enable=1 etc.), but this did not make a difference (ChatGPT gave it as suggestion).

This brings me to the very first time that I needed to do a roll-back, 3004.388.9_2 is working again with HA integration on.

I had the same issue on RT-AX86U. Authentication method was set to HTTP, changed it to default now it works over https.

 

[The PyroPath]

I saw the instability with browser login and mobile app with beta 1 - had better success when I switched the access from allow "both" to https only and made sure that the HA integration was configured for https / 8443 as well. Suddenly all started working properly again. I had brought it up in the beta thread: https://www.snbforums.com/threads/asuswrt-merlin-3004-388-10-beta-is-now-available.95740/post-970225

I have it set up as https since day one, which is for quite a few years now. I have had trouble when changing from "both" to "https only" in the past though. When I do that I get locked out of the webinterface, app and what not. So I'm a bit iffy on doing that again Because atm it's working and I dread the moment I get locked out again and a have to start over yet again...

Maybe tomorrow during the day, but not again at 11 pm

 

[Khadanja]

Mine has randomly rebooted thrice in the last 12 hours since I updated. Anyone else experiencing this? Some errors in log before it reboots, not sure what they mean.

Oct  6 20:29:28 kernel: [ERROR pktrunner] buildFlowKey,210: LAN flow is not supported: Rx 0, Tx 6
Oct  6 20:43:26 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=1
Oct  6 20:44:12 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=1025
Oct  6 20:44:53 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=2049
Oct  6 20:46:14 kernel: [ERROR pktrunner] buildFlowKey,210: LAN flow is not supported: Rx 0, Tx 6
Oct  6 20:46:14 kernel: [ERROR pktrunner] __fhwPktRunnerActivate,388: New Mcast flow but key_in<0x003000d9> accel <0>

 

[bartj12]

I had the same issue on RT-AX86U. Authentication method was set to HTTP, changed it to default now it works over https.

Changed the integration to https://asusrouter.vaskivskyi.com/, same result. I'm now using HTTP for Home Assistent to be able to connect via HTTPS to the GUI. Somehow I can't use Home Assistant integration over HTTPS and login via HTTPS at the same time. Connecting to the GUI through HTTP (setting is on both) does not work for me at all.

Still getting the certificate message (see image) when trying to login, but at least i'm able to skip that now to access the router. the App (know it is not supported) does not work anymore (connects, but does not see any device).

Will do some more trial and error later. Any tips/advice is always welcome.

 

[Lee MacMillan]

This release was so quick that I only ran beta 2 for a couple days. Dirty flashed and no issues on my simple setup.

 

[evo17paul]

Dirty upgrade and no dramas. Interface definitely seems more responsive