Posted: Sun Aug 28, 2022 6:03 Post subject: New Build - 08/28/2022 - r49934
Welcome to Marvell r49934 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.
Ok, thank you. Colours it's not the biggest issue. Mac filters for me. It's the biggest. Not saving any mac numbers on my list. When I go back to the oldest firmware update, everything works fine.
Posted: Sun Aug 28, 2022 22:53 Post subject: It's Alive!
Background: I'd been unable to connect over WiFi (with FreeRadius authentication) since the build after r49681, but couldn't determine the cause. I'd posted a log in the build thread for the second build after that (see https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=332788&highlight=). Today I CLI flashed and booted this r49934 build, but initially experienced the same problem with lack of successful WiFi connection from any clients (although wired connection always worked). I eventually gave up and switched/rebooted from the old r49681 build's partition and WiFi promptly connected again.
Progress: Then I decided to give this new r49934 build another try, so simply switched/rebooted again from the new build's partition (that is, no reflash or any config changes, but just switched boot_part and rebooted). Amazingly, WiFi connected automatically from several clients without me making any changes whatsoever! I hadn't made any changes to router settings, but the one difference is that on today's last reboot I happened to have a usually off client actually powered on and active, which automatically connected to this router's WPA3-Personal VLAN, while my other clients automatically connect to this router's Enterprise VLANs. So, at the moment it appears that FreeRadius doesn't authenticate my enterprise clients (since just after build r49681) until a personal client has already connected via WiFi using personal rather than enterprise authentication (that is, the personal client bypassing FreeRadius seems to give the router a kick-start to finally authenticate the enterprise clients).
Router/Version: Linksys WRT1900ACSv1 / DD-WRT v3.0-r49934 std (08/28/22)
File/Kernel: ddwrt-linksys-wrt1900acs-webflash.bin / Linux 4.9.326 #3384 SMP Sun Aug 28 03:56:29 +07 2022 armv7l
Previous/Reset: r49681 / No
Mode/Status: Gateway, OpenVPN Client, FreeRadius Server / Uptime 1:21, Load Average 3%
0.06, 0.01, 0.00, Temperatures CPU 76.5 °C / WL0 47.6 °C / WL1 49.1 °C
Issues/Errors: FreeRadius (and/or WiFi) / This ACSv1 is running well after some reboots, although FreeRadius only authenticates enterprise WiFi clients after a personal WiFi client has connected first. That is, if there is no personal client (which was not needed for build r49681 and earlier), then the enterprise clients are never authenticated. Thanks! _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
