From owner-freebsd-xen@FreeBSD.ORG  Tue May 19 06:05:05 2015
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
Delivered-To: freebsd-xen@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id CDC80FD9
 for <freebsd-xen@FreeBSD.org>; Tue, 19 May 2015 06:05:05 +0000 (UTC)
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 B7A261FAF
 for <freebsd-xen@FreeBSD.org>; Tue, 19 May 2015 06:05:05 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t4J655bh055654
 for <freebsd-xen@FreeBSD.org>; Tue, 19 May 2015 06:05:05 GMT
 (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: Tue, 19 May 2015 06:05:05 +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: raitech@gmail.com
X-Bugzilla-Status: In Progress
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-188261-23905-9F8oPJtqlc@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.20
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: Tue, 19 May 2015 06:05:05 -0000

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

raitech@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |raitech@gmail.com

--- Comment #6 from raitech@gmail.com ---
(In reply to Sean Bruno from comment #4)

Following Sean's idea, I was playing with the PV network frontend options, and
got one FreeBSD 10.1 RELEASE to get its traffic routed by another FreeBSD 10.1
RELEASE, both within the same XenServer 6.5 host and both with xn1 over the
same host-VLAN.

router0# ifconfig xn1 -txcsum -tso4 -lro
vm0# ifconfig xn1 -txcsum -tso4 -lro

Without this config on both domUs, I can not do a:

# fetch http://www.google.com/
  (obs.: on success, result will be stored in fetch.out; 
         needs two control-C to stop)

But with the indicated configuration, I can exec the above command like a
charm. I could even SSH into the vm0 from the Internet.

Best regards,
Raimundo Santos

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