Posted: Tue May 23, 2023 6:26 Post subject: New Build - 05/23/2023 - r52656
Welcome to Marvell r52656 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.
List router model & version or revision, operating & wireless modes & exact filename/firmware image flashed.
CLI Flash: 'cd /tmp' then 'wget {file URL}' (httponly) or 'curl -O {file URL}' (http, https, ftp). 'write {file} linux' then 'reboot'.
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.
Netgear R7000 - loaded R52656, factory default settings.
Changed IP to 192.168.3.1, set router name, added a 2.4GHx VAP, no password. Applied.
Can not connect to VAP from laptop and from cell. The message is "Can not connect to ssid-vap".
Tried adding a 5GHz vap - same issue.
Netgear R7000 - loaded R52656, factory default settings.
Changed IP to 192.168.3.1, set router name, added a 2.4GHx VAP, no password. Applied.
Can not connect to VAP from laptop and from cell. The message is "Can not connect to ssid-vap".
Tried adding a 5GHz vap - same issue.
I had the same experience with R52596.
Likely a configuration issue but post this and steps to reproduce in Broadcom r52656 build thread.