Alex Ruben
How To Configure pfSense WAN and LAN Interfaces on Proxmox – Part 4
Setting up pfSense inside Proxmox can be a little tricky if you’re not familiar with the quirks, but it’s doable. One thing that trips people up is making sure the interfaces are correctly assigned and configured with static IPs, especially since Proxmox’s network bridge setup can be weird sometimes. Here’s what’s generally worked for those who’ve struggled with this. Not perfect, but hopefully it saves some head-scratching.
Prerequisites
Before jumping into configs, make sure:
- Proxmox VE is installed and awake.
- pfSense VM is spun up in Proxmox, with at least two network interfaces assigned.
- Some basic networking smarts—like knowing what an IP address or subnet mask is, and how virtual networks tend to behave.
Step 1: Access the pfSense Installer & Initial Wizard
After powering up pfSense, you’ll see the first setup screen. It prompts for network basics. Here’s where you tell pfSense which interfaces are WAN and LAN.
- When asked about VLANs, just pick N unless you want VLANs—most setups don’t need ’em right away.
- For the WAN interface, type in
vt0(assuming Proxmox assigned it as such). Hit Enter. - For LAN, input
vt1. Hit Enter. - Confirm your choices with Y, then hit Enter.
Note: If your interfaces are named differently—like enp3s0 or eth0—you’ve gotta replace vt0 and vt1 with whatever br0 or your actual interface is called. Check by running ifconfig at the console if you’re unsure.
Step 2: Assign Static WAN IP
Why bother with static? Because DHCP inside Proxmox, especially on virtual interfaces, sometimes acts flaky or assigns different IPs after reboot, which confuses pfSense and other devices. Setting a static IP helps keep everything predictable.
- In the pfSense menu, pick 2 to go to Interface assignments.
- Choose 1 for WAN.
- When asked about IPv4 configuration Type, select N for No to skip DHCP, or choose DHCP if you want dynamic. If static, then proceed:
- At the IP address prompt, type your desired static IP, like
192.168.100.2or whatever fits your network. - Set subnet bits to
24(which is 255.255.255.0). Usually, just hit Enter to confirm default. - Next, input your gateway—probably the main router, e.g.,
192.168.100.1. - Disabling IPv6 can help avoid confusing routing issues if those aren’t set up yet. Just say N.
- Finish by confirming the settings. Sometimes, after rebooting, the interface might not be reachable immediately—rebooting pfSense or the VM can help clear things up if that happens.
Step 3: Set Up LAN with a Static IP & DHCP
LAN should be internal and stable. Here’s what usually works:
- Back in Interface assignment, pick 2 again, then choose the LAN interface.
- Assign a static IP like
10.10.10.1. Think of this as your LAN gateway. - Set subnet to
24again (255.255.255.0). - Leave the default gateway blank, since this is the internal network.
- Enable DHCP server on LAN (so your devices get IPs automatically). Confirm starting IP
10.10.10.10and ending at10.10.10.254. That’s a common range for home setups. - Save and apply your settings.
Pro tip: If DHCP refuses to work or you can’t reach the web interface after changes, check if your VM network settings or Proxmox bridge are correctly configured—sometimes the VM’s virtual NICs are not connected or don’t match the assigned bridge.
Extra Tips & Common Pitfalls
- Doubled check your IPs—conflicting addresses are a pain in the ass.
- If pfSense can’t reach the internet after setup, verify your Proxmox network bridge settings—are you bridging the correct interfaces? Is the physical NIC plugged in?
- Document your commands and configs—pro tip for troubleshooting later. Sometimes that typo or missed step causes days of confusion.
Sometimes Things Just Don’t Play Nice
For some setups, plugging the VM into the wrong network bridge causes no connectivity. Or the VM might pick up a different interface name than you expect, so running ifconfig from the pfSense console helps trace what’s going on. Also, Proxmox’s network model sometimes resets after a host reboot, so double-check you’re on the right bridge.
Summary
- Assign interfaces correctly at initial setup—vt0 and vt1 are common placeholders.
- Set static IPs on the WAN side, use DHCP on LAN for comfort.
- Adjust Proxmox bridge configs if the VM refuses to route or connects weirdly.
- Keep backups of your configs—because of course, Windows has to make it harder than necessary.
Hopefully this shaves off a few hours for someone. If this gets one update moving, mission accomplished. Just something that worked on multiple machines.