Posted: Thu Jan 01, 2026 22:46 Post subject: New Build - 01/01/2026 - r63230
Welcome to Marvell r63230 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'. Debug Analyze: stracetcpdump.
• 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: 1900ACv1
File/Kernel: 63230
Previous/Reset: 59045/Factory Reset
Mode/Status: AP
Issues/Errors: Client traffic not being routed to internet. This was tested on factory defaults. Back to 59045.
Notes
Installed on partition 1 resetting to defaults. Rebooted and set new password.
No internet access as before.
"iptables -L" run in Administration/Commands. No rules appeared.
"ubootenv list" problem still exists:
Used power switch procedure to manually switch partitions and boot back into 59045 and reload prior settings.
Joined: 06 Jun 2006 Posts: 7773 Location: Dresden, Germany
Posted: Fri Jan 02, 2026 6:44 Post subject:
Rickers wrote:
Router/Version: 1900ACv1
File/Kernel: 63230
Previous/Reset: 59045/Factory Reset
Mode/Status: AP
Issues/Errors: Client traffic not being routed to internet. This was tested on factory defaults. Back to 59045.
Notes
Installed on partition 1 resetting to defaults. Rebooted and set new password.
No internet access as before.
"iptables -L" run in Administration/Commands. No rules appeared.
please use iptables-nft on that device. you are doing it wrong
"ubootenv list" problem still exists:
Used power switch procedure to manually switch partitions and boot back into 59045 and reload prior settings.
works for me
so in any way. use the device as specified and it will work. dont use wrong command and you will be happy _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Joined: 06 Jun 2006 Posts: 7773 Location: Dresden, Germany
Posted: Fri Jan 02, 2026 6:46 Post subject:
Rickers wrote:
Router/Version: 1900ACv1
File/Kernel: 63230
Previous/Reset: 59045/Factory Reset
Mode/Status: AP
Issues/Errors: Client traffic not being routed to internet. This was tested on factory defaults. Back to 59045.
Notes
Installed on partition 1 resetting to defaults. Rebooted and set new password.
No internet access as before.
"iptables -L" run in Administration/Commands. No rules appeared.
"ubootenv list" problem still exists:
Used power switch procedure to manually switch partitions and boot back into 59045 and reload prior settings.
please use iptables-nft on that device. you are doing it wrong
i assume you are using custom iptables rules and you are using the wrong iptables command (instead of iptables-nft). so you tricked yourself
so in any way. use the device as specified and it will work. dont use wrong command and you will be happy _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Router/Version: 1900ACv1
File/Kernel: 63230
Previous/Reset: 59045/Factory Reset
Mode/Status: AP
Issues/Errors: Client traffic not being routed to internet. This was tested on factory defaults. Back to 59045.
Notes
Installed on partition 1 resetting to defaults. Rebooted and set new password.
No internet access as before.
"iptables -L" run in Administration/Commands. No rules appeared.
"ubootenv list" problem still exists:
Used power switch procedure to manually switch partitions and boot back into 59045 and reload prior settings.
please use iptables-nft on that device. you are doing it wrong
i assume you are using custom iptables rules and you are using the wrong iptables command (instead of iptables-nft). so you tricked yourself
so in any way. use the device as specified and it will work. dont use wrong command and you will be happy
Everything I did was at factory defaults. No custom anything. @egc suggested checking with "iptables -L" a while back. iptables-nft gives more information.
However, genius, you totally overlooked the "ubootenv list" error which I and others are having. What's the solution there to what appears to be a missing device? Or am I doing that wrong, too?
