[Release] Asuswrt-Merlin 384.13 is now available

[Wallace_n_Gromit]

Maybe the other router has developed a bad contact between the cpu heat sink and cpu?

That may be true. I updated both routers to 384.13. Before the update BOTH routers were performing very similar heat wise. I am waiting for a ebay order of thermal pads/fans before I take on opening the case and taking a look. right now using active cooling -- that one is still running hot (not to the touch on the case, just on the GUI)

 

[fiasko]

Should be in the LAN 1 port.

That did the trick. Thanks you!
Now the router works with 384.13 firmware. I wonder what has changed in the WAN port code. Why after all these years it suddenly stops working. Especially when my AC88U and AC66U (with Johns firmware) works when WAN port is used to connect the AP in LAN.

 

[skeal]

Something else I noticed on the AX88U running 384.13. When denying internet access to a device in the client list I get this and my whole network loses access to the internet.

Aug  2 08:09:59 rc_service: httpd 1163:notify_rc restart_firewall
Aug  2 08:09:59 nat: apply nat rules (/tmp/nat_rules_eth0_eth0) error!
Aug  2 08:09:59 custom_script: Running /jffs/scripts/firewall-start (args: eth0)
Aug  2 08:10:00 Skynet: [%] Startup Initiated... ( skynetloc=/tmp/mnt/stuff/skynet )

 

[Bamba]

That did the trick. Thanks you!
Now the router works with 384.13 firmware. I wonder what has changed in the WAN port code. Why after all these years it suddenly stops working. Especially when my AC88U and AC66U (with Johns firmware) works when WAN port is used to connect the AP in LAN.

Interesting, it didn't work for me. Can you please connect to the router via ssh and run 'robocfg show' and paste here the result?

 

[Kingp1n]

Put the command into the startup-scripts.

Dumb question...so enabling this power trick to on we'll run the router at lower temps? I own a RT-AC86U and I'm wondering if I sld turn on?

 

[skeal]

Dumb question...so enabling this power trick to on we'll run the router at lower temps? I own a RT-AC86U and I'm wondering if I sld turn on?

Asus disabled it for some reason, do so at your own risk.

 

[SNBForums User]

Dirty upgrade from 384.11 was smooth as silk and appears to have addressed previously reported SMB issues with 384.12.

 

[nzwayne]

To help some; this code level worked with my Epson 837 Artisan printer since installing 384.13 without any tweaks to the 2.4GHz wireless band (it can't connect to 5GHz BTW), then today a solid communication error on sending a print doc. To correct, as like all other code levels, was disable "Universal Beamforming" on 2.4GHz (RT-AX88U)

PS: If I have "Enable Smart Connect" enabled, the Epson printer will not connect to the 2.4GHz.

 

[RMerlin]

Also when I uploaded firmware for the AirMesh node a pop-up window with a login screen opened up and then it asked me to upload a file. When I was running stock Asus I thought this was inline but not 100% sure as I have been enjoying Merlin for a while now

Not for AiMesh nodes, it has to redirect you to the node to upload the firmware. This is how stock firmware does it.

 

[RMerlin]

There will be zero change to temperatures for all other models, only the RT-AX88U had a power management change. There was no change at all on any of the other models.

 

[SuperDuke]

Hello all.....first time poster, long time lurker.....

.13 (dirty) upgraded.....no issues....has anyone else seen previously dead port 53 traffic start up post flash? Was dead quiet after .11 (didn't think to look .12) but for giggle did a port sniff after .13 and saw some traffic......anyone have theories on why? thanks

 

[rgnldo]

Fixed issue with 'service reboot' command that caused AC86U to shut down, not booting. Very good work.

 

[Swistheater]

Hello all.....first time poster, long time lurker.....

.13 (dirty) upgraded.....no issues....has anyone else seen previously dead port 53 traffic start up post flash? Was dead quiet after .11 (didn't think to look .12) but for giggle did a port sniff after .13 and saw some traffic......anyone have theories on why? thanks

The traffic is due to a change in the routers local traffic, (not client traffic) it is because dns caching is now done by upstream dns and not by local cache, so all local router traffic will appear to show on port 53, and if you are using dns privacy option , all client traffic will still be traveling port 853. It was the option of local cache that was allowing router related traffic to not traverse port 53, but now that it is passed to upstream via merlin default(upstream dns cache) and the traffic for it shows up on port 53.

 

[SuperDuke]

The traffic is due to a change in the routers local traffic, (not client traffic) it is because dns caching is now done by upstream dns and not by local cache, so all local router traffic will appear to show on port 53, and if you are using dns privacy option , all client traffic will still be traveling port 853. It was the option of local cache that was allowing router related traffic to not traverse port 53, but now that it is passed to upstream via merlin default(upstream dns cache) and the traffic for it shows up on port 53.
View attachment 18855

Wonderful....and thanks for the thorough explanation! Appreciate it!

 

[Stevens243]

To help some; this code level worked with my Epson 837 Artisan printer since installing 384.13 without any tweaks to the 2.4GHz wireless band (it can't connect to 5GHz BTW), then today a solid communication error on sending a print doc. To correct, as like all other code levels, was disable "Universal Beamforming" on 2.4GHz (RT-AX88U)
View attachment 18852
PS: If I have "Enable Smart Connect" enabled, the Epson printer will not connect to the 2.4GHz.

Similar issue with an older android tablet. Only 2.4 wifi modem and was rock solid on 13.beta with smart connect on. After the upgrade to final, kept bouncing (and disconnecting) but turning of universal beamforming fixed it. Thanks!

 

[nzwayne]

The mystery with the 5GHz not enabled on the AX88U continues with 384.13. Noticed today LED disabled on the AX88U, was lit yesterday. Only way I could get 5GHz to enable, was to enable 160MHz Channel Bandwidth.

Only other quirk for me, my Garmin Index Scale usually won't connect to the AX88U (only 2.4GHz band device). Works perfectly on a RT-N56U. Some debug time necessary to sort this all out if it's a product/code/setup bug. May have to buy another AX88U to have as a play/development tool...ASUS the winner here?!

 

[octopus]

Just updated and everything working just fine.
I have two RT-AC66U_B1 which I running aimesh nod(s) but one of them I can't get connected.
I have tried everything I know of.

I have one of them replaced and new one connecting to AiMesh node immediately.
I wish I could trim the power so I could trim the nodes.

 

[ionutz4u]

No one has a sollution for this?

Aug 2 18:14:40 wsdd2[700]: wsdd-http-v6: open_ep: bind: Address already in use
Aug 2 18:14:53 wsdd2[700]: wsdd-http-v6: open_ep: bind: Address already in use
Aug 2 18:14:55 wsdd2[700]: wsdd-http-v6: open_ep: bind: Address already in use
Aug 2 19:00:49 wsdd2[700]: wsdd-http-v6: open_ep: bind: Address already in use
Aug 2 19:00:52 wsdd2[700]: wsdd-http-v6: open_ep: bind: Address already in use
Aug 2 20:01:32 wsdd2[700]: wsdd-http-v6: open_ep: bind: Address already in use
Aug 2 20:01:34 wsdd2[700]: wsdd-http-v6: open_ep: bind: Address already in use

 

[dave14305]

No one has a sollution for this?

Aug 2 18:14:40 wsdd2[700]: wsdd-http-v6: open_ep: bind: Address already in use
Aug 2 18:14:53 wsdd2[700]: wsdd-http-v6: open_ep: bind: Address already in use
Aug 2 18:14:55 wsdd2[700]: wsdd-http-v6: open_ep: bind: Address already in use
Aug 2 19:00:49 wsdd2[700]: wsdd-http-v6: open_ep: bind: Address already in use
Aug 2 19:00:52 wsdd2[700]: wsdd-http-v6: open_ep: bind: Address already in use
Aug 2 20:01:32 wsdd2[700]: wsdd-http-v6: open_ep: bind: Address already in use
Aug 2 20:01:34 wsdd2[700]: wsdd-http-v6: open_ep: bind: Address already in use

Check what else is listening on port 3702

netstat -nap | grep 3702

 

[ionutz4u]

Check what else is listening on port 3702

netstat -nap | grep 3702

netstat -nap | grep 3702
tcp 0 0 0.0.0.0:3702 0.0.0.0:* LISTEN 700/wsdd2
tcp 0 0 :::3702 :::* LISTEN 700/wsdd2
udp 0 0 0.0.0.0:3702 0.0.0.0:* 700/wsdd2
udp 0 0 :::3702 :::* 700/wsdd2
udp 0 0 :::3702 :::* 700/wsdd2