Struggling with poor performance wireless and wired. Not sure where to start

I've been using OpenWT on the OpenWRT One router for about a year. Recently wireless performance has fallen to the point that, at times, I can't watch a video on my phone and struggle to load websites. On my wired desktop computer, I notice lag spikes every few seconds that go from 20 ms up to 300-1000 ms. I see similar spikes when I look at the Bandwidth Real-Time Graphs in OpenWRT, but I don't really know how to interpret what I'm seeing.

I'm pretty new to this and not sure how to proceed with troubleshooting this problem. Any guidance is much appreciated. I'm happy to post any logs or anything else that's needed. Thank you.

The best starting point is to look at the configs...

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 (red circle; this works best in the 'Markdown' composer view in the blue oval):

Screenshot 2025-10-20 at 8.14.14 PM

Remember to redact passwords, VPN keys, 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

Thanks you. I hope this is formatted correctly.

root@OpenWrt:~# ubus call system board
{
        "kernel": "6.6.63",
        "hostname": "OpenWrt",
        "system": "ARMv8 Processor rev 4",
        "model": "OpenWrt One",
        "board_name": "openwrt,one",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "24.10.0-rc2",
                "revision": "r28161-ea17e958b9",
                "target": "mediatek/filogic",
                "description": "OpenWrt 24.10.0-rc2 r28161-ea17e958b9",
                "builddate": "1733226068"
        }
}
root@OpenWrt:~# ^C

root@OpenWrt:~# 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 'fd8b:8256:bf86::/48'

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

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'

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

config interface 'wan6'
        option device 'eth0'
        option proto 'dhcpv6'

root@OpenWrt:~# ^C

root@OpenWrt:~# cat /etc/config/wireless

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-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'OpenWrt'
        option encryption 'psk2'
        option key ''

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 wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option ssid 'OpenWrt'
        option encryption 'psk2'
        option key ''

root@OpenWrt:~# cat /etc/config/dhcp

config dnsmasq
        option domainneeded '1'
        option boguspriv '1'
        option filterwin2k '0'
        option localise_queries '1'
        option rebind_protection '1'
        option rebind_localhost '1'
        option local '/lan/'
        option domain 'lan'
        option expandhosts '1'
        option nonegcache '0'
        option cachesize '1000'
        option authoritative '1'
        option readethers '1'
        option leasefile '/tmp/dhcp.leases'
        option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
        option nonwildcard '1'
        option localservice '1'
        option ednspacket_max '1232'
        option filter_aaaa '0'
        option filter_a '0'

config dhcp 'lan'
        option interface 'lan'
        option start '100'
        option limit '150'
        option leasetime '12h'
        option dhcpv4 'server'
        option dhcpv6 'server'
        option ra 'server'
        option ra_slaac '1'
        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'

root@OpenWrt:~# cat /etc/config/firewall
config defaults
        option syn_flood        1
        option input            REJECT
        option output           ACCEPT
        option forward          REJECT
# Uncomment this line to disable ipv6 rules
#       option disable_ipv6     1

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

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

config forwarding
        option src              lan
        option dest             wan

# We need to accept udp packets on port 68,
# see https://dev.openwrt.org/ticket/4108
config rule
        option name             Allow-DHCP-Renew
        option src              wan
        option proto            udp
        option dest_port        68
        option target           ACCEPT
        option family           ipv4

# Allow IPv4 ping
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

# Allow DHCPv6 replies
# see https://github.com/openwrt/openwrt/issues/5066
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

# Allow essential incoming IPv6 ICMP traffic
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

# Allow essential forwarded IPv6 ICMP traffic
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


### EXAMPLE CONFIG SECTIONS
# do not allow a specific ip to access wan
#config rule
#       option src              lan
#       option src_ip   192.168.45.2
#       option dest             wan
#       option proto    tcp
#       option target   REJECT

# block a specific mac on wan
#config rule
#       option dest             wan
#       option src_mac  00:11:22:33:44:66
#       option target   REJECT

# block incoming ICMP traffic on a zone
#config rule
#       option src              lan
#       option proto    ICMP
#       option target   DROP

# port redirect port coming in on wan to lan
#config redirect
#       option src                      wan
#       option src_dport        80
#       option dest                     lan
#       option dest_ip          192.168.16.235
#       option dest_port        80
#       option proto            tcp

# port redirect of remapped ssh port (22001) on wan
#config redirect
#       option src              wan
#       option src_dport        22001
#       option dest             lan
#       option dest_port        22
#       option proto            tcp

### FULL CONFIG SECTIONS
#config rule
#       option src              lan
#       option src_ip   192.168.45.2
#       option src_mac  00:11:22:33:44:55
#       option src_port 80
#       option dest             wan
#       option dest_ip  194.25.2.129
#       option dest_port        120
#       option proto    tcp
#       option target   REJECT

#config redirect
#       option src              lan
#       option src_ip   192.168.45.2
#       option src_mac  00:11:22:33:44:55
#       option src_port         1024
#       option src_dport        80
#       option dest_ip  194.25.2.129
#       option dest_port        120
#       option proto    tcp

First comment is why are you running an old release candidate from last years stable? Why, at bare minimum, start with 25.12.5 before troubleshooting? mt76 driver has come a long way since then especially with a new product like the One.

Start with setting the country code for each wireless device.

Performance is typically restricted or suboptimal when the country code is unset (often shown as “driver default” in LuCI). This is because the radio falls back to a conservative regulatory domain.

But how will this help with a wired connection?

It won't.
What's upstream of your OO? Maybe the problem isn't your router, but your connection to your ISP?

So, looking at your config, things look to be nearly default.

The very first thing to do, if not already done, is to upgrade to 25.12.5 as suggested earlier. When you upgrade, do not keep the settings. This way you'll start with a completely clean slate. (you can of course reset to defaults even after the upgrade). Then, set up wifi (configure the country code, SSID name, encryption type, passphrase, and enable the radios).

At this point, it's best to test with a wired computer directly connected to the lan port of the One. If the performance isn't good, you'll want to test the upstream connection by removing the OpenWrt One and instead connecting your computer directly to the ISP. If that improves things, we'll try to figure out what else could cause problems on the OpenWrt side.

If wired is okay, move on and test wireless and see what happens... if wifi has issues, it may be related to general radio interference, but we can dig deeper at that point.

This isn't my router. This question was for those who are fixated on advice about WiFi and only WiFi.

So you think hi-jacking the thread makes it right?

I think that if the problem occurs not only over Wi-Fi but also via a wired connection, then it can't be solved just by troubleshooting the Wi-Fi. I also highly doubt that the firmware, even if it's old, would just suddenly break out of nowhere.

I like the advice given above: check the internet connection directly via cable without the router, since there is a PC with a network card available. It's quite possible that a contact in the RJ45 (8P8C) connector is just damaged and the cable simply needs to be recrimped.

You could, of course, check how the port is behaving in LuCI, but since the user hasn't done that yet, they either don't know how to do it, or... well, then I don't know either))). It's also entirely possible that the wired PC caught some malware and is just hogging all the bandwidth, to the point where even the router lags and LuCI becomes inaccessible.

One thing is for sure: you won't solve this problem by just fixing the Wi-Fi.

This One has a Filogic series SoC which has great upstream Linux support, but this model has fairly slow CPU clocks at only 1.3GHz, so most people will want to use hardware acceleration to hit higher throughputs (e.g. gigabit or higher on the 2.5gbps port etc):

  1. Upgrade with clean config to 25.12.5
  2. Enable packet steering. I believe this is on by default now.
  3. Enable HFO and WED.
  4. Configure Wi-Fi then enable it.

This is all discussed on the doc page. I just updated the page to make it more clear by adding a new Configuration section and consolidating this info.

People just try, to narrow down one issue at a time.

The other thing is yes things can suddenly break.
Like with a huge uptime suddenly there is an error in one register or the binary firmware of the chip has an issue with the Kernel driver. Things like that.

Second, if there is no reason to run one particular snapshot then as always go to a latest stable release.

Good luck with identifying your issue.

Edit correction. You arent even OP :roll_eyes:

Sorry for the late update and thank you for all of the suggestions. This has been a learning experience. I've upgraded the firmware to 25.12.5 and restored the config from backup. I got stuck at "Flashing....", but after about 30 min I just opened a new browser tab and reconnected through Luci and everything seems fine.

I've also set the country code for each device (wireless radio?) and enabled packet steering (all gpu's) and set RPS to 128. I enabled HFO but not WED as I'm waiting for an opportunity to reboot the router. Once I've completed that step I'll start testing both the wireless and wired experience and see if there's an improvement. If I still see issues I'll connect directly to the ISP on my wired desktop and test that connection.

Going through this exercise has shown me just how many people and devices in my house are dependent on one wireless router. I think it's time to install another as an access point for redundancy if nothing else.

Thanks again everyone.

Nice and well done, it can be a little daunting the very first time glad it all worked.

Now that it's all setup you can go to the LuCI webUI to System → Attended Sysupgrade page, run that it'll upgrade you firmware for you anytime in the future.

I enabled WED once I figured out that I needed a text editor. Nano did the job. I ran several Waveform buffer float tests with my wired desktop computer and wireless phone.

Wired connected to router:

Latency: 20ms unloaded. +17ms download. +1ms upload.
Speed: 916Mbps download. 897Mbps upload.

Wired connected to ISP, no router:

Latency: 22ms unloaded. +31ms download. +0ms upload.
Speed: 934Mbps download. 939Mbps upload.

Wireless near router:

Latency: 24ms unloaded. +65ms download. +54ms upload.
Speed: 860Mbps download. 742Mbps upload.

Wireless far from router:

Latency: 17ms unloaded. +35ms download. +80ms upload.
Speed: 530Mbps download. 264Mbps upload.

Upload and download speeds seems pretty good until I'm on the far side of my house on wireless. Latency is inconsistent? I'm not sure how to interpret more from the results. Overall the experience using both wired and wireless seems to have improved. Videos on wireless play smoothly with minimal buffering. I haven't noticed the latency spikes when gaming on my wired computer.

Have I solved my problem? Everything feels better to use, but I wonder if there's more I can do to reduce latency.

What's upstream of your OO? Maybe the problem isn't your router, but your connection to your ISP?

Immediately upstream I have a cable/ethernet adapter. We have fiber at the house, so I assume there are one or more adapters to convert to cable before entering the house. The adapters probably aren't helping things.

You can always use the sed command to enable WED without a text editor, but nano works great too. Anyway, you will likely see a bit more bufferbloat with WED since it bypasses AQL (there are actually big threads about AQL analysis and we have some recommendations on the mt6000 doc page). It's up to you, if you aren't using the main CPUs for much else can leave it disabled. WED is very performant if bufferbloat is not an issue.

530/264 Mbps is actually pretty good...

When running the Waveform bufferfloat test I was getting grades ranging from B to C. I'm not running any other applications on the router, so I assume that the CPU load is minimal. Maybe I should favor reducing bufferfloat and disable WED until I need to optimize CPU usage.