Proxmox and pfSense

[allanl]

I have Proxmox 8.3 installed on a Dell server. One of the vm's is pfSense 2.7.2 which works well. The problem is that everytime I reboot the pfSense vm it needs to be reconfigured to use the two physical NICs in the server, one for the WAN and the other, LAN.

It keeps asking if I want to configure the VLANs, which I don't have. I have just removed the VPN configurations in pfSense but it doesn't make any difference.

On the pve network tab it shows two NIC and four eno network devices, two of which are active and autostart. I don't want to delete or change them since the system may not restart.

How can I lock the two network ID's to the WAN and LAN and ignore all of the other WAN options that are available, or pfSense shows that there are, but aren't?

This app used to run on vmWare without any issues on reboot. Now the reboots are an ongoing problem.

Thanks.

 

[DBS]

Can you please share some screenshots?
Another question (for my knowledge) did you install the pfsense software and configure it afterwards on the console?
The final configuration then is done in the web GUI.

regards,
Ronald

 

[allanl]

The initial installation of pfSense is via the DOS console and then work done in the GUI. The problem is that on reboot, it will not use the VTNET 0 and 1 without stating that no virtual lans are to be configurated and then it asks for an assignment for 0 and 1.

In the event of a random reboot, access to the LAN remotely will be blocked, since although Proxmox will come back to life, without pfSense working there won't be any access!

 

[DBS]

Hi Allanl,

Please correct me if I'm wrong but it seems that the initial configuration is not finished.

first, install pfsense
Complete configuration in the Terminal console (DOS box)
This means, configure the LAN and WAN network choices and skip the vlan questions, then you wil end up with something like this:



After this your initial config is saved and you have to configure the rest of your setup in the pfsense web GUI

And for this question the answer is n(o)



Regards,
Ronald

 

[allanl]

DBS, all this was done bypassing configuring VLANs and just the two NICs in the machine. The problem is that everytime the pfSense is rebooted it asks the same questions and forces manual entry. So a power failure or other problem will force a manual configuration.

In other words, the configuration (file?) is not saved so it's a "new" installation at every reboot.

When is was running under ESXi, never a problem.

 

[mugopain]

I just ran into the same problem yesterday.. I had migrated/restored my pfsense from vmware to proxmox. The problem was after migration, in the pfsense vm settings, i assigned virtio nics and removed the vmxnics. I fixed it by answering all the questions about assigning the vtnet interfaces, but skipped the VLAN questions. After that i logged in thru the Web GUI. went to interfaces and VLANs and found that it had kept my vmx nics assigned to VLANs there. So i deleted all the Vlans and then set the Vlans back up using vtnet nics. Did a reboot and it worked.

 

[DBS]

Hi mugopain, that should do the trick!

@allanl, I run 2 pfsense VM's in production and 1 in a test proxmox environment without a problem ( for a couple of years.)

Maybe the solution from mugopain will work for you as well?

Regards,
Ronald

 

[DBS]

If it really won't work I can provide you with a clean installed pfsense VM which you can configure yourself?

Regards,
Ronald

 

[allanl]

I finally fixed it. I installed a NEW pfSense 2.7.2 program under Proxmox and had the same Vlan problem. When I examined the configuration under the web interface, I found that two Vlans were actually set up! I deleted both Vlans and rebooted. It worked! I have no idea where Camera and Guest came from, since they were also installed on a new install. Perhaps PfSense, although no problem on ESXi. Thanks for everyone's help.