[Release] Asuswrt-Merlin 384.16 (and 384.13_6) are now available

[Centrifuge]

children are the best network monitors I know).

Do these children have physical/virtual access to your router while you are indisposed by any chance? Check this too.

 

[HorseCalledHorse]

Mesh or no mesh set up for you guys?

No AiMesh for me. Not using Smart Connect either. Each band is set to a specific channel.

 

[HorseCalledHorse]

Do these children have physical/virtual access to your router while you are indisposed by any chance? Check this too.

No, they don't. They just whine loudly whenever they don't have internet access, wherever they are in the world

 

[teo1966]

Same thing just happened to my ac86u with a similar log. Completely lost WiFi and had to reboot. All is good for now

me to see log ac88u whit 2x ac68u in aimesh
Apr 11 12:02:18 dnsmasq-script[374]: [SEND_AMAS_NODE_EVENT4684)] ERROR connecting:No such file or directory.
Apr 11 12:04:38 dnsmasq-script[374]: connect error: No such file or directory
Apr 11 12:04:38 dnsmasq-script[374]: [SEND_AMAS_NODE_EVENT4684)] ERROR connecting:No such file or directory.
Apr 11 12:05:18 dnsmasq-script[374]: connect error: No such file or directory
Apr 11 12:05:18 dnsmasq-script[374]: [SEND_AMAS_NODE_EVENT4684)] ERROR connecting:No such file or directory.
Apr 11 12:08:18 dnsmasq-script[374]: connect error: No such file or directory
Apr 11 12:08:18 dnsmasq-script[374]: [SEND_AMAS_NODE_EVENT4684)] ERROR connecting:No such file or directory.
Apr 11 12:12:48 dnsmasq-script[374]: connect error: No such file or directory
Apr 11 12:12:48 dnsmasq-script[374]: [SEND_AMAS_NODE_EVENT4684)] ERROR connecting:No such file or directory.
Apr 11 12:14:39 dnsmasq-script[374]: connect error: No such file or directory
Apr 11 12:14:39 dnsmasq-script[374]: [SEND_AMAS_NODE_EVENT4684)] ERROR connecting:No such file or directory.
Apr 11 12:15:48 dnsmasq-script[374]: connect error: No such file or directory
Apr 11 12:15:48 dnsmasq-script[374]: [SEND_AMAS_NODE_EVENT4684)] ERROR connecting:No such file or directory.
Apr 11 12:15:48 dnsmasq-script[374]: connect error: No such file or directory
Apr 11 12:15:48 dnsmasq-script[374]: [SEND_AMAS_NODE_EVENT4684)] ERROR connecting:No such file or directory.
Apr 11 12:17:18 dnsmasq-script[374]: connect error: No such file or directory
Apr 11 12:17:18 dnsmasq-script[374]: [SEND_AMAS_NODE_EVENT4684)] ERROR connecting:No such file or directory.
Apr 11 12:22:20 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc DCC:E2:7E:12D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Apr 11 12:22:20 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc DCC:E2:7E:12D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Apr 11 12:23:18 dnsmasq-script[374]: connect error: No such file or directory
Apr 11 12:23:18 dnsmasq-script[374]: [SEND_AMAS_NODE_EVENT4684)] ERROR connecting:No such file or directory.
Apr 11 12:24:40 dnsmasq-script[374]: connect error: No such file or directory
Apr 11 12:24:40 dnsmasq-script[374]: [SEND_AMAS_NODE_EVENT4684)] ERROR connecting:No such file or directory

 

[Jasso]

Since the upgrade to 384.16 on my AC88u I've noticed this flooding my syslog, any idea what the cause is?

Apr 5 20:00:21 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:21 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:21 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:21 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:21 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:21 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:21 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:21 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:21 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:22 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:22 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:22 dnsmasq[323]: failed to send packet: Operation not permitted

Did you get a fix for this? I had the same problem but got no answer ... back to 384.15 and OK

 

[htismaqe]

I did a full reset and upgraded from 384-15 stable to 384-16 stable. I didn't install any alphas or betas previously.

I reset to factory defaults, loaded the new FW, factory reset again.

Everything appears to be working BUT...

The network map tab is extremely slow to load. When first logging in that's the default page, so it hangs for a bit there. If I wait, it finally loads and I can navigate as normal to any tab but the network map tab. It loads slowly no matter where in the GUI I was before.

 

[cmillar6]

Nope, I went back to 384.15 as well. Not really sure what the message means but figured it couldn't be good.

 

[toyosup88]

Mesh or no mesh set up for you guys?

No mesh for me

 

[ECHK1]

Lan, Switch Control, I enable "Bonding/ Link aggregation" and connect a link aggregation .. it keep disassociated and deauth ...

Any hints I can resolve it ?

-------------------------------------------------------------------------------
Apr 11 18:02:03 syslog: WLCEVENTD wlceventd_proc_event(401): eth2: Disassoc xx:xx:xx:xx:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Apr 11 18:02:03 syslog: WLCEVENTD wlceventd_proc_event(386): eth2: Deauth_ind xx:xx:xx:xx:xx:xx, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Apr 11 18:02:31 syslog: WLCEVENTD wlceventd_proc_event(386): eth2: Deauth_ind xx:xx:xx:xx:xx:xx, status: 0, reason: Disassociated due to inactivity (4)
Apr 11 18:02:31 syslog: WLCEVENTD wlceventd_proc_event(401): eth2: Disassoc xx:xx:xx:xx:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Apr 11 18:03:36 syslog: WLCEVENTD wlceventd_proc_event(386): eth2: Deauth_ind xx:xx:xx:xx:xx:xx, status: 0, reason: Disassociated due to inactivity (4)
Apr 11 18:03:36 syslog: WLCEVENTD wlceventd_proc_event(401): eth2: Disassoc Exx:xx:xx:xx:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Apr 11 18:04:13 syslog: WLCEVENTD wlceventd_proc_event(420): eth2: Auth 88:xx:xx:xx:xx:xx:xx, status: 0, reason: d11 RC reserved (0)
Apr 11 18:04:13 syslog: WLCEVENTD wlceventd_proc_event(449): eth2: Assoc xx:xx:xx:xx:xx:xx, status: 0, reason: d11 RC reserved (0)
Apr 11 18:06:37 syslog: WLCEVENTD wlceventd_proc_event(386): eth2: Deauth_ind xx:xx:xx:xx:xx:xx, status: 0, reason: Disassociated due to inactivity (4)
Apr 11 18:06:37 syslog: WLCEVENTD wlceventd_proc_event(401): eth2: Disassoc xx:xx:xx:xx:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)

 

[ECHK1]

I have fix the channel in 2.4 & 5

Apr 11 22:38:44 acsd: COEX: downgraded chanspec 0x1805 to 0x1003: channel 1 used by exiting BSSs
Apr 11 22:38:44 acsd: selected channel spec: 0x1003 (3)
Apr 11 22:38:44 acsd: Adjusted channel spec: 0x1003 (3)
Apr 11 22:38:44 acsd: selected channel spec: 0x1003 (3)

anyway to fix this ? thanks in advance

 

[JWoo]

Asus has a new version for the RT-AX58U which is 3.0.0.4.384.8601 and the only content is "improved connection stability". Not clear whether this is new WIFI/ethernet drivers or what.

 

[octopus]

Today I lost my internet when my ip number changed. At the same time, isp forgot to send with some dns servers.
Took me a while to figure this out. Looking for some working dns: now it works at the moment.

However, discovered that the DDNS update did not work when using WAN dns settings.
Receives "DDNS status Request error! Please try again." And the exclamation point appears in connected DNS.

Seems not update /tmp/inadyn.cache
EDIT: Really strange, /var/run/inadyn.pid was blocking update. Deleted it and working again.
@RMerlin

 

[Vexira]

Today I lost my internet when my ip number changed. At the same time, isp forgot to send with some dns servers.
Took me a while to figure this out. Looking for some working dns: now it works at the moment.
However, discovered that the DDNS update did not work when using WAN dns settings.
Receives "DDNS status Request error! Please try again." And the exclamation point appears in connected DNS.

Try cloud flare DNS, I use open DNS with DNS O Matic to update my ddns

 

[RMerlin]

I have fix the channel in 2.4 & 5

Apr 11 22:38:44 acsd: COEX: downgraded chanspec 0x1805 to 0x1003: channel 1 used by exiting BSSs
Apr 11 22:38:44 acsd: selected channel spec: 0x1003 (3)
Apr 11 22:38:44 acsd: Adjusted channel spec: 0x1003 (3)
Apr 11 22:38:44 acsd: selected channel spec: 0x1003 (3)

anyway to fix this ? thanks in advance

Set 2.4 GHz to 20 MHz. 40 MHz is nearly impossible to achieve due to the amount of interference on that band - what you saw is simply your router downgrading bandwidth because of that.

 

[octopus]

Try cloud flare DNS, I use open DNS with DNS O Matic to update my ddns

Thanks, I found some other from my provider. Seems faster then "original" one.

 

[WildMW]

Reporting 16 happy hours after applying 384.16 to my RT-AX58U last night.

I had been living with terrible router firmware (AT&T combo modem) before switching to Spectrum with their basic cable modem last month and buying an RT-AX58U. FIOS isn't offered in my area, so I cannot take advantage anything like this router's full performance, but I am now blissfully returned to ASUSWRT-Merlin after several years hiatus.

My router needs are humble but I appreciate having rock-solid, community tested firmware. I used to run ASUSWRT-Merlin on a NT-66U but the ex-wife got that in the divorce. I also ran Tomato on an old Netgear router with decent results but I missed the beautiful design of ASUSWRT-Merlin. It's the #1 reason for buying an ASUS router in my opinion.

Thanks for staying with this project through the years, RMerlin! Donation coming your way.

CORRECTION: Donation completed

 

[maus73]

Can anyone help with the following errors present on the log? I get this every restart on 384.16. Have done a full reset to Factory, re-installation of 384.16, then on to manual config restore (refer M&M), but the messages still appear. No other behavior issues, noting tat Wifi is kept with Smart Connect disabled due to disconnect issues since 384.13.

May 5 17:05:17 wsdd2[1115]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
May 5 17:05:17 wsdd2[1115]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
May 5 17:05:19 modprobe: module scsi_wait_scan not found in modules.dep
May 5 17:05:19 modprobe: module uas not found in modules.dep
May 5 17:05:19 modprobe: module mbcache not found in modules.dep
May 5 17:05:19 modprobe: module jbd not found in modules.dep
May 5 17:05:19 modprobe: module ext3 not found in modules.dep
May 5 17:05:19 modprobe: module ext4 not found in modules.dep
May 5 17:05:19 modprobe: module ext2 not found in modules.dep
May 5 17:05:19 modprobe: module btusbdrv not found in modules.dep
May 5 17:05:20 kernel: sd 0:0:0:0: [sda] No Caching mode page found
May 5 17:05:20 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through

 

[rd1600]

Hi All,

After upgrading to 384.16 on my 86U, I noticed that the actual Wifi channel on 2.4 band is not the same as what I set the control channel to. I have my control channel as 1 but the router is broadcasting on channel 2. I ran Wifi-analyzer and it indeed is on channel 2.

See pic.

Any idea what can be the issue here?

 

[ATLga]

Hi All,

After upgrading to 384.16 on my 86U, I noticed that the actual Wifi channel on 2.4 band is not the same as what I set the control channel to. I have my control channel as 1 but the router is broadcasting on channel 2. I ran Wifi-analyzer and it indeed is on channel 2.

See pic.

Any idea what can be the issue here?

View attachment 22573

I had a similar issue running stock firmware several weeks ago. Never did find the cause of it, but unplugging it from power for a few minutes and then powering up resolved it. Not just a restart but complete power off.

 

[Grisu]

I had 2 86Us, one has been ok and the other didn't apply WiFi settings (and maybe some others too) without reboot.
Later I learned only need to SSH and 'service restart_wireless' did it, or disable 2,4G and reenable in GUI.