From owner-freebsd-xen@freebsd.org  Wed Jun  8 11:22:09 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 6DB7DB6F755
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Wed,  8 Jun 2016 11:22:09 +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 5DF60118D
 for <freebsd-xen@FreeBSD.org>; Wed,  8 Jun 2016 11:22:09 +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 u58BM8X1069896
 for <freebsd-xen@FreeBSD.org>; Wed, 8 Jun 2016 11:22:09 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: Wed, 08 Jun 2016 11:22:09 +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: royger@freebsd.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-188261-23905-150PYbtPAz@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: 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: Wed, 08 Jun 2016 11:22:09 -0000

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

--- Comment #21 from Roger Pau Monn=C3=83=C2=A9 <royger@freebsd.org> ---
(In reply to kpielorz from comment #20)
Yes, I think I know what the issue is. What OS are the other DomUs on the s=
ame
host using?

If you can provide me with complete tcpdump traces on both interfaces
(xn0/xn1), that would help me quite a lot, the following rune should get you
the traces:

# tcpdump -n -i <if> -s0 -w <output>.pcap

The resulting pcap files are going to be quite big, so you will probably ha=
ve
to upload them somewhere. Just 10s of capture while trying to route traffic=
 is
probably fine.

Thanks, Roger.

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