From owner-freebsd-xen@freebsd.org Wed Jul 15 07:44:10 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 59B8D9A239C for ; Wed, 15 Jul 2015 07:44:10 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 218D514A1; Wed, 15 Jul 2015 07:44:10 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from [192.168.18.125] (unknown [81.83.8.162]) by venus.codepro.be (Postfix) with ESMTPSA id C514811AB2; Wed, 15 Jul 2015 09:44:04 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) Subject: Re: Networking under Xen From: Kristof Provost In-Reply-To: <1436901780.3211878.323698017.360F8D73@webmail.messagingengine.com> Date: Wed, 15 Jul 2015 09:44:02 +0200 Cc: Colin Percival , freebsd-xen@freebsd.org, gnn@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <20F2398D-ECDF-4CF4-966D-18C894779C4C@FreeBSD.org> References: <4E7B7075-4E0D-4EA7-9F5D-6D252CFBD487@gmail.com> <1436890526.3162974.323521249.6B73E6E2@webmail.messagingengine.com> <55A55AE8.4090101@freebsd.org> <1436901780.3211878.323698017.360F8D73@webmail.messagingengine.com> To: Mark Felder X-Mailer: Apple Mail (2.2102) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jul 2015 07:44:10 -0000 > On 14 Jul 2015, at 21:23, Mark Felder wrote: > On Tue, Jul 14, 2015, at 13:54, Colin Percival wrote: >> On 07/14/15 09:15, Mark Felder wrote: >> 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. >>=20 >=20 > 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. >=20 I wouldn=E2=80=99t expect so. As far as I know I=E2=80=99ve not fixed = anything TSO or checksum related. In fact, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D172648 is at the top of my TODO list right now. Regards, Kristof=