What's new

Asuswrt-Merlin 378.50 is out

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

All the wifi credit should actually go to Asus. I'm just reusing their drivers, chances are the newer version I'm using is better than their last public release.

For AC68U, the wifi is just awesome. Performance increased by up to 50% compared to .48 build!
 
For AC68U, the wifi is just awesome. Performance increased by up to 50% compared to .48 build!

I can also confirm your finding I have two of them and I do see huge increase in overall performance. However boot time has increased.
 
Give them time - the release happened late Friday night, and it's currently the weekend.

They could of been working on this whilst in beta, nothing you did was going to affect this change by Asus.

We will let you know when we add support for this new version. In the meantime, please use older compatible version.
 
I have a lot of this, and I know it's reported problem, 378_50_ta.
On one router 378_50 and no such behave.

I'm using vlan10 on iptv, internet VID 10 prio 0

Feb 7 18:04:16 crond[642]: time disparity of 98943 minutes detected
Feb 7 18:04:24 kernel: Dead loop on virtual device vlan10, fix it urgently!
Feb 7 18:04:24 kernel: Dead loop on virtual device vlan10, fix it urgently!
Feb 7 18:04:24 kernel: Dead loop on virtual device vlan10, fix it urgently!

octopus
 
Could anyone compare the new wifi performance to the old 374.43 build (and older ones)?
Thanks.
 
This release has fixed a great many issues for me, and i know that Asus and Merlin have been working hard on this error:

Feb 7 22:46:09 kernel: br0: received packet on vlan1 with own address as source address
Feb 7 22:47:04 kernel: br0: received packet on vlan1 with own address as source address
Feb 7 22:47:48 kernel: br0: received packet on vlan1 with own address as source address


However in my case it hasn't gone, but what was interesting, i didn't have the error with the current Asus firmware ending .3885

Regards
 
Astrill need to update their app for the changes Asus made but they refuse until 378.50 was out of beta

I have notified them that it is now out of beta but no reply yet.

I urge everyone who is using the Astrill app to submit a support ticket to get this fixed.

I've also just notified them a few mins ago.
 
Looks like Teaming on Lan port 1 and 2 hasn't been resolved.
I'm still getting frequent freezes when remote control on teaming enabled PC on port 1 and 2. Other then that, using any of two Ethernet ports 2, 3 and 4 will not have any freezing issues.

Could it be due to the architecture for port 1 is on Quantenna/ Realtek chip and the rest is on Broadcom? Thus causing incompatibility issues?
Annoyed by the fact that Asus indicate on Lan 1 and 2 is for Teaming..

Any care to share on their experience on this 378_50 built.
Thanks

87U-Layout-Block-Diagram.png
 
EDIT: I have now switch back to 378_50 build and all kernel complain is gone.
resolv.dnsmasq still contain 4 rows


I have found interssting issue between my two 68U regarding, kernel: Dead loop on virtual device vlan10, fix it urgently!

If I look at "resolv.dnsmasq" in 378_50_ta build i get:

cat /tmp/resolv.dnsmasq
server=/myprovider.com/my.dns.98.2 <<== already in resolv.conf
server=/local/my.dns.98.2
server=/myprovider.com/my.dns.101.3 <<== already in resolv.conf
server=/local/my.dns.101.3

cat /tmp/resolv.conf
nameserver my.dns.98.2
nameserver my.dns.101.3

There I have no kernel message.
and in 378_50 build:

cat /tmp/resolv.dnsmasq
server=/local/my.dns.199.12
server=/local/my.dns.199.13

cat /tmp/resolv.conf
nameserver my.dns.199.12
nameserver my.dns.199.13
 
Last edited:
SMB password length issue

On RT-AC87U, 378.50.

When I mount an SMB share using Windows 10 Technical Preview, I can successfully get to the files on the AC87U. But, syslog shows the following:

Feb 8 09:11:06 smbd[9183]: [2015/02/08 09:11:06.591939, 0] ../libcli/auth/ntlm_check.c:54(smb_pwd_check_ntlmv1)
Feb 8 09:11:06 smbd[9183]: smb_pwd_check_ntlmv1: incorrect password length (74)
Feb 8 09:11:06 smbd[9183]: [2015/02/08 09:11:06.593464, 0] ../libcli/auth/ntlm_check.c:54(smb_pwd_check_ntlmv1)
Feb 8 09:11:06 smbd[9183]: smb_pwd_check_ntlmv1: incorrect password length (74)
Feb 8 09:12:26 smbd[9183]: [2015/02/08 09:12:26.068810, 0] ../libcli/auth/ntlm_check.c:54(smb_pwd_check_ntlmv1)
Feb 8 09:12:26 smbd[9183]: smb_pwd_check_ntlmv1: incorrect password length (74)
Feb 8 09:12:26 smbd[9183]: [2015/02/08 09:12:26.070316, 0] ../libcli/auth/ntlm_check.c:54(smb_pwd_check_ntlmv1)
Feb 8 09:12:26 smbd[9183]: smb_pwd_check_ntlmv1: incorrect password length (74)
Feb 8 09:12:59 smbd[9183]: [2015/02/08 09:12:59.554153, 0] ../libcli/auth/ntlm_check.c:54(smb_pwd_check_ntlmv1)
Feb 8 09:12:59 smbd[9183]: smb_pwd_check_ntlmv1: incorrect password length (74)
Feb 8 09:12:59 smbd[9183]: [2015/02/08 09:12:59.556055, 0] ../libcli/auth/ntlm_check.c:54(smb_pwd_check_ntlmv1)
Feb 8 09:12:59 smbd[9183]: smb_pwd_check_ntlmv1: incorrect password length (74)
Feb 8 09:13:40 smbd[9183]: [2015/02/08 09:13:40.661159, 0] ../libcli/auth/ntlm_check.c:54(smb_pwd_check_ntlmv1)
Feb 8 09:13:40 smbd[9183]: smb_pwd_check_ntlmv1: incorrect password length (74)
Feb 8 09:13:40 smbd[9183]: [2015/02/08 09:13:40.663094, 0] ../libcli/auth/ntlm_check.c:54(smb_pwd_check_ntlmv1)
Feb 8 09:13:40 smbd[9183]: smb_pwd_check_ntlmv1: incorrect password length (74)

You can see from the timestamps, the first 4 were from first opening the share. The next 4 are from opening a directory on the share. The last 4 are from opening a file from another directory.

I have "Allow guest login" on.

Maybe a Windows 10 thing? I don't recall see this with the earlier beta's. I did a grep on /tmp/syslog.log-1 and no sign of smb_pwd errors.
 
AC56U, updated from Beta 2, factory reset, restored manually all the settings, it has been working great for the last 10 hours, with all the AiSecurity settings turned on.

There is a bug: whenever I go to the Traffic Analyzer page, that stalls the asuswrt webpage; Internet works fine, but I cannot access the router anymore via the configuration page, it's accessible only via telnet. Works fine after a reboot, as long as I don't go to that Traffic page again!
 
AC56U, updated from Beta 2, factory reset, restored manually all the settings, it has been working great for the last 10 hours, with all the AiSecurity settings turned on.

There is a bug: whenever I go to the Traffic Analyzer page, that stalls the asuswrt webpage; Internet works fine, but I cannot access the router anymore via the configuration page, it's accessible only via telnet. Works fine after a reboot, as long as I don't go to that Traffic page again!
Weird, I don't have this particular bug. Upgraded from beta 2 without reset.
 
Will any improvements be noticeable on the AC66U since it won't get the TA?
 
Samba password length error

On RT-AC87U, 378.50.

When I mount an SMB share using Windows 10 Technical Preview, I can successfully get to the files on the AC87U. But, syslog shows the following:

Feb 8 09:11:06 smbd[9183]: [2015/02/08 09:11:06.591939, 0] ../libcli/auth/ntlm_check.c:54(smb_pwd_check_ntlmv1)
Feb 8 09:11:06 smbd[9183]: smb_pwd_check_ntlmv1: incorrect password length (74)
Feb 8 09:11:06 smbd[9183]: [2015/02/08 09:11:06.593464, 0] ../libcli/auth/ntlm_check.c:54(smb_pwd_check_ntlmv1)
Feb 8 09:11:06 smbd[9183]: smb_pwd_check_ntlmv1: incorrect password length (74)
Feb 8 09:12:26 smbd[9183]: [2015/02/08 09:12:26.068810, 0] ../libcli/auth/ntlm_check.c:54(smb_pwd_check_ntlmv1)
Feb 8 09:12:26 smbd[9183]: smb_pwd_check_ntlmv1: incorrect password length (74)
Feb 8 09:12:26 smbd[9183]: [2015/02/08 09:12:26.070316, 0] ../libcli/auth/ntlm_check.c:54(smb_pwd_check_ntlmv1)
Feb 8 09:12:26 smbd[9183]: smb_pwd_check_ntlmv1: incorrect password length (74)
Feb 8 09:12:59 smbd[9183]: [2015/02/08 09:12:59.554153, 0] ../libcli/auth/ntlm_check.c:54(smb_pwd_check_ntlmv1)
Feb 8 09:12:59 smbd[9183]: smb_pwd_check_ntlmv1: incorrect password length (74)
Feb 8 09:12:59 smbd[9183]: [2015/02/08 09:12:59.556055, 0] ../libcli/auth/ntlm_check.c:54(smb_pwd_check_ntlmv1)
Feb 8 09:12:59 smbd[9183]: smb_pwd_check_ntlmv1: incorrect password length (74)
Feb 8 09:13:40 smbd[9183]: [2015/02/08 09:13:40.661159, 0] ../libcli/auth/ntlm_check.c:54(smb_pwd_check_ntlmv1)
Feb 8 09:13:40 smbd[9183]: smb_pwd_check_ntlmv1: incorrect password length (74)
Feb 8 09:13:40 smbd[9183]: [2015/02/08 09:13:40.663094, 0] ../libcli/auth/ntlm_check.c:54(smb_pwd_check_ntlmv1)
Feb 8 09:13:40 smbd[9183]: smb_pwd_check_ntlmv1: incorrect password length (74)

You can see from the timestamps, the first 4 were from first opening the share. The next 4 are from opening a directory on the share. The last 4 are from opening a file from another directory.

I have "Allow guest login" on.

Maybe a Windows 10 thing? I don't recall see this with the earlier beta's. I did a grep on /tmp/syslog.log-1 and no sign of smb_pwd errors.

This error can be fixed by modifying some Windows settings. In XP and Win7, it is fixed by using Windows' policy editor. Most likely, the same thing can be done in Win8 and Win10.

On the Windows machine, open Control Panel -> System and Security -> Administrative Tools, then select Local Security Policy.

When the tool opens, expand "Local Policies" and select "Security Options" in the left hand tree. Scroll the list on the right to "Network security: LAN Manager authentication level". Double-click that item and change the option to "Use NTLMv2 session security if negotiated".

The router error messages should go away.
 
RT-AC87U_3.0.0.4_378.50_beta3b_ta

Call me crazy but for my RT-AC87 the RT-AC87U_3.0.0.4_378.50_beta3b_ta firmware runs faster than the released .50. Also you have the traffic analyzer.

Merlin whats the exact difference between the released and this version. It is based on same code correct?

Ran the released version and returned to the beta version and it is running perfectly.

CC
 
Did you yet try the 378.50_ta ? (none-beta but still experimental )
 
This error can be fixed by modifying some Windows settings. In XP and Win7, it is fixed by using Windows' policy editor. Most likely, the same thing can be done in Win8 and Win10.

On the Windows machine, open Control Panel -> System and Security -> Administrative Tools, then select Local Security Policy.

When the tool opens, expand "Local Policies" and select "Security Options" in the left hand tree. Scroll the list on the right to "Network security: LAN Manager authentication level". Double-click that item and change the option to "Use NTLMv2 session security if negotiated".

The router error messages should go away.

Thanks, I made the change and it did go away.

For Windows 10 Preview, I needed to edit the Registry.

In:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

Add a new DWORD called LmCompatibilityLevel and set the value to 1.

Thanks again.
 
Any chances for alternative hosting? mediafire gives <5kBps transfer rate...

EDIT: it gives 0kpbs speed, downloading the FW is simply impossible, maybe any donators link?
 
Last edited:
Any chances for alternative hosting? mediafire gives <5kBps transfer rate...

EDIT: it gives 0kpbs speed, downloading the FW is simply impossible, maybe any donators link?

what is your router, maybe I can grab it and post a link
 

Similar threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top