Asuswrt-Merlin 378.51 is out

[Shawn Holmes]

Plus the added electrical cost of a fan running 24/7.

You're right... That extra few dollars /year it will probably cost me isn't worth it... or is it?

 

[maddy_in65]

I had upgraded firmware my Asus AC66u to 378.51 and attached new 3TB external HDD. It has 3 partition and one have entware installed. I am trying to share remaining two partition but can see sda6 drive while trying to access it. Is it issue with inbuilt samba application.

Filesystem                Size      Used Available Use% Mounted on
/dev/root                27.1M     27.1M         0 100% /
tmpfs                   117.0M      4.4M    112.6M   4% /tmp
devfs                   117.0M         0    117.0M   0% /dev
/dev/mtdblock5           32.0M      1.1M     30.9M   3% /jffs
/dev/sda5                14.4G    173.4M     13.5G   1% /tmp/mnt/sda5
/dev/sda6                 1.7T      1.1T    659.4G  62% /tmp/mnt/sda6
/dev/sda7              1017.8G    199.4M    965.9G   0% /tmp/mnt/sda7

 

[JunKhaos]

nvram unset bwdpi_sig_ver
nvram unset bwdpi_rsa_check
nvram unset bwdpi_dpi_ver
nvram commit
service stop_wrs_force
service start_wrs

Either it's a mismatch in engine/sig version, or there was a problem with the rsa-signed version of the rules file.

I did all three commands and the Apps analysis is working correctly now. Thank you very much.

 

[JockC]

378.51 working well for me on an RT-AC68U. The only one issue that I have is that, if I go to the Traffic Analyzer, I lose the web interface and get the message .......
"Settings have been updated. Web page will now refresh.
Changes have been made to the IP address or port number. You will now be disconnected from RT-AC68U."

After that, I have to reboot it to get it working again.
I only run mine in AP mode if that helps. Any ideas?

 

[VANT]

87u
i turn off 5GHz radio but led is still on. IMO 5GHz LED should be off, when radio is off.
WPA Pre-Shared Key is also visible on 87 like in 66u. But other passowrd is hidden eg. PPPoE pass.
temp my 87u

 

[matthew_eli]

Hi guys, do you know if the data of the new Traffic Analyzer is stored in the same location of all the traffic data? Thanks

 

[jmone]

Just had my 87u drop my WAN connection and I could not log into it. Had to manually reboot the router. Could be a one off (but it has never happened before). Anyone else seeing any issues like this?
Thanks
Nathan

 

[chrisinsocalif]

I had a problem using my chromecast on 378.50 but it seems to work on 378.51. Does it matter if i am using an older bootloader(1.0.0.7)? My temps seem to be good: 2.4 GHz: 54°C - 5 GHz: 60°C. I am using an AC66u.

 

[joegreat]

Re: Logging on custom config/script execution

Hi Merlin,

Thanks for adding the logging on the start of the custom config/script execution!
I think it would be beneficial to have also the stop time and return code of the script logged.

Is there a chance to add this into your updated firmware version?

With kind regards
Joe

PS.: As you can see from the syslog example below, I have added code into the scripts to track the entrance and the exit of the script.

Dec  1 01:00:28 custom script: Running /jffs/scripts/post-mount (args: /tmp/mnt/Data)
Dec  1 01:00:28 START_post-mount: started [/tmp/mnt/Data]
Dec  1 01:00:29 dhcp client: bound 84.113.170.61 via 84.113.170.1 during 344970 seconds.
Dec  1 01:00:29 miniupnpd[1020]: HTTP listening on port 56310
Dec  1 01:00:29 miniupnpd[1020]: Listening for NAT-PMP/PCP traffic on port 5351
Dec  1 01:00:30 ntp: start NTP update
Mar  8 12:27:52 rc_service: ntp 1018:notify_rc restart_upnp
Mar  8 12:27:52 rc_service: ntp 1018:notify_rc restart_diskmon
Mar  8 12:27:52 rc_service: waitting "restart_upnp" via ntp ...
Mar  8 12:27:52 miniupnpd[1020]: shutting down MiniUPnPd
Mar  8 12:27:52 miniupnpd[1033]: HTTP listening on port 59915
Mar  8 12:27:52 miniupnpd[1033]: Listening for NAT-PMP/PCP traffic on port 5351
Mar  8 12:27:55 disk monitor: be idle
Mar  8 12:27:56 admin: Started transmission-daemon from .
Mar  8 12:27:56 STOP_post-mount: return code 0

Start logging in the scripts:

#!/bin/sh
/usr/bin/logger -t START_$(basename $0) "started [$@]"

Stop logging in the scripts:

/usr/bin/logger -t STOP_$(basename $0) "return code $?"

 

[spatzenpost]

Hi,
I' using the latest Merlin Version
Model RT-AC68U
Firmware Version 3.0.0.4.378.51
Is this normal that I cannot switch the NAT Acceleration to AUTO?
QOS is turned off
NAT Acceleration Disable Auto NAT traffic is processed by CPU.

Second question,
I have the Clock frequency turned on to 1000/800, but if I' making a on the website a speedtest.net a speediest, cpu 1 is during this time over 90% percent, the download rate is that what my ISP promised (250 down, 25 up).
spatzenpost

 

[muzykcb]

AC66U - do I need a hard reset after upgrading to .51 from .50?

Wireless log page is corrupted after update

View attachment 3409

perform reset factory settings

 

[oric1]

Hello everyone.

Long time reader, 1st time post...

I am running 2 x RT-AC87U routers. Main one in Wireless router mode, and the 2nd in Access Point mode.

Just upgraded from Merlin 378.50 to 378.51 on my main RT-AC87U and have had this stuff flooding my logs since 378.50 and am wondering what it is:

Mar 7 14:26:20 kernel: br0: port 1(vlan1) received tcn bpdu
Mar 7 14:26:20 kernel: br0: topology change detected, propagating
Mar 7 14:26:42 kernel: br0: port 1(vlan1) received tcn bpdu
Mar 7 14:26:42 kernel: br0: topology change detected, propagating
Mar 7 14:27:04 kernel: br0: port 1(vlan1) received tcn bpdu
Mar 7 14:27:04 kernel: br0: topology change detected, propagating
Mar 7 14:27:26 kernel: br0: port 1(vlan1) received tcn bpdu
Mar 7 14:27:26 kernel: br0: topology change detected, propagating
Mar 7 14:27:48 kernel: br0: port 1(vlan1) received tcn bpdu
Mar 7 14:27:48 kernel: br0: topology change detected, propagating
Mar 7 14:28:10 kernel: br0: port 1(vlan1) received tcn bpdu
Mar 7 14:28:10 kernel: br0: topology change detected, propagating
Mar 7 14:28:32 kernel: br0: port 1(vlan1) received tcn bpdu
Mar 7 14:28:32 kernel: br0: topology change detected, propagating
Mar 7 14:28:54 kernel: br0: port 1(vlan1) received tcn bpdu
Mar 7 14:28:54 kernel: br0: topology change detected, propagating
Mar 7 14:29:16 kernel: br0: port 1(vlan1) received tcn bpdu
Mar 7 14:29:16 kernel: br0: topology change detected, propagating
Mar 7 14:29:38 kernel: br0: port 1(vlan1) received tcn bpdu
Mar 7 14:29:38 kernel: br0: topology change detected, propagating
Mar 7 14:30:00 kernel: br0: port 1(vlan1) received tcn bpdu
Mar 7 14:30:00 kernel: br0: topology change detected, propagating
Mar 7 14:30:22 kernel: br0: port 1(vlan1) received tcn bpdu
Mar 7 14:30:22 kernel: br0: topology change detected, propagating
Mar 7 14:30:44 kernel: br0: port 1(vlan1) received tcn bpdu
Mar 7 14:30:44 kernel: br0: topology change detected, propagating
Mar 7 14:31:06 kernel: br0: port 1(vlan1) received tcn bpdu
Mar 7 14:31:06 kernel: br0: topology change detected, propagating

The above is just a snip. It goes on and on and on.... Doesn't seem to be hurting anything though as I can still surf.

Any ideas? I searched but can't find anyone mentioning the above before.

Thanks in advance!

I'm also seeing these log every few seconds after upgraded to 378.51, never had such log when running 378.50.

My main router is AC87U as Wireless Router mode and my other RT66U is connected via LAN cable to AC87U port 1.

Mar 8 22:07:41 kernel: br0: port 1(vlan1) neighbor 8000.78:24:af:94:6c:fc lost
Mar 8 22:07:41 kernel: br0: topology change detected, propagating
Mar 8 22:08:03 kernel: br0: port 1(vlan1) neighbor 8000.78:24:af:94:6c:fc lost
Mar 8 22:08:03 kernel: br0: topology change detected, propagating
Mar 8 22:08:25 kernel: br0: port 1(vlan1) neighbor 8000.78:24:af:94:6c:fc lost
Mar 8 22:08:25 kernel: br0: topology change detected, propagating
Mar 8 22:08:47 kernel: br0: port 1(vlan1) neighbor 8000.78:24:af:94:6c:fc lost
Mar 8 22:08:47 kernel: br0: topology change detected, propagating
Mar 8 22:09:09 kernel: br0: port 1(vlan1) neighbor 8000.78:24:af:94:6c:fc lost
Mar 8 22:09:09 kernel: br0: topology change detected, propagating
Mar 8 22:09:31 kernel: br0: port 1(vlan1) neighbor 8000.78:24:af:94:6c:fc lost
Mar 8 22:09:31 kernel: br0: topology change detected, propagating

Merlin, is there anyway we could suppress these messages? Thanks.

 

[XIII]

What issue was that?

Suddenly loosing the 2.4 GHz band until the next router reboot.

 

[oversim]

Nat loopback default setting is "Merlin".
I have an ARM router (ac68u) and I don't use nat loopback: in order to save cpu can I disable this feature?

 

[pepeEL]

I'm also seeing these log every few seconds after upgraded to 378.51, never had such log when running 378.50.

My main router is AC87U as Wireless Router mode and my other RT66U is connected via LAN cable to AC87U port 1.

Mar 8 22:07:41 kernel: br0: port 1(vlan1) neighbor 8000.78:24:af:94:6c:fc lost
Mar 8 22:07:41 kernel: br0: topology change detected, propagating
Mar 8 22:08:03 kernel: br0: port 1(vlan1) neighbor 8000.78:24:af:94:6c:fc lost
Mar 8 22:08:03 kernel: br0: topology change detected, propagating
Mar 8 22:08:25 kernel: br0: port 1(vlan1) neighbor 8000.78:24:af:94:6c:fc lost
Mar 8 22:08:25 kernel: br0: topology change detected, propagating
Mar 8 22:08:47 kernel: br0: port 1(vlan1) neighbor 8000.78:24:af:94:6c:fc lost
Mar 8 22:08:47 kernel: br0: topology change detected, propagating
Mar 8 22:09:09 kernel: br0: port 1(vlan1) neighbor 8000.78:24:af:94:6c:fc lost
Mar 8 22:09:09 kernel: br0: topology change detected, propagating
Mar 8 22:09:31 kernel: br0: port 1(vlan1) neighbor 8000.78:24:af:94:6c:fc lost
Mar 8 22:09:31 kernel: br0: topology change detected, propagating

Merlin, is there anyway we could suppress these messages? Thanks.

I also have this message in logs... please RMerlin explained us what is it.

 

[CiscoX]

I also have this message in logs... please RMerlin explained us what is it.

I think this is the br0 (VLAN loop) issue we all have on RT-AC87U.
ASUS have release an unofficial beta that fix this issue and some other bugs.
RMerlin don't have the latest source yet so i don't think he can fix this until ASUS release a newer source.

 

[doubleroll]

WiFi is much more stable now with 51 on my AC66R. With 50 it was all over the place especially with Apple devices. Thanks for reverting the driver! So far all ok at least in AP mode.


Sent from my iPad using Tapatalk HD

 

[dlandon]

Merlin NAT Loopback is not working on AC3200. I have to use ASUS.

 

[Iam Singho]

Regression from .50 version.

I am using freedns.afraid.org for my DDNS. Custom script is working fine and IP address is being updated.

However in the syslog is being filled up with entries that update is unsuccessful.

Mar  8 21:26:11 watchdog: start ddns.
Mar  8 21:26:11 rc_service: watchdog 585:notify_rc start_ddns
Mar  8 21:26:11 custom script: Running /jffs/scripts/ddns-start (args: a.b.c.d)
Mar  8 21:26:12 ddns: Custom ddns update failed
Mar  8 21:26:41 watchdog: start ddns.
Mar  8 21:26:41 rc_service: watchdog 585:notify_rc start_ddns
Mar  8 21:26:41 custom script: Running /jffs/scripts/ddns-start (args: a.b.c.d)
Mar  8 21:26:42 ddns: Custom ddns update failed
Mar  8 21:27:11 watchdog: start ddns.
Mar  8 21:27:11 rc_service: watchdog 585:notify_rc start_ddns
Mar  8 21:27:11 custom script: Running /jffs/scripts/ddns-start (args: xxxx)
Mar  8 21:27:12 ddns: Custom ddns update failed
Mar  8 21:27:41 watchdog: start ddns.
Mar  8 21:27:41 rc_service: watchdog 585:notify_rc start_ddns
Mar  8 21:27:41 custom script: Running /jffs/scripts/ddns-start (args: xxxx)
Mar  8 21:27:42 ddns: Custom ddns update failed

 

[Ronv42]

Merlin,

Your steps below solved the traffic analyzer for me also. Apps analyizer also reporting just fine. Haven't had time yet to enable adaptive QOS but later today I will give it a shot.

I had that issue for a few weeks until I ran a few commands while troubleshooting something. I'm not sure which of these commands did resolve the issue for me, so give it a try.

nvram unset bwdpi_sig_ver
nvram unset bwdpi_rsa_check
nvram unset bwdpi_dpi_ver
nvram commit
service stop_wrs_force
service start_wrs

Either it's a mismatch in engine/sig version, or there was a problem with the rsa-signed version of the rules file.