OpenWrt One: intermittent WAN packet loss (7–42%) on both Ethernet ports, other router on same modem is clean

Hi all,

I have an OpenWrt One (bought Feb 2025, original 12V PD supply) with intermittent packet loss on the WAN, and I’ve run out of things to rule out on my side. I’d appreciate any ideas, or confirmation if this looks like a hardware fault.

Setup: cable ISP (Tigo, Colombia), modem in bridge mode, OpenWrt One as main router (AdGuard Home + Tailscale).

Symptom: ping to 8.8.8.8 from the router loses 7–42% of packets in 300–1000 packet runs. It comes and goes on its own (clean periods of minutes to a few hours). Link stays up at 1000/Full, no link flaps in logs, rx_crc_errors 0, temperature ~64 °C.

What I tested:

  • OpenWrt 25.12.6 and 24.10.8: both show the loss, including a factory-default config with Wi-Fi off and no LAN devices connected.
  • WAN on the 2.5G port (EN8811H) and on the 1G port (eth1, reassigned as WAN): loss on both.
  • Limiting the 2.5G port to advertise 1000baseT only: no change.
  • 3 cables, 2 modem ports, 2 MAC addresses, 2 power supplies (original 12V PD and an Anker 140W PD): no change.
  • Laptop connected directly to the second modem port at the same time the router was losing 19–34%: 0% loss (3 runs of 300).
  • TP-Link Archer A6 v2 (OpenWrt 25.12.6) on the same modem and cable: 0 lost out of 1000.
  • After a modem reboot, the One dropped to 8/1000 lost. I’m now logging loss every 5 minutes to see if it comes back.

Questions:

  1. Has anyone seen similar behavior on the OpenWrt One, on either port?
  2. Is there any diagnostic you’d suggest (counters, debug, PHY/MAC registers) that would show where the packets are lost?
  3. Could this be a hardware issue with the MT7981B Ethernet, since both ports are affected?

Port counters on eth1 (current WAN) are clean:

rx_fcs_errors: 0
rx_short_errors: 0
rx_long_errors: 0
rx_checksum_errors: 1
rx_xdp_drop: 0
rx_xdp_tx_errors: 0
tx_xdp_xmit_errors: 0

So whatever is being lost doesn’t show up as RX errors at the MAC.

I can post full command outputs. Thanks!

I’ve seen this behavior!

I was running tcpdump without compacting / reclaiming memory. Memory usage skyrocketed, the router bogged, packets were dropped. It does it especially badly if you run tcpdump with the -v or -vv flag… gets so bad it’ll OOM tcpdump.

Are you running any memory-heavy packages?

Thanks for the pointer! In my case it doesn’t seem to be memory. I’m not running tcpdump or anything heavy, just AdGuard Home and Tailscale (~196 MB RSS combined). The router uses ~225 MB of ~987 MB, /proc/buddyinfo shows 141 free order-10 blocks (~564 MB), and there are no page allocation failures or OOM messages in dmesg/logread.

Also, the loss persisted after a factory reset, and it went away after rebooting the cable modem (Tigo, bridge mode). Since then the One has logged only 3 lost pings out of ~17,500 over ~3 days (20 pings every 5 min). An Archer A6 on the same modem and cable showed 0/1000 right after the modem reboot, vs. 8/1000 on the One, so I keep a small suspicion on the One, but the main cause looks like the modem. Funny enough, your own drops also came from the ISP side (bad coax).

Is your ISP upgrading to DOCSIS 4.0 or something beyond DOCSIS 3.1? I have the Motorola MB8611 modem, and it’s not playing nice with Comcast’s network upgrades (they’re not going to DOCSIS 4.0 strictly, they’re doing something else), so I bought a NetGear NightHawk CM3000 that I’ll be getting set up this weekend.

Motorola’s cable modem business hit a rough patch, so now there’s no DOCSIS updates that can be pushed to the modem by Comcast… strangely, the Motorola modem is practically on par with the Netgear modem… but without that DOCSIS update to properly provision the modem, it drops packets badly. Drop in a bad coax on top of that, and there are thousands of dropped packets per minute when bandwidth is pushed to the limit.

So, you might check with your cable provider to see if they have a DOCSIS file they can push to your modem. If your modem has mid/high-split capability, be sure they set the DOCSIS file up for that.