Date: Mon, 21 Dec 2020 13:22:25 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 252015] Enabling LRO on network interfaces by default considered harmful Message-ID: <bug-252015-227-gVEZWDpK54@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-252015-227@https.bugs.freebsd.org/bugzilla/> References: <bug-252015-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252015 daniel sch=C3=BCtze <dms@cwa.uk.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dms@cwa.uk.com --- Comment #1 from daniel sch=C3=BCtze <dms@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 t= he 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 eval= uate the environment and enable LRO when possible. To enable: # ifconfig ixlX lro It can be disabled by using: # ifconfig ixlX -lro ENQUOTE --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-252015-227-gVEZWDpK54>