From owner-freebsd-xen@freebsd.org  Mon May  9 16:08:30 2016
Return-Path: <owner-freebsd-xen@freebsd.org>
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 EC7C9B331C6
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Mon,  9 May 2016 16:08:30 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id DD87E1BFF
 for <freebsd-xen@FreeBSD.org>; Mon,  9 May 2016 16:08:30 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u49G8TCI006549
 for <freebsd-xen@FreeBSD.org>; Mon, 9 May 2016 16:08:30 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-xen@FreeBSD.org
Subject: [Bug 197344] tx checksum broken on XEN
Date: Mon, 09 May 2016 16:08:30 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: pgadmin@pse-consulting.de
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-197344-23905-7CPO8HZT2G@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-197344-23905@https.bugs.freebsd.org/bugzilla/>
References: <bug-197344-23905@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2016 16:08:31 -0000

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

--- Comment #3 from Andreas Pflug <pgadmin@pse-consulting.de> ---
#188261 apparently describes the same problem.

How to reproduce:

DomU #1 <-> DomU/Router <-> DomU #2
all on same Xen host.

Accessing DomU#2 from DomU#1 (e.g. ssh) hardly works, until tx checksum is
disabled. When a host that's not hosted on the same Xen machine is involved,
everything works as expected.

Tested with Xen4.1 and 4.4, DomU/Router FreeBSD 10.1 (pfSense) and 10.2
(opnSense).

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