OPNSense as Virtual Machine

[daven2411]

Is it possible to install OPNSense as a Virtual Machine running on a Windows 10 PC? Can someone send me a link on how to do it.

[Patrick M. Hausen]

If you can run Vagrant on your Windows PC you might want to try my project:
https://github.com/punktDe/vagrant-opnsense

You need to stick to Virtualbox 6.x at the moment. I need to update the network topology for Virtualbox 7. They actively removed features. *sigh*

[daven2411]

Thanks. I will investigate the possibility.

[bimmerdriver]

Is it possible to install OPNSense as a Virtual Machine running on a Windows 10 PC? Can someone send me a link on how to do it.

It runs on Hyper-V, so yes, it should be able to run on a PC running Windows 10 Pro.

[daven2411]

I've tried Hyper-V but I still cannot get into the GUI. Did you follow some instructions off the Internet.? Can you send me a link to follow.

[daven2411]

I can ping 8.8.8.8 but cannot ping any other devices on my LAN which is 192.168.1.0/24. Also, my gateway is 192.168.1.254 but most of the tutorials have the gateway as 192.168.1.1.
Should I be using .1 or .254?

[Patrick M. Hausen]

A factory new OPNsense has got 192.168.1.1 on its LAN interface and this is the DHCP server, gateway, and DNS server for all devices in that network.

If you already have an existing network using 192.168.1.0/24 and want to use that as the upstream (WAN) for your OPNsense, you need to change either that existing network or OPNsense's LAN. You cannot have the same network on two interfaces. OPNsense can be changed at the console, which should be easily accessible in a hypervisor environment.

[Supermule]

Use VmWare Player...

Much better support for drivers

https://www.vmware.com/dk/products/workstation-player/workstation-player-evaluation.html

[daven2411]

Does the WAN interface have to be a different network as well as the LAN?

[Supermule]

You need to isolate the WAN on the virtual machine so it cant get in touch with anything on the physical machine...

[Patrick M. Hausen]

Does the WAN interface have to be a different network as well as the LAN?

The WAN and the LAN have to be different from each other. For testing or whatever it is you want to do with your virtualised environment you can connect your WAN to your existing network and configure it to use DHCP (which is the default, anyway).

The LAN on OPNsense must be a different network. You can configure a host-only network in your hypervisor of choice, enable the DHCP server on OPNsense in that network, then tell your Windows PC to use that host-only network as its Internet uplink. Thereby connecting your Windows through the virtualised OPNsense to your existing network infrastructure and finally to the Internet.

Or create a second virtual machine running e.g. Windows, connect that to said host-only network, let that one access the Internet through the virtualised OPNsense ... it all depends on what you want to do.

Basic networking knowledge will be required.

If your idea is to run your PC in production through a virtualised OPNsense to add ... well, what exactly? ... that's probably possible but difficult.

My Vagrant project - just check the README on github - has got some hints on how to route traffic through the virtualised firewall for selected target addresses.

HTH,
Patrick

[daven2411]

The WAN is 192.168.1.2 which is the same as my internal LAN. The LAN is 192.168.10.100 which is specific to the VM. Screenshots below, if you wouldn't mind taking a look. I am using Hyper-V on Windows 10. Regards, Dave.

https://i.imgur.com/odMqgXR.png

https://i.imgur.com/ikPqUMf.png

https://i.imgur.com/P3kVMQ8.png

[jlab]

with out vlans to seperate the traffic OR a second nic, this is going to be hard.

[daven2411]

Even though I am installing it as a VM with virtual NIC's???

[Patrick M. Hausen]

You can run OPNsense with two virtual NICs. What exactly are you trying to do with it, then?