Posted: Sun Jun 26, 2022 9:53 Post subject: New Build - 06/26/2022 - r49361
Welcome to Marvell r49361 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, CB, WDS, Mesh) and applicable configurations to reproduce.
Router/Version: Linksys WRT1900ACS v2 / DD-WRT v3.0-r49361 std (06/26/22)
File/Kernel: CLI webflash / Linux 4.9.319 #3292 SMP Sun Jun 26 05:19:52 +07 2022 armv7l
Previous/Reset: r49326 / No
Mode/Status: Gateway, DNSmasq, OpenVPN Client, FreeRADIUS Server, VLANs, VAPs, WPA3, Custom ScanList / Uptime 1:03
Issues/Errors: The 5 GHz custom ScanList is still being ignored. With ScanList set as in the attached screenshot to only scan channels 36-48 and 149-161, I changed from fixed channel 48 to autochannel which looked promising the first time when it properly chose allowed channel 161 (which I'd included in scanlist), but it failed the second time when it still chose a disallowed channel 52 (which I'd excluded from scanlist).
EDIT: Syslog added. I searched for instances of "wlan0: selected:" and compared messages after 5805 (non-DFS channel 161) with messages after 5260 (DFS channel 52). I didn't see any sign of what's wrong, other than that "hostapd: wlan0:" confirmed client connection on 161 but not on 52. _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
Router/Version: Linksys WRT1900ACS v2
File: ddwrt-linksys-wrt1900acsv2-webflash.bin
Firmware: DD-WRT v3.0-r49361 std (06/26/22) (prev. DD-WRT v3.0-r49139 std (06/10/22))
Kernel: Linux 4.9.319 #3292 SMP Sun Jun 26 05:19:52 +07 2022 armv7l
Mode: Gateway, SFE enabled, Wifi disabled, Wireguard for external access, WAN to DSL, Keep Alive reboot 5:00 in the morning
Reset: No
Status: Up since yesterday, ok. Load average 0.00, 0.00, 0.00, Temperatures CPU 76.0 °C / WL0 50.5 °C / WL1 52.1 °C