Posted: Tue Aug 01, 2023 5:16 Post subject: New Build - 08/01/2023 - r53339
Welcome to Atheros r53339 beta release thread for reporting, feedback to developers and 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'. Debug Analyze: stracetcpdump.
• 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.
Linksys EA8500...main gateway
DD-WRT v3.0-r53339 std (08/01/23)
Linux 4.9.337 #2106 SMP Tue Aug 1 01:43:08 +07 2023 armv7l
scp 'firmware.bin' install over r53323
all good
#
Linksys WRT160NL
DD-WRT v3.0-r53339 std (08/01/23)
Linux 3.10.108-d11 #139357 Tue Aug 1 03:15:24 +06 2023 mips
GUI install over r53323
used as OVPN server ...all good.
its radio usually off but it does worky fine ...checked it
Netgear WNDR3700 V4
DD-WRT v3.0-r53339 std (08/01/23)
Linux 3.18.140-d6 #178559 Tue Aug 1 05:56:22 +06 2023 mips
GUI install over r53323
WAP + isolated guest net
all ok
---
EDIT:
ugrade Daughter's EA8500 ...main gateway
GUI install over r53001
tis all good
#
upgrade WNDR3700v4
GUI install over r53001
used as 2.4 staion ...5GHz AP
all worky fine
Router: TL-WDR3600 v1
Firmware: tl-wdr3600_us-webflash.bin (v3.0-r53339 std)
Kernel: Linux 3.10.108-d11 #139353 Tue Aug 1 03:09:34 +06 2023 mips
Status: working
Reset: No
Notes on configuration:
Station
Errors:
1. 5Ghz wireless light is not on (2.4Ghz light works)
Router: DIR-825 rev B1
Firmware: dir825-firmware.bin (v3.0-r53339 std)
Kernel: Linux 3.10.108-d11 #139351 Tue Aug 1 02:49:50 +06 2023 mips
Status: Working
Reset: None
Notes on configuration: Used for Wifi Lab (no internet)
Errors:
None
Router: Archer-A7 v5
Firmware: tplink_archer-a7-v5.bin (v3.0-r53339 std)
Kernel: Linux 3.18.140-d6 #178543 Tue Aug 1 05:19:38 +06 2023 mips
Status: Working
Reset: None
Notes on configuration:
DNSMasq
Virtual wireless with bridging x2
multiple DHCP server
Router/Version: TP-Link TL-WR841ND v11
Update method: WebUpgrade
File/Kernel: tl-wr841nd-webflash.bin_r53339 / Linux 3.18.140-d6 #178517 Tue Aug 1 04:38:11 +06 2023 mips
Previous/Reset: r53323 / no
Mode/Status: AP wired and wireless / Up and running for 6:15 hours
Issues/Errors: Nothing significant
The fact is that the router connected to the Internet (to the Internet provider). And it reports an error, the orange WAN indicator flashes (the icon in the form of a planet). Internet is working, I just think it's a glitch
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 56029
Broadcom
Asus RT-AC87U R - DD-WRT 56029
Asus RT-N66U - DD-WRT 55819
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
Router/Version: TP-Link ARCHER-C7 v5
Update method: WebUpgrade
File/Kernel: DD-WRT v3.0-r53339 std (08/01/23) / Linux 3.18.140-d6 #178541 Tue Aug 1 05:15:58 +06 2023 mips
Previous/Reset: 07-15-2023-r53323 / No
Mode/Status: Gateway / Up and running for 10 Mins.
Issues/Errors: pppoe redial not working:
"[ppp_redial] : Error on startup, returncode 1"
The router has connected its wan port to a DSL modem (bridge mode), using pppoe for connection to the ISP.
I started using this router with version 05-27-2023-r52720, I noticed that when there is a power outage, as the router boots faster then the DSL modem (before the DSL modem ends its DSL negotiation / DSL not ready), it doesn't connect and never retries to connect.
Connection Strategy Keep Alive: Redial Period 30 seconds.
Of course, if I reboot the router when the DSL modem already booted and DSL is active, the ppoe connecs fine.
Checking the logs I found the problem, it looks like there is something wrong in the configuration as it registers the error:
"[ppp_redial] : Error on startup, returncode 1"
Tried changing the "Redial Period" to other values, just to test.
I saw, by login via ssh, that the "redial" process was not running (only the "pppd file /tmp/ppp/options.pppoe" was running).
If I manually run "redial" (redial 30), it doesn't show any error, keeps running, and after the redial period it connects without problem.
So currently I had to add the command "redial 30" to Startup, after that change, it runs the "redial" at Startup, and connects successfully when the DSL link becomes ready.
(I've tried with a clean installations / Reset with versions: r52720, r53045, r53112, r53133, r53323, r53339, of course, configuring the essential data for the pppoe connection)
----------------------
Other than the above mentioned everything is working properly.
Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Mon Aug 07, 2023 22:29 Post subject:
Router/Version: Netgear XR500
Update method: WebUpgrade
File/Kernel: dd-wrt-webupgrade.bin_r53339 / Linux 4.9.337 #2108 SMP Tue Aug 1 02:06:41 +07 2023 armv7l
Previous\Reset: r53045 / no
Mode/Status: Gateway / Ran 2 days...then random reboot.
Issues/Errors: After the random reboot I reverted back to my fallback build of r53045.
I haven't found a build since 53045 that is reliable for the long term. And...unfortunately, I don't have anything in the log...it just crashed and provides no error outputs.
redhawk
Last edited by redhawk0 on Mon Aug 07, 2023 22:41; edited 2 times in total
Router/Version: Netgear XR500
Update method: WebUpgrade
File/Kernel: dd-wrt-webupgrade.bin_r53339 / Linux 4.9.337 #2108 SMP Tue Aug 1 02:06:41 +07 2023 armv7l
Previous: r53045
Mode/Status: Gateway / Ran 2 days...then random reboot.
Issues/Errors: After the random reboot I reverted back to my fallback build of r34045.
I haven't found a build since 34045 that is reliable for the long term. And...unfortunately, I don't have anything in the log...it just crashed and provides no error outputs.
redhawk
That is an old build. I think you should flash the latest version and erase nvram, and then enter your settings by hand. I don't think you can upgrade from 34045 to 53045 _________________ Netgear R9000
DD-WRT v3.0-r56029 std (04/27/24)
Linux 4.9.337-rt197 #727 SMP Fri Apr 26 17:07:43 +07 2024 armv7l
Gateway, AP, DNSMasq, Clock 2000MHz
VAP on wlan1 for internet devices
IPv4 & IPv6 (Prefix Delegation)
Static Leases & DHCP
CloudFlare, no SFE, SmartDNS, no QoS
2.4GHz: Vanilla, Airtime Fairness, NG-Mixed, ACK Timing 3150, WPA2 w/AES & WPA3
5GHz: Vanilla, Airtime Fairness, AC/N Mixed, ACK Timing 3150, WPA2 w/AES & WPA3
2 Netgear AX1800 WiFi Mesh Extenders
Xfinity 1.2Gbps/35Mbps
Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Mon Aug 07, 2023 22:40 Post subject:
Quote:
That is an old build. I think you should flash the latest version and erase nvram, and then enter your settings by hand. I don't think you can upgrade from 34045 to 53045
That was a fat finger brain hemorrhage moment on my part...I've been running 53045 since June off and on.
That was a fat finger brain hemorrhage moment on my part...I've been running 53045 since June off and on.
I was wondering! Maybe you could post the changes from the defaults you use? We can't dig any further without some details. Just for reference, about a year ago my R9000 started to have lots of weird issues including freezing and reboots. I thought the router was bad. Doing the nvram erase, reboot and reenter settings was a pain, I'm not going to sugarcoat that, but since then. No issues. You can see most of my settings in my signature. _________________ Netgear R9000
DD-WRT v3.0-r56029 std (04/27/24)
Linux 4.9.337-rt197 #727 SMP Fri Apr 26 17:07:43 +07 2024 armv7l
Gateway, AP, DNSMasq, Clock 2000MHz
VAP on wlan1 for internet devices
IPv4 & IPv6 (Prefix Delegation)
Static Leases & DHCP
CloudFlare, no SFE, SmartDNS, no QoS
2.4GHz: Vanilla, Airtime Fairness, NG-Mixed, ACK Timing 3150, WPA2 w/AES & WPA3
5GHz: Vanilla, Airtime Fairness, AC/N Mixed, ACK Timing 3150, WPA2 w/AES & WPA3
2 Netgear AX1800 WiFi Mesh Extenders
Xfinity 1.2Gbps/35Mbps
root@Citadel-Station-Homeworld:~# uptime && date
21:59:16 up 6 days, 11:48, load average: 0.06, 0.12, 0.06
Mon Aug 7 21:59:16 CDT 2023
root@Citadel-Station-Homeworld:~#
Connection to citadel-station-homeworld.mrjcd.com closed.
mrjcd@daDeb:~$
just a bit of this old mess ...ain't nothing new to me
yeahuh I am using VANILLA for both radios
Code:
[66012.178446] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[66012.178488] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[66012.185631] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[66012.193870] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[66012.202005] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[66012.210158] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[66012.218311] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[66012.226426] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[66012.234649] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[296215.983099] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[296215.983137] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[296215.990349] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[296215.998581] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[297876.119898] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[297876.119942] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[297876.127085] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[297876.135406] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
