From owner-freebsd-bugs@freebsd.org  Fri Oct 16 08:03:15 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 51DD0A165A5
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Fri, 16 Oct 2015 08:03:15 +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 3D3D117DE
 for <freebsd-bugs@FreeBSD.org>; Fri, 16 Oct 2015 08:03:15 +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 t9G83FIO082949
 for <freebsd-bugs@FreeBSD.org>; Fri, 16 Oct 2015 08:03:15 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: Fri, 16 Oct 2015 08:03:15 +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: weh@microsoft.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-QCeuXOhbsT@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: Fri, 16 Oct 2015 08:03:15 -0000

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

--- Comment #9 from Wei Hu <weh@microsoft.com> ---
(In reply to Eddy from comment #8)

> This is what I did:
>
> - Create a clean new VM with FreeBSD 10.2 on the Hyper-V server.
> - Activated IP forwarding: sysctl net.inet.ip.forarding=1
> - On another computer (same LAN, running Windows 10): set the default gateway to the new FreeBSD test VM. Ping/tracert to the internet work. TCP doesn't work.

In above setting, how can pinging from Windows 10 machine to internet work? The
machine in the internet doesn't have routing knowledge to send the packet back
to Windows 10 client which is inside LAN. 

Are you using NAT on the FreeBSD 10.2 server? When I enabled the NAT,
everything seems working in on 10.2 as a gateway. 

So overall, I think the r285236 is the cause of the problem. However, since I
still cannot reproduce and r285236 is a big change, I cannot narrow down to
smaller part for sure. 

We come up with a suspecting code path. Attached is another patch which you can
test for us. Please apply this directly on clean 10.2 code (not on the patch I
attached earlier.) This new patch just disabled the checksum offloading. See if
this one can help solve the issue you are seeing.

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