Posted: Tue Sep 28, 2021 6:32 Post subject: New Build - 09/28/2021 - r47495
[WARNING]: This thread is only for feedback on this beta release for developers and the community's benefit.
DO NOT flash this beta release unless you understand the 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:
• DNScrypt 1.95 can still be used in the GUI, but v2 (not compatible) requires Golang and thus Entware. #6246
• 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. Use client or repeater instead.
• VAPs not working at bootfixed for unbridged VAPs in40562 - 40566. Effective startup commandsdiscussion thread is here.
• If start-up scripts do not work from USB add a delay, e.g. wait script or 'sleep 25'.
• Broadcom ARM devices if 5 GHz channels are missing, via Telnet/SSH: 'nvram set brcm_unlock=1' 'nvram commit' 'reboot'
• Show us your findings with steps to reproduce, configuration, output, logs and important information below!
Important:
• For issues provide applicable info: 'dmesg', 'cat /tmp/var/log/messages', syslog, klog, serial, strace, tcpdump, wireshark etc.
• Any firewall NAT or WAN issues, show output: 'iptables -vnL', 'iptables -t nat -vnL', 'iptables -t mangle -vnL' and /tmp/.ipt file.
• Search SVN tickets & discuss in forum before opening. Before reporting: reset & manually set up, not restore from a backup.
• Please include operating & wireless modes (e.g. Gateway, Router, AP, CB, WDS, Mesh) & relevant configuration information.
Linksys E2500
DD-WRT v3.0-r47495 mega (09/28/21)
Linux 4.4.285 #12070 Tue Sep 28 06:51:51 +07 2021 mips
'dd-wrt.v24-47495_NEWD-2_K3.x_mega.bin'
GUI install over r47481
used as simple WAP
Joined: 18 Mar 2014 Posts: 12882 Location: Netherlands
Posted: Tue Sep 28, 2021 12:53 Post subject:
Router Model: Netgear R6400v1
Firmware Version: DD-WRT v3.0-r47495M Community Build (09/28/21)
Kernel Version: Linux 4.4.285 #1 SMP Tue Sep 28 13:37:23 CEST 2021 armv7l
Upgraded from: DD-WRT v3.0-r47479M Community Build (09/23/21)
Reset: No not this time
Status: Up and running for 2 hours, basic setup as Gateway, static leases, Advanced routing, Port Forwarding, IPv4, 2.4 GHz and 5 GHz, OpenVPN client working, WireGuard client working.
Thanks egc I might tinker with some my oldass WRTs to see what's what.
...iffin reset is required (seems like good idea anyways) it'll be a PITA to update the ones in use cause couple (WDS link & wired AP) are mounted in rafters of shop ...hmmm, we'll see
Joined: 08 May 2018 Posts: 14217 Location: Texas, USA
Posted: Tue Sep 28, 2021 15:30 Post subject:
Router Model & Version: Linksys E4200 #1
Firmware: DD-WRT v3.0-r47495 mega (09/28/21)
File: dd-wrt.v24-47495_NEWD-2_K2.6_mega-nv60k.bin
Kernel: Linux 2.6.24.111 #24028 Tue Sep 28 04:40:38 +07 2021 mips
Previous: DD-WRT v3.0-r44213 mega (08/18/20)
Reset: No
Mode: CB (5GHz), AP (2.4GHz)
Uptime: ~11hrs
Status: Ok
Issues/Errors: None
Router Model & Version: Linksys E4200 #2
Firmware: DD-WRT v3.0-r47495 mega (09/28/21)
File: dd-wrt.v24-47495_NEWD-2_K3.x_mega.bin
Kernel: Linux 4.4.285 #12070 Tue Sep 28 06:51:51 +07 2021 mips
Previous: DD-WRT v3.0-r47225 mega (08/23/21)
Reset: No
Mode: Switch
Uptime: ~11hrs
Status: Ok
Issues/Errors: None
Router Model & Version: Netgear R7000P
Firmware: DD-WRT v3.0-r47495 std (09/28/21)
File: netgear-r7000p-webflash.bin
Kernel: Linux 4.4.285 #4136 SMP Tue Sep 28 06:24:35 +07 2021 armv7l
Previous: DD-WRT v3.0-r47225 mega (08/23/21)
Reset: No
Mode: 2.4GHz Client, 5GHz AP, Gateway
Uptime: ~11hrs
Status: Ok
Issues/Errors: None _________________ "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
Router/Version: Netgear R7000 Firmware: DD-WRT v3.0-r47495 std (09/28/21) Kernel: Linux 4.4.285 #4130 SMP Mon Sep 27 04:27:57 +07 2021 armv7l Mode: Gateway, Wireless AP, Static Leases. CTF & FA Enabled. NAT and QOS Off. All services off under Status>Sys-info. Reset: Nope. Previous: 09-24-2021-r47481 Status: Working really well so far, still testing. Temperatures: CPU 68.0 °C / WL0 54.0 °C / WL1 55.5 °C Base CFE: Modified Asus ASUS RT-AC68P/ASUS RT-AC68U (C0 Model CFE V1.3.0.7) Configured as a stock R7000.
Speedtest.jpg
Description:
Speedtest Over 5.8GHz Wireless.
Filesize:
61.51 KB
Viewed:
9911 Time(s)
Logs.txt
Description:
Full system logs. MAC scrubbed, password scrubbed, the fun stuff at the bottom as usual!
This time something went wrong, the only thing I did different this time is that I selected "reset to default settings", after the reboot it entered in a boot loop, I had to recover it using the serial TTL to the stock FW.
Installing dd-wrt didn't work using the last "factory-to-ddwrt.bin" it also boot loops...also tried in the CFE the "nvram erase", no success...here is my boot output from the brick:
To install dd-wrt, I only got it to install using the "factory-to-ddwrt" from 44715 and after I upgraded it with the same Webflash version, and finally upgraded to the 47495, any other combinations of recent factory/webflash versions resulted in a boot loop.
TY BrainSlayer!
Last edited by pawhtiobo on Fri Oct 01, 2021 8:33; edited 2 times in total
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Wed Sep 29, 2021 18:00 Post subject:
Router/Version: Asus RT-AC68U E1 / DD-WRT v3.0-r47495 std (09/28/21)
File/Kernel: Linux 4.4.285 #4130 SMP Mon Sep 27 04:27:57 +07 2021 armv7l
Previous/Reset: DD-WRT v3.0-r47481 std (09/24/21) / none, reset is not for all upgrades. Be reasonable.
Mode/Status: Gateway / mostly operational
Issues/Errors: 3 issues, nr 2) unrelated it seems.
1) VAP (wl1.1) clients get disconnected on clicking Apply on any page for any reason. Wont reconnect until - Known workaround command line interfaces/NAS down/up via ssh/telnet OR (its also stored as a startup/firewall command in admin/commands) thx egc for firewall cmd tip it gets run after apply is clicked..
2) website loading issue fixed, Secondary DNS 1.0.0.1 set, Cloudflare main DNS is likely buggy in some geo-locations.
3) After upgrading FW via UI and message/IP successful router IP (https://IP/successful.asp) is set automatically to as follows after router reboots.
Problem: When router becomes available and goes to this IP automatically it will cause another reboot, and another until you set to https://IP or https://IP/somethingelsebutupgrade.cgi unless you closed the tab and started again, this is a bug IMO. WHY pp dont notice this, my guess is laziness or lies.
I dont know if all routers do this after upgrade, mine is doing it now for the last 12+builds maybe more I really have lost count.
Is anyone using UI to upgrade? What the point if you dont, its designed to work if no one is testing this, it should be NOTED on their reports, so main template is flawed.
Joined: 08 May 2018 Posts: 14217 Location: Texas, USA
Posted: Wed Sep 29, 2021 18:32 Post subject:
There's a workaround for the webUI upgrade "issue": It's called using an unmanaged switch in between your PC and the router. The only other "fix" is patience; I have sat and waited and it corrected itself, or have just navigated back to the main setup page manually after waiting 5 minutes. The code has had changes several times in the past 3+ years alone. I don't think there is a one-size-fits-all solution.
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Wed Sep 29, 2021 20:31 Post subject:
kernel-panic69 wrote:
There's a workaround for the webUI upgrade "issue": It's called using an unmanaged switch in between your PC and the router. The only other "fix" is patience; I have sat and waited and it corrected itself, or have just navigated back to the main setup page manually after waiting 5 minutes. The code has had changes several times in the past 3+ years alone. I don't think there is a one-size-fits-all solution.
The report template is a result of brevity and TL;DR-ness. I have a more complete template in my notes, but I don't include all of it
Again, these are workarounds an actual bug, like the VAP issue.
Easier is just to close the tab or click a bookmark that goes only to router IP.
Neither is a bug fix. Essentially the router should not set any IP's that send it on a endless reboot cycle, right?
So lets handle bugs as bugs and workarounds as just that, otherwise threads like this are helping who exactly fix actual issues? Whats the actual point of these threads otherwise?
Just for the fun of it, wasting time? Who are we helping here?