New Build - 09/24/2020 - r44467

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page 1, 2, 3  Next
Author Message
blkt
DD-WRT Guru


Joined: 20 Jan 2019
Posts: 2816

PostPosted: Thu Sep 24, 2020 19:18    Post subject: New Build - 09/24/2020 - r44467 Reply with quote
[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.


Downloads: (DD-WRT website) HTTPS & FTP (try another if a link doesn't work)

CLI Flash: 'cd /tmp' then 'wget {file URL}' (or 'curl -k {file URL} -o {file}') with http (not https) or ftp. Then 'write {file} linux'.

Repository: Trac SVN changelog since last build r44406 (GitHub mirror)

Notes:
r41664 or later for SFE NAT (k3.2+), KRACK (k24+), PBR+SFE, CAKE & FQ_CODEL_FAST (reset!), GTK Rekey timer fixes.
• Reset button was broken at 40571, then fixed in build r40750.
Experimental build option for Broadcom 8MB+ K2.x devices (limited currently): broadcom_K3X_mipsel32r1
• CVE-2019-14899 VPN fix (applicability depends on VPN setup) and GUI toggle. 6920, 6928, 6931, 6932 (WIP 7040)
In-kernel Samba has been implemented this year and default min/max versions have changed 6954, 6957, with WSD support.
• Broadcom MIPS devices are now on kernel 4.4. N66U/AC66U half memory is fully resolved.
• Local DNS option removed from Services->DNSMasq in changesets 43080 and 43081; ref: #7092
• DHCP and DNS help (English) updated in 43083; ref: #7091
• WAN lease time approaching zero bug on WRT54* devices fixed in 43191; ref: #6456
• Images for WNR3500Lv2 (BRCM NAND flash crash bug) fixed in 43219 (43217); ref: #7098
• WireGuard 1.0.20200908 & Tools: PBR, Kill Switch, Inbound Firewall, Naming of Peers, Status, Key, Guides. Thanks BS & egc!

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 boot fixed 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.

Example Template:
Code:
[b]Router/Version: [/b]
[b]File/Kernel: [/b]
[b]Previous/Reset: [/b]
[b]Mode/Status: [/b]
[b]Issues/Errors: [/b]
Sponsor
bushant
DD-WRT Guru


Joined: 18 Nov 2015
Posts: 1570
Location: WCentral Indiana USA

PostPosted: Thu Sep 24, 2020 23:45    Post subject: Reply with quote
R6200v2 WLAN Rep. 2.4 GHz
DD-WRT v3.0-r44467 std (09/24/20)
Linux 4.4.236 #1134 SMP Thu Sep 24
TFTP R6250.chk upgrade over 44432

Uptime 11:47
All working fine.

Thank You BrainSlayer and others.

_________________
STUBBY DoT install guide----Forum Guide Lines (Please read!) --- How to get help the right way----PIA Setup Guide by egc----
flyzipper
DD-WRT User


Joined: 21 Feb 2016
Posts: 473

PostPosted: Fri Sep 25, 2020 0:35    Post subject: Reply with quote
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r44467 std (09/24/20)
Kernel: Linux 4.4.236 #1134 SMP Thu Sep 24 10:35:23 +04 2020 armv7l
Previous: r44406
Mode/Status: Gateway / working
Reset: no
Issues/Errors: Working well so far.

Uptime: 42mins
Temperatures: CPU 65.2 °C / WL0 45.8 °C / WL1 51.8 °C
mac913
DD-WRT Guru


Joined: 02 May 2008
Posts: 1626
Location: Canada

PostPosted: Fri Sep 25, 2020 1:01    Post subject: Reply with quote
R7000 - IPTV Gateway (Streaming to BOTH: ISP 4K PRV & 4K TVBox)
-DHCP WAN
-Mode Gateway
-SFE Enabled
-SSH -Custom Port, No-Key Password Required & Local Only
-Syslog Enabled
-NTP server left blank
-QoS - Disabled
-TCP Congestion - bic
-Filter Multicast Disabled
-IGMP Snooping On - br0 only
-USB Disabled
-IPv6 Disabled
-STP All Off
-DDNS Disabled
-WiFi Disabled
-Telnet Disabled
-ttraff Disabled
-Info Site Password Protection Enabled
-Custom Startup Script

Router: Netgear R7000 for ISP 4K IPTV Gateway
Firmware: DD-WRT v3.0-r44467 std (09/24/20) [From: DD-WRT v3.0-r44406 std (09/18/20)]
Linux Rel: Linux 4.4.236 #1134 SMP Thu Sep 24 armv7l [From: Linux 4.4.236 #1070 SMP Thu Sep 17 armv7l]
Reset: No, CLI Upgrade & Reboot
Status & Uptime over 3 hours. Multi-Streaming AV from ISP 4K TV Boxes, All Good!
Issues/Fixes: none/none

_________________
Home Network on Telus PureFibre - 10GbE Copper Backbone
2x R7800 - Gateway & WiFi & 3xWireGuard - DDWRT r46329 Std
R7000 - Wired ISP 4K IPTV Gateway - DDWRT r44483 Std

Off Site 1

R7000 - Gateway & WiFi & WireGuard - DDWRT r44483 Std
WRT610Nv1 - Client Bridge - DDWRT r33679 Mega K2.4

Off Site 2

R7000 - Gateway & WiFi - DDWRT r44483 Std
E2000 - Wired ISP IPTV PVR Blocker - DDWRT r35531


YAMon 3.4.6 | DNSCrypt-Proxy V2
hanta
DD-WRT Novice


Joined: 02 Apr 2007
Posts: 12
Location: Richmond, CA

PostPosted: Fri Sep 25, 2020 2:41    Post subject: Reply with quote
Router: Netgear R8000
Firmware: DD-WRT v3.0-r44467 std (09/24/20)
Kernel: Linux 4.4.236 #1139 SMP Thu Sep 24 11:04:17 +04 2020 armv7l
Temperatures: CPU 56.4 °C / WL0 44.0 °C / WL1 45.5 °C / WL2 42.5 °C
Previous/Reset: r44340 experimental driver (09/10/20) / yes
Mode/Status: Gateway, up for 35 min
Issues/Errors: looks good so far, even the sonos speaker that couldn't connect for weeks is back up

Whether it was the new firmware, or resetting and reconfiguring, it is great this is working. Fingers crossed for stability and robustness.

THANK YOU!!!
liweilee
DD-WRT Novice


Joined: 17 Sep 2020
Posts: 10

PostPosted: Fri Sep 25, 2020 6:46    Post subject: Reply with quote
Router/Version: TP-Link Archer C8 V1
Firmware: DD-WRT v3.0-r44340 std (09/10/20)
Kernel: Linux 4.4.235 #1027 SMP Thu Sep 10 08:20:07 +04 2020 armv7l
Previous: r44251
Mode: Gateway, AP
Reset: Yes
Status:

Working fine on iOS 12/13 for years but after upgraded iPhone to IOS 14.0, usb tethering iPhone not working.

I plug the iPhone(iOS14) in the laptop and desktop computer(windows 10/macOS Catalina) and the USB tethering works, but it doesn’t work on my TP-Link Archer C8 V1.

Related links:

Working fine on IOS 13 but after upgraded iPhone to IOS 14, usb tethering iPhone not working.
https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1217124#1217124

iOS 14 USB tethering support
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=326630

iphone tethering not working on ios14
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=326650




syslog below: (physical address modified to xx:xx:xx:xx:xx:xx)

Jan 1 08:00:08 TP-Link Archer C8 syslog.info syslogd started: BusyBox v1.32.0
Jan 1 08:00:08 TP-Link Archer C8 user.info : resetbutton : resetbutton daemon successfully started
Jan 1 08:00:08 TP-Link Archer C8 user.info : bridge : bridge br0 successfully added
Jan 1 08:00:08 TP-Link Archer C8 daemon.info mstpd[647]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 8
Jan 1 08:00:08 TP-Link Archer C8 daemon.info mstpd[647]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 8
Jan 1 08:00:08 TP-Link Archer C8 user.info : bridge : interface vlan1 successfully added to bridge br0
Jan 1 08:00:08 TP-Link Archer C8 user.info : bridge : interface vlan2 successfully added to bridge br0
Jan 1 08:00:09 TP-Link Archer C8 user.info : bridge : interface eth1 successfully added to bridge br0
Jan 1 08:00:15 TP-Link Archer C8 user.info : bridge : interface eth2 successfully added to bridge br0
Jan 1 08:00:15 TP-Link Archer C8 user.info : syslogd : syslog daemon successfully stopped
Jan 1 08:00:15 TP-Link Archer C8 user.info : wland : daemon successfully started
Jan 1 08:00:15 TP-Link Archer C8 user.info : telnetd : daemon successfully started
Jan 1 08:00:15 TP-Link Archer C8 syslog.info syslogd exiting
Jan 1 08:00:15 TP-Link Archer C8 syslog.info syslogd started: BusyBox v1.32.0
Jan 1 08:00:15 TP-Link Archer C8 user.info : sfe : shortcut forwarding engine successfully started
Jan 1 08:00:15 TP-Link Archer C8 user.info : cron : daemon successfully started
Jan 1 08:00:15 TP-Link Archer C8 cron.info cron[918]: (CRON) STARTUP (fork ok)
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq[925]: started, version 2.82 cachesize 1500
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq[925]: compile time options: IPv6 GNU-getopt no-DBus no-UBus no-i18n no-IDN DHCP DHCPv6 no-Lua no-TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect no-inotify no-dumpfile
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq-dhcp[925]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 1d
Jan 1 08:00:15 TP-Link Archer C8 user.info : dnsmasq : daemon successfully started
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq[925]: using only locally-known addresses for domain test
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq[925]: using only locally-known addresses for domain onion
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq[925]: using only locally-known addresses for domain localhost
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq[925]: using only locally-known addresses for domain local
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq[925]: using only locally-known addresses for domain invalid
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq[925]: using only locally-known addresses for domain bind
Jan 1 08:00:15 TP-Link Archer C8 daemon.warn dnsmasq[925]: no servers found in /tmp/resolv.dnsmasq, will retry
Jan 1 08:00:15 TP-Link Archer C8 daemon.info dnsmasq[925]: read /etc/hosts - 3 addresses
Jan 1 08:00:17 TP-Link Archer C8 kern.crit usbmuxd[988]: [0] libusb_init failed: LIBUSB_ERROR_OTHER
Jan 1 08:00:17 TP-Link Archer C8 user.info : ppp_redial : redial process successfully started
Jan 1 08:00:17 TP-Link Archer C8 user.info : ttraff : traffic counter daemon successfully started
Jan 1 08:00:17 TP-Link Archer C8 daemon.info httpd[1011]: httpd : httpd server started at port 80
Jan 1 08:00:17 TP-Link Archer C8 user.info : httpd : http daemon successfully started
Jan 1 08:00:19 TP-Link Archer C8 daemon.info dnsmasq-dhcp[925]: DHCPDISCOVER(br0) xx:ad:34:87:e0:4c
Jan 1 08:00:19 TP-Link Archer C8 daemon.info dnsmasq-dhcp[925]: DHCPOFFER(br0) 192.168.1.136 c4:ad:34:87:e0:4c
Jan 1 08:00:19 TP-Link Archer C8 daemon.info dnsmasq-dhcp[925]: DHCPREQUEST(br0) 192.168.1.136 c4:ad:34:87:e0:4c
Jan 1 08:00:19 TP-Link Archer C8 daemon.info dnsmasq-dhcp[925]: DHCPACK(br0) 192.168.1.136 c4:ad:34:87:e0:4c MikroTik
Jan 1 08:00:24 TP-Link Archer C8 user.info : nas : wait for network init
Jan 1 08:00:34 TP-Link Archer C8 user.info : nas : start nas lan
Jan 1 08:00:34 TP-Link Archer C8 user.info : nas : start nas for wl0
Jan 1 08:00:34 TP-Link Archer C8 user.info : nas : NAS lan (wl0 interface) successfully started
Jan 1 08:00:34 TP-Link Archer C8 user.info : nas : start nas lan
Jan 1 08:00:34 TP-Link Archer C8 user.info : nas : start nas for wl1
Jan 1 08:00:34 TP-Link Archer C8 user.info : nas : NAS lan (wl1 interface) successfully started
Jan 1 08:00:35 TP-Link Archer C8 user.info : nas : daemon successfully stopped
Jan 1 08:00:37 TP-Link Archer C8 user.info : nas : daemon hanging, send SIGKILL
Jan 1 08:00:37 TP-Link Archer C8 user.info : nas : start nas lan
Jan 1 08:00:37 TP-Link Archer C8 user.info : nas : start nas for wl0
Jan 1 08:00:37 TP-Link Archer C8 user.info : nas : NAS lan (wl0 interface) successfully started
Jan 1 08:00:37 TP-Link Archer C8 user.info : nas : start nas lan
Jan 1 08:00:37 TP-Link Archer C8 user.info : nas : start nas for wl1
Jan 1 08:00:37 TP-Link Archer C8 user.info : nas : NAS lan (wl1 interface) successfully started
Jan 1 08:00:37 TP-Link Archer C8 user.info : httpd : daemon successfully stopped
Jan 1 08:00:37 TP-Link Archer C8 daemon.info httpd[1015]: httpd : httpd server shutdown
Jan 1 08:00:37 TP-Link Archer C8 daemon.info httpd[1060]: httpd : httpd server started at port 80
Jan 1 08:00:37 TP-Link Archer C8 user.info : httpd : http daemon successfully started
Jan 1 08:00:37 TP-Link Archer C8 user.info : resetbutton : daemon successfully stopped
Jan 1 08:00:37 TP-Link Archer C8 user.info : resetbutton : resetbutton daemon successfully started
Jan 1 08:01:20 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:01:21 TP-Link Archer C8 kern.err usbmuxd[1361]: [1] ERROR: client_write: sending to fd 12 failed: Broken pipe
Jan 1 08:01:21 TP-Link Archer C8 kern.err usbmuxd[1361]: [1] connection_teardown: aborting buffer flush to client after error.
Jan 1 08:01:52 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:01:52 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:01:52 TP-Link Archer C8 kern.err usbmuxd[1444]: [1] ERROR: client_write: sending to fd 12 failed: Broken pipe
Jan 1 08:01:52 TP-Link Archer C8 kern.err usbmuxd[1444]: [1] ERROR: client_write: sending to fd 12 failed: Broken pipe
Jan 1 08:01:52 TP-Link Archer C8 kern.err usbmuxd[1444]: [1] connection_teardown: aborting buffer flush to client after error.
Jan 1 08:02:24 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:02:24 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:02:25 TP-Link Archer C8 kern.err usbmuxd[1534]: [1] ERROR: client_write: sending to fd 12 failed: Broken pipe
Jan 1 08:02:25 TP-Link Archer C8 kern.err usbmuxd[1534]: [1] ERROR: client_write: sending to fd 12 failed: Broken pipe
Jan 1 08:02:25 TP-Link Archer C8 kern.err usbmuxd[1534]: [1] connection_teardown: aborting buffer flush to client after error.
Jan 1 08:02:56 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:02:56 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:02:56 TP-Link Archer C8 kern.err usbmuxd[1616]: [1] ERROR: client_write: sending to fd 12 failed: Broken pipe
Jan 1 08:02:56 TP-Link Archer C8 kern.err usbmuxd[1616]: [1] ERROR: client_write: sending to fd 12 failed: Broken pipe
Jan 1 08:02:56 TP-Link Archer C8 kern.err usbmuxd[1616]: [1] connection_teardown: aborting buffer flush to client after error.
Jan 1 08:03:28 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:04:00 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:04:00 TP-Link Archer C8 kern.err usbmuxd[1818]: [1] ERROR: client_write: sending to fd 12 failed: Broken pipe
Jan 1 08:04:00 TP-Link Archer C8 kern.err usbmuxd[1818]: [1] connection_teardown: aborting buffer flush to client after error.
Jan 1 08:04:32 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:04:32 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:04:32 TP-Link Archer C8 kern.err usbmuxd[1908]: [1] ERROR: client_write: sending to fd 12 failed: Broken pipe
Jan 1 08:04:32 TP-Link Archer C8 kern.err usbmuxd[1908]: [1] ERROR: client_write: sending to fd 12 failed: Broken pipe
Jan 1 08:04:32 TP-Link Archer C8 kern.err usbmuxd[1908]: [1] connection_teardown: aborting buffer flush to client after error.
Jan 1 08:05:03 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:05:04 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:05:14 TP-Link Archer C8 daemon.info dnsmasq-dhcp[925]: DHCPDISCOVER(br0) xx:xx:xx:xx:xx:xx
Jan 1 08:05:14 TP-Link Archer C8 daemon.info dnsmasq-dhcp[925]: DHCPOFFER(br0) 192.168.1.111 xx:xx:xx:xx:xx:xx
Jan 1 08:05:14 TP-Link Archer C8 daemon.info dnsmasq-dhcp[925]: DHCPDISCOVER(br0) xx:xx:xx:xx:xx:xx
Jan 1 08:05:14 TP-Link Archer C8 daemon.info dnsmasq-dhcp[925]: DHCPOFFER(br0) 192.168.1.111 xx:xx:xx:xx:xx:xx
Jan 1 08:05:15 TP-Link Archer C8 daemon.info dnsmasq-dhcp[925]: DHCPREQUEST(br0) 192.168.1.111 xx:xx:xx:xx:xx:xx
Jan 1 08:05:15 TP-Link Archer C8 daemon.info dnsmasq-dhcp[925]: DHCPACK(br0) 192.168.1.111 xx:xx:xx:xx:xx:xx iPad
Jan 1 08:05:35 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:05:36 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:05:36 TP-Link Archer C8 kern.err usbmuxd[2076]: [1] ERROR: client_write: sending to fd 12 failed: Broken pipe
Jan 1 08:05:36 TP-Link Archer C8 kern.err usbmuxd[2076]: [1] ERROR: client_write: sending to fd 12 failed: Broken pipe
Jan 1 08:05:36 TP-Link Archer C8 kern.err usbmuxd[2076]: [1] connection_teardown: aborting buffer flush to client after error.
Jan 1 08:05:43 TP-Link Archer C8 daemon.info dnsmasq-dhcp[925]: DHCPREQUEST(br0) 192.168.1.111 xx:xx:xx:xx:xx:xx
Jan 1 08:05:43 TP-Link Archer C8 daemon.info dnsmasq-dhcp[925]: DHCPACK(br0) 192.168.1.111 xx:xx:xx:xx:xx:xx iPad
Jan 1 08:05:49 TP-Link Archer C8 daemon.info dnsmasq-dhcp[925]: DHCPRELEASE(br0) 192.168.1.111 xx:xx:xx:xx:xx:xx
Jan 1 08:06:08 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:06:08 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:06:21 TP-Link Archer C8 daemon.err httpd[1064]: httpd : Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 08:06:40 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:06:40 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:07:12 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:07:12 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:07:43 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:07:44 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:08:16 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:08:16 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:08:48 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:08:48 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:09:20 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:09:20 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:09:52 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:09:52 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:09:52 TP-Link Archer C8 kern.err usbmuxd[2908]: [1] ERROR: client_write: sending to fd 12 failed: Broken pipe
Jan 1 08:09:52 TP-Link Archer C8 kern.err usbmuxd[2908]: [1] ERROR: client_write: sending to fd 12 failed: Broken pipe
Jan 1 08:09:52 TP-Link Archer C8 kern.err usbmuxd[2908]: [1] connection_teardown: aborting buffer flush to client after error.
Jan 1 08:10:24 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:10:24 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:10:56 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:10:56 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:10:56 TP-Link Archer C8 kern.err usbmuxd[3095]: [1] ERROR: client_write: sending to fd 12 failed: Broken pipe
Jan 1 08:10:56 TP-Link Archer C8 kern.err usbmuxd[3095]: [1] connection_teardown: aborting buffer flush to client after error.
Jan 1 08:11:28 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:11:28 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:11:28 TP-Link Archer C8 kern.err usbmuxd[3183]: [1] ERROR: client_write: sending to fd 12 failed: Broken pipe
Jan 1 08:11:28 TP-Link Archer C8 kern.err usbmuxd[3183]: [1] ERROR: client_write: sending to fd 12 failed: Broken pipe
Jan 1 08:11:28 TP-Link Archer C8 kern.err usbmuxd[3183]: [1] connection_teardown: aborting buffer flush to client after error.
Jan 1 08:12:00 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:12:00 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:12:32 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:12:32 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
Jan 1 08:13:04 TP-Link Archer C8 user.info : usbmuxd : IPhone Mux daemon successfully stopped
Jan 1 08:13:04 TP-Link Archer C8 user.info : udhcpc : DHCP Client successfully stopped
liweilee
DD-WRT Novice


Joined: 17 Sep 2020
Posts: 10

PostPosted: Fri Sep 25, 2020 6:51    Post subject: Reply with quote
Sorry, I forgot to modify the information of [Firmware]
, [kernel] and [Previous]. It should be below...

Router/Version: TP-Link Archer C8 V1
Firmware: DD-WRT v3.0-r44467 std (09/24/20)
Kernel: Linux 4.4.236 #1136 SMP Thu Sep 24 10:51:01 +04 2020 armv7l
Previous: r44406
Mode: Gateway, AP
Reset: Yes
amadeus
DD-WRT Novice


Joined: 06 Nov 2019
Posts: 33

PostPosted: Fri Sep 25, 2020 9:56    Post subject: Reply with quote
Router: Netgear R6700 v3
Firmware: DD-WRT v3.0-r44467 std (09/24/20)
Kernel: Linux 4.4.236 #1134 SMP Thu Sep 24 10:35:23 +04 2020 armv7l
Previous: r44406
Mode/Status: Gateway / working
Reset: no
Issues/Errors: none so far

Uptime: 15 min
Temperatures: CPU 76.9 °C / WL0 49.6 °C / WL1 56.9 °C
IONK
DD-WRT User


Joined: 19 Aug 2011
Posts: 231

PostPosted: Fri Sep 25, 2020 12:51    Post subject: Reply with quote
Router/Version: D-Link DIR-868L Rev.A1
File/Kernel: dir868a-webflash.bin / Linux 4.4.236 #1134 SMP Thu Sep 24 10:35:23 +04 2020 armv7l
Previous/Reset: DD-WRT v3.0-r44406 std (09/18/20) / no
Mode/Status: Repeater Bridge on 5GHz AC/N-Mixed (wl0 is purposely turned off) / working
Issues/Errors: none
Iceberger
DD-WRT User


Joined: 03 Jun 2018
Posts: 56

PostPosted: Fri Sep 25, 2020 13:27    Post subject: Reply with quote
Router Model / Version: Trendnet TEW818DRU
File: trendnet-818dru-webflash.bin
Firmware: DD-WRT v3.0-r44467 std (09/24/20)
Kernel: Linux 4.4.236 #1136 SMP Thu Sep 24 10:51:01 +04 2020 armv7l
Previous: DD-WRT v3.0-r44236 std (08/22/20)
Reset: No
Mode: Gateway / AP
Uptime: ~ 30 minutes
Status: working
Issues / Errors:
aerogems
DD-WRT Novice


Joined: 25 Sep 2020
Posts: 7

PostPosted: Fri Sep 25, 2020 16:53    Post subject: Reply with quote
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r44467 std (09/24/20)
Kernel: Linux 4.4.236 #1134 SMP
Mode/Status: AP
Reset: Yes
Issues/Errors: Frequent Wireless Dropouts While Streaming

I switched over from Tomato to the 8/15/20 build and everything has been working great. Decide to try to update to one of the September builds and when streaming shows from my Plex server to my nVidia Shield TV (2019), the shows frequently just stop playing. They don't freeze, it's as if they reached the end of the file. This has happened with the 9/10/20, 9/18/20, and 9/24/20 builds and with multiple different files each time.

My Plex server is being run from my Synology NAS, which is wired directly to my R7000, and then my Shield connects wirelessly (via 5GHz) to the R7000. So everything is within my LAN.

The files being streamed are 1080p video with AC3 Stereo audio. Total file size is about 1GB for a 40min episode, so bandwidth shouldn't be an issue, and again, the 8/15/20 build works flawlessly. Usually it takes 25-30 minutes before the issue presents itself, but with the 9/24/20 build I had it happen after about 30 minutes and then 2-3 more times within the next six minutes worth of the episode.

I tried flashing the 9/24/20 build and then doing a factory reset, manually entering in the settings instead of using a backup. No change in symptoms. Had similar experiences with the 9/10/20 and 9/18/20 builds.

I have also tried rebooting the router and the Shield which does not resolve the issue.
dwardo
DD-WRT User


Joined: 07 Feb 2013
Posts: 86
Location: France

PostPosted: Fri Sep 25, 2020 19:14    Post subject: Reply with quote
Router/Version: TP-Link Archer C9 v1
File/Kernel: Linux 4.4.236 #1136 SMP Thu Sep 24 10:51:01 +04 2020 armv7l
Previous/Reset: r44406/no
Mode/Status: Gateway/2.4GHz & 5GHz AP/Openvpn server/Wireguard server/DHCP server/DNS Server/Port forwarding
Issues/Errors: nothing new so far after 18min uptime
js290
DD-WRT Novice


Joined: 21 Sep 2014
Posts: 13

PostPosted: Sat Sep 26, 2020 0:18    Post subject: Reply with quote
js290 wrote:
httpd process will not stay running on WRT54Gv5 broadcom/dd-wrt.v24_micro_generic.bin.

GUI transition from saving/applying/rebooting not smooth nor seamless in 44467. Seems to pass traffic, fine, though.

GUI upgrade from 44406 was not smooth, required multiple 30/30/30 resets. 44406 is a better micro build.


Router/Version: Linksys WRT54Gv5
File/Kernel: v3.0-r44467 micro (09/24/20)
Previous/Reset: r44406
Mode/Status: AP
Issues/Errors:

Initially posted that in the wrong 44467 thread (for Atheros). The WRT54Gv5 stabilized on 44467. httpd does not want to stay running, but wireless & routing seems to work fine. 44467 is not a worse micro build than 44406. The real problem with the WRT54Gv5 is the 8MB of RAM, which is probably why httpd keeps dying.

Router/Version: Linksys WRT54G2v1
File/Kernel: v3.0-r44467 micro (09/24/20)
Previous/Reset: r44406
Mode/Status: AP
Issues/Errors:

Now testing this micro build on a WRT54G2v1, which has 16MB RAM, but I was struggling with latency issues on this router before. Will report back...
Updated: Runs fine, except for latency issues (related to this hardware platform) that affect the usability of RDP. Otherwise seems like a good build since changeset 44407 for micro got rolled up into this build.


Last edited by js290 on Sun Sep 27, 2020 4:23; edited 1 time in total
Welshchris
DD-WRT User


Joined: 05 May 2010
Posts: 122

PostPosted: Sat Sep 26, 2020 1:13    Post subject: Reply with quote
Router: Netgear R8000
Firmware: DD-WRT v3.0-r44467 std (09/24/20)
Kernel: Linux 4.4.236 #1139 SMP Thu Sep 24 11:04:17 +04 2020 armv7l
Temperatures: CPU 63.6 °C / WL0 49.5 °C / WL1 47.0 °C / WL2 47.5 °C
Previous/Reset: r44406 (09/18/20) / yes
Mode/Status: Gateway, up for 7hrs 51 mins
Issues/Errors: all seems well

All seems well.
Abboo
DD-WRT User


Joined: 03 Apr 2016
Posts: 170

PostPosted: Sat Sep 26, 2020 1:36    Post subject: Reply with quote
Router Model: Netgear R8000
Firmware Version: DD-WRT v3.0-r44467 std (09/24/20)
Kernel Version: Linux 4.4.236 #1142 SMP Thu Sep 24 11:21:56 +04 2020 armv7l
Previous Version: DD-WRT v3.0-r44340 std (09/10/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
Uptime: 1 day, 2:12
Reset: no
Errors: as reported in the syslog below

Dec 31 20:00:20 DD-WRT user.err wsdd2[1203]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Dec 31 20:00:20 DD-WRT local5.err ksmbd: [ksmbd-worker/1218]: ERROR: Can't open `/tmp/smb.db': No such file or directory
Dec 31 20:00:20 DD-WRT local5.err ksmbd: [ksmbd-worker/1218]: ERROR: User database file does not exist. Only guest sessions (if permitted) will work.
Sep 24 19:08:16 DD-WRT user.err wsdd2[1203]: Terminated received.
Sep 24 19:08:16 DD-WRT local5.err ksmbd: [ksmbd-manager/1217]: ERROR: WARNING: child process exited abnormally: 1218
Sep 24 19:08:17 DD-WRT local5.err ksmbd: [ksmbd-worker/1930]: ERROR: Can't open `/tmp/smb.db': No such file or directory
Sep 24 19:08:17 DD-WRT local5.err ksmbd: [ksmbd-worker/1930]: ERROR: User database file does not exist. Only guest sessions (if permitted) will work.
Sep 24 19:08:19 DD-WRT local5.err ksmbd: [ksmbd-manager/2206]: ERROR: Failed to create lock file: File exists
Sep 24 19:13:25 DD-WRT daemon.err httpd[1315]: httpd : Request Error Code 408: No request appeared within a reasonable time period.
Sep 25 21:19:19 DD-WRT daemon.err httpd[1315]: httpd : Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Goto page 1, 2, 3  Next Display posts from previous:    Page 1 of 3
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum