Hello @MikeFromOz, Indeed, I went to Orange with the Max 2 Gbps/800 Mbps offer, which is extremely stable, in my area anyway. I use the 2.5 Gbps port of the Livebox 6 with pfSense to benefit from the 2 Gbps, even if I have a ready installation with an ONU SFP GPON 2.5 Gbps module because I sometimes had problems with the link re-establishing during a physical disconnection test. I totally agree that Free's hardware is very good and much more "flexible".

@Khoomn Proxomx management port needs to be connected to your lan. If you are using pass through for the pfsense NIC that will need to be done by connecting a third NIC on your Proxmox box to your physical network switch. If you are connecting the pfsense VM to virtual NICs then you will be connecting each virtual NIC to a bridge (software switch) in Proxmox. You can then connect your Proxmox management interface to the LAN virtual switch (define an IP address for it in the Proxmox network tab)

@yobyot said in Do you have performance tips for Proxmox virtualized pfSense?: Actually, no. pfSense was running on an external Vault. When I migrated it to Proxmox, I put it on vmbr1. I haven't found a way to renumber the bridges so that it "looks" right and now I kinda like it. Well, if it works for you, hooray...I just shared what the pfSense document says...like I installed using UEFI for pfSense on Proxmox, as well as, install Proxmox on ZFS.

I waited for 2.7.0 but the issue remains there. That's very, very bad. Seems to be an issue with underlying FreeBSD as this is recognized there too, also in OPNSense. Irritating is for me the fact that there are different amounts of LAN interfaces causing this issue. Clean booting a newer pfSense image hits the same issue...

@NollipfSense Thanks for the reply. Ifconfig doesn't have a setting for FEC, but fortunately I found the solution by using the intel driver specifically for the E823-L which offers a wide range of tunable parameters. Unfortunately that driver doesn't compile correctly using the the latest FreeBSD 14.0 CURRENT release and the RELEASE version has been delayed. So it looks like I'm stuck on pfSense 2.6 until I can compile a driver for the latest update.

@Patch said in Some packages fail to start after issuing "reboot VM" command on Proxmox: Try it. When watching the process on the Proxmox console for pfsense it proceeds cleanly. I actually did, a boot up though using Proxmox...just can't see myself doing a shutdown.

@viragomann I didnt change anything, its set to VMX3, not e1000

@jacky said in Proxmox hosted pfSense Netgate Device ID changes on reboot: The changes on the MAC address on this USB NIC is the cause of the changes of the NDI. Interesting, indeed; that will do it....

@digdug3 Thank you, your suggestion still works. link text

@andrew_241 I thought you would be using esxi or something. I like Hyper-V better as it's native in Windows and works really good now.

Unfortunately I have zero control over the hypervisor… I’ll ask the hoster

@provels Thanks I'll give that a try. I think what im going to do first is make a new backup of the physical box tested with that isnt using PFSense Plus and try to restore that config to the VM first to see what happens. If that doesn't work I'll do as you suggested.

@NollipfSense that's why it works correctly, it disables it automatically (although it's always good to disable it ALSO manually) Thank you very much

@Richard-1 said in No DHCP on proxmox: On my Win11 VM I receive ip configuration from DHCP server, on my physical PC no DHCP configuration received, I need to enter ip, subnetmask, gateway, ... manually to connect to network. It's the way you have it setup...please see here: https://docs.netgate.com/pfsense/en/latest/recipes/virtualize-proxmox-ve.html Did you connect your physical PC to pfSense LAN? Nothing is wrong to connect manually though. You should consider amending your title as Proxmox doesn't do DHCP.