Posted: Thu Apr 20, 2023 4:39 Post subject: New Build - 04/20/2023 - r52369
Welcome to Atheros r52369 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'. 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.
All Working ok so far...running stuff from my signature...!
Thanks BS and devs !
P.S.
Router Model Netgear R9000 Nighthawk X10
Firmware Version DD-WRT v3.0-r52369 std (04/20/23)
Kernel Version Linux 4.9.337 #665 SMP Sun Mar 26 02:43:53 +07 2023 armv7l
update: CLI r52242 > r52369
reset: NO
mode: Gateway
status: Operational 12h+
errors: Nothing new, yet... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Last edited by Alozaros on Sat Apr 29, 2023 11:00; edited 1 time in total
Joined: 18 Mar 2014 Posts: 12912 Location: Netherlands
Posted: Thu Apr 20, 2023 13:28 Post subject:
Router Model: Linksys EA8500
Firmware Version: DD-WRT v3.0-r52369M Community Build by EGC (04/20/23)
Upgraded from: DD-WRT v3.0-r52330M Community Build by EGC (04/15/23)
Reset: No not this time
Status: Up and running for 4 hours, basic setup as Gateway, static leases, 2.4 GHz and 5 GHz switched off, OpenVPN server working, WireGuard Server working (multiple clients e.g. phone, laptop and site-to-site connection with remote location), NAS and Samba working, Avahi and Avahi-utils working.
IPv6 working.
Joined: 05 Oct 2008 Posts: 666 Location: Helsinki, Finland / nr. Alkmaar, Netherlands
Posted: Thu Apr 20, 2023 15:36 Post subject:
R7800:
upgrade from 52306 to 52330 some days ago already stopped the router from giving out IP to my laptop thus loosing control.
Downgraded to 52306 until next version 52369 today. Upgrade without reset.
Still no IP to my laptop.
Erased nvram and entered all settings from scratch (GUI prints).
Then I figured I could set laptop IP and dns manually. This regained me control of the router.
It still wouldn't work as usual, as if the Reserved IPs file on /jffs wasn't having any effect and hostnames were just * and failing internet access. The file was there alright.
After much checking of the settings making just minor corrections in text fields (some broken lines), I eventually downgraded to build 52306 once more. I kept the settings as I had re-entered them for 52369 and .... router works again ....
So, both the set of settings kept through upgrades and the settings re-entered today fail to work (for me) on 52330 and 52369.
I have used a local DNS server PiHole on a Raspberry Pi for a long time without problems. I haven't changed anything there. Just rebooted it a few times today while working on the router settings (controlled shutdown button on its UPS).
To me it looks like something has changed with respect to DNS in the last two builds.
At least in as far as my settings are concerned ...
Static lease file on jffs (conf-file=/jffs/staticleas-file) ?
Don't do this. I did a few years ago and it is asking for trouble. I had very similar issues as you and the logs showed a mess. Been there, got the scars, learned my lesson. _________________ Netgear R9000
DD-WRT v3.0-r55819 std (04/17/24)
Linux 4.9.337 #722 SMP Wed Apr 17 04:16:49 +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: 05 Oct 2008 Posts: 666 Location: Helsinki, Finland / nr. Alkmaar, Netherlands
Posted: Thu Apr 20, 2023 16:28 Post subject:
Sorry, the problem looks like it originates from DHCP.
However, if DHCP doesn't work as intended, a client gets an IP which I don't recognize and DNS won't work either, because the PiHole is advertised as DNS server by its intended IP ...
My PiHole DNS server is set up to not do DHCP.
In my current setup DHCP is taken care of by the router itself. Maybe I should rethink that.
All 'permanent' clients have their IP and hostname listed by MAC in file /jffs/Reserved_IPs.custom.
(The PiHole does have its own list of hostnames by IP, but that's for local DNS purposes.)
When re-entering the router settings, I mostly did them page by page without much rebooting and only left some pages like QoS, networking and wireless for later after first testing. Obviously I need to use a more systematic approach ...
My reason for re-entering settings was to do away with possible 'gremlins', which are so often referred to. I take them to be obsolete nvram variables. I did not immediately expect my settings as such to be at fault since they had been working w/o problems for many builds in sequence, but there's obviously no other way to find out the cause than by re-entering settings a little at a time and check when the router starts to disagree ...
Last edited by ArjenR49 on Thu Apr 20, 2023 16:38; edited 1 time in total
