Hyper-V 2012 R2 and pfSense?


  • Banned

    Im thinking of switching from ESXi to Hyper-V 2012 R2 because we are using it at work and I must say, it is pretty nice :)

    I wanted to know what compatibility issues I may or may not have compared to my current ESXi 5.5 installation.

    Im putting it on a HP N54L just in case.



  • I can't speak to 2012 R2, but I've been testing PFSense on Windows 8.1 Pro with Hyper-V and it seems to work fine.

    Pfsense 2.2+ recognizes the synthetic network adapters, so you don't need to use the legacy network adapters.



  • I use pfSense w/Server 2012 R2 w/hyper-v. Works fine.

    Although I notice that in general the CPU usage is higher than other physical pfSense systems I have, mainly in the interrupt time used. CPU utilization is still low overall though, so isn't anything worry about - just an observation.

    I've never used pfSense with VMware (although I use VMware extensively for other things at work), so I can't compare between them for pfSense use.



  • Currently using pfSense with Hyper-V 2012 R2 without issues.
    It nicely recognizes the virtual NIC's, and runs OK, even with VLAN
    However if you want to work with VLAN tagging, the supported way of doing this is to add a virtual NIC for every VLAN you have in use, and set the VLAN tag on VM level settings

    (Yes there is a workaround, however you might run into complications using this, as there is no official way to set a virtual machine NIC to trunk mode)



  • @riahc3:

    Im thinking of switching from ESXi to Hyper-V 2012 R2 because we are using it at work and I must say, it is pretty nice :)

    I wanted to know what compatibility issues I may or may not have compared to my current ESXi 5.5 installation.

    Im putting it on a HP N54L just in case.

    Well I have hyper-v installed on my N410L machine. The only issue i'm having is getting pfsense to work in hyper-v . I setup everything up even with the script that gets the ip address from my router. the issue i'm having is when i try to ping from the vm I get "request time out"

    I tried everything and nothing seems to work. When I go to pfsense option 7 to ping it works. I'm able to ping google and stuff.

    What am i missing ? If anyone could help me out that would be great.

    Thanks,



  • What do you mean by pinging from option 7?  Are you pinging a public ip?  Are both entries of the script using the same gateway ip?  What if you manually enter via the shell?



  • @XanderVR:

    Currently using pfSense with Hyper-V 2012 R2 without issues.
    It nicely recognizes the virtual NIC's, and runs OK, even with VLAN
    However if you want to work with VLAN tagging, the supported way of doing this is to add a virtual NIC for every VLAN you have in use, and set the VLAN tag on VM level settings

    (Yes there is a workaround, however you might run into complications using this, as there is no official way to set a virtual machine NIC to trunk mode)

    There is a small problem with the 1 NIC per VLAN solution that I ran into, in that there is a limitation in Hyper-V of 12 NICS per VM: 8 synthetic and 4 legacy NICS.  However, using Powershell, you can set a Hyper-V switch port to trunk mode: https://technet.microsoft.com/en-us/library/hh848475.aspx.

    The following sets the port on the VM named Redmond to trunkmode and allows access to VLANs 1-100 and tags all untagged traffic to VLAN 10:

    PS C:\> Set-VMNetworkAdapterVlan -VMName Redmond -Trunk -AllowedVlanIdList 1-100 -NativeVlanId 10
    


  • @rudelerius:

    @XanderVR:

    Currently using pfSense with Hyper-V 2012 R2 without issues.
    It nicely recognizes the virtual NIC's, and runs OK, even with VLAN
    However if you want to work with VLAN tagging, the supported way of doing this is to add a virtual NIC for every VLAN you have in use, and set the VLAN tag on VM level settings

    (Yes there is a workaround, however you might run into complications using this, as there is no official way to set a virtual machine NIC to trunk mode)

    There is a small problem with the 1 NIC per VLAN solution that I ran into, in that there is a limitation in Hyper-V of 12 NICS per VM: 8 synthetic and 4 legacy NICS.  However, using Powershell, you can set a Hyper-V switch port to trunk mode: https://technet.microsoft.com/en-us/library/hh848475.aspx.

    The following sets the port on the VM named Redmond to trunkmode and allows access to VLANs 1-100 and tags all untagged traffic to VLAN 10:

    PS C:\> Set-VMNetworkAdapterVlan -VMName Redmond -Trunk -AllowedVlanIdList 1-100 -NativeVlanId 10
    

    Thank you so much sir. After many many hours of search and research, your solution worked for me (Windows Server 2012 R2 + HyperV + pfSense 2.3.1)

    Just one comment: on allowedVlanIdList, do not include VLAN 1, since on most switches, it´s the default untagged. On my environment (Dell Switches) it didn´t work at all until I used -AllowedVlanIdList 2-XXXX and -NativeVlanId 1 so I can access through my server


Log in to reply