Pfsense 2.1 under hyper-b attached to a teamed NIC not working



  • All of my VM hosts have 4 nics, so two of them are teamed together using Microsoft's nic teaming to give the VMs a faster connection. and then the teamed interface is assigned to the VM as a single adapter.  This seems to work with everything except for pfsense.  When I have pfsense attached to a teamed nic, my throughput drops, and I can see the interface go up and down about every 3-5 minutes, which probably corresponds to when the traffic goes out the other NIC.  As soon as I remove all but one of the adapters from the team, it works perfectly.  I have tried enabling MAC spoofing and that doesn't work, and it's not the actual NICs because no matter which of the three remaining nics are assigned, it does the same thing.



  • What pfSense build are you using? The official build with legacy deX drivers or the custom build with synthetic hnX drivers?

    In my experience when using legacy drivers, Linux and pfSense won't function if you have teamed adapters with VMQ or VMDq or other acceleration technologies enabled. For this environments, I ended up having to setup a team and virtual switch for legacy VMs (ie, a team of 2 for Windows VMs, and a single adapter or a team of 2 for Linux VMs).

    In my environment, the synthetic drivers build works ok with teams based on Intel and Broadcom native teams. I haven't tried with Windows Server 2012 teams.

    See http://forum.pfsense.org/index.php/topic,56565.msg362435.html#msg362435 for a synthethic driver build (and there are other variations).



  • @zootie:

    What pfSense build are you using? The official build with legacy deX drivers or the custom build with synthetic hnX drivers?

    In my experience when using legacy drivers, Linux and pfSense won't function if you have teamed adapters with VMQ or VMDq or other acceleration technologies enabled. For this environments, I ended up having to setup a team and virtual switch for legacy VMs (ie, a team of 2 for Windows VMs, and a single adapter or a team of 2 for Linux VMs).

    In my environment, the synthetic drivers build works ok with teams based on Intel and Broadcom native teams. I haven't tried with Windows Server 2012 teams.

    See http://forum.pfsense.org/index.php/topic,56565.msg362435.html#msg362435 for a synthethic driver build (and there are other variations).

    I believe I have the synthetic build version, I have it assigned native hyper-v NICs and it's working great.  I tried disabling all the performance tweaks and it still has the same issue.