Posted: Sat May 13, 2023 14:37 Post subject: New Build - 05/13/2023 - r52509
Welcome to Broadcom r52509 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.
List router model & version or revision, operating & wireless modes & exact filename/firmware image flashed.
CLI Flash: 'cd /tmp' then 'wget {file URL}' (httponly) or 'curl -O {file URL}' (http, https, ftp). 'write {file} linux' then 'reboot'.
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.
• 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: Sat May 13, 2023 15:52 Post subject: DD-WRT BS build 52509 and Asus RT-N18U
Router/Version:Asus RT-N18U (rev. A1)
Firmware: DD-WRT v3.0-r52509 std (05/13/23)
Kernel: Linux 4.4.302-st38 #9333 Sat May 13 09:30:16 +06 2023 armv7l
Previous: DD-WRT v3.0-r52369 std (04/20/23)
Mode: WAN @ DHCP, Wireless @ AP (Mixed)
Status: Working {
Not 24/7; Not using CTF, FA, STP, IPv6, VPN, VAP;
USB storage(/jffs, /opt); NAS (ksmbd, lighttpd, minidlna);
WAN DNS disabled; DDNS (no-ip.com) OK
DNSmasq not serving DNS; Recursive DNS Unbound (/jffs/etc/unbound.conf);
Entware core (CPU: armv71) installed without problem
}
Reset: No RESET during firmware upgrade
File:https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2023/05-13-2023-r52509/asus-rt-n18u/
Summary
No strange problems, before and after cold boot. Not testing CTF & FA this time.
First time flashing firmware NOT via WEBUI.
Code:
~# nohup mtd write asus_rt-n18u-firmware.trx linux &
~# cat nohup.out
Unlocking linux ...
[flash] : Could not unlock MTD device: linux
linux: Not supported
Writing from asus_rt-n18u-firmware.trx to linux ... [w]
Warning unaligned data, we use manual padding to avoid errors. size was 90112!!!
~# reboot -n
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
From my Nagios instance: connect to address 192.168.xx.x and port xx: Connection refused
attempts to connect using putty, connection refused.
power cycle and reboot temporarily fixes the issue.
** RECOVERY Service Alert: Second Floor ASUS AC66U/SSH is OK **
***** Nagios *****
Notification Type: RECOVERY
Service: SSH
Host: Second Floor ASUS AC66U
Address: 192.168.xx.x
State: OK
Date/Time: Sat May 13 15:10:33 EDT 2023
Additional Info:
SSH OK - dropbear_2022.83 (protocol 2.0)
Router: Buffalo WZR-1750DHP
Firmware: buffalo-wzr-1750dhp-webflash.bin (v3.0-r52509 std)
Kernel: Linux 4.4.302-st38 #9329 SMP Sat May 13 09:02:03 +06 2023 armv7l
Status: Working
Reset: No
Notes on configuration:
Media Network
DNSMasq
Port Forwarding
DHCP reservation
DNSSEC
SFE -- Disabled
Joined: 26 Mar 2013 Posts: 1857 Location: Hung Hom, Hong Kong
Posted: Sun May 14, 2023 6:51 Post subject:
Pdobrien3 wrote:
still having issues with ssh on Asus RT-AC68U.
From my Nagios instance: connect to address 192.168.xx.x and port xx: Connection refused
attempts to connect using putty, connection refused.
power cycle and reboot temporarily fixes the issue
Dropbear was not started properly right after the first reboot of firmware uprade and BEFORE the cold boot? Soft and cold boots are really 2 test cases. And cold boot is the most important step.
I understand that some mission-critical applications cannot afford cold boots and even soft reboots, and there are people expecting a long Linux uptime.
Next time, check the status of Dropbear by executing "ps aux | grep -i bear"in Admin->Command. See if you could detect the problem. _________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
Router/Version: Asus RT-AC87U R
Update method: WebUpgrade
File/Kernel: asus_rt-ac87u-firmware.trx 52509 / Linux 4.4.302-st38 #9337 SMP Sat May 13 09:55:55 +06 2023 armv7l
Previous/Reset: 52485 / no
Mode/Status: Gateway / Up and running for 2:30 hours
Issues/Errors: Nothing significant
As always, the Quantenna chip has its own characteristics.
Can't set channel. You can't disable 5.0 GHz either.
Even through the schedule menu.
Errors in wireless RX packets.
The fact is that the router is connected to the Internet (to the Internet provider). And it reports an error, the red WAN indicator flashes (the icon in the form of a planet). The internet works, I just think it's a glitch.
____________________________________________________________________________________________
Router/Version: Linksys WRT54GL v1.1
Update method: WebUpgrade / TFTP
File/Kernel: dd-wrt.v24 mini generic r52509 / 0 2023 mips
Previous/Reset: r52485 / yes
Mode/Status: AP wired and wireless / 0.
Issues/Errors: YES
Failed to update. The update was successfully downloaded through the browser, but the version remained the same. After rebooting the router TTL - 100. Installed via TFTP, 52485 returned. I think this is all because of the size of the flash drive.
Thank you BS and gurus! _________________ Atheros
Netgear XR500 Nighthawk - DD-WRT 54545
Tp-Link TL-WDR4900 v1.3 - DD-WRT 53133
TP-Link WR1043ND v4 - DD-WRT 51838
TP-Link WR1043ND v2 - Gargoyle OS 1.13.0
TP-Link WR841ND v11 - DD-WRT 55779
Broadcom
Asus RT-AC87U R - DD-WRT 55819
Asus RT-N66U - DD-WRT 55779
Linksys WRT54GL v1.1 - DD-WRT 54517M
Linksys WRT54GL v1.1 - FreshTomato 2023.4_MIPS_K26
Linksys WRT54GL v1.1 - Gargoyle OS 1.6.2
Last edited by KACTET on Sun May 14, 2023 15:27; edited 1 time in total
From my Nagios instance: connect to address 192.168.xx.x and port xx: Connection refused
attempts to connect using putty, connection refused.
power cycle and reboot temporarily fixes the issue
Dropbear was not started properly right after the first reboot of firmware uprade and BEFORE the cold boot? Soft and cold boots are really 2 test cases. And cold boot is the most important step.
I understand that some mission-critical applications cannot afford cold boots and even soft reboots, and there are people expecting a long Linux uptime.
Next time, check the status of Dropbear by executing "ps aux | grep -i bear"in Admin->Command. See if you could detect the problem.
Is works for an inconsistent amount of time after firmware upgrade, cold boot, and restart. I will run that command and get back to you though. Thanks.
Linksys E2500
DD-WRT v3.0-r52509 mega (05/13/23)
Linux 4.4.302-st38 #23619 Sat May 13 10:17:23 +06 2023 mips
scp 'firmware.bin' install over r52459
'dd-wrt.v24-52509_NEWD-2_K3.x_mega.bin'
used as WAP --- all good
From my Nagios instance: connect to address 192.168.xx.x and port xx: Connection refused
attempts to connect using putty, connection refused.
power cycle and reboot temporarily fixes the issue
Dropbear was not started properly right after the first reboot of firmware uprade and BEFORE the cold boot? Soft and cold boots are really 2 test cases. And cold boot is the most important step.
I understand that some mission-critical applications cannot afford cold boots and even soft reboots, and there are people expecting a long Linux uptime.
Next time, check the status of Dropbear by executing "ps aux | grep -i bear"in Admin->Command. See if you could detect the problem.
Is works for an inconsistent amount of time after firmware upgrade, cold boot, and restart. I will run that command and get back to you though. Thanks.
2782 root sh -c alias ping='ping -c 3'; eval "ps aux | grep -i bear" > /tmp/ping.log 2>&1 &
2784 root grep -i bear
Joined: 26 Mar 2013 Posts: 1857 Location: Hung Hom, Hong Kong
Posted: Sun May 14, 2023 14:41 Post subject:
Pdobrien3 wrote:
Pdobrien3 wrote:
Is works for an inconsistent amount of time after firmware upgrade, cold boot, and restart. I will run that command and get back to you though. Thanks.
2782 root sh -c alias ping='ping -c 3'; eval "ps aux | grep -i bear" > /tmp/ping.log 2>&1 &
2784 root grep -i bear
No "dropbear", no SSH! I could not guess why it's not loaded. Next time Dropbear was not listed, capture the output of command "free" and "grep -i bear /var/log/messages".
And you could always manually start Dropbaer by "service sshd start"!
Joined: 01 Dec 2021 Posts: 289 Location: Maryland, United States
Posted: Sun May 14, 2023 18:42 Post subject:
Router/Version: Netgear R7000P
Firmware Version: DD-WRT v3.0-r52509 std (05/13/23))
Kernel Version: Linux 4.4.302-st38 #9335 SMP Sat May 13 09:44:40 +06 2023 armv7l
Previous/Reset: r52485 / No Reset
Mode/Status: Gateway / Working
Issues/Errors: Slowdown in upload speeds with Verizon FiOS.
Several builds ago, I was getting an upload speed of 340Mbps. In the past two or three builds it went down to 255Mbps, with this build it decreased to about 215Mbps. Upload speed had remained as it should at 310Mbps.
here is the crash(results of grep -i bear /var/log/messages):
May 14 10:10:33 Second_Floor_68U authpriv.info dropbear[2748]: Child connection from 192.168.xx.xx:xx
May 14 10:10:33 Second_Floor_68U authpriv.info dropbear[2748]: Exit before auth from <192.168.xx.xxx:xx>: Error reading: Connection reset by peer
the child connection is my nagios instance loggjng in. it worked multiple times before 10:10:33
