OPNsense on Hyper-V

[weust]

@DirtySpiv, Because FreeBSD can make use of options offered by the Integration Tools.
Maybe you don't need all of them, but for automation they can come in handy. Like the save state/pause/shutdown of the VM when shutting down the host server.
FreeBSD may have support for some virtual hardware offered by Hyper-V, but the Hyper-V cannot control the VM.

The Hyper-V VMSwitch is a Layer 2 switch. You cannot create multiple VMSwitches using the same physical (or teamed) network adapter. You even get a message saying you can't because the adapter is already bound to another VMSwitch.
So if you want to use multiple networks you would need to setup VLANs on your physical switch, and use VLAN tagging on the vNIC or inside the guest OS to be able to work with multiple networks.

If you did something else, you're not explaining it well.

[DirtySpiv]

franco, there are no issues on FreeBSD 10.1/pfSense, but with FreeBSD 10.2/OPNsense port forwarding is not working and my routing table being reset after any config change from the web UI (i'm setting upstream gateway for wan interface manually).

weust, this functionality comes with FreeBSD from the box, you don't need to install additional software, except KVP daemon, as stated on FreeBSD wiki. So I can control my VM from hypervisor.

You cannot create multiple VMSwitches using the same physical (or teamed) network adapter. You even get a message saying you can't because the adapter is already bound to another VMSwitch.
So if you want to use multiple networks you would need to setup VLANs on your physical switch, and use VLAN tagging on the vNIC or inside the guest OS to be able to work with multiple networks.

Are you talking about two External virtual switches binded to the same NIC? I have only one External, and one Internal, and can create as many Internal virtual switches as I want. There is some misunderstanding between us. Keep in mind that I'm not a nix guru or professional sysadmin. I can provide screenshot of my setup, just say what you are actually interested in.

[weust]

Internal and Private VMSwitches are fine. Now I get you.
Though that means you can only use VM's on the same Hyper-V host to connect to and through the OPNsense VM for internet connectivity.

I never disable the Integration Tools, and when I forget to enable some options upon enabling them the console will detect them.
I will check the wiki page later.

[DirtySpiv]

Though that means you can only use VM's on the same Hyper-V host to connect to and through the OPNsense VM for internet connectivity.

It depends how much additional IPs do you have. If you have enough - just bind them on guest OS network interface and expose it to internet without routing.

[franco]

franco, there are no issues on FreeBSD 10.1/pfSense, but with FreeBSD 10.2/OPNsense port forwarding is not working and my routing table being reset after any config change from the web UI (i'm setting upstream gateway for wan interface manually).

That may be the issue that weust is having in a different wrapping. We've had no such issues in 15.7 with 10.1, 10-STABLE works again according to weust.

When you install 15.7.18 (images are still up on the mirrors), one can safely upgrade to 15.7.25 with one update. It should be relatively easy to verify this with a snapshot + ISO installer config import/quick install if you find the time.

Meanwhile, we are working on pinning down with patch is missing here on 10.2.

[Hektor]

Just a short info:

I updated to 16.1 via opnsense-update. Besides it didn't boot anymore because I did set up the VM with /dev/ada and changing it to /dev/da... (thanks to weust for confirming my change) -> network is dead here, too. See here for details:
https://forum.opnsense.org/index.php?topic=2114.0

I'm running Hyper-V Server 2012 R2 (free edition) on a HP ProLiant ML370 G5. I didn't install integration services manually.

So it seems to be a general issue when using Hyper-V Server 2012 R2.