Ongoing RX Dropped Packets on Linux (Ubuntu) when connected to Deco BE85 series

Ongoing RX Dropped Packets on Linux (Ubuntu) when connected to Deco BE85 series

Ongoing RX Dropped Packets on Linux (Ubuntu) when connected to Deco BE85 series
Ongoing RX Dropped Packets on Linux (Ubuntu) when connected to Deco BE85 series
Yesterday
Model: Deco BE85  
Hardware Version: V2
Firmware Version: 1.2.2 Build 20260408

Hi,

I am experiencing a persistent issue where a significant number of "RX dropped" packets are recorded on my Linux (Ubuntu 24.04) machine whenever it is connected to my Deco X series mesh system.

I have conducted extensive troubleshooting to isolate the cause, and the results strongly suggest that the Deco units are the trigger.

 

[My Environment]

  • ISP/Modem: NTT PR-500KI (HGW) with "v6 Plus" (IPoE IPv6)

  • Deco Units: Deco X series (2-unit setup)

  • Client PC: Linux Ubuntu 24.04 (Reproduced on both Wired NIC: enp8s0 and Wireless NIC: wlp6s0)

  •  

[Troubleshooting Steps Taken]

  1. Direct Connection to Modem (Baseline): When the PC is connected directly to the ISP modem (PR-500KI) via a standard Ethernet cable, zero dropped packets occur. The connection is perfectly stable. This confirms the PC hardware, OS, and cables are functioning correctly.

  2. Deco Connection (Problem): As soon as the PC is connected to the Deco network (either via Ethernet or Wi-Fi), RX dropped counts begin to increase rapidly (monitored via watch -n 1 ip -s link show).

  3. Operating Modes: The issue persists regardless of whether the Deco is in "Router Mode" or "Access Point (AP) Mode."

  4. Physical Power Correlation: The moment the Deco units are powered off, the packet drops on the PC stop immediately.
     

[Hypothesis] Since the issue only occurs when Deco is active, I suspect that specific control packets sent by Deco (e.g., STP, LLDP, or proprietary mesh backhaul protocols) might be causing conflicts or being rejected by the Linux kernel/NIC driver.

 

[Questions]

  • Are there any known compatibility issues between Deco's control protocols and specific Linux kernel versions or NIC drivers?

  • Is there a way to access Deco's internal logs or disable specific background protocols (like loop detection or STP) to see if it resolves the drops?

  • Has anyone else observed this behavior on Linux clients within a Deco mesh environment?

I appreciate any technical insights you can provide.

0
0
#1