Firmware: v3.0-r46446 std (04/24/21)
Router/Version: Netgear R7000 Kernel: Linux 4.4.267 #2623 SMP Fri Apr 23 07:31:02 +07 2021 armv7l
Previous: v3.0-r46395 std (04/19/21)
Mode/Status: AP wired and wireless, Up and running for 26 hours.
Reset: Soft boot before and after upgrade
Temperatures: CPU 57.5 °C / WL0 45.0 °C / WL1 50.4 °C
Issues/Errors: Nothing significant
Updated via webif. No 'nvram erase' this time, last one was in July 2018 (r36325).
Upload and Download speeds are to ISP spec. Nothing unexpected in the syslog.
Current basic R7000 setup (subject to change of course):
- Static WAN IP
- SFE - On
- STP - On
- IPv4 only, both WAN and LAN
- LAN DHCP Enabled
- Wireless: AP, Regulatory Domain = CANADA, wl0 Mixed (ch. 6), wl1 AC/N-Mixed (ch. 149, VHT80), AES
- 1 wireless VLAN on wl0
- SNMP disabled, SSH enabled, Telnet disabled
- Firewall enabled, Log Level high
- Syslog: to local server. klogd: disabled.
- USB support - Off
- No custom scripts
- NO: ttraf, Tor, VNC, Zabbix, VPN, Radius, OpenVPN
- NO: UPnP, DMZ, QoS
- NO: Samba, CIFS, JFFS2, miniDLNA, Entware, Optware _________________ Netgear R7000: v3.0-r54248 std (11/29/23)
EdgeRouter-X: EdgeOS v2.0.9-hotfix 7
Joined: 29 Sep 2020 Posts: 260 Location: United States
Posted: Fri Apr 30, 2021 18:08 Post subject:
Router: Netgear R7000P
Kernel: Linux 4.4.267 #2629 SMP Sat Apr 24 11:31:48 +07 2021 armv7l
Reset: no
Mode/Status: Gateway AP 2.4GHz 5Ghz IPv6 Unbound custom conf JFFS2 SFE:Disable static leases / working
Issues: running well thanks BrainSlayer and dd-wrt community
Last edited by itwontbewe on Sun Sep 05, 2021 21:47; edited 2 times in total
Joined: 18 Mar 2014 Posts: 12915 Location: Netherlands
Posted: Thu May 06, 2021 7:30 Post subject:
Router Model: Linksys E2000 (converted N320)
Firmware Version: DD-WRT v3.0-r46446 mega (04/24/21)
Kernel Version: Linux 4.4.267 #8391 Sat Apr 24 15:42:38 +07 2021 mips
Upgraded: from DD-WRT v3.0-r45820 mega (02/23/21)
Reset: Yes
Status: Up and running for 4 hours, basic setup as Gateway, static leases, OpenVPN client (tun) (on Keepsolid) up and running, VPN download speed 5-6 Mb/s, Wifi 2,4GHz working.
OpenVPN server working, WireGuard client working ( speed around 18 Mb/s )
Router/Version: R7000P
File/Kernel: factory to ddwrt
Previous/Reset: No reset
Mode/Status: AP, DHCP, Wifi 2.4G and 5G, Privoxy, WireGuard server and client, keep alive reboot once a week
Issues/Errors: none so far. Up for one week.
Posted: Thu May 06, 2021 21:56 Post subject: Asus RT-AC3200 experimental driver
Router: Asus RT-AC3200
Firmware: v3.0-r46446 std(04/2/21) experimental driver
CPU Model: Broadcom BCM4708
Status: not working properly.
Mode: Gateway
Reset: No
Services: NordVPN w/ openvpn client, SAMBA, FTP.
Wifi: 2.4 loose his connections after 12hours / 5.0Ghz stable
FTP service is also unstable, folders are failing to open.
Back to Version: DD-WRT v3.0-r46395 std (04/19/21) _________________ RT-AC68U
RT-AC3200
TL-MR3020
TL-WDR3600 v1
Router/Version: Netgear R7000 (x2)
File/Kernel: Linux 4.4.267 #2623 SMP Fri Apr 23 07:31:02 +07 2021 armv7l
Previous/Reset: r45993
Mode/Status: Unit 1: Gateway, DHCP, Wifi, USB/NAS, Unit 2: Wifi Repeater
Issues/Errors: After upgrading as requested regarding NAS/Samba issues, connectivity resistance is better though not 100% reliable. Also seeing quite a few Samba-related errors. Only errors related to Unit 1 are of import.
Here's a sample (from last non-err entry to next):
May 6 19:25:43 ROUTER daemon.info process_monitor[2054]: cyclic NTP Update success (servers mx.pool.ntp.org)
May 6 19:28:26 ROUTER daemon.err httpd[2089]: httpd : Request Error Code 408: Unexpected connection close in intitial request
May 6 19:29:43 ROUTER daemon.err httpd[2089]: httpd : Request Error Code 408: Unexpected connection close in intitial request
May 6 19:30:59 ROUTER daemon.err httpd[2089]: httpd : Request Error Code 408: Unexpected connection close in intitial request
May 6 19:39:16 ROUTER daemon.err httpd[2089]: httpd : Request Error Code 408: Unexpected connection close in intitial request
May 6 19:43:15 ROUTER daemon.err httpd[2089]: httpd : Request Error Code 408: Unexpected connection close in intitial request
May 6 19:44:31 ROUTER daemon.err httpd[2089]: httpd : Request Error Code 408: Unexpected connection close in intitial request
May 6 19:45:47 ROUTER daemon.err httpd[2089]: httpd : Request Error Code 408: Unexpected connection close in intitial request
May 6 20:23:51 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:51 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:51 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:51 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:51 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:52 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:52 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:52 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:52 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:52 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:52 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:52 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:52 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:25:44 ROUTER daemon.debug ntpclient[13393]: Connecting to mx.pool.ntp.org [192.36.143.130] ...
Router/Version: Broadcom Northstar (Linksys EA6200) File/Kernel: Linux 4.4.267 #2623 SMP Fri Apr 23 07:31:02 +07 2021 armv7l Previous/Reset: No Mode/Status: OK Issues/Errors: Usual Linksys EA6xxx stuff
This would be a really nice router if it could actually USE it's full 64k nvram. So far even though it says it has 64k nvram the router starts screwing up once it goes much above 32k usage of nvram (mainly dropping configuration entries) After cleaning nvram with the https://wiki.dd-wrt.com/wiki/index.php/Useful_Scripts cleanout script and rebooting you end up with 31k of nvram in use.
Web based "factory reset" button DOES NOT work but I think this is by design on these device
You have to flash it 2 times since there's 2 partitions. The router does properly switch over to the "backup" partition after flashing it the first time. (well it did for me)
Router/Version: Netgear WNDR4500v1 File/Kernel: Linux 4.4.267 #8375 Sat Apr 24 15:27:29 +07 2021 mips Previous/Reset: No Mode/Status: WL0,WL1=WAN Client Issues/Errors: None
tedm wrote:
....This would be a really nice router if it could actually USE it's full 64k nvram. So far even though it says it has 64k nvram the router starts screwing up once it goes much above 32k usage of nvram (mainly dropping configuration entries)....
Router/Version: Netgear WNDR4000
File/Kernel: DD-WRT v3.0-r46446 mega (04/24/21)/Linux 4.4.267 #8391
Previous/Reset: r45735 / no
Mode/Status: AP/full access wifi and guest wifi
Issues/Errors: None so far, more stable than previous r45735
This is my upstairs access point. It used to have r45735 but our son complained about losing wifi connections at irregular intervals. A reboot would fix that, but only for a while. Sometimes an hour, sometimes several days.
So far the r46446 build seems more stable. Been running over a week now and it has not needed a single reboot.
Router/Version: Netgear R7000 (x2)
File/Kernel: Linux 4.4.267 #2623 SMP Fri Apr 23 07:31:02 +07 2021 armv7l
Previous/Reset: r45993
Mode/Status: Unit 1: Gateway, DHCP, Wifi, USB/NAS, Unit 2: Wifi Repeater
Issues/Errors: After upgrading as requested regarding NAS/Samba issues, connectivity resistance is better though not 100% reliable. Also seeing quite a few Samba-related errors. Only errors related to Unit 1 are of import.
Here's a sample (from last non-err entry to next):
May 6 19:25:43 ROUTER daemon.info process_monitor[2054]: cyclic NTP Update success (servers mx.pool.ntp.org)
May 6 19:28:26 ROUTER daemon.err httpd[2089]: httpd : Request Error Code 408: Unexpected connection close in intitial request
May 6 19:29:43 ROUTER daemon.err httpd[2089]: httpd : Request Error Code 408: Unexpected connection close in intitial request
May 6 19:30:59 ROUTER daemon.err httpd[2089]: httpd : Request Error Code 408: Unexpected connection close in intitial request
May 6 19:39:16 ROUTER daemon.err httpd[2089]: httpd : Request Error Code 408: Unexpected connection close in intitial request
May 6 19:43:15 ROUTER daemon.err httpd[2089]: httpd : Request Error Code 408: Unexpected connection close in intitial request
May 6 19:44:31 ROUTER daemon.err httpd[2089]: httpd : Request Error Code 408: Unexpected connection close in intitial request
May 6 19:45:47 ROUTER daemon.err httpd[2089]: httpd : Request Error Code 408: Unexpected connection close in intitial request
May 6 20:23:51 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:51 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:51 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:51 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:51 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:52 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:52 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:52 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:52 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:52 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:52 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:52 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:23:52 ROUTER local5.err ksmbd: [ksmbd-worker/11067]: ERROR: SRVSVC: unsupported INVOKE method 21
May 6 20:25:44 ROUTER daemon.debug ntpclient[13393]: Connecting to mx.pool.ntp.org [192.36.143.130] ...
Hey when it messes up to the point it is dropping connections can you use Telnet on it using a ethernet connection and log into the console and run a command "top" to see if Ksmbd is using all the processor? Which will explain the dropped connections and other problems. I have a Dell Studio 540 here running it. The recent builds the ksmbd which is part of the NAS sharing in DD-WRT has been super buggy with the processor being fully utilized at random. Once it happens a reboot will fix it for a short time until it happens again.
I just want to know if this is isolated to x64 version or if it is effecting the broadcom routers too.