[Bug 252015] Enabling LRO on network interfaces by default considered harmful

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Dec 21 13:22:25 UTC 2020


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252015

daniel schütze <dms at cwa.uk.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dms at cwa.uk.com

--- Comment #1 from daniel schütze <dms at cwa.uk.com> ---
To confirm I experienced this issue with LRO on a host causing problems on two
VirtualBox virtual machines.  One a gateway and one a VPN.  In both cases the
virtual machines were rendered unusable due to the forwarding elements being
restricted.

The effect was observable with any client connected to the VPN or using the
gateway getting very low transfer speeds of 20kbytes/second or so when going
through a tunnel or  gateway.

The resolution was to restart the networking on the host with the -lro flag (as
an aside vboxnet also needed be restarted in order to ensure the host could
directly network with the VMs)

Also note the information on the intel driver for the interface

https://downloadmirror.intel.com/25160/eng/readme.txt

QUOTE
LRO
---
LRO (Large Receive Offload) may provide Rx performance improvement. However, it
is incompatible with packet-forwarding workloads. You should carefully evaluate
the environment and enable LRO when possible.

To enable:

# ifconfig ixlX lro

It can be disabled by using:

# ifconfig ixlX -lro
ENQUOTE

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list