Release Asuswrt-Merlin 3004.388.4 is now available

[Damit1]

1h run, done whole system reboot.
The only thing that bugs me, is 5Ghz kicks in 1m later- but Merlin mentioned earlier it is due to DFS 160Mhz scanning.

31 devices are all online...

 

[aex.perez]

Rock Solid Router AX88 Nodes AX86, Evevrything connected, Everything running, WiFi Solid 160Mhz stable

No surprises!

 

[BenWish]

GT-AX600, RT-AX86U and RT-AX88U all up without any hickup. Up and running with dirty upgrade. Thanks Merlin!

 

[charlie2alpha]

Upgraded my RT-AX86U without issues. Haven't reset it ever since I bought it, 2 years ago. Not using 160MHz on my Wi-Fi, only have one device that can use it and takes way to long to perform the DFS scanning. Also, the 5GHz spectrum here is quite populated. 160MHz and higher is really meant for 6Ghz, but the average user won't have such equipment until a few years later. Users in this forum hardly count, we're not the average user!

 

[spykos]

@RMerlin

Just tried the 3004.388.4 as I missed the beta 3 one on my AX86U and ddns-start script does not kick in when you disconnect from the GUI under network map. My understanding from your posts in the beta thread was that it was fixed in beta 3. Is this not correct ? Also noticed that even if I see the new IP in GUI wan0_realip_ip is empty.

​

 

[dbell]

Couple of logging anomalies but not sure what / if they are affecting anything:

Aug 22 10:41:42 dnsmasq-script[1757]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory

but that file does exist in /jffs.

And then:

Aug 22 10:41:38 wlceventd: main(1239): wlceventd Start...
Aug 22 10:41:38 networkmap: Error locking /var/lock//usr/networkmap/nmp_conv_type.js.lock: 2 No such file or directory
Aug 22 10:41:38 networkmap: Error unlocking -1: 9 Bad file descriptor
Aug 22 10:41:38 networkmap: Error locking /var/lock//usr/networkmap/nmp_vendor_type.js.lock: 2 No such file or directory
Aug 22 10:41:38 networkmap: Error unlocking -1: 9 Bad file descriptor
Aug 22 10:41:38 networkmap: Error locking /var/lock//usr/networkmap/nmp_bwdpi_type.js.lock: 2 No such file or directory
Aug 22 10:41:38 networkmap: Error unlocking -1: 9 Bad file descriptor
Aug 22 10:41:38 kernel: br0: port 3(eth5) entered learning state

The nmp*_type.js files are in /usr/networkmap but there are no corresponding .lock files in /var/lock.

Lastly, 160mhz won't stick for more than about 30 secs after `dfs state: in state monitoring` starts and dropping back to `dfs state: idle` unless the channel is Auto. Log levels are debug/all and there is no hint as to why; no mention of radar detection for example. Also curious that I don't see any chanspec output detailing the step down from 160 to 80. When I tried Auto it chose 116 and was stable for the few minutes I tried before trying with fixed channel again.

 

[PR3MIUM]

WPS is not working for me.
Did a Hard Reset and WPS is turned ON, but no light is on to indicate that WPS is turned ON.

kernel: CFGP2P-ERROR) wl_cfgp2p_find_ndev :  p2p inactive
kernel: wfd_unregisterdevice Successfully unregistered ifidx 4 wfd_idx 0
kernel: CFG80211-ERROR) wl_add_remove_eventmsg : Get event_msgs error (-19)
kernel: CFG80211-ERROR) wl_cfg80211_add_virtual_iface : Recvd application provided mac address:xx:xx:xx:xx:xx:xx

 

[octopus]

Updated two routers and working fine.

160MHz working fine and stays connected at 160mhz. maby therefore my Aimesh keeps it connected at 160MHz channel.

a little wonder though, this doesn't seem to work as it should.

update-notification doesn't trigger when bell icon blinks.
Working when trigger it manually. (update-notification)

the ssd disk mounting doesn't work. Neither after reboot nor after software update. Had to manually power off/on the ssd drive to mount.

Thank you for new build!

 

[ZeustheAsus]

wow final build, just moved to RMerlin from stock firmware last week

still on 388.2_2 but maybe ill upgrade my GT-AX6000 tonight. Didnt realize 388.2_2 was from April , I'm guessing theres a ton of changes in general?

been rock solid so far though, I dont think ill be going back to stock asus

the non-rog build makes my eyeballs not cringe upon browsing

 

[ColDen]

Dirty upgrade from beta3 without issues.

Thanks RMerlin!

 

[AntonK]

Asuswrt-Merlin 388.4 is purring like a kitten here. Thanks RMerlin!

 

[ColinTaylor]

Couple of logging anomalies but not sure what / if they are affecting anything:

Aug 22 10:41:42 dnsmasq-script[1757]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory

but that file does exist in /jffs.

And then:

Aug 22 10:41:38 wlceventd: main(1239): wlceventd Start...
Aug 22 10:41:38 networkmap: Error locking /var/lock//usr/networkmap/nmp_conv_type.js.lock: 2 No such file or directory
Aug 22 10:41:38 networkmap: Error unlocking -1: 9 Bad file descriptor
Aug 22 10:41:38 networkmap: Error locking /var/lock//usr/networkmap/nmp_vendor_type.js.lock: 2 No such file or directory
Aug 22 10:41:38 networkmap: Error unlocking -1: 9 Bad file descriptor
Aug 22 10:41:38 networkmap: Error locking /var/lock//usr/networkmap/nmp_bwdpi_type.js.lock: 2 No such file or directory
Aug 22 10:41:38 networkmap: Error unlocking -1: 9 Bad file descriptor
Aug 22 10:41:38 kernel: br0: port 3(eth5) entered learning state

The nmp*_type.js files are in /usr/networkmap but there are no corresponding .lock files in /var/lock.

Those are all normal networkmap messages that have been present for years. Typically seen after you issue a reboot.

Lastly, 160mhz won't stick for more than about 30 secs after `dfs state: in state monitoring` starts and dropping back to `dfs state: idle` unless the channel is Auto. Log levels are debug/all and there is no hint as to why; no mention of radar detection for example. Also curious that I don't see any chanspec output detailing the step down from 160 to 80. When I tried Auto it chose 116 and was stable for the few minutes I tried before trying with fixed channel again.

Normal behaviour unless you have a 160MHz capable client currently connected.

 

[prosperot]

A dirty upgrade attemped failed. It gave no errors but really slow internetspeeds.
A fresh upgrade did the job, no problems since.

 

[dbell]

Those are all normal networkmap messages that have been present for years. Typically seen after you issue a reboot.


Normal behaviour unless you have a 160MHz capable client currently connected.

Is it though; shouldn't the dfs state remain as in-service monitoring unless it is tripped by radar ? Looks like @octopus has had that for 10+ hrs. That has been my prior experience and this time around my laptop wouldn't connect at anything but 80mhz using channel 36 but did connect at 160mhz when using auto.

 

[brummygit]

In 2023, having to perform a factory reset and reprogram is pure and utter BS. I'm not going in and reprogramming a thing. I've been a CCIE for 20 years and the day I have to go in and do a factory reset to upgrade a Cisco device is the day I quit I.T.

I also work in IT, but unfortunately these are consumer devices and you simply can't just pull in your config from a text file like you can on your cisco routers. There was a cryptic note in the release notes for firmware 3.0.0.4.388.23110 that stated a factory reset is required. Also sometimes previous bug can cause inaccessible parameters to be corrupted. It's frustrating I agree.

ASUS RT-AX88U Pro will qualify for the ‘Engineered for Intel® Evo™’ designation only when used with firmware version 3.0.0.4.388.23110 or greater. Please download that update to ensure the best experience in compatibility and performance. After Firmware upgrade, please do factory reset to apply the changes.

Sadly Asus choose to store some default config values such that we can't just write them easily from either UI or a CLI, and sometimes a factory reset is the only way to get them re-written.

 

[Paliv]

Waiting patiently to give this a shot tonight when no one is working or watching something. Have to do a reset and initialize since I'll be coming from stock.

 

[AntonK]

Does anyone know if this is just standard background noise, or does it represent a misconfiguration, etc.? Thanks.

Aug 21 22:43:04 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 21 22:43:07 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 1000 mbps full duplex
Aug 21 22:43:20 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 21 22:43:22 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 1000 mbps full duplex
Aug 21 23:28:48 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 21 23:28:51 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 100 mbps full duplex
Aug 22 07:51:05 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 22 07:51:09 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 1000 mbps full duplex
Aug 22 11:58:04 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 22 11:58:06 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 100 mbps full duplex
Aug 22 12:30:18 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 22 12:30:22 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 1000 mbps full duplex
Aug 22 15:32:17 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 22 15:32:19 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 1000 mbps full duplex
Aug 22 15:32:33 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 22 15:32:36 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 1000 mbps full duplex

 

[IcerJo]

Everything is stable but I am getting spammed with
Aug 22 14:49:58 Mastiff: init

Edit: I misread a post/fix from the beta thread, I enabled the Disable:Asusnat Tunnel and all is well.

 

[XIII]

Upgraded from 3004.388.4 Beta 3 to 3004.388.4_0 on my GT-AX6000.

Probably just a coincidence, but PS Remote Play is no longer working... (worked fine 2 days ago with Beta 3)

 

[maxbraketorque]

Does anyone know if this is just standard background noise, or does it represent a misconfiguration, etc.? Thanks.

Aug 21 22:43:04 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 21 22:43:07 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 1000 mbps full duplex
Aug 21 22:43:20 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 21 22:43:22 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 1000 mbps full duplex
Aug 21 23:28:48 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 21 23:28:51 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 100 mbps full duplex
Aug 22 07:51:05 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 22 07:51:09 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 1000 mbps full duplex
Aug 22 11:58:04 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 22 11:58:06 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 100 mbps full duplex
Aug 22 12:30:18 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 22 12:30:22 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 1000 mbps full duplex
Aug 22 15:32:17 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 22 15:32:19 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 1000 mbps full duplex
Aug 22 15:32:33 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 22 15:32:36 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 1000 mbps full duplex

Your signature says you have a GT-AX6000. eth5 on the GT-AX6000 is the 2.5 gbps LAN port.