Posted: Fri Oct 17, 2025 14:51 Post subject: New Build - 10/17/2025 - r62365
Welcome to Marvell r62365 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: WRT1900AC v1
File/Kernel: DD-WRT v3.0-r62365 std (10/17/25)
Previous/Reset: none
Mode/Status: AP
Issues/Errors: getting an error msg from wireguard and WAN is ok but no internet through the tunnel, reverting to r62192
Oct 19 15:46:02 root WireGuard PBR 192.168.xxx.xxx:IPv4 via oet6 table 26 │
│Oct 19 15:46:02 root WireGuard PBR 192.168.xxx.xxx:IPv4 via oet6 table 26 │
│Oct 19 15:46:02 root WireGuard Killswitch on PBR activated for oet6 │
│Oct 19 15:46:02 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:46:02 root WireGuard NAT via oet6 for xxxxxxxxx enabled │
│Oct 19 15:46:02 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:46:02 root WireGuard IPv4 internet access for xxxxxxxxxxxx/24 enabled │
│Oct 19 15:46:02 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:46:02 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:46:02 root WireGuard released /tmp/oet-tunnels.lock for prewall │
│Oct 19 15:46:02 root WireGuard firewall removing temporary killswitch for IPv4 │
│Oct 19 15:46:03 is-mounted /opt/etc/Ipset mounted after 1 seconds │
│Oct 19 15:46:03 root WireGuard IPSET: ToWan restored from /opt/etc/Ipset/ToWan for oet6 │
│Oct 19 15:46:03 root WireGuard IPSET: ToWan fwmark:26 set to table:226 │
│Oct 19 15:46:03 root WireGuard adding local routes to table 26 │
│Oct 19 15:46:03 root WireGuard: DNSMasq restarted due to active ipset │
│Oct 19 15:46:03 dnsmasq exiting on receipt of SIGTERM │
│Oct 19 15:46:03 - [dnsmasq] : daemon successfully stopped │
│Oct 19 15:46:03 dnsmasq started, version UNKNOWN cachesize 1500
Oct 19 15:59:25 dnsmasq using only locally-known addresses for mask.icloud.com │
│Oct 19 15:59:25 dnsmasq using only locally-known addresses for use-application-dns.net │
│Oct 19 15:59:25 dnsmasq using only locally-known addresses for test │
│Oct 19 15:59:25 dnsmasq using only locally-known addresses for onion │
│Oct 19 15:59:25 dnsmasq using only locally-known addresses for localhost │
│Oct 19 15:59:25 dnsmasq using only locally-known addresses for local │
│Oct 19 15:59:25 dnsmasq using only locally-known addresses for invalid │
│Oct 19 15:59:25 dnsmasq using 1 more local addresses │
│Oct 19 15:59:25 dnsmasq read /etc/hosts - 10 names │
│Oct 19 15:59:26 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:59:26 root WireGuard NAT via oet1 for xxxxxxxxxxx enabled │
│Oct 19 15:59:26 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:59:26 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:59:26 root WireGuard released /tmp/oet-tunnels.lock for prewall │
│Oct 19 15:59:26 root WireGuard firewall removing temporary killswitch for IPv4 │
│Oct 19 16:00:51 httpd [httpd] : httpd SSL server started at port 443
Joined: 18 Mar 2014 Posts: 13822 Location: Netherlands
Posted: Mon Oct 20, 2025 13:46 Post subject:
wrtbob wrote:
Router/Version: WRT1900AC v1
File/Kernel: DD-WRT v3.0-r62365 std (10/17/25)
Previous/Reset: none
Mode/Status: AP
Issues/Errors: getting an error msg from wireguard and WAN is ok but no internet through the tunnel, reverting to r62192
Oct 19 15:46:02 root WireGuard PBR 192.168.xxx.xxx:IPv4 via oet6 table 26 │
│Oct 19 15:46:02 root WireGuard PBR 192.168.xxx.xxx:IPv4 via oet6 table 26 │
│Oct 19 15:46:02 root WireGuard Killswitch on PBR activated for oet6 │
│Oct 19 15:46:02 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:46:02 root WireGuard NAT via oet6 for xxxxxxxxx enabled │
│Oct 19 15:46:02 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:46:02 root WireGuard IPv4 internet access for xxxxxxxxxxxx/24 enabled │
│Oct 19 15:46:02 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:46:02 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:46:02 root WireGuard released /tmp/oet-tunnels.lock for prewall │
│Oct 19 15:46:02 root WireGuard firewall removing temporary killswitch for IPv4 │
│Oct 19 15:46:03 is-mounted /opt/etc/Ipset mounted after 1 seconds │
│Oct 19 15:46:03 root WireGuard IPSET: ToWan restored from /opt/etc/Ipset/ToWan for oet6 │
│Oct 19 15:46:03 root WireGuard IPSET: ToWan fwmark:26 set to table:226 │
│Oct 19 15:46:03 root WireGuard adding local routes to table 26 │
│Oct 19 15:46:03 root WireGuard: DNSMasq restarted due to active ipset │
│Oct 19 15:46:03 dnsmasq exiting on receipt of SIGTERM │
│Oct 19 15:46:03 - [dnsmasq] : daemon successfully stopped │
│Oct 19 15:46:03 dnsmasq started, version UNKNOWN cachesize 1500
Oct 19 15:59:25 dnsmasq using only locally-known addresses for mask.icloud.com │
│Oct 19 15:59:25 dnsmasq using only locally-known addresses for use-application-dns.net │
│Oct 19 15:59:25 dnsmasq using only locally-known addresses for test │
│Oct 19 15:59:25 dnsmasq using only locally-known addresses for onion │
│Oct 19 15:59:25 dnsmasq using only locally-known addresses for localhost │
│Oct 19 15:59:25 dnsmasq using only locally-known addresses for local │
│Oct 19 15:59:25 dnsmasq using only locally-known addresses for invalid │
│Oct 19 15:59:25 dnsmasq using 1 more local addresses │
│Oct 19 15:59:25 dnsmasq read /etc/hosts - 10 names │
│Oct 19 15:59:26 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:59:26 root WireGuard NAT via oet1 for xxxxxxxxxxx enabled │
│Oct 19 15:59:26 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:59:26 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:59:26 root WireGuard released /tmp/oet-tunnels.lock for prewall │
│Oct 19 15:59:26 root WireGuard firewall removing temporary killswitch for IPv4 │
│Oct 19 16:00:51 httpd [httpd] : httpd SSL server started at port 443
Redacting private ip addresses is not necessary as those are private but it makes it more difficult to give support.
Are you sure it is build number 62192 which is working for you? Because after that build there have been no changes to Wireguard (of course a lot of other changes e.g. new kernel with iptables etc wich could trigger errors).
To diagnose the problem we need to see the the list from the troubleshooting section in the WireGuard Server setup guide (guides are a sticky in the Advanced networking forum):
Quote:
Send detailed information when asking for help:
Start with Screenshots of WireGuard page (whole page) and Basic Setup page (whole page).
If you use anything other than plain DNSMasq for DNS resolving also report that and add a screenshot of the Service > Services page.
If more detailed information is needed then show the output of the following commands (CLI, with telnet/putty) after you attempted to make a connection:
wg
wg showconf oet1 #if you have more tunnels dan also: wg showconf oetX where X is the tunnel number
ip route show
grep -E -i 'oet|wireguard|eop' /var/log/messages
iptables -vnL FORWARD | grep oet
iptables -vnL INPUT
iptables -vnL -t nat
iptables -vnL -t raw
get_wanface
nvram get wan_ipaddr
plus we need to see the log with debugging of the firewall enabled:
To enable debug logging of the WireGuard firewall:
Joined: 07 Jan 2025 Posts: 220 Location: Bethel Park, PA, USA
Posted: Mon Oct 20, 2025 14:33 Post subject:
Router/Version: Linksys WRT1900AC v1
File/Kernel: DD-WRT v3.0-r62365 std (10/17/25)
Previous/Reset: DD-WRT v3.0-r61745 std (06/12/25), last reset r61745
Mode/Status: Gateway (SFE Disabled), Access Point (5GHZ-VHT80 AC/N mixed, WPA2/WPA3, domain:UNITED STATES), IPV6 (DHCP6 w/ prefix delegation), Entware, DOT via SmartDNS/DNSMasq, Wireguard Server
No WAN access from client machines after update, with SFE on or off. Rolled back to r61745.
Thank you Brainslayer. _________________ Formerly dpp3530 Linksys MR7350
Gateway, 2 wired APs, NSS-ECM , Clock 1440MHz
VAPs on wlan0 and wlan1 for guest/IOT devices
IPv4 & IPv6 (Prefix Delegation)
Static Leases & DHCP
SmartDNS (DOT using NextDNS, Cloudflare), DNSMasq
Wireguard and OpenVPN server
2.4GHz: dd-wrt, AX Only, ACK Timing 1350, WPA3 SAE & WPA2 w/AES
5GHz: dd-wrt, AX/AC/N Mixed, ACK Timing 1350, WPA3 SAE & WPA2 w/AES
Verizon Fios, 500/500Mbps
Router/Version: WRT1900AC v1
File/Kernel: DD-WRT v3.0-r62365 std (10/17/25)
Previous/Reset: none
Mode/Status: AP
Issues/Errors: getting an error msg from wireguard and WAN is ok but no internet through the tunnel, reverting to r62192
Oct 19 15:46:02 root WireGuard PBR 192.168.xxx.xxx:IPv4 via oet6 table 26 │
│Oct 19 15:46:02 root WireGuard PBR 192.168.xxx.xxx:IPv4 via oet6 table 26 │
│Oct 19 15:46:02 root WireGuard Killswitch on PBR activated for oet6 │
│Oct 19 15:46:02 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:46:02 root WireGuard NAT via oet6 for xxxxxxxxx enabled │
│Oct 19 15:46:02 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:46:02 root WireGuard IPv4 internet access for xxxxxxxxxxxx/24 enabled │
│Oct 19 15:46:02 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:46:02 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:46:02 root WireGuard released /tmp/oet-tunnels.lock for prewall │
│Oct 19 15:46:02 root WireGuard firewall removing temporary killswitch for IPv4 │
│Oct 19 15:46:03 is-mounted /opt/etc/Ipset mounted after 1 seconds │
│Oct 19 15:46:03 root WireGuard IPSET: ToWan restored from /opt/etc/Ipset/ToWan for oet6 │
│Oct 19 15:46:03 root WireGuard IPSET: ToWan fwmark:26 set to table:226 │
│Oct 19 15:46:03 root WireGuard adding local routes to table 26 │
│Oct 19 15:46:03 root WireGuard: DNSMasq restarted due to active ipset │
│Oct 19 15:46:03 dnsmasq exiting on receipt of SIGTERM │
│Oct 19 15:46:03 - [dnsmasq] : daemon successfully stopped │
│Oct 19 15:46:03 dnsmasq started, version UNKNOWN cachesize 1500
Oct 19 15:59:25 dnsmasq using only locally-known addresses for mask.icloud.com │
│Oct 19 15:59:25 dnsmasq using only locally-known addresses for use-application-dns.net │
│Oct 19 15:59:25 dnsmasq using only locally-known addresses for test │
│Oct 19 15:59:25 dnsmasq using only locally-known addresses for onion │
│Oct 19 15:59:25 dnsmasq using only locally-known addresses for localhost │
│Oct 19 15:59:25 dnsmasq using only locally-known addresses for local │
│Oct 19 15:59:25 dnsmasq using only locally-known addresses for invalid │
│Oct 19 15:59:25 dnsmasq using 1 more local addresses │
│Oct 19 15:59:25 dnsmasq read /etc/hosts - 10 names │
│Oct 19 15:59:26 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:59:26 root WireGuard NAT via oet1 for xxxxxxxxxxx enabled │
│Oct 19 15:59:26 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:59:26 eop-tunnel-firewall.sh Illegal instruction │
│Oct 19 15:59:26 root WireGuard released /tmp/oet-tunnels.lock for prewall │
│Oct 19 15:59:26 root WireGuard firewall removing temporary killswitch for IPv4 │
│Oct 19 16:00:51 httpd [httpd] : httpd SSL server started at port 443
Redacting private ip addresses is not necessary as those are private but it makes it more difficult to give support.
Are you sure it is build number 62192 which is working for you? Because after that build there have been no changes to Wireguard (of course a lot of other changes e.g. new kernel with iptables etc wich could trigger errors).
To diagnose the problem we need to see the the list from the troubleshooting section in the WireGuard Server setup guide (guides are a sticky in the Advanced networking forum):
Quote:
Send detailed information when asking for help:
Start with Screenshots of WireGuard page (whole page) and Basic Setup page (whole page).
If you use anything other than plain DNSMasq for DNS resolving also report that and add a screenshot of the Service > Services page.
If more detailed information is needed then show the output of the following commands (CLI, with telnet/putty) after you attempted to make a connection:
wg
wg showconf oet1 #if you have more tunnels dan also: wg showconf oetX where X is the tunnel number
ip route show
grep -E -i 'oet|wireguard|eop' /var/log/messages
iptables -vnL FORWARD | grep oet
iptables -vnL INPUT
iptables -vnL -t nat
iptables -vnL -t raw
get_wanface
nvram get wan_ipaddr
plus we need to see the log with debugging of the firewall enabled:
To enable debug logging of the WireGuard firewall:
Quote:
nvram set wg_debug_firewall=1 && nvram commit
To disable debug logging:
Quote:
nvram unset wg_debug_firewall && nvram commit
yes I upgraded from r62192 which works pretty well. I waited quite a while before upgrading from r57956 as with r59045 I couldn't properly generate freeradius certificates (maybe human error), indeed the first thing I checked was the wg changelog before posting. Should I reply here with the logs or create new post under Advanced networking forum?
