Date: Tue, 14 Jul 2015 14:23:00 -0500 From: Mark Felder <feld@FreeBSD.org> To: Colin Percival <cperciva@freebsd.org>, freebsd-xen@freebsd.org Cc: gnn@freebsd.org, Kristof Provost <kp@FreeBSD.org> Subject: Re: Networking under Xen Message-ID: <1436901780.3211878.323698017.360F8D73@webmail.messagingengine.com> In-Reply-To: <55A55AE8.4090101@freebsd.org> References: <4E7B7075-4E0D-4EA7-9F5D-6D252CFBD487@gmail.com> <1436890526.3162974.323521249.6B73E6E2@webmail.messagingengine.com> <55A55AE8.4090101@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 14, 2015, at 13:54, Colin Percival wrote: > On 07/14/15 09:15, Mark Felder wrote: > > On Tue, Jul 14, 2015, at 07:36, Sydney Meyer wrote: > >> - Dropped/Stalled Connections with TCP Segmentation Offload and pf > >> enabled. > > > > TSO is a known issue. I've been turning it off for years to get FreeBSD > > to play nice on Xen. > > More precisely *pf* is a known issue. It's inserting TCP checksums > into TSO packets. I reported this a long time ago and I don't know > why pf still hasn't been fixed. > I think Kristof may have solved this in HEAD with all of the care and feeding he has been doing to pf, but I haven't verified.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1436901780.3211878.323698017.360F8D73>