Looking at the changelog I see that fixes are applied, but there is a new problem.
Now after upgrading I don't have Flow Acceleration in GUI anymore so I can't set CTF & FA.
I do not use QoS, WAN is DHCP, LAN is static, I did two restarts. According to the wiki then the Flow Acceleration menu should appear, but it's not the case unfortunately.
Joined: 26 Mar 2013 Posts: 1857 Location: Hung Hom, Hong Kong
Posted: Mon Jul 19, 2021 20:43 Post subject:
kernel-panic69 wrote:
@mwchang: The only problem with manually setting parameters is if you ever do a reset in the future without doing an nvram erase, those changes are permanent, if I am not mistaken.
If I saved all settings via Admin->Backup, I supposed I could always restore those settings without accidents.
Then I could reset everything back to factory defaults, just to find out why Samba failed.
That maybe the way to go. Or should I expect to hit some strange bugs related to Backup/Restore?
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
Router/Version: Netgear R8000
File/Kernel: Firmware: DD-WRT v3.0-r47073 std
Previous/Reset: DD-WRT v3.0-r3.0r47040 std / no reset
Mode/Status: WiFi AP, WAN as DHCP client with VLAN tagging 10.
Issues/Errors: The Wireless Security -> Apply Settings button is still not working. Click on it will break the internet connection.
The Privoxy is not working for a long time. When it's enabled the internet connection is broken.
You're absolutely right, how could I forgot...
Attaching them.
Also I found this in log:
Code:
Jan 1 01:00:11 RT-AC56U-VPN kern.info kernel: attaching FA
Jan 1 01:00:11 RT-AC56U-VPN kern.info kernel: CHIPID 53010, rev 2
Jan 1 01:00:11 RT-AC56U-VPN kern.info kernel: not FA capable
But it is a Northstar Chip: BCM4708
According to the Wiki northstar CPUs are capable of FA
Joined: 26 Mar 2013 Posts: 1857 Location: Hung Hom, Hong Kong
Posted: Tue Jul 20, 2021 14:15 Post subject:
I think I found the problem of Smaba 3! It's /tmp/smb.conf! If I manually service-started samba3 using the following trimmed smb.conf, everything was working!