From owner-freebsd-xen@freebsd.org  Mon May  9 11:12:07 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 15A2AB34ED9
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Mon,  9 May 2016 11:12:07 +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 05F841D9C
 for <freebsd-xen@FreeBSD.org>; Mon,  9 May 2016 11:12:07 +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 u49BC6WK096951
 for <freebsd-xen@FreeBSD.org>; Mon, 9 May 2016 11:12:06 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: Mon, 09 May 2016 11:12:06 +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: meyer.sydney@gmail.com
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-ba0TqLx7M9@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: Mon, 09 May 2016 11:12:07 -0000

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

--- Comment #9 from Sydney Meyer <meyer.sydney@gmail.com> ---
In its most basic form, without doing nat, without have pf loaded, the prob=
lem
comes up e.g. in the following setup:

(PC1) 10.0.1.2/24 on xn0 <--> 10.0.1.1/24 on xn0 (FreeBSD DomU Router)
10.0.2.1/24 on xn1 <--> (PC2) 10.0.2.2/24 on xn0.

- Install FreeBSD on DomU Router with 2 paravirtual network interfaces in
different subnets
- sysctl net.inet.ip.forwarding=3D1 on Router
- Setup PC1/2 with FreeBSD/Linux/Windows with the FreeBSD Router as their
Gateway.
- On PC1: dd if=3D/dev/zero bs=3D1M | nc -l 5001
- On PC2: nc 1.2.3.4 5001 | dd of=3D/dev/zero bs=3D1M
- Or any other TCP-Connection, e.g. ssh, for that matter.

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