Joined: 08 May 2018 Posts: 14249 Location: Texas, USA
Posted: Mon Dec 21, 2020 23:09 Post subject: New Build - 12-21-2020-r45073
[WARNING]: This thread is only for feedback on this beta release for developers and the community's benefit.
DO NOT flash this beta release unless you understand the risks involved and specific device recovery methods.
Avoid discussions! Create threads for questions, general problems or use search; this thread is not for support.
Please list router model & revision, operating & wireless mode(s) and exact filename/firmware image flashed.
Issues, observations, and/or workarounds reported:
• DNScrypt 1.95 can still be used in the GUI but v2 (not compatible) requires Golang and thus Entware. 6246
• WDS does not work on Broadcom ARM devices(only MIPS<->MIPS) & bridge modes on k4.4 devices may sometimes work in some configurations in certain builds but are not supported by the bcmdhd driver. Use client or repeater instead.
• VAPs not working at bootfixed for unbridged VAPs with r40564:40566.Workaround startup command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas(there are a few alternatives, search).
• If start-up scripts do not work from USB add a delay (e.g. wait script or 'sleep 25').
• For Broadcom ARM devices missing 5GHz channels, via telnet/ssh: 'nvram set brcm_unlock=1' 'nvram commit' 'nvram reboot'
Important:
• If reporting issues provide applicable info: 'dmesg', 'cat /tmp/var/log/messages', syslog, serial output, strace, tcpdump etc.
• For firewall NAT or WAN issues provide 'iptables -vnL', 'iptables -t nat -vnL', 'iptables -t mangle -vnL' and the /tmp/.ipt file.
• Search existing SVN tickets before opening a new one. Before reporting, reset and manually setup (no nvram backup).
• Be sure to include operating and wireless modes (Gateway, AP, CB, etc.) along with relevant configuration information.
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r45073 std (12/21/20)
Kernel: Linux 4.4.248 #1602 SMP Sun Dec 20 10:16:32 +07 2020 armv7l
Previous: r45036
Mode/Status: Gateway / working
Issues/Errors: Working well so far.
Uptime: 2hrs 10mins
Upgrade: via web UI, no issues
Reset: no
Temperatures: CPU 66.9 °C / WL0 46.4 °C / WL1 52.2 °C
Joined: 18 Mar 2014 Posts: 12922 Location: Netherlands
Posted: Tue Dec 22, 2020 15:49 Post subject:
Router Model: Netgear R6400v1
Firmware Version: DD-WRT v3.0-r45073 Community Build (12/22/20)
Kernel Version: Linux 4.4.248 #1 SMP Tue Dec 22 11:00:40 CET 2020 armv7l
Upgraded from: DD-WRT v3.0-r44980 std (12/12/20)
Reset: No not this time
Status: Up and running for 4 hours, basic setup as Gateway, static leases, Advanced routing, Port Forwarding, IPv4, DynDNS, 2.4 GHz and 5 GHz.
Running one WireGuard tunnel to Keepsolid and second WireGuard tunnel to own WG server for site-to-site connection.
Errors: No
Router Model: Netgear R8000
Firmware Version: DD-WRT v3.0-r45073 std (12/21/20)
Kernel Version: Linux 4.4.248 #1610 SMP Mon Dec 21 16:03:56 +07 2020 armv7l
Previous Version: DD-WRT v3.0-r45036 std (12/18/20)
Drivers: Experimental
Services: samba, wireguard client, openvpn client, dhcp, wifi 2.4 ghz, usb, nas
Status: working
Updated: via webgui
Mode: AP/gateway
Issues: none
Reset: no
Uptime: 1 day, 22 min
Errors: as reported in the syslog below
Dec 31 20:00:19 DD-WRT user.err wsdd2[1180]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Dec 31 20:00:19 DD-WRT local5.err ksmbd: [ksmbd-worker/1200]: ERROR: Can't open `/tmp/smb.db': No such file or directory
Dec 31 20:00:19 DD-WRT local5.err ksmbd: [ksmbd-worker/1200]: ERROR: User database file does not exist. Only guest sessions (if permitted) will work.
Dec 21 21:25:26 DD-WRT user.err wsdd2[1180]: Terminated received.
Dec 21 21:25:28 DD-WRT local5.err ksmbd: [ksmbd-worker/2016]: ERROR: Can't open `/tmp/smb.db': No such file or directory
Dec 21 21:25:28 DD-WRT local5.err ksmbd: [ksmbd-worker/2016]: ERROR: User database file does not exist. Only guest sessions (if permitted) will work.
Dec 21 21:25:30 DD-WRT local5.err ksmbd: [ksmbd-manager/2294]: ERROR: Failed to create lock file: File exists
Dec 22 07:42:47 DD-WRT daemon.err httpd[1312]: httpd : Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Posted: Wed Dec 23, 2020 12:58 Post subject: After settings reset unable to set Multiple DHCPD option
Router Model: ASUS RT-AC68U
Firmware Version: DD-WRT v3.0-r45073 std (12/21/20)
Previous Version: 44863
Status: Guest network won't give IPs
Updated: via webgui
Reset: Yes
After settings reset and setting everithing up back again, i'm unable to set dhcp for wl0.1
Is there any way to make missing "multiple dhcpd" block to appear in settings? Or i'll have to revert back to 44863 ?
Jan 1 02:00:11 Linksys daemon.info mstpd[684]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 10
Jan 1 02:00:11 Linksys daemon.info mstpd[684]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 10
Jan 1 02:00:11 Linksys daemon.info mstpd[684]: error, CTL_set_msti_bridge_config: Couldn't find bridge with index 10
Jan 1 02:00:12 Linksys daemon.info mstpd[684]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 10
Jan 1 02:00:12 Linksys daemon.info mstpd[684]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 10
Jan 1 02:00:22 Linksys local5.err ksmbd: [ksmbd-manager/1241]: ERROR: Can't open `/tmp/ksmbd.subauth': No such file or directory
Jan 1 02:00:22 Linksys user.err wsdd2[1238]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Dec 24 09:08:16 Linksys user.err wsdd2[1238]: Terminated received.
Dec 24 09:08:16 Linksys local5.err ksmbd: [ksmbd-manager/1241]: ERROR: WARNING: child process exited abnormally: 1242
Dec 24 09:08:20 Linksys local5.err ksmbd: [ksmbd-manager/1985]: ERROR: Failed to create lock file: File exists
Dec 24 09:08:20 Linksys local5.err ksmbd: [ksmbd-manager/2055]: ERROR: Failed to create lock file: File exists
Dec 24 09:53:25 Linksys daemon.err dnsmasq[1282]: failed to send packet: Address family not supported by protocol
Dec 24 10:21:28 Linksys daemon.err dnsmasq[1282]: failed to send packet: Address family not supported by protocol
Dec 24 10:44:04 Linksys daemon.err dnsmasq[1282]: failed to send packet: Address family not supported by protocol
Dec 24 10:50:13 Linksys daemon.err dnsmasq[1282]: failed to send packet: Address family not supported by protocol
Dec 24 10:58:48 Linksys daemon.err dnsmasq[1282]: failed to send packet: Address family not supported by protocol
Dec 24 10:58:48 Linksys daemon.err dnsmasq[1282]: failed to send packet: Address family not supported by protocol
Dec 24 10:59:08 Linksys daemon.err dnsmasq[1282]: failed to send packet: Address family not supported by protocol
Dec 24 10:59:11 Linksys daemon.err dnsmasq[1282]: failed to send packet: Address family not supported by protocol
Dec 24 10:59:12 Linksys daemon.err dnsmasq[1282]: failed to send packet: Address family not supported by protocol
Dec 24 11:01:19 Linksys daemon.err httpd[1522]: httpd : Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases