OpenWRT One Restart of Device will stop passing Internet Traffic

Tristan · June 15, 2025, 5:09am

Hello fellow OpenWRT users. I purchased an OpenWRT One and I must say I love the device coming from products from GLInet and Netgear devices. Currently having a bit of an odd issue where if I restart the OpenWRT One I appear to lose internet access until I physically unplug the cat 6 cable and plug it back in again after a period of 5-10 seconds.

The Quantum Fiber Modem that I currently have in transparent/bridge mode.

I have attempted things like restarting the interface in OpenWRT. I have attempted to disable it and enable it again. None of those seem to get things going again. The only thing that seems to work is unplugging it and plugging it back in again.

I have attempted things like powering off the modem and powering it on again. Thinking that is the same thing as unplugging the ethernet cable. But that doesn't seem to do it.

I grabbed a copy of the system log and put it on my paste instance. If that's not allowed apologies in advanced. https://tp.paste.lol/openwrt-logs-event/raw

I had been looking for perhaps some command I can trigger from a script that would mimic the physical act of removing the cable and plugging it back in again. So I don't need to do this manual physical process anytime a power outage or something like that happens again.

I see some information in the logs that SIGTERM of attempting to release the public IP and the upstream DHCP server. So not sure if that process is failing upstream or on the OpenWRT One.

Sat Jun 14 19:52:28 2025 daemon.notice netifd: wan (4237): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Sat Jun 14 19:52:28 2025 daemon.notice netifd: Interface 'wan' is now down
Sat Jun 14 19:52:29 2025 user.err : jail: failed to load dependencies
Sat Jun 14 19:52:29 2025 daemon.info procd: Instance sysntpd::instance1 s in a crash loop 8 crashes, 0 seconds since last crash
Sat Jun 14 19:52:31 2025 daemon.notice netifd: Network device 'eth0' link is up
Sat Jun 14 19:52:31 2025 daemon.notice netifd: Interface 'wan' has link connectivity
Sat Jun 14 19:52:31 2025 daemon.notice netifd: Interface 'wan' is setting up now
Sat Jun 14 19:52:31 2025 kern.info kernel: [  161.643378] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Sat Jun 14 19:52:31 2025 daemon.notice netifd: wan (4364): udhcpc: started, v1.36.1
Sat Jun 14 19:52:31 2025 daemon.notice netifd: wan (4364): udhcpc: broadcasting discover
Sat Jun 14 19:52:34 2025 daemon.notice netifd: wan (4364): udhcpc: broadcasting discover
Sat Jun 14 19:52:37 2025 daemon.notice netifd: wan (4364): udhcpc: broadcasting discover
Sat Jun 14 19:52:38 2025 daemon.notice netifd: Network device 'eth0' link is down
Sat Jun 14 19:52:38 2025 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sat Jun 14 19:52:38 2025 kern.info kernel: [  169.250413] mtk_soc_eth 15100000.ethernet eth0: Link is Down
Sat Jun 14 19:52:38 2025 daemon.notice netifd: wan (4364): udhcpc: received SIGTERM
Sat Jun 14 19:52:38 2025 daemon.notice netifd: wan (4364): udhcpc: entering released state
Sat Jun 14 19:52:38 2025 daemon.notice netifd: wan (4364): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Sat Jun 14 19:52:38 2025 daemon.notice netifd: Interface 'wan' is now down

So probably a bit long winded here. But would love any ideas or suggestions to make sure any reboot of the OpenWRT One comes back up properly without having to unplug the ethernet cable and plug it back in again to restore Internet access.

Thank You.

frollic · June 15, 2025, 5:33am

Are you running 24.10, or the RC2 it shipped with ?

Tristan · June 15, 2025, 5:50am

Firmware Version:

OpenWrt 24.10.1 r28597-0425664679 / LuCI openwrt-24.10 branch 25.161.59576~cb94dcc

psherman · June 15, 2025, 5:51am

It would make sense to take a look at the complete config. In addition, please let us know if you've installed any additional packages.

Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:

Remember to redact passwords, MAC addresses and any public IP addresses you may have:

ubus call system board
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall

Tristan · June 15, 2025, 6:02am

Sure thing.

Ran all the commands one by one and redirected the output to a file that I copied and pasted below.

If you want them each one by one in seperate fields I can do that as well.

{
        "kernel": "6.6.86",
        "hostname": "xxxx-xxxxxxx",
        "system": "ARMv8 Processor rev 4",
        "model": "OpenWrt One",
        "board_name": "openwrt,one",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "24.10.1",
                "revision": "r28597-0425664679",
                "target": "mediatek/filogic",
                "description": "OpenWrt 24.10.1 r28597-0425664679",
                "builddate": "1744562312"
        }
}

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd8c:1d59:d93c::/48'
        option packet_steering '1'

config device
        option name 'br-lan'
        option type 'bridge'

config interface 'lan'
        option device 'eth1'
        option proto 'dhcp'
        option type 'bridge'

config interface 'wan'
        option device 'eth0'
        option proto 'dhcp'


config wifi-device 'radio0'
        option type 'mac80211'
        option path 'platform/soc/18000000.wifi'
        option band '2g'
        option channel '1'
        option htmode 'HE20'
        option num_global_macaddr '7'
        option cell_density '0'

config wifi-device 'radio1'
        option type 'mac80211'
        option path 'platform/soc/18000000.wifi+1'
        option band '5g'
        option channel '36'
        option htmode 'HE80'
        option num_global_macaddr '7'
        option cell_density '0'


config dnsmasq
        option domainneeded '1'
        option localise_queries '1'
        option rebind_protection '1'
        option rebind_localhost '1'
        option local '/lan/'
        option domain 'xxxx-xxx.net'
        option expandhosts '1'
        option cachesize '1000'
        option readethers '1'
        option leasefile '/tmp/dhcp.leases'
        option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
        option localservice '1'
        option ednspacket_max '1232'

config dhcp 'lan'
        option interface 'lan'
        option start '100'
        option limit '150'
        option leasetime '12h'
        option dhcpv4 'server'
        option dhcpv6 'hybrid'
        option ra 'hybrid'
        list ra_flags 'managed-config'
        list ra_flags 'other-config'

config dhcp 'wan'
        option interface 'wan'
        option ignore '1'

config odhcpd 'odhcpd'
        option maindhcp '0'
        option leasefile '/tmp/hosts/odhcpd'
        option leasetrigger '/usr/sbin/odhcpd-update'
        option loglevel '4'


config defaults
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'REJECT'
        option synflood_protect '1'

config zone
        option name 'lan'
        option input 'ACCEPT'
        option output 'ACCEPT'
        option forward 'ACCEPT'
        list network 'lan'

config zone
        option name 'wan'
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'REJECT'
        option masq '1'
        option mtu_fix '1'
        list network 'wan'

config forwarding
        option src 'lan'
        option dest 'wan'

config rule
        option name 'Allow-DHCP-Renew'
        option src 'wan'
        option proto 'udp'
        option dest_port '68'
        option target 'ACCEPT'
        option family 'ipv4'

config rule
        option name 'Allow-Ping'
        option src 'wan'
        option proto 'icmp'
        option icmp_type 'echo-request'
        option family 'ipv4'
        option target 'ACCEPT'

config rule
        option name 'Allow-IGMP'
        option src 'wan'
        option proto 'igmp'
        option family 'ipv4'
        option target 'ACCEPT'

config rule
        option name 'Allow-DHCPv6'
        option src 'wan'
        option proto 'udp'
        option dest_port '546'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-MLD'
        option src 'wan'
        option proto 'icmp'
        option src_ip 'fe80::/10'
        list icmp_type '130/0'
        list icmp_type '131/0'
        list icmp_type '132/0'
        list icmp_type '143/0'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-ICMPv6-Input'
        option src 'wan'
        option proto 'icmp'
        list icmp_type 'echo-request'
        list icmp_type 'echo-reply'
        list icmp_type 'destination-unreachable'
        list icmp_type 'packet-too-big'
        list icmp_type 'time-exceeded'
        list icmp_type 'bad-header'
        list icmp_type 'unknown-header-type'
        list icmp_type 'router-solicitation'
        list icmp_type 'neighbour-solicitation'
        list icmp_type 'router-advertisement'
        list icmp_type 'neighbour-advertisement'
        option limit '1000/sec'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-ICMPv6-Forward'
        option src 'wan'
        option dest '*'
        option proto 'icmp'
        list icmp_type 'echo-request'
        list icmp_type 'echo-reply'
        list icmp_type 'destination-unreachable'
        list icmp_type 'packet-too-big'
        list icmp_type 'time-exceeded'
        list icmp_type 'bad-header'
        list icmp_type 'unknown-header-type'
        option limit '1000/sec'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-IPSec-ESP'
        option src 'wan'
        option dest 'lan'
        option proto 'esp'
        option target 'ACCEPT'

config rule
        option name 'Allow-ISAKMP'
        option src 'wan'
        option dest 'lan'
        option dest_port '500'
        option proto 'udp'
        option target 'ACCEPT'

config redirect
        option dest 'lan'
        option target 'DNAT'
        option name 'Redirect-DNS'
        option src 'lan'
        option src_ip '192.168.0.50'
        option src_port '53'
        option src_dport '53'
        option dest_ip '192.168.0.50'
        option dest_port '53'

config nat
        option name 'Masquerade-DNS'
        list proto 'tcp'
        list proto 'udp'
        option src 'lan'
        option dest_ip '192.168.0.50'
        option dest_port '53'
        option target 'MASQUERADE'

config redirect
        option dest 'lan'
        option target 'DNAT'
        option name 'BirdBox-Cloudflare'
        option family 'ipv4'
        list proto 'tcp'
        option src 'wan'
        option src_dport '443'
        option dest_ip '192.168.0.65'
        option dest_port '443'

config rule
        option name 'Allow-Birdbox'
        list proto 'tcp'
        option src 'wan'
        option dest 'lan'
        option dest_port '443'
        option target 'ACCEPT'
        list dest_ip 'x.x.x.x'
        list dest_ip 'x.x.x.x'
        list dest_ip 'x.x.x.x'

config rule 'dot_fwd'
        option name 'Deny-DoT'
        option src 'lan'
        option dest 'wan'
        option dest_port '853'
        option proto 'tcp udp'
        option target 'REJECT'

psherman · June 15, 2025, 6:06am

A few major issues here:

First, put eth1 back into br-lan.
Next, use br-lan device in the lan interface
Third, remove the bridge line
And finally - why is the lan setup as a dhcp client?

Tristan · June 15, 2025, 7:02am

Alright set that up in the order that appears to match what you were pointing out.

cat /etc/config/network


config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd8c:1d59:d93c::/48'
        option packet_steering '1'

config interface 'lan'
        option device 'eth1'
        option proto 'dhcp'

config interface 'wan'
        option device 'eth0'
        option proto 'dhcp'

config device
        option name 'eth1'

config device
        option name 'eth0'

config device
        option type 'bridge'
        option name 'br-lan'
        list ports 'eth1'

Took a couple of errors and rebuilding the interfaces to get things back in order.

The reason that DHCP Client on the LAN is that I have a raspberry pi that manages DNS and DHCP via the PiHole Application.

psherman · June 15, 2025, 7:04am

This should be device br-lan.

Always set your router with an actual static ip. It is very bad practice to use dhcp client for your lan.

Be sure to disable the dhcp server on the lan if you’re using an external dhcp server.

Tristan · June 15, 2025, 7:11am

Alright I just had the routers MAC in the DHCP reserved list in the DHCP Server on the LAN.

cat network 

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd8c:1d59:d93c::/48'
        option packet_steering '1'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.0.1'
        option netmask '255.255.255.0'
        option gateway '192.168.0.1'

config interface 'wan'
        option device 'eth0'
        option proto 'dhcp'

config device
        option name 'eth1'

config device
        option name 'eth0'

config device
        option type 'bridge'
        option name 'br-lan'
        list ports 'eth1'

Seems to be in a working state for network traffic at the moment. But restarting the full device still seems to be putting it into a state where I am not connected to the internet until I unplug and plug the WAN ethernet jack in again.

Tristan · June 17, 2025, 5:16am

Thank you for all the guidance. It looks like setting up the interfaces in the settings suggested here with the br-lan interface for the lan. Not sure why exactly that would fix it and having the internet coming up every time. Since nothing changed in regards to the WAN interface.

But if anyone has any insight would love to hear it. Or if these just get marked as resolved and it moves along.

psherman · June 17, 2025, 5:28am

The reason is that you had eth1 used in two locations (br-lan and as the device for the lan interface). This tends to mess up things lower down in the network stack, as each device should only be used in one location.

If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.
Thanks!

Tristan · June 17, 2025, 5:44am

Makes sense to me. Thanks for the assist.

system · June 27, 2025, 5:45am

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.