It completely depends how you have the VM configured in VBox. If the host NIC is passed to the VM then it would not have a connection using that and would need some other connection via the VM.

Steve

@thatsysadmin

we tested passthrough of the 10G NIC with almost the same results.

Bare metal on the same machine works fine.

I think this is an issue with esxi and pfsense. We see very high interrupts on pfsense during bandwidth testing on ESXI even if we passthrough the NIC.

@lostnil Have any update on your Proxmox throughput issue? Were you ever able to determine if you could route gigabit traffic through your pfSense VM?

I was able to disable it from the shell. Using

pfSsh.php playback disabledhcpd

My main issue is using my own DHCP server within VirtualBox to now assign an IP to the LAN interface

Hmm, higher throughput with higher MTU like that implies something in that local link it hitting a PPS limit. Mismatched MTU will cause horrible throughput issues generally.

But, yeah as mentioned, the first thing I would be doing here connecting something basic and baremetal to the connection to prove it can do 1Gbps. That really shouldn't be very demanding though.

Steve

@canaparo67 said in Hyper-v processor compatibility fatal trap 1:

amd epyc 7452 32-core

Don't know for sure, but could be an unanticipated condition running a 2013 OS on a 2020 processor. I, on the other hand, run that 2013 OS on a 2008 processor(Intel). LOL

Might need to bust out the credit card. Again.
No help, I know.
734f226f-9f1b-4de8-9db3-84e0a46dae3c-image.png
3cc19c57-739c-4fd7-98a5-13a8cc58ffac-image.png

Although the Redmine Ticket seems to show this fixed back in 2.5.1, your problem seems eerily similar to this one: https://redmine.pfsense.org/issues/11483. Might be something weird going on with the way Hyper-V is presenting the virtual disks ???

I hit this when I tried using ZFS as the file system with expanding disks. It went runaway and eventually caused an outage.

I've been meaning to go back and try again with a fixed size disk instead of an expanding one, but haven't got around to it yet, and EXT seems to be fine...

Hi,

all on the sameb subnet?
If so this should be problem of proxmox.
Even if u r not able to 'ping' from unifi controller to pfsense.
Are you?

Can the unifi controller reach out to the internet?

regards,

CAT

Hi Livio,

have you solved the issue in your case?
We are planing to go bare metal in our case.

I think I got it working! I couldn't access the Proxmox web interface anymore either no matter what I tried so I reinstalled Promox entirely. After reinstalling it still didn't work, so I tried again using another subnet in the network configuration during setup, and manually connecting my laptop to that subnet. After that I was able to access the Proxmox web interface again, so I continued following the steps like I did before. I was now able to connect to the pfSense interface too. I think the issue was with DHCP not working yet because the setup of pfSense in the web interface wasn't completed yet; the new subnet I used is the same subnet I used for pfSense (192.168.1.x), so that's probably why I was able to connect now.

For now I can't test any further until tomorrow because our switch is in my parents bedroom, and they're asleep now. I did test another laptop and that did immediately get an IP within the subnet, it also was able to connect to the internet.