Posted: Fri May 05, 2023 10:01 Post subject: BROKEN New Build - 05/05/2023 - r52432
This build seems broken as in no IPv4 traffic passing from LAN <> WAN
Welcome to Marvell r52432 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.
My WRT1900ACS V1 works stable on r52411 on IP V4 only.
How ever, upgrade without reset on r52432, all clients connection on router only IP v4 cannot get DNS IP, how ever, login router via ssh, unbound/dns-proxy/dnsmasq works, ping www.yelp.com can find the real IP without problems.
I did not config IP V6 at all.
Ran r52411 for 24 hrs with no issues not realizing it had been pulled.
Upgraded to r52432 with no issues with upgrade process. Router appeared to be connected, OS (Linux) indicated I was connected but I could not reach any site with two different browsers.
Rebooted router with no change. Shut-down/re-started browsers several times with no joy.
Reinstalled r52369 and everything works as usual.
Edit: I've had IPv6 disabled for years. Possible cause??
Every time, I reported the bugs. The next build usually will cause router break so I do not recommend user about installation the last upgrade when you saw my post and comment in the recent build!
Thanks to all build thread reports, and @hvanderkruijf (Henry) investigation, IPv4 iptables issue is nDPI (xt_ndpi).
So as a temporary solution or workaround anyone using r52432 can add "modprobe xt_ndpi" to the startup script.