I solved the issue "the easy way". I went into Proxmox and changed VMBR0 bridge from old interface NIC to new interface NIC instead of having a new bridge along with setting back the IP and gateway. And subsequently I changed the same in PfSense back to use the old NIC. As it works and I'm no network genius, I'll leave it be for now :)

[image: 1616701082973-netdiag-page-1.jpg]

EDIT: just change some DNS Resolver settings, like the outgoing network interfaces (selected only WAN), disable DNSSEC, enabling Forwarding Mode and also disable IPv6 on WAN and LAN on the interfaces setting and now it's working!

@ikifar If E1000 works what is the issue with that. Check the throughput using iPerf and speed test to ensure it works as expected. If you don’t see any performance drop happy days.

@KOM I appreciate the insight. I think that will be my backup plan. I realized my office computer has a wifi adapter. I never used it. I'm thinking I will connect it to my current Netgear router so that network is not taken down. I'll connect my ethernet to Pfsense. I found a program called ForceBindIP, which I'm thinking could force Firefox to use the ethernet adapter, so I can configure PFsense in the web gui. I have to make sure the WAF is stable...

@limez17 yes [image: 1614181710607-easy-tek.png] that's the setup the problem is that in aws you can't add specific routes so my next guess is to portforward in the dmz are websites and rdp is a must for admin emp dev network thx for the help

It seems this could be an ISP issue now, I am still troubleshooting, changed nothing and am now getting around 850 mbps https://twitter.com/MathesonStep/status/1362429291838001154

@raitd said in vmx NIC ordering for pfSense on vSphere 5.5+: @jimp I've seen many linux distro's handle having several nics in vmware and handle adding more perfectly fine. Linux is vastly different in their default naming schemes. The current default names in Linux are based on bus locations which likely wouldn't change in those cases. FreeBSD counts up from 0 for each instance of the driver it finds when probing, so if the probe order changes, so does the NIC assignment order. Does pfSense / FreeBSD have an option where you can force binding to a particular MAC address? If so I imagine many people would love to have this as a selectable option. No.

@bullz3y3 Have same issue in 2021, and fixed by changing the Network Type from Virtio to e1000 also. Your finding in 2015 is still helping others. Thanks. My case is having a PCI Passthrough WAN, and 2 bridge LAN, hosted on KVM on debian 10

@talaverde the only thing that is actually of interest to me is whether a solution is within reach / uncomplicated nearness. Therefore I think it is unnecessary to open an extra thread ...

Hi, I decide to do a clean install of 2.5.0 RC on my backup firewall. Everything is vanilla, and same problem appear. I was thinking maybe this was only an VMware/pfSense bug. [image: 1613161047780-image001-1.jpg] After RESET LOG FILES under Status - System logs [image: 1613160796184-image001.jpg]

@thejaguar I already figured it out... working now with no problems. You only need to change to static ip every time you connect to mngt port.

@teamits Oh man I completely missed that! I'll submit something now. Thanks!

@robca402 If anyone ever see this, my problem was that I needed to toggle the AES CPU flag on in proxmox

@oiyae How has it been going since? How did you get them to offer up a SH4 by the way, the people you usually speak to are non-=technical and quite often refuse

@maverickws have you checked iperf3 speeds between pfsense and xcp-ng itself? Mine is bad. Additionally from pfsense to xcp-ng it has many retries during transfer