Sometimes the network is slow and you cannot figure out why.

I had a laptop getting 250 Mbps on a gigabit connection. Speedtest said one thing, actual downloads said another. I checked the router, the cables, the ISP - nothing obvious.

Then I noticed the Ethernet cable was going through a USB-C dock.

The Problem

USB-C docks with Ethernet ports share bandwidth with everything else going through that single USB-C connection. Display, storage, network - all fighting for the same pipe.

But the real issue is not bandwidth. It is flow control.

When packets start dropping, TCP retransmits. Retransmissions look like slow speeds, not broken connections. Your throughput tanks while the connection technically stays up.

Checking Flow Control

The ethtool command shows what is happening:

# See the driver and current settings ethtool -i eth0 ethtool -a eth0 # Enable flow control if it is off sudo ethtool -A eth0 rx on tx on 

Flow control lets the network tell the sender to pause when buffers fill up. Without it, packets just get dropped under load.

The Fix

Two options:

  1. Enable flow control on the dock Ethernet interface if your switch supports it.

  2. Bypass the dock and use a direct USB-C to Ethernet adapter. These usually have dedicated controllers that do not share bandwidth with displays and storage.

What to Check

When network speeds seem off:

  • Are you going through a hub, dock, or monitor with Ethernet?
  • What does ethtool -a say about flow control?
  • Do you see packet errors in ip -s link?
  • Does a direct connection perform better?

The Takeaway

Every hop in the network path is a potential bottleneck. USB-C docks are convenient, but they are not always transparent pass-through devices. Sometimes they are the variable you are missing.

When debugging slow connections, check everything between your machine and the switch.