From owner-freebsd-bugs@freebsd.org  Thu Oct  8 22:59:27 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 778369D1B95
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Thu,  8 Oct 2015 22:59:27 +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 63E201E1
 for <freebsd-bugs@FreeBSD.org>; Thu,  8 Oct 2015 22:59:27 +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 t98MxRdW011085
 for <freebsd-bugs@FreeBSD.org>; Thu, 8 Oct 2015 22:59:27 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 203630] [Hyper-V] [nat] [tcp] 10.2 NAT bug in TCP stack or
 hyperv netsvc driver
Date: Thu, 08 Oct 2015 22:59:27 +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: 10.2-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: kjcamann.lists@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-203630-8-VBBDe96kwf@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-203630-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-203630-8@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-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Oct 2015 22:59:27 -0000

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

--- Comment #2 from Ken Camann <kjcamann.lists@gmail.com> ---
Hi Alexandr,

Those are tunables for the vtnet driver, the virtio-based virtual network
driver. Hyper-V has its own (netsvc) and doesn't use the vtnet. In some VM
programs like VirtualBox, you have a choice to use virtio if you want it, but I
don't see that option in Client Hyper-V. Are you using Hyper-V with vtnet
somehow? I have never used Windows Server Hyper-V, but I know if it offers
different options than the Hyper-V that comes with Windows Professional
Edition, some of which relate to networking. I tried adding the tunable anyway,
but it didn't do anything. Do you have a vtnet0 interface?

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