Posted: Sat Sep 03, 2022 4:51 Post subject: New Build - 09/03/2022 - r50057
Welcome to Marvell r50057 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 WRT1900ACSv1 / DD-WRT v3.0-r50057 std (09/03/22)
File/Kernel: ddwrt-linksys-wrt1900acs-webflash.bin / Linux 4.9.326 #3390 SMP Sat Sep 3 02:10:56 +07 2022 armv7l
Previous/Reset: r49934 / No
Mode/Status: Gateway, OpenVPN Client, FreeRadius Server / Uptime 7 min
Issues/Errors: FreeRadius enterprise clients will not connect over WiFi for me on r50057. If I switch back to r49934, FreeRadius enterprise clients connect but only if I use the trick of connecting a non-enterprise client after reboot before any enterprise clients attempt to connect, but that trick no longer works for later builds. The last build that let FreeRadius enterprise clients connect without any non-enterprise clients having to connect first was build r49681 (and earlier). Log attached _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
Router/Version: Linksys WRT3200ACM
File: ddwrt-linksys-wrt1900ac-webflash.bin
Firmware: DD-WRT v3.0-r50057 std (09/03/22)
Kernel: Linux 4.9.326 #3390 SMP Sat Sep 3 02:10:56 +07 2022 armv7l
Mode: AP
Reset?: N
Status: up 3 days, 6:06, load average: 0.00, 0.00, 0.00. no issues works great. feel like 5ghz performance is slightly worst than r49934 and VHT160 still missing since r49934.
Router/Version: Linksys WRT1900ACS v2
File: ddwrt-linksys-wrt1900acsv2-webflash.bin
Firmware: DD-WRT v3.0-r50057 std (09/03/22) (prev. DD-WRT v3.0-r49866 std (08/24/22))
Kernel: Linux 4.9.326 #3390 SMP Sat Sep 3 02:10:56 +07 2022 armv7l
Mode: Gateway, SFE enabled, Wifi disabled, Wireguard for external access, WAN to DSL, samba to access USB3-ext4 SSD, Keep Alive reboot 5:00 in the morning
Reset: No
Status: Installed at release, ok. Load average 0.00, 0.00, 0.00, Temperatures CPU 79.8 °C / WL0 52.9 °C / WL1 54.6 °C
This update the dual partition Layout came in handy. I accidentally closed the browser tab during firmware upgrade *DOH*
Joined: 12 Dec 2007 Posts: 764 Location: Pittsburgh, PA USA
Posted: Wed Sep 07, 2022 21:35 Post subject:
Router/Version: WRT1900AC v1
File/Kernel: DD-WRT v3.0-r50057 std (09/03/22)
Previous/Reset: r49838 std / Full reset/reconfigure
Mode/Status: Gateway (SFE enabled), Access Point, IPV6 via Hurricane / native Verizon, Entware, DOT via Stubby, OpenVPN server, Wireguard Server, Privoxy
Issues/Errors:
Sporadic issues with DNS resolution. It will work fine, then after a reboot, can't resolve DNS at all, even from the router commmand line. Another reboot and it may be fine, maybe not. Eliminating Stubby doesn't solve the issue. Even a full reconfigure didn't resolve. Turning off IPV6 seems to make it stable.
I was previously using IPV6 from Hurricane Tunnelbroker, but my ISP finally turned IPV6 up in my area last week, so I was using DHCP6 with Prefix Delegation when I did the upgrade. I saw the same issue under both configurations.
Finally rolled back to r49838 and restored the previous config from that build (which was using DHCP6) and it's back to being solid.
Probably should note that I'm using Cloudflare DNS servers (1.1.1.1) _________________ __________________________
Netgear R7800
DD-WRT v3.0 STD
Linksys WRT1900AC
DD-WRT v3.0 STD
Router/Version: WRT1900AC v1
File/Kernel: DD-WRT v3.0-r50057 std (09/03/22)
Previous/Reset: r49838 std / Full reset/reconfigure
Mode/Status: Gateway (SFE enabled), Access Point, IPV6 via Hurricane / native Verizon, Entware, DOT via Stubby, OpenVPN server, Wireguard Server, Privoxy
Issues/Errors:
Sporadic issues with DNS resolution. It will work fine, then after a reboot, can't resolve DNS at all, even from the router commmand line. Another reboot and it may be fine, maybe not. Eliminating Stubby doesn't solve the issue. Even a full reconfigure didn't resolve. Turning off IPV6 seems to make it stable.
I was previously using IPV6 from Hurricane Tunnelbroker, but my ISP finally turned IPV6 up in my area last week, so I was using DHCP6 with Prefix Delegation when I did the upgrade. I saw the same issue under both configurations.
Finally rolled back to r49838 and restored the previous config from that build (which was using DHCP6) and it's back to being solid.
Probably should note that I'm using Cloudflare DNS servers (1.1.1.1)
I'm having similar issues now. suddenly internet cuts out or is slow with DNS resolution issues. However i'm IPV4.
Router/Version: Linksys WRT3200ACM
File: ddwrt-linksys-wrt1900ac-webflash.bin
Firmware: DD-WRT v3.0-r50057 std (09/03/22)
Kernel: Linux 4.9.326 #3390 SMP Sat Sep 3 02:10:56 +07 2022 armv7l
Mode: AP
Reset?: N
Use CTRL+F5 or clear browser cache manually / reload page. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
Running wlan0 (5ghz), wlan1 (2.4ghz), and wlan1.1 (VAP guest). All wlans are on separate SSIDs.
Positive notes:
All wireless PCs seem to have no issues with connections. This includes one MacBook Pro running Monterey and one iPad.
2 Android phones seem to also be behaving normally.
Google Homes, Chromecast units, and Nest Hubs seem to be fine.
Issues/Errors:
At least one active device is probably ESP8266 based and would not work until WMM was disabled on wlan1 as per the workarounds.
I have a Samsung SL-M2020W wireless laser printer. Using this router, it's become mostly unusable wirelessly. I've had to resort to printing with a USB cable. Pinging the printer gives some "Destination Host Unreachable" messages followed by pings that vary wildly in latency. Trying to bring up the printer's sync thru webpage sometimes works, sometimes just hangs. Printer is connected to wlan1
Setting up the guest network DHCP by trying to add a second DHCPD daemon in the Setup->Networking->DHCPD and applying it to wlan1.1, causes the guest network SSID to disappear from the available networks. Rebooting doesn't help and removing the added DHCPD allows the guest network to show up again. I had to use the DNSMasq method of getting DHCP to the guest network which works.
So far I've tried 2 different channels for wlan1, but it had no effect on the problems I'm seeing. Noise levels and signal strength on both channels I tried was very good.
Wireless speed seems to be very slow. I've just switched to Verizon 5G home internet and when I connected only my Asus laptop running Linux mint with an "N" capable adapter to the Verizon gateway via wi-fi and did a speed test, I would get around 250mbs download. After switching their gateway to passthru mode and adding my Linksys router, the download speed on the same laptop is slightly under 100mbs. For contrast, running the speedtest from a hard wired pc is giving 350mbs downloads.
Two Harmony remote hubs seem to be struggling a bit with their wi-fi connectivity.