Date: Wed, 14 Oct 2015 16:49:41 +0000 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 Message-ID: <bug-203630-8-zPkDyT4QDd@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/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203630 --- Comment #8 from Eddy <onyx@netfusion.fr> --- Everything seems to work with the patch. 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. - Patch netvsc with the r285236 file you provided, in the /usr/src/sys/dev/hyperv/netvsc/ folder (patch -i r285236) - Rebuild and install the kernel, then reboot. - TCP works from the LAN machines. Thanks Wei! Please note that I couldn't test it in a PPTP or NAT configuration. Now I wait for the patch to be included in the next FreeBSD update (since I usually don't build custom kernel). -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-203630-8-zPkDyT4QDd>