Posted: Fri Jan 06, 2023 6:43 Post subject: New Build - 01/06/2023 - r51184
Welcome to Marvell r51184 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.
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.
• 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.
Router/Version: Linksys WRT1900ACS v2
File: ddwrt-linksys-wrt1900acsv2-webflash.bin
Firmware: DD-WRT v3.0-r51184 std (01/06/23)
Kernel: Linux 4.9.336 #3589 SMP Fri Jan 6 03:07:47 +07 2023 armv7l
Mode: Gateway, SFE enabled, Wifi disabled, Wireguard for external access, WAN to DSL Modem, samba to access USB3-ext4 SSD, Keep Alive reboot 5:00 in the morning
Reset: No
Status: Installed, ok. Load average 0.00, 0.00, 0.00, Temperatures CPU 69.8 °C / WL0 43.5 °C / WL1 45.1 °C
Joined: 12 Dec 2007 Posts: 780 Location: Pittsburgh, PA USA
Posted: Fri Jan 06, 2023 15:20 Post subject:
Router/Version: WRT1900AC v1
File/Kernel: DD-WRT v3.0-r51184 std (01/06/23)
Previous/Reset: DD-WRT v3.0-r51154 std (01/03/23), No reset this time, no config changes.
Mode/Status: Gateway (SFE enabled), Access Point, IPV6 (DHCP6 w/ prefix delegation), Entware, DOT via SmartDNS, OpenVPN server, Wireguard Server, Privoxy
Issues/Errors:
After upgrade, no DNS resolution, from the client machines or from the router CLI itself. Tried the following:
1. Multiple reboots.
2. From the build thread in the Atheros forum, I tried release/renew on the WAN mulitiple times. While I got new IP addresses, nothing changed.
3. Disabled SmartDNS. DNS resolution worked but no DOH or DOT.
4. Re-enabled SmartDNS and tried various configuration changes. I would get DNS resolution (no DOH or DOT) after apply but not after reboot.
5. Gave up and reverted back to r51154. Works as expected.
SmartDNS config in case anyone is interested.
Enable SmartDNS Resolver - Enabled
Dualstack IP Selection - Disabled
Prefetch Domain - Enabled
Serve Expired - Disabled
Use Additional Servers Only - Enabled
Additional SmartDNS Options:
Tried disabling prefetch and use additional servers only. Also tried removing everything after the first server-tls line in the config. As I said above, it worked after Apply, but did not survive a reboot. _________________ __________________________
Netgear R7800
DD-WRT v3.0 STD
Linksys WRT1900AC
DD-WRT v3.0 STD
Joined: 24 Feb 2013 Posts: 1634 Location: Belgrade
Posted: Fri Jan 06, 2023 20:45 Post subject:
dpp3530 wrote:
Router/Version: WRT1900AC v1
File/Kernel: DD-WRT v3.0-r51184 std (01/06/23)
Previous/Reset: DD-WRT v3.0-r51154 std (01/03/23), No reset this time, no config changes.
Mode/Status: Gateway (SFE enabled), Access Point, IPV6 (DHCP6 w/ prefix delegation), Entware, DOT via SmartDNS, OpenVPN server, Wireguard Server, Privoxy
Issues/Errors:
After upgrade, no DNS resolution, from the client machines or from the router CLI itself. Tried the following:
1. Multiple reboots.
2. From the build thread in the Atheros forum, I tried release/renew on the WAN mulitiple times. While I got new IP addresses, nothing changed.
3. Disabled SmartDNS. DNS resolution worked but no DOH or DOT.
4. Re-enabled SmartDNS and tried various configuration changes. I would get DNS resolution (no DOH or DOT) after apply but not after reboot.
5. Gave up and reverted back to r51154. Works as expected.
SmartDNS config in case anyone is interested.
Enable SmartDNS Resolver - Enabled
Dualstack IP Selection - Disabled
Prefetch Domain - Enabled
Serve Expired - Disabled
Use Additional Servers Only - Enabled
Additional SmartDNS Options:
Tried disabling prefetch and use additional servers only. Also tried removing everything after the first server-tls line in the config. As I said above, it worked after Apply, but did not survive a reboot.
There was a change regarding ipv6 firewall. It would be good if you could try it again but with reset and setting it up "from scratch" without restoring previous settings...
Try it first with basic setting, then ad service by service... and enable kernel and ssystem log...
Joined: 12 Dec 2007 Posts: 780 Location: Pittsburgh, PA USA
Posted: Sat Jan 07, 2023 2:37 Post subject:
Mile-Lile wrote:
There was a change regarding ipv6 firewall. It would be good if you could try it again but with reset and setting it up "from scratch" without restoring previous settings...
Try it first with basic setting, then ad service by service... and enable kernel and ssystem log...
I was intending to do a full reconfig, just need to find time to do so. Will enable the logs in case it doesn't work. _________________ __________________________
Netgear R7800
DD-WRT v3.0 STD
Linksys WRT1900AC
DD-WRT v3.0 STD
Router Model Linksys WRT1900ACS v2
Firmware Version DD-WRT v3.0-r51184 std (01/06/23) Kernel Version
Linux 4.9.336 #3589 SMP Fri Jan 6 03:07:47 +07 2023 armv7l
Uptime 9:38
update-browser waterfox, I switched from partition 1 from Linksys firmware
connection Type PPPoE - IPv6 Type DHCPv6 with Prefix Delegation 1Gbps
IPv6 Type DHCPv6 with Prefix Delegation-On - Ok
Operating Mode Gateway/AP
Shortcut Forwarding Engine-On
Schedule Reboot-On,
Web Access Protocol - HTTPS,
SSH (public key)
Port Forwarding - Ok,
USB - System Log -Ok
Schedule Reboot - At a Set Time - On
Wireless Interface 5GHz-Wireless Mode AP-Wireless Network Mode-AC/N, Width VHT 80 Mhz-Wireless Channel-36,Short GI, Short Preamble, Single User Beamforming, Radio Scheduling, Enable-WPA2 Personal-CCMP-128 (AES, Regulatory Domain Romania , all-ok
Wireless Interface 2.4GHz-Wireless Mode AP-Wireless Network Mode-N, Width VHT 40 Mhz-Wireless Channel-6, Extension Channel Lower,Short Preamble, Short GI , Radio Scheduling, Enable-WPA2 Personal-CCMP-128 (AES)all-ok _________________ Internet provider https://en.wikipedia.org/wiki/RCS_%26_RDS 1Gbps
WDR3600 rev.1.5 - DD-Wrt
Linksys WRT1900ACS v.2 DD-Wrt/-OpenWrt
Joined: 12 Dec 2007 Posts: 780 Location: Pittsburgh, PA USA
Posted: Sat Jan 07, 2023 20:59 Post subject:
Even a complete reconfig didn't work. I can either have IPV6 or SmartDNS enabled, but if I enable both, no DNS resolution. Log file after reboot is attached. _________________ __________________________
Netgear R7800
DD-WRT v3.0 STD
Linksys WRT1900AC
DD-WRT v3.0 STD
Joined: 12 Dec 2007 Posts: 780 Location: Pittsburgh, PA USA
Posted: Sat Jan 07, 2023 22:23 Post subject:
Weird, I stopped using Stubby when I switched to SmartDNS. I even did an opkg remove on it. looks like I still had S61stubby.sh in /opt/etc/init.d. Full reconfig didn't include my thumb drive. Stubby definately isn't running though. I deleted the S61stubby.sh script.
Joined: 12 Dec 2007 Posts: 780 Location: Pittsburgh, PA USA
Posted: Sat Jan 07, 2023 22:45 Post subject:
egc wrote:
The problem is that NTP (time server) does not resolve properly.
See the smartdns guide how to setup smartdns in combination with resolving NTP.
I had
server=/ntp.org/8.8.8.8
In my DNSMasq config. That previously let it resolve 2.us.pool.ntp.org. Even with
server=/2.us.pool.ntp.org/8.8.8.8
it still failed NTP.
I changed the NTP server in the Basic Setup page to "69.164.213.136 144.172.118.20" and it works. I hate hardcoded IPs though. _________________ __________________________
Netgear R7800
DD-WRT v3.0 STD
Linksys WRT1900AC
DD-WRT v3.0 STD
Joined: 01 Feb 2016 Posts: 54 Location: Oregon, U.S.
Posted: Sun Jan 08, 2023 5:09 Post subject:
Quote:
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: strace tcpdump wireshark.
• 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.
Router/Version: Linksys WRT1900AC v1
File/Kernel: DD-WRT v3.0-r51184 std (01/06/23) File: ddwrt-linksys-wrt1900ac-webflash.bin
Previous/Reset: DD-WRT v3.0-r50841 std (11/09/22) / Factory Reset prior to F/W upload.
Mode/Status: Gateway - Nothing connected except power supply & Win10 desktop via ethernet using static IP. Usually use SAFEDNS filtering service using Forced DNS redirect in DNSMASQ.
Issues/Errors: No DNSMASQ/DHCP, No SSH, No Telnet, No SYSLOGD.
Files I downloaded for R51184:
- ddwrt-linksys-wrt1900ac-webflash.bin [SHA-1 Checksum: EFCC207D2113483125E4A67720B713BA533893CD]
- factory-to-ddwrt.bin [SHA-1 Checksum: 66651DD232A67AF5D6F589C8E5B6F8062CE6A78F]
I would really like to provide you with a mountain of logs and configurations, but I am not alble to access any of those.
- First, I factory reset r50841 using NVRAM ERASE && REBOOT from SSH session.
- Next, COLD BOOTED the router after changing default password.
- Uploaded and applied R51184 that I downloaded from: https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2023/01-06-2023-r51184/linksys-wrt1900ac/ddwrt-linksys-wrt1900ac-webflash.bin
- The router took an extremely long time to update and reboot, 23 minutes.
- When router did reboot I could not get a IP address via DHCP. (This was first hint of problems)
- Set static IP.
- Changed LAN IP to desired network, specified NTP server: time-c-b.nist.gov(132.163.96.3)
- Set DHCP range and lease time.
- Unplugged the router. Connected ONT to WAN port.
- Cold booted the router. (Released static IP on desktop to use DHCP.)
- Could not obtain IP from DHCP. Set Static IP for new network.
- Once logged in I found that router did not connect to internet.
- Went to STATUS/WAN clicked <RELEASE> waited 30 seconds, clicked <RENEW>. No Connection. (Seems DHCP client is not working.) My ISP will not accept static configuration. Rebooted. No change.
- So figured it was time to start collecting logs and configs as requested in the above quote.
- So I enabled SSH in the GUI & copy/pasted RSA key from a text file. Clicked Apply.
- Opened PUTTY only to be repeatedly greeted with "Remote side unexpectedly closed network connection."
- Removed the RSA Key from the GUI and enabled PASSWORD LOGIN.
- Went back to PUTTY, only to get same error. Rebooted.
- Reconfigured PUTTY settings to use telnet. "Connection Refused"
- Tried resetting the TELNET server by disabling then enable in the GUI. No Change. Rebooted
- Went back to SSH and tried toggling the SSH service off, reboot, then back on. No Change.
- This is when I noticed that the SSH section does not have an option to select KEY SIZE when generating a key. There is no drop down menu for the KEY size or a label. See attached image.
- OKay. I'll do it the hard way using the COMMANDS feature in the Administration tab. So I go to the SERVICES/SYSTEM LOG section and enable SYSLOGD & KLOGD, click Apply settings. Router became unresponsive. Waited couple mins.
- Pressed reset button - nothing.
- Unplugged the router. Plugged back in. Would not boot. tried this two more times, then ended up at the LINKSYS OEM firmware.
- Used the REVERT TO PREVIOUS Firmware feature in OEM F/W. Would not boot, had to repeat manual partition swap process.
- Used OEM firmware to install Factory-to-ddwrt.bin file for r51184.
- This upgrade process only took about four minutes. (Seems normal.)
- Again no DHCP. Changed P/W. Rebooted
- CHanged LAN address, set DHCP options, added 1.1.1.1 as DNS, added time-c-b.nist.gov for NTP. connected wan.
- Rebooted. This time WAN got an Public IP (That's an improvement.)
- Discovered system time would not update because there is no DNSMASQ to resolve the address. Changed NTP entry to 132.163.96.3 and system time immediately updated.
- Tried browsing internet using router as DNS(DNSMASQ), nothing. Had to use desktop's DNS client to browse internet.
- Went to add RSA Key to SSH. Found KEY LENGTH still missing. Again SSH will not connect.
- Again Telnet will not connect.
- Went to enable Logging again in the GUI. Complete crash again. Ended up at the OEM firmware again after several boot attempts.
- That is where I abandoned r51184.
I went back to r50841 from the OEM Firmware. No issues of any kind, I think I 'm going to stay with this one for a while.
Yes, I realize the factory-to-ddwrt file is not the complete firmware, but it should have the basics - DHCP, DNSMASQ, SSH, Telnet, and logging, but it didn't.
Now this is completely off topic for this thread, but is relevant to my individual experience with R51184.
I downloaded the appropriate R51184 webflash files for Netgear R8000 & ASUS RT-AC66U.
They are both currently in a brick state after updating from R44467.
Joined: 24 Feb 2013 Posts: 1634 Location: Belgrade
Posted: Sun Jan 08, 2023 6:33 Post subject:
well, if you cannot connect via ssh... you can use telnet client (its enabled by default) or you can enable mactelnet (I use mactelnet). you just need mactelnet client but you can download it from internet... mactelnet is good because it works on l2 layer... you don't need IP to connect... so it will work even if your dhcp (dnsmasq) doesn't starts... I am sorry to hear that you bricked so many units... netgear r8000 is easy to unbrick... you can use nmrpflash
btw BS added option some time ago, and after 5 boot failure unit will erase nvram... and this usually helps but you have to wait long...
About ssh... ssh server changed default key lenght... for security reason... find egcs post about it... you need to remove old key from your client machine... and after you got working unit it is easy... do cat /tmp/dnsmasq.conf or dmesg and you will see why dnsmasq doesn't starts... usually some typo in conf file... and check ntp... that could be problem too...
Joined: 18 Mar 2014 Posts: 12907 Location: Netherlands
Posted: Sun Jan 08, 2023 7:16 Post subject:
dpp3530 wrote:
egc wrote:
The problem is that NTP (time server) does not resolve properly.
See the smartdns guide how to setup smartdns in combination with resolving NTP.
I had
server=/ntp.org/8.8.8.8
In my DNSMasq config. That previously let it resolve 2.us.pool.ntp.org. Even with
server=/2.us.pool.ntp.org/8.8.8.8
it still failed NTP.
I changed the NTP server in the Basic Setup page to "69.164.213.136 144.172.118.20" and it works. I hate hardcoded IPs though.
I am not a fan of hard coding either.
As a test can you revert to the former non working setup e.g. with the domain names in NTP?
Check that you indeed do not get the correct time after reboot and then in Administration/Commands Save Firewall add this:
Joined: 18 Mar 2014 Posts: 12907 Location: Netherlands
Posted: Sun Jan 08, 2023 7:37 Post subject:
@TedCheeze
SSH has been updated, you can generate exclusively ED25519 keys which are much smaller but still safer and those do not have a key length (they do but it is always 256 if I remember correctly).
If you have trouble connecting with SSH then download the latest Putty and make sure under SSH/Host keys to move ed25519 to the top and untick "Prefer Algorithms for which a host key is known" or forget your known HOST keys (the fingerprints) from your client.
If you have trouble connecting with WinSCP under Tools/Clean up Clear Cache
Joined: 24 Feb 2013 Posts: 1634 Location: Belgrade
Posted: Sun Jan 08, 2023 8:37 Post subject:
@dpp3530
I just enabled smartdns DOH with nexdns on my r8000... it is working out of the box... although I just used ipv4 for test case... but I think it is not problem in your case because u use dualstack...
