Hyper-V (2012 R2) and pfSense = network trouble



  • Hi All

    I've been using pfSense on Hyper-V for a while now. Using legacy network adapters of course since the hyper-v specific ones don't pick up in pfSense.

    The issue I am having is my interfaces will not come up automatically on boot. It appears that the LAN interface (static IP, dhcp server) is the one that's impacted by this. The WAN interface (static IP) does not appear to suffer this issue.

    Is there going to be a solution for this? So far the solution I am using is to set up a autorun script that will automatically run ifconfig de1 down && ifconfig de1 up every boot.



  • Can you please post your system logs.
    The interfaces are brought up on boot when being configured so this should not be an issue.
    As you say yourself the WAN interfaces comes up automagically and there is no difference for LAN.



  • Since you're running the legacy network adapters I'd recommend checking out this thread: https://forum.pfsense.org/index.php?topic=73258.0

    These are the synthetic drivers compiled by zootie.

    I have been running 2.1.2 -> 2.1.3 -> 2.1.5 on Hyper-V with those synthetic drivers without any significant issues but my pfsense installation is basic and I have no additional packages installed. I'd highly recommend fully reading the thread (even the ranting that is occurring in it) before implementing those synthetic drivers.

    The other option I've seen recommended in the forums is to try the 2.2 beta build which includes support for Hyper-V. Personally I am waiting for a 2.2 stable release before going this route.

    @breakaway:

    Hi All

    I've been using pfSense on Hyper-V for a while now. Using legacy network adapters of course since the hyper-v specific ones don't pick up in pfSense.

    The issue I am having is my interfaces will not come up automatically on boot. It appears that the LAN interface (static IP, dhcp server) is the one that's impacted by this. The WAN interface (static IP) does not appear to suffer this issue.

    Is there going to be a solution for this? So far the solution I am using is to set up a autorun script that will automatically run ifconfig de1 down && ifconfig de1 up every boot.



  • I have been quite successfully running 2.2 in hyper-v 2012 R2 for some time now.  No issues at all with synthetic network adapters.

    2.2 also supports some of the guest services out of the box, but not dynamic memory… but it's nice that it supports host shutdown etc.

    I just wish I could get it to install in a Generation 2 VM but when I attempted it last I could not get past boot.



  • You really should be running a 2.2 RC snapshot now.

    CARP has been fixed with the synthetic driver.


Log in to reply