From owner-freebsd-xen@FreeBSD.ORG  Wed Jun 18 13:04:03 2014
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
Delivered-To: freebsd-xen@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id A7F7F159
 for <freebsd-xen@FreeBSD.org>; Wed, 18 Jun 2014 13:04:03 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8A518204D
 for <freebsd-xen@FreeBSD.org>; Wed, 18 Jun 2014 13:04:03 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s5ID43uh037730
 for <freebsd-xen@FreeBSD.org>; Wed, 18 Jun 2014 14:04:03 +0100 (BST)
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-xen@FreeBSD.org
Subject: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic
 for other Xen PV guests on same Dom0 Host.
Date: Wed, 18 Jun 2014 13:04:03 +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: 9.2-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kpielorz@tdx.co.uk
X-Bugzilla-Status: In Discussion
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-188261-23905-IiKxd7H7TT@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-188261-23905@https.bugs.freebsd.org/bugzilla/>
References: <bug-188261-23905@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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.18
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jun 2014 13:04:03 -0000

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

--- Comment #2 from kpielorz@tdx.co.uk ---

Having setup a test system with FreeBSD 9.2-STABLE, 10-STABLE, 11-CURRENT etc.
this bug still exists on all of those, regardless of version.

For a 'Client' (i.e. a guest VM trying to route traffic through the other
FreeBSD 'router' machine) you can do:

  ifconfig xn0 -txcsum

And it will fix that single client. No amount of option fiddling (other than
restarting in HVM mode) will fix the 'router' machine - i.e. it's not possible
to fix the 'router' machine so that clients don't need any fix.

I've been unable to test disabling txcsum on Windows clients running on the
same XenServer as I can't see where I can do that.

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