Date: Thu, 29 Oct 2015 23:10:38 -0500 From: Adam Vande More <amvandemore@gmail.com> To: Larry Baird <lab@gta.com> Cc: FreeBSD virtualization <freebsd-virtualization@freebsd.org> Subject: Re: Issues gatewaying through Hyper-V Message-ID: <CA%2BtpaK2VxH3f_Mp5otRtHMJp2pQAiwiFACP2EDmmrLBA_hb6pQ@mail.gmail.com> In-Reply-To: <20151030034535.GA19514@gta.com> References: <20151030034535.GA19514@gta.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK2VxH3f_Mp5otRtHMJp2pQAiwiFACP2EDmmrLBA_hb6pQ>