From owner-freebsd-virtualization@freebsd.org  Fri Oct 30 04:10:40 2015
Return-Path: <owner-freebsd-virtualization@freebsd.org>
Delivered-To: freebsd-virtualization@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 D8C61A207DB
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Fri, 30 Oct 2015 04:10:40 +0000 (UTC)
 (envelope-from amvandemore@gmail.com)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com
 [IPv6:2a00:1450:400c:c05::231])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 79ADB1111
 for <freebsd-virtualization@freebsd.org>; Fri, 30 Oct 2015 04:10:40 +0000 (UTC)
 (envelope-from amvandemore@gmail.com)
Received: by wicfx6 with SMTP id fx6so2611206wic.1
 for <freebsd-virtualization@freebsd.org>; Thu, 29 Oct 2015 21:10:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=1qXuMI7QfPu2kqKvus3Q4zTY+ZgKSXpIhxh8Buo6QYQ=;
 b=qVu4/4mQQt1Lge44QhB+PPnc9Yk3ZleI9M8/KJuwKQ7Nli8YIMZ8J1hOEflpLRymBL
 5b1Zwd6lyoO7BK4b+u826qDdDGt5IPV1O3w9YPMCQpL+612bIlhZ5i/CF6/hdC++eedL
 u3RVD/OwIzHJeVO+BxJCGsA6fWUMYBjvX8s1fm8Eh/SDtAassbUfxC4h5voTccd6x6dW
 a02fnXbrxTUQkMzfJVItJEXOCYDPFCYLHCSPGcWmg0Eux6GwZzqatLtSAJ8nPqZ0oAKB
 yvOgh7THadtO6K41N9kCCVUwfRiitf7ZhD9kns7y5orDA0moPH70Aic/Ft98arIX0YZK
 uOmQ==
MIME-Version: 1.0
X-Received: by 10.194.86.98 with SMTP id o2mr6573335wjz.142.1446178238813;
 Thu, 29 Oct 2015 21:10:38 -0700 (PDT)
Received: by 10.194.16.231 with HTTP; Thu, 29 Oct 2015 21:10:38 -0700 (PDT)
In-Reply-To: <20151030034535.GA19514@gta.com>
References: <20151030034535.GA19514@gta.com>
Date: Thu, 29 Oct 2015 23:10:38 -0500
Message-ID: <CA+tpaK2VxH3f_Mp5otRtHMJp2pQAiwiFACP2EDmmrLBA_hb6pQ@mail.gmail.com>
Subject: Re: Issues gatewaying through Hyper-V
From: Adam Vande More <amvandemore@gmail.com>
To: Larry Baird <lab@gta.com>
Cc: FreeBSD virtualization <freebsd-virtualization@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.20
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2015 04:10:41 -0000

On Thu, Oct 29, 2015 at 10:45 PM, Larry Baird <lab@gta.com> wrote:

> I have two identical setups on Hyper-V 2012R2 and Hype-V windows 10.
>
> I have two FreeBSD 10.2-RELEASE-p6 Hyper-V hosts in both cases.
> The first FreeBSD host (client) has one NIC configured to use a Private
> network. The second (gateway) has two nics. One private and one external.
> The gateway box has the gateway_enable option set to YES in its rc.conf.
> The boxes otherwize of very vanilla.
>
> I get failures forwarding thru gateway on both versions of Hyper-V. But
> they fail in different ways.
>

There was a similar issue w/ PF resolved earlier and I'm pretty sure the
fix wasn't in 10.2.

If PF is in use, does switching to ipfw fix it?

I know nothing of HyperV, but I also saw similar behavior on KVM.
Switching the VM NIC away from virtio to intel was a successful workaround.

-- 
Adam