Posted: Mon Nov 21, 2022 8:37 Post subject: New Build - 11/21/2022 - r50927
Welcome to Broadcom r50927 beta release thread for reporting, feedback to developers & community benefit.
Please do not flash builds until installation is understood, risks involved and device specificrecovery 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:
• WebUI: Clear history or use a portable. Temporary cache bypass: Ctrl+F5, Cmd+Shift+R or new private window/incognito.
• WDS does not work on Broadcom ARM devices (only MIPS<->MIPS) & bridge modes on k4.4 devices may sometimes work
in some configurations for certain builds but are not supported by the bcmdhd driver. Try station or repeater mode but YMMV.
• Please report findings with steps needed to reproduce, configuration, clients, output, logs and important information below!
Important:
• Detail issues & relevant configs, logs: syslog klog 'dmesg' 'cat /tmp/var/log/messages' nvram set console_debug=1, serial.
• Firewall NAT: 'iptables -vnL' 'iptables -t nat -vnL' 'iptables -t mangle -vnL' & 'cat /tmp/.ipt'. Misc: stracetcpdumpwireshark.
• Gremlins: reboot. cold boot. Reset & reconfigure not restore backup. Search Trac & discuss in forum before opening tickets.
• Include operating & wireless modes (e.g. Gateway, Router, AP, SB, WDS, Mesh) and applicable configurations to reproduce.
r7000 still getting "DD-WRT local5.err ksmbd: [ksmbd-manager/1231]: ERROR: Can't open `/tmp/ksmbd.subauth': No such file or directory" which has been happening since I upgrade for the last several builds.
also been getting these errors since forever
"DD-WRT daemon.err transmission-daemon[3936]: UDP Failed to set receive buffer: requested 4194304, got 524288 (tr-udp.c:97)
DD-WRT daemon.err transmission-daemon[3936]: UDP Failed to set send buffer: requested 1048576, got 524288 (tr-udp.c:105)"
> ssh 172.21.1.1 -l root -p 4813 -v -F /dev/null
OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
debug1: Reading configuration data /dev/null
debug1: Connecting to 172.21.1.1 [172.21.1.1] port 4813.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\user/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\user/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\user/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\user/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\user/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\user/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\user/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\user/.ssh/id_ed25519-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\user/.ssh/id_xmss type -1
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\user/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_7.7
debug1: Remote protocol version 2.0, remote software version dropbear_2022.83
debug1: no match: dropbear_2022.83
debug1: Authenticating to 172.21.1.1:4813 as 'root'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: rsa-sha2-256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
Connection closed by 172.21.1.1 port 4813
Putty can't connect, "remote side unexpectedly closed network connection".
Nevermind: cleared my known hosts and it works now. _________________ 1x Netgear R7800 (latest); 3x Netgear R7000 (latest); 2x Asus RT-N16 (v3.0-r47656); 2x Fonera 2100 (v3.0-r45454).
Linksys E2500
DD-WRT v3.0-r50927 mega (11/21/22)
Linux 4.4.302-st25 #20233 Mon Nov 21 05:51:08 +06 2022 mips
GUI install over r50906
'dd-wrt.v24-50927_NEWD-2_K3.x_mega.bin'
used as a WAP ...all ok
r7000 now multiple devices are reporting "no internet". I think I had this before because I didn't reset. Can't be bothered manually setting up for the millionth time again so I will revert to the previous build.
Devs should probably give notice when a reset is likely needed.
Last edited by portsup on Tue Nov 22, 2022 20:41; edited 1 time in total
r7000 now multiple devices are reporting "no internet". I think I had this before because I didn't reset. Can't be bothered manually setting up for the millionth time again so I will revert to the previous build.
Check your DNS settings, that might be the origin of the problem. _________________ 1x Netgear R7800 (latest); 3x Netgear R7000 (latest); 2x Asus RT-N16 (v3.0-r47656); 2x Fonera 2100 (v3.0-r45454).
Probably but I have just reverted now so cant be bothered. Thing is the internet does work it's just some of the time it reports it doesn't. Like a phone I had to restart it then it did work. I had behavior like this before and the wifi restarting randomly and other weird things but resetting solved it. It's very annoying that there is not an easy way to keep settings between builds.