On Thu, Oct 29, 2015 at 10:45 PM, Larry Baird <l...@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 _______________________________________________ email@example.com mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"