What's new

[Fork] Asuswrt-Merlin 374.43 LTS releases (V44EA)

ColinTaylor

Part of the Furniture
... was connected to the 5GHz guest network (with vlan) ...
You obviously have a very non-standard WiFi setup so I suspect that is what is causing the problem. When I last tested the WiFi scheduler it was working as expected.
 

000111

Senior Member
Easy question for anyone familiar with nvram show|grep commands...
Every time I execute an nvram show|grep command on the router the results contain the size and space left for nvram-
size: xxxxx bytes (xxxxx left)

Is there a way to execute an nvram show|grep command without showing this?
 

ColinTaylor

Part of the Furniture
Easy question for anyone familiar with nvram show|grep commands...
Every time I execute an nvram show|grep command on the router the results contain the size and space left for nvram-
size: xxxxx bytes (xxxxx left)

Is there a way to execute an nvram show|grep command without showing this?
Fortunately the unwanted "size:" line is being sent to stderr so it can be removed like so:
Code:
nvram show 2>/dev/null | grep wan0_hwaddr
 

dave14305

Part of the Furniture
I added a function to /jffs/configs/profile.add since I was searching nvram so often.
Bash:
nsg() {
        if [ -n "$1" ]; then
                nvram show 2>/dev/null | grep -i "$1" | sort
        else
                echo "ERROR: search string required."
        fi
}
Then I can just run nsg wan0_hwaddr
 

bejoysat

New Around Here
I was on 380.70 for a long time on my N66U. Recently I observed the router getting reset while my phone gets connected to the 5GHz network. Could it be a issue with the AC standard client connection causing problem? I have the phone for over a year but the issue is observed only recently.
Quoting myself just to update about this issue. The reset was still happening and upon further googling, it seems many have reported the issue with the OnePlus 6 phone and N66U combination causing the router to reset when connected in either wireless bands.
https://www.reddit.com/r/OnePlus6/comments/8suqm8
Solution suggested is to disable the NAT acceleration and seems to have worked for many. I have also tried and monitoring now. Though I am not very convinced with the solution because the issue cropped up only very recently though I have been using this phone for last 1.5 years.

Before trying this out, i tried disabling the MAC randomization in the Phone, but still the router was resetting.

Question: Is there any way to debug the router logs to see what is causing this issue? I don't see anything in the system logs before the reset happened.

PS. This issue has nothing to do with this build, but seems affecting all firmwares.
 

dave1000

New Around Here
Hi all,
I've been using john's fork and lurking this forum for awhile now but finally decided to get an account.
The discussion on this thread is great and everyone seems so helpful.

As for my (minor, but possibly important to some such as myself) contribution, I have discovered that recent versions of Linux are using samba 4.11+ which defaults to SMB2 as the minimum protocol.
Samba does not appear to allow decoupling NetBIOS from the SMB version like Windows 10 does.
This has the effect of breaking the Network Map -> Client Status screen in the sense that Linux PCs receive the "other" icon rather the "PC" icon (even with samba and winbind installed and firewall set correctly).

The fix/workaround I have found is relatively easy:
On the affected client, under /etc/samba/smb.conf place "server min protocol = NT1" under the "workgroup = WORKGROUP" line, save, then reboot.
This will restore NetBIOS (and SMB1 :/) functionality to make the PC icon appear on the Client List once again and should not interfere with connecting to Windows 10 machines.
Connecting from Windows 10 to Linux may be affected but that was not the case on my network; based on distro/version, YMMV.

Ultimately, it may be better for someone more knowledgeable than myself to find a way to make the Client List use a newer discovery method such as avahi/wsdd.
As you are all likely to be aware, re-enabling SMB1 may introduce a security risk in some environments.
I found I can mitigate this somewhat by adding "restrict anonymous = 2" under the "server min protocol = NT1" line.
 
Last edited:

Latest threads

Sign Up For SNBForums Daily Digest

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