Proxmox All-in-One

pfSense

• Install pfSense (a link)
  • Set up a second network bridge internally (& give it a secondary physical NIC if you have one)
  • Build the pfSense VM
    • 8GB drive, 4 cores, 4096MB RAM
    • Add a second network device (on the second bridge... duh...)
  • Do a BACKUP
  • Open the VM console & pretend you're building a normal pfSense router
  • Once the VM is booted into pfSense...
  • Do a BACKUP
  • Then move on to:

Management VM

• Pick your favourite OS & build a VM (Or... Ya know... Since ya gave that second network bridge a physical NIC (Ya did, right?)... You could just plug a computer in there.)
  • Point its network device at the second network bridge
  • Sign into https://192.168.1.1 (from the Management VM)
  • Go into Services / DHCP Server / LAN
    • Under Servers, add in your DNS server(s) address(es)
  • Restart networking on the Management VM
  • Feed access to this VM through the pfSense firewall
• & continue messing with pfSense
  • Do a BACKUP

Taking it LIVE

Here's where things get a bit fugly...

Up to this point, your server works fine on an internal network. Unfortunately, as far as the world outside the box is concerned, there are 2 machines there. The Proxmox install AND a pfSense install. They both show up on the network.

So...

Let's fix that.

1. Swap all of the network connections on all existing VMs
   • Go into the Hardware tab for each VM...
   • edit any Network Device(s) they have configured...
   • basically, swap them to the opposite Bridge (vmbr) from what they currently use.
2. SSH into Proxmox & change vmbr0 back to static
   • Give it the IP address your pfSense VM should be assigning it & the IP of the pfSense VM as its gateway.
   • It'd be a good idea to edit /etc/hosts to match the new address.
3. Switch the physical network cables.
   • If NIC #1 is currently plugged into your network, swap it for NIC #2 (or whichever NIC you set your second bridge up to use...)
4. Reboot the machine.