That's what it looks like to me.

I'll go ahead an answer my own question here: the issue was apparently driver related. On my third time installing pfSense, I manually uninstalled and reinstalled an updated version of the Intel PRO/1000 PT driver. After that, it worked without any issues exactly how I wanted it to. I'm not sure why that would be the case as even the updated driver was only slightly newer, but either way it works and is invisible to the host OS, which is all I need. I'm getting full gigabit speeds both ways with only 2ms more latency than I had before. I'm running Snort.

@raqib But it is not helping in every case, I had problems on Server 2022 and this only helped some of the time. What "helped" me all of the time was using two separate, external vSwitches, one only for pfSense and one for all the other VMs. And that meant there had to be a physical switch in place to connect those two vSwitches. Thankfully it is working in the latest Plus-version.

@bob-dig Vodafone gigafiber it works find on dedicated box

@stephenw10 Thanks, will check. as of now no issues with Ubuntu after setting up static DNS and IP.

OK ! What a nice feature XD Many thanks for your reply

I'm having this same problem in ESXi 6.5 with standard vSwitches. Same Duplex issues two different VMware clusters. Seeing it in the cisco logs because LLDP/CDP is turned on. CARP seems to work just fine for me after enabling promiscuous mode in the vSwitch. PFSense 2.6.0. Intel 82599 NIC. I can see this in the logs on our Cisco 6509 and Nexus 5K switches depending which hypervisor is running the VM. 6509s connect to the hypervisors with a standard LACP port channel, the Nexus switches are a vPC LACP bond. I also do not have any other gear throwing these errors. I can see this issue on both stand alone and clustered PFSense VMs.

Not to a VM. Not yet. However I tested the upgrade process over the weekend and it completed no problem so I would expect a clean install of 2.6 then upgrade to 22.01 and then 22.05 to work fine. Steve

Adding new hardware devices to the VM, such as NICs, will likely change the NDI and hence the subscription. Cores or RAM should not. I suggest adding as many NICs as you might need before you start. You can always simply leave them disabled in pfSense or even disconnected in Proxmox. Steve

Ah, so more like a full AWS/Azure setup. That seems...complex!

@patch https://www.youtube.com/watch?v=3l0AySgYlkg&t=380s

@michelvdriel https://www.youtube.com/watch?v=3l0AySgYlkg&t=380s

What is 192.168.100.7? What IP are you pinging from? Which adapter is that subnet on? I recommend not using Net networks in VBox unless you have no choice, it makes everything much more complex. Steve

Yeah, this issue is the same. I was trying in my OpenStack Queen and Train, but still like pfSense having a bottleneck in hypervisor KVM. I don't know why. Someone say 'https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165059#c24' Maybe you can try from this ref https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165059

@viragomann For now, I will leave it at 2GB. I have a new SFF box coming which has 32GB of RAM. Plans are to move all of this over there, and put a few more VMs on it. The box that I am currently using has 16GB RAM and 2 VMs (this one now at 2GB and the other at 8GB). I may need to increase the RAM as I install packages and re-setup CloudFlare DDNS on here. I appreciate your and @Patch input.