Messages

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, 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.

This is based on FreeBSD, not Linux. But why do you not install the tools?

For newer FreeBSD releases, BIS is built in to the FreeBSD operating system, and no separate download or installation is required except for a KVP ports download that is needed for FreeBSD 10.0.

Latest pfSense is 10.1, OPNsesne 10.2 - why would I bother installing something?

You have one physical NIC which you use as a uplink for a VMswitch.
There is no way to have a VMswitch with two virtual networks unless you use VLANs.
I doubt pfsense can do what you describe. It just doesn't make any sense based on what you describe.

Would you clarify this statement? Because my setup is working right now with pfSense.

I don't install Integration Tools on linux machines and I don't use VLANs.

Btw, I have reinstalled OPNsense and on initial config it says that my network adapters are Synthetic, but I can't make port forwarding to work. I want to publish DNS server on VM with Windows Server 2012 R2 - no success. Looks like I will fallback to pfSense :{

I'm on Server 2012 R2 Datacenter. I do not install Integration Tools on VMs.

- Barebone with 1 NIC connected to ISP (static IP + 1 Failover IP on different subnet);
- vSwitch has two virtual networks: External (WAN) (connected to NIC, shared with management OS) and Internal (LAN);
- VM has both virtual networks, MAC address spoofing is enabled on LAN.

[ifconfig]

WEB UI doesn't show link speed for network adapter, neither do ifconfig (no media info).
I've checked pfSense - with legacy adapter it will show 100TX, for non-legacy show no link speed (like OPNsense).

Keep in mind that 16.1 will most likely not work on Hyper-V 2012 R2.

I don't get you. Mine is almost working, except port forwarding (haven't configured rules yet).

How do I ensure my network adapters are synthetic?

Opps, I was wrong - you can use non-legacy network adapter on gen1.

There is a tweet on OPNsense (https://twitter.com/opnsense/status/569396467636576256) with link to post on Reddit:

So I read about monowall recommending OPNsense and decided to give it a try - after installing (without reading much ahead) I realised it supports the Hyper-V network interfaces by default.

Man says that OPNsense supports Synthetic Network Adapters. You need to run a gen2 VM to use them.

How do i boot OPNsense 16.1 on Hyper-V VM Generation 2?
I'm getting error "Boot Failed. No Operating System was Loaded."