Release Asuswrt-Merlin 3004.388.10 is now available

[tallytr]

Dirty upgrade to 3004.388.10_2 from 3004.388.10_1. No issues.

Same here. Works.

 

[aex.perez]

Just noticed, that everytime I use the App (testing) I see this in the log after a few seconds of starting it. Both on the nodes and the router.

Oct 31 15:07:43 Router HTTPD: [LOGIN][https][APP] success (192.168.1.173)
Oct 31 15:07:54 Router rc_service: cfg_server 1498:notify_rc stop_fw_check
Oct 31 15:07:54 Router custom_script: Running /jffs/scripts/service-event (args: stop fw_check)
Oct 31 15:07:55 Router rc_service: cfg_server 1498:notify_rc start_fw_check
Oct 31 15:07:55 Router custom_script: Running /jffs/scripts/service-event (args: start fw_check)

Not so with logging in to the GUI/Web. Doesn't appear to cause any issues but I did get this, the first time I use the App but have not been able to reproduce it so maybe coincidence

Oct 31 15:03:32 Router kernel: Init chrdev /dev/idp with major 190
Oct 31 15:03:32 Router kernel: tdts: tcp_conn_max = 8000
Oct 31 15:03:32 Router kernel: tdts: tcp_conn_timeout = 300 sec
Oct 31 15:03:34 Router kernel: SHN Release Version: 2.0.2 36f59aa
Oct 31 15:03:34 Router kernel: UDB Core Version: 0.2.20
Oct 31 15:03:34 Router kernel: Init chrdev /dev/idpfw with major 191
Oct 31 15:03:34 Router kernel: IDPfw: flush fc
Oct 31 15:03:34 Router kernel: IDPfw: IDPfw is ready
Oct 31 15:03:34 Router kernel: sizeof forward pkt param = 280
Oct 31 15:03:51 Router kernel: IDPfw: Exit IDPfw
Oct 31 15:03:51 Router kernel: mod epilog takes 0 jiffies
Oct 31 15:03:51 Router kernel: IDPfw: Exit IDPfw
Oct 31 15:03:51 Router kernel: Exit chrdev /dev/idpfw with major 191
Oct 31 15:03:51 Router kernel: Exit chrdev /dev/idp with major 190

 

[shivaprasadh]

Please give these test builds a try. They include the fix provided by Asus for the httpd server crashing when logging in using the APP API.

OneDrive

www.asuswrt-merlin.net

This is the only change at this time.

Dirty upgrade from 3004.388.10 to 3004.388.10_1-g74977d9bf4. Now the AsusRouter iOS App is working as expected. Thank you so much @RMerlin for the Test Build, which fixes this issue.

 

[MacG32]

Updated and all is running smooth. Thank you @RMerlin for everything!

 

[RMerlin]

Just noticed, that everytime I use the App (testing) I see this in the log after a few seconds of starting it. Both on the nodes and the router

It just means that the application automatically triggers a check for new firmware whenever you connect with it. Nothing unusual there, it`s probably simply how it works.

 

[Jeep]

Dirty upgrade from 3004.388.10 to 3004.388.10_2 on main router, ~90 minutes in and smooth as silk. Great stuff! (AiMesh node still on stock.)

 

[aex.perez]

It just means that the application automatically triggers a check for new firmware whenever you connect with it. Nothing unusual there, it`s probably simply how it works.

Nice to know. Because I run Scribe, it generates the entry in the systen log I'll just ignore it
From my service-event in /jffs/scripts...
/jffs/scripts/scribe service_event "$@" & # added by scribe

 

[davidwford]

Asus Router app works fine with new build, thanks RMerlin!

 

[Unetwork]

Update completed from version 3004.388.10 to the new version 3004.388.10_2.

Rock solid so far.

Thank you RMerlin for your work...

 

[Vuelta91]

Everything updated to 10_2.
Everything is fine except for the inability to update AiMesh nodes remotely.
Thanks @RMerlin

 

[jksmurf]

Everything is fine except for the inability to update AiMesh nodes remotely.

Could you please expand on this, do you mean through the WebGui?

I don’t have an issue doing this if I VPN (Tailscale or Wireguard) to my remote router and upload FW to the nodes via the Router’s WebGui (where you use a Node Login screen), for nodes that do not support Merlin or (my preference) via the very capable MerlinAU Addon which does that “locally” if you have it installed on the Node (for nodes supporting Merlin and thus amtm).

 

[MacG32]

Parental Controls didn't pick up the time change and locked the network for my child an hour earlier. A reboot fixed it.

 

[Vuelta91]

Could you please expand on this, do you mean through the WebGui?

I don’t have an issue doing this if I VPN (Tailscale or Wireguard) to my remote router and upload FW to the nodes via the Router’s WebGui (where you use a Node Login screen), for nodes that do not support Merlin or (my preference) via the very capable MerlinAU Addon which does that “locally” if you have it installed on the Node (for nodes supporting Merlin and thus amtm).

via WebGui in 2 instalations diferents, one with Wireguard and the other whitout Wireguard. In local net, without problems.

 

[jksmurf]

via WebGui in 2 instalations diferents, one with Wireguard and the other whitout Wireguard. In local net, without problems.

Hmm odd. Maybe start a new separate thread detailing with screenshots or logs where appropriate, your steps taken and specifically what happens when you try to update FW remotely, error messages or observations. Include (blanking private information) screenshots or logs showing VPN is connected.

As above if the VPN tunnel is working correctly there should be no impediment to you accessing the WebGUI on the same router IP address as you do locally and updating the FW via the GUI.

 

[saison2023]

Dirty upgraded my RT-AX86U from 3004_388.10 to 3004_388.10_2.
Update went fine and router rebooted well.
Thank you very much for your work

 

[Diablo99]

Dirty upgrade from 3004.388.10 to 3004.388.10_2 on my RT-AX86U.
Works good.

So now I can use the Asus router app?

 

[visortgw]

Dirty upgrade from 3004.388.10 to 3004.388.10_2 on my RT-AX86U.
Works good.

So now I can use the Asus router app?

That's what fix was for. Try it...

 

[sanxion]

Probably a stupid question, but can anybody explain what "Dirty upgrade" is?

I suppose is to upgrade without doing a factory reset, but I'm not sure.

 

[ColinTaylor]

Probably a stupid question, but can anybody explain what "Dirty upgrade" is?

I suppose is to upgrade without doing a factory reset, but I'm not sure.

Correct. It's a misnomer really as it's a "normal" update. I believe it comes about as attempted humour to indicate the opposite of a "clean install" (that Microsoft Windows users are familiar with).