@keitetran The reason you would like different lans could be policies.
Binding them all together at the esxi level (in software) could work, but again why?

Hi awebster,

you're right, i have solved my issue. the origin of my problem is in igbn driver. with the vmlinux driver "igb" all is fine.

you can find all details here : https://communities.vmware.com/message/2905942#2905942

thanks for your reply

Ah, OK. That is certainly possible. I was confused by the discussion of 'teaming' which is not what you want at all.

You have two choices here:

Pass though 3 three NIC to pfSense and bridge them. That will give your the behaviour you want but as (I now see) you initially said it's a very inefficient way of creating a switch. Bridging can be awkward in pfSense. Create a vswitch in hyper-v and connect all 3 to it. It's still doing it in software which is not as good as a real switch but at least it's trying to be a switch rather than a bridge. That also simplifies the pfSense config significantly that would then only have a single LAN interface internally connected to the vswitch.

Steve

It was working for two days.
After i woke up, no internet...
I had to restart pfSense and had a new public IP and it was working again.

I217 is always unidentified...

Nobody here has pfSense running in Hyper-V on Windows 10?

That's odd. i350 is very widely used. Unless it was one of the many fake Intel cards that are about...

@Riano-desouza did that work for you?

thank you so much =)

Thank you very much! Im starting right away! Thanks @provels !

seems the problem was the cpu configuration as soon as i change from "copy host CPU configuration" to westmere the pfsense vm booted.

not sure what this setting entails thou ill have to search for it see if can learn about it

thanks @kiokoman your parameters helped me

@bmeeks

I will take a look at the links later - thanks.

As for a backup config.xml - this was a clean HA install, so the config should also be clean, however I have resolved the proxying issue, the ports being blocked I believe is more firewall related since I cannot connect to those IPs internally either, which do not go through the proxy, but will go to PfSense as a gateway.

I appreciate the help, but I think for the most part I have moved on from this for now, my only real issue is one I can bear with for now since I have used different IPs.

I thought AES-NI was going to be required from pfSense 2.5 onwards? At least it doesn't seem to be discouraged...

I confirmed my LiveCD findings, however, by disabling cryptodev in the "Advanced" section of the KVM virtualized pfSense instance, leaving only AES-NI. OpenSSL runs at host-comparable speeds now. Use of the cryptodev module is what makes it slow.

Deleting your original question and not stating how you fixed it wont help anyone else facing the same issue.

@mrbankheadgmail-com

I know this topic is quite old, but I'm experiencing the same thing on multiple proxmox hosts and pfSense. Did you ever find a solution?