NOTE: You probably just want to skip this and get the PfSense VMware Appliance.
Contents |
While running under VMware can be less secure than running on a physical machine, for home use or testing in particular it can be a good way of running pfSense that avoids the need to have yet another PC powered on all the time.
If you are going to do this, it is better not to have pfSense (and its host machine) directly exposed to the internet - it is better to have it behind a router or a simple firewall (or even just a NATing modem).
This way of running pfSense also allows you to run other VMs that are directly connected to the modem / router if you want to do this. I use this approach to upgrade pfSense by cloning the current version and then upgrading it. You can then quickly and easily run the upgraded version or the original version by just shutting down 1 VM and starting up the other.
This diagram outlines the setup that this page will describe. The first connection (right hand one on the diagram) is the main network connection, and the host machine uses this for communication with other computers on the internal network. Windows will have an IP address and other services enabled (such as file sharing) that you use to access the host machine as a standard windows computer.
The next connection (middle on the diagram) is the connection to your router / modem to the internet. This connection should be disconnected from all normal windows services (including TCP/IP). It should physically be connected only to your router / modem.
The final connection (left of the diagram) is for a second router / modem. If you only have 1 internet connection you don't need this, alternatively if you have more than 2 you can add further connections here. (Being able to properly share and easily setup 2 internet connections was why I first started using pfSense)
The first connection is the host computer's connection to the internal network. It is configured with the normal windows services you need to use and with VMWare bridge protocol. This will normally have been set up by installing VMWare. This figure shows the settings on my host computer.
The second connection is used to connect only to internet router / modem. In windows it is only connected to VMware bridge protocol and all other (windows) services are disabled on this interface. I'm not sure how good windows is at this area, but it should stop anyone being able to get at the host machine via this network connection.
If (like me) you have 2 separate internet connections, then you will want one more physical network connection. This will connect only to your second internet router / modem. As for the first internet connection, this is connected only to VMware bridge protocol. Use the same settings as the section above.
In the Host Virtual Network Mapping tab (accessed from VMware Server Console, Host - Virtual Network Settings), you need to set up further VMware networks, one for each Internet connection. Don't change the VMware networks already set up, add the new one(s) you require starting at VMnet2. Use the drop down list at the right hand side to allocate the VMware networks to physical network connections.
Once you are done, it should like something like this (There are two additional connections here, one for each Internet ADSL line.
Now that the network connections are setup, it's time to create the new VM.
Your Virtual Machine settings should now look something like this.... Before you start the VM, you can tweak the settings to make it run better under VMWare. You can't do this through the GUI, but the setup here: [1] shows how to do this. It is better to do this before you build the VM, if you do it later you have to re-setup the interface assignments.
Point the CD-ROM at the ISO image of pfSense. Your VM is now ready to build.... Start up the VM and use these Installing_pfSense.
Ignore the first parts about BIOS setup etc. Now you can carry on. Use the setup guide most appropriate to you.