Posted: Wed Oct 05, 2022 5:21 Post subject: New Build - 10/05/2022 - r50357
Welcome to Broadcom r50357 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.
Joined: 26 Mar 2013 Posts: 1857 Location: Hung Hom, Hong Kong
Posted: Wed Oct 05, 2022 6:44 Post subject: DD-WRT BS build 50357 and Asus RT-N18U
Router/Version:Asus RT-N18U (rev. A1)
Firmware: DD-WRT v3.0-r50357 std (10/05/22)
Kernel: Linux 4.4.302-st25 #7682 Wed Oct 5 03:08:07 +07 2022 armv7l
Previous: DD-WRT v3.0-r50274 std (09/27/22)
Mode: WAN @ DHCP, Wireless @ AP (Mixed)
Status: Working {
Not 24/7; Not using SFE, CTF/FA, STP, ttraff, IPv6, VPN, VAP;
DDNS (no-ip.com) OK; SFE + Port-forwarding OK;
USB storage(/jffs, /opt); NAS (ksmbd, lighttpd);
Recursive DNS Unbound(need restart by USB script);
Entware core (CPU: armv71) installed without problem
}
Reset: No RESET during firmware upgrade
File:https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2022/10-05-2022-r50357/asus-rt-n18u/
Warning(s)/Error(s)
Code:
# grep -i err /var/log/messages
Jan 1 08:00:12 rt-n18u kern.err kernel: [ 0.000123] smp_twd: clock not found -2
Jan 1 08:00:12 rt-n18u kern.err kernel: [ 2.075367] bcmsflash: found no supported devices
Jan 1 08:00:13 rt-n18u daemon.info mstpd[637]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 8
Jan 1 08:00:13 rt-n18u daemon.info mstpd[637]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 8
Jan 1 08:00:23 rt-n18u local5.err ksmbd: [ksmbd-manager/1161]: ERROR: Can't open `/tmp/ksmbd.subauth': No such file or directory
Oct 5 18:30:17 rt-n18u kern.err kernel: [ 38.102559] hub 3-0:1.0: config failed, hub doesn't have any ports! (err -19)
Oct 5 18:30:19 rt-n18u local5.err ksmbd: [ksmbd-manager/1161]: ERROR: WARNING: child process exited abnormally: 1162
Oct 5 18:30:19 rt-n18u local5.err ksmbd: [ksmbd-manager/1161]: ERROR: can't execute kill 1162: No such process
Oct 5 18:30:39 rt-n18u user.info : [unbound] : Error on startup, returncode 1
Oct 5 18:30:42 rt-n18u user.info : [lighttpd] : Error on startup, returncode 255
Oct 5 18:30:42 rt-n18u user.info : [lighttpd] : Error on startup, returncode 255
Unbound still needed restart to use /jffs/etc/unbound.conf in USB storage!!
Netgear R8500
Firmware Version DD-WRT v3.0-r50357 std (10/05/22)
Kernel Version Linux 4.4.302-st25 #7684 SMP Wed Oct 5 03:22:08 +07 2022 armv7l
Current Time Wed, 05 Oct 2022 14:59:19
Uptime 1 min
GUI over 50313
Reset: no
Issues: upgraded fine
Joined: 18 Mar 2014 Posts: 12889 Location: Netherlands
Posted: Thu Oct 06, 2022 6:52 Post subject:
This build has WireGuard obfuscation, we are still working on it and maybe the definitive implementation will change, so it is not yet in the manual.
But it works and is intended to obfuscate WG traffic so it should be able to pass a blocking firewall.
On the server side enable it and set the password in the tunnel section.
Note the whole tunnel is obfuscated.
On the client (the side which has an endpoint enabled in the peer)
Do the same but it should be set in the Peer section just under the endpoint.
Use the same password.
It will lower throughput.
I have also made an implementation were you set the obfuscation per peer on the server side but in that case you also have to set the Remote listen port, advantage is that a server can have clients with and without obfuscation.
Short Report, since I cannot test currently. BUT I found this:
Something seems not right at Administration --> Management --> Login Credentials:
1) Click the Eye Icon to reveal Username or Password.
2) The correct Username and Password are not shown, instead a number/letter combination is given.
I never changed the standard username, it should be root, but instead username and password fields show:
d6nw5v1****7st** -
(I inserted *** to avoid accidently leaking a hash or something).
The same behaviour on all of my devices, not only Broadcom.
Previous Version installed was r50274 - 09/27/22.
Posted: Thu Oct 06, 2022 22:04 Post subject: New Build - 10/03/2022 - r50313
Router/Version: Netgear R7000
File/Kernel: netgear-r7000-webflash.bin, Linux 4.4.302-st25 #7678 SMP Wed Oct 5 02:42:28 +07 2022 armv7l
Previous/Reset: r49741, no reset
Mode/Status: AP, WAN disabled, DHCP disabled, USB Storage enabled (OPT & NTFS), SMB, DLNA
Issues/Errors: saw 1 instance of USB reset 5 min after install but not seen again after reset for 24 hours.
Fixed SMB issue with drive reporting 0 free space making it read only from clients. suspect this was fixed by Changeset 49786
BTW ksmbd seems to now be at version 3.4.5 not 3.4.4
Code:
# ksmbd.mountd --version
ksmbd-tools version : 3.4.5
This is the logs from the USB error I saw:
Code:
[ 299.598903] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 299.761939] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 299.921860] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 300.081790] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 300.241772] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 300.411650] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 300.432205] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 300.440412] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 23 41 e5 28 00 01 00 00
[ 300.448027] blk_update_request: I/O error, dev sda, sector 591521064
[ 321.489294] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 321.652331] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 321.822254] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 321.992185] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 322.152118] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 322.312043] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 322.332637] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 322.340866] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 01 ce 58 d6 00 01 00 00
[ 322.348478] blk_update_request: I/O error, dev sda, sector 30300374
[ 325.880474] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 326.050410] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 326.220358] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 326.390256] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 326.547084] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 326.710116] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 326.730567] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 326.738774] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 01 b0 7f 70 00 01 00 00
[ 326.746402] blk_update_request: I/O error, dev sda, sector 28344176
[ 330.215483] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 330.378500] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 330.535354] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 330.698377] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 330.858294] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 331.018211] xhci_hcd 0000:00:0c.0: ERROR: unexpected setup address command completion code 0x11.
[ 331.238063] xhci_hcd 0000:00:0c.0: ERROR: unexpected setup address command completion code 0x11.
[ 331.457938] usb 4-1: device not accepting address 2, error -22
[ 331.667881] xhci_hcd 0000:00:0c.0: ERROR: unexpected setup address command completion code 0x11.
[ 331.884691] xhci_hcd 0000:00:0c.0: ERROR: unexpected setup address command completion code 0x11.
[ 332.094563] usb 4-1: device not accepting address 2, error -22
[ 332.307612] xhci_hcd 0000:00:0c.0: ERROR: unexpected setup address command completion code 0x11.
[ 332.524403] xhci_hcd 0000:00:0c.0: ERROR: unexpected setup address command completion code 0x11.
[ 332.737367] usb 4-1: device not accepting address 2, error -22
[ 332.944241] xhci_hcd 0000:00:0c.0: ERROR: unexpected setup address command completion code 0x11.
[ 333.154121] xhci_hcd 0000:00:0c.0: ERROR: unexpected setup address command completion code 0x11.
[ 333.363995] usb 4-1: device not accepting address 2, error -22
[ 333.424049] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 333.432278] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 0c 40 5d 83 00 01 00 00
[ 333.439886] blk_update_request: I/O error, dev sda, sector 205544835
[ 333.446379] usb 4-1: USB disconnect, device number 2
[ 333.454062] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[ 333.462303] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 0c 40 5e 83 00 01 00 00
[ 333.469952] blk_update_request: I/O error, dev sda, sector 205545091
[ 333.476415] Read-error on swap-device (8:0:1943040072)
[ 333.482254] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[ 333.490526] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 0c 40 5d 83 00 00 08 00
[ 333.498161] blk_update_request: I/O error, dev sda, sector 205544835
[ 333.505740] ntfs3: sda1: failed to read volume at offset 0xb600
Joined: 08 May 2018 Posts: 14223 Location: Texas, USA
Posted: Thu Oct 06, 2022 23:27 Post subject:
Zyxx wrote:
Short Report, since I cannot test currently. BUT I found this:
Something seems not right at Administration --> Management --> Login Credentials:
1) Click the Eye Icon to reveal Username or Password.
2) The correct Username and Password are not shown, instead a number/letter combination is given.
I never changed the standard username, it should be root, but instead username and password fields show:
d6nw5v1****7st** -
(I inserted *** to avoid accidently leaking a hash or something).
The same behaviour on all of my devices, not only Broadcom.
Previous Version installed was r50274 - 09/27/22.
Are you sure this hasn't been the case for some time? I don't even have the ability to unmask the information in those fields for username and password. What browser are you using, and what extensions, etc. and browsing mode is in use? Not to mention, this information is salted by default in nvram, etc. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Are you sure this hasn't been the case for some time? I don't even have the ability to unmask the information in those fields for username and password. What browser are you using, and what extensions, etc. and browsing mode is in use? Not to mention, this information is salted by default in nvram, etc.
Thank you for your response @kernel-panic69!
This unhide Icon seems to be not DD-WRT related. Sorry for the inconvenience.
Just another darn thing the unwanted G5 Update for Waterfox / two days ago seems to introduce.
--> No DD-WRT quirk. As it does not appear on Duckduckgobrowser or unpatched Waterfox on my ubuntu machine. Also checked msedge, no eye icon.
EDIT - seemingly the installation introduced or altered this setting in about:config:
Code:
layout.forms.reveal-password-button.enabled
changed it to false and the strange icons disappeared.
HATE IT
/EDIT
<rant>
I'm so tired of browsers changing their UI for the sake of having done anything.
Thought Waterfox was a suitable alternative to this, but instead alot of dumbing down happening the last few patches.
Waterfox is related to firefox code and needs to use it somehow but... heavens sake I hate it when software gets slaughtered like this. Why don't they stay away from UI and only fix bugs?
-.-
Above unhide "feature" that does not work, unwanted icons in context menu, chromish look and feel enabled by default (!), cannot download our videos anymore....
*Puke*
</rant>
@Zyxx Waterfox development took a nose dive after being sold to System1, especially Classic it's basically abandoned.
Really sad because they could have used help and advice from Pale Moon for Classic security updates, but just ignored.
Have not tried Waterfox G5.0.1 (ESR 102.x) but it is easy enough to use about:config to disable junk in Firefox or ESR.
That's all Waterfox was, Firefox with stripped out disabled features. There were performance optimizations, but today?
Good you found it layout.forms.reveal-password-button.enabled, always something, was disabled here Firefox 105.0.2.
Short Report, since I cannot test currently. BUT I found this:
Something seems not right at Administration --> Management --> Login Credentials:
1) Click the Eye Icon to reveal Username or Password.
2) The correct Username and Password are not shown, instead a number/letter combination is given.
I never changed the standard username, it should be root, but instead username and password fields show:
d6nw5v1****7st** -
(I inserted *** to avoid accidently leaking a hash or something).
The same behaviour on all of my devices, not only Broadcom.
Previous Version installed was r50274 - 09/27/22.
This is the "fake password" or the placeholder that is displayed in the fields.
DD-WRT does not store the password in plain text, but as a seeded hash.
Therefore DD-WRT cannot show you the real password.
And for this reason there is no "unmask function" at this place.
R8000 #1 Router/Version: Netgear Nighthawk R8000 / V1
File/Kernel: netgear-r8000-webflash.bin (r50357)/ Linux 4.4.302-st25 #7683 SMP Wed Oct 5 03:15:23 +07 2022 armv7l
Previous/Reset: DD-WRT v3.0-r50313 std (22.10.03)/ NO
Mode/Status: Gateway + Access Point (2.4 & 5 Ghz) + USB Storage (guide by egc) + SSL entware + Wireguard Tunnels.
Issues/Errors: GUI updated, kept config. No functional issues to report.
One cosmetic problem - the USB subsection is again reporting partitions with exabytes. The behaviour is limited to my 1GB jffs partition. 1Gb optware, 1Gb swap and 5.5Gb FAT32 data partitions are reported correctly
R8000 #2 Router/Version: Netgear Nighthawk R8000 / V1
File/Kernel: netgear-r8000-webflash.bin (r50357)/ Linux 4.4.302-st25 #7683 SMP Wed Oct 5 03:15:23 +07 2022 armv7l
Previous/Reset: DD-WRT v3.0-r50313 std (22.10.03)/ NO
Mode/Status: Gateway + Access Point (2.4 & 5 Ghz) + USB Storage (guide by egc) + SSL entware + Wireguard Tunnels.
Issues/Errors: GUI updated, kept config. No functional issues to report.
Same USB size error - different USB size, different partition sizes (2gb here), again the jffs partition.
My R9000 running r50357 shows correct size of jffs (4gb in this instance). I've got some more USB sticks coming so I'll be able to test further in coming days.
