Speed drops?

Started by RouterGuy2019, November 18, 2026, 06:40:44 PM

Previous topic - Next topic
I have been having an issue for awhile where if I have heavy traffic all at the same time my 1gb connection will start to slow drop in speed until it gets super slow like 1-3mb, sometimes if I wait like 5 mins it will go back to normal speeds on it's own.  But sometimes I have to reboot the modem to get the speed back to normal.  I assumed this was a problem with my ISP, but I was told it was and issue with opnsense (not really opnsense, freebsd and intel NIC's) because of the fact that I have intel 2.5gb NIC's. So I was told to do this...

Uncheck...
Disable hardware checksum offload
Disable hardware TCP segmentation offload
Disable hardware large receive offload

Navigate to System > Settings > Tunables and make sure EEE is disabled for the igc driver, or disable it directly via shell/SSH:

Set hw.igc.eee_setting=0Verification


Hardcode Speed and Duplex

Go to Interfaces > [WAN / LAN] in OPNsense.

Scroll down to Speed and duplex.

Change it from Autosense to 2500base-T Full-Duplex (or match whatever your modem port speed is).

I am just wondering if anyone can tell me if this is sound advice?

Thanks.

Diddling the offloads may be helpful. I'd do one at a time, and test. EEE is garbage, but it usually results in link failures, which should be pretty obvious. Can't hurt to disable it, and see if it makes any difference. I would not fix speed and duplex unless autonegotiation fails to deliver proper speed and duplex.

Any other symptoms? What does the CPU widget (or better, top from a shell) indicate? How about various netstat displays ("Interfaces: Diagnostics: Netstat" or shell) - any bad counters incrementing?

November 18, 2026, 09:50:20 PM #2 Last Edit: November 18, 2026, 09:52:59 PM by RouterGuy2019
Quote from: pfry on November 18, 2026, 09:36:42 PMDiddling the offloads may be helpful. I'd do one at a time, and test. EEE is garbage, but it usually results in link failures, which should be pretty obvious. Can't hurt to disable it, and see if it makes any difference. I would not fix speed and duplex unless autonegotiation fails to deliver proper speed and duplex.

Any other symptoms? What does the CPU widget (or better, top from a shell) indicate? How about various netstat displays ("Interfaces: Diagnostics: Netstat" or shell) - any bad counters incrementing?

I am not seeing anything weird in either of those at the moment. If you mean when it gets slow I will check the next time it happens.

Can diddling the offloads have any serious negative side effects?

Quote from: RouterGuy2019 on November 18, 2026, 09:50:20 PM[...]If you mean when it gets slow I will check the next time it happens.

For top, yes, best to look during the issue. The netstat counters will accrue and persist until cleared or the firewall is restarted.

QuoteCan diddling the offloads have any serious negative side effects?

Yes, but it depends on the driver, and in the case of Intel hardware, the NVM. (Many other devices use firmware loaded from the driver.) There is no actual fail-safe set of parameters (too many variables), but for the most part, disabling offloads is the safer bet. You might try digging through the giant i226 thread, for instance, for experiences/recommendations (although it's mostly firmware-related).

Re-reading...
Quote[...]But sometimes I have to reboot the modem to get the speed back to normal[...]

...could suggest a link- or load-related issue, but solving the problem by poking the modem doesn't tend to implicate the firewall. Still, it's best to rule it out as well as possible. Unfortunately the process for (successfully) troubleshooting ISP issues is usually  "customer determines the issue and presents it to the ISP".