What's new

pfsense in a VM?

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

hyelton

Senior Member
Is it a good idea to run pfsense in a VM? and just dedicate 2 network cards to the VM? I have a small server an older custom build Core 2 Duo which is only mostly used as a file server. Could I install pfsense in a VM and it run good? Or is it just recommend to use dedicated hardware? I have another computer to use but its a lower end AMD from 2008
 
Yes,
Is it a good idea to run pfsense in a VM? and just dedicate 2 network cards to the VM? I have a small server an older custom build Core 2 Duo which is only mostly used as a file server. Could I install pfsense in a VM and it run good? Or is it just recommend to use dedicated hardware? I have another computer to use but its a lower end AMD from 2008

Yes, you definitely can. I am running it in an ESXi-hosted vm anyway.
But with the hardware you laid out there, I have some question marks. You should use an energy efficient config, the electric bill can be big if you use a desktop class setup. I haven't heard of any 2008-era AMD cpu that's energy efficient.
Also, assuming you'd want to use OpenVPN, you should look at one of the AES-NI capable processors - Avoton, Rangeley, Pentium N3700 - for hw accelerated encryption.
 
General guidance from experienced pfSense folks is not to run in a VM, basically due to security issues in the host platform - while pfSense is very secure, all of the hypervisors out there are under intense scrutiny right now by various security "researchers"...
 
General guidance from experienced pfSense folks is not to run in a VM, basically due to security issues in the host platform - while pfSense is very secure, all of the hypervisors out there are under intense scrutiny right now by various security "researchers"...

The virtual WAN NIC is the only one exposed to the internet. The traffic through it is obviously inspected by pfSense. The ESXi management NIC only has a private static IP and it's definitely separate from the virtual LAN NIC that serves the internal network. There's no direct link between ESXi and internet. I fail to see how security could be compromised here. The only port opened to the world is OpenVPN.

Forgot to mention that the mainboard I'm using has 4 gigabit NICs, which makes it easy to allocate one for each purpose.
 
Last edited:
some VMs can dedicate a physical component to a VM so if you were using VMware and running pfsense you could give the physical NICs to the OS and save 1 NIC for managing the VM. To do this you should at least get yourself a quad port server NIC and use onboard to manage the VM and the entire card to pfsense.
 
Those are just words of wisdom from the pfSense forum hivemind - obviously they're more experienced with this question and potential issues than many here...
 
I always allocated a physical NIC per VM when using Microsoft's VM. I think if I ran pfsense in a VM I would allocate 2 physical NICs for a VM with pfsense. NICs are cheap.
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top