Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Installing Pfsense on Hyper-V server

    Scheduled Pinned Locked Moved Virtualization
    3 Posts 3 Posters 2.5k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      alfjonny
      last edited by

      Hi,

      I want to install Pfsense on my Hyper-V server for home use with no experience with Pfsense at all.
      Can you please let me know if I need two NIC's on my Hyper-V server for this to work?
      This is due to only one available NIC today.

      My current setup is as follows:
      Bridge mode between the network box from the internet vendor and my Asus Dark Knigt router.
      The Hyper-V server is connected to the Asus Router.

      Is it possible to use the virtual Pfsense as gateway and route the traffic to the Asus router as a worktrough without two NIC's?

      If this is not possible, can I still use the virutal Pfsense in a test enviroment?
      Is it then possible to use eth WAN and create "internal virtual network" as test environment?

      All help will be very well received.

      1 Reply Last reply Reply Quote 0
      • G
        gjaltemba
        last edited by

        @alfjonny:

        Is it then possible to use eth WAN and create "internal virtual network" as test environment?

        Define a internal vswitch for your VMs including pfsense. In pfsense use add vnic for your lan interface. Set a static ip and start dhcpd. In VMs add vnic and set as dhcp.

        Define a external vswitch with your nic. Use this for management and in pfsense add vnic for your wan interface. Use a static ip on the same subnet as the asus router lan. Use dhcp if dhcpd is running on asus router.

        Check the device list on asus router to see hyperv and pfsense is connected.

        Have fun.

        1 Reply Last reply Reply Quote 0
        • M
          mkmahmoud2100
          last edited by

          Dear gjaltemba & alfjonny
          I have machine that runs Windows Server 2008 R2.
          In order to run Pfsense over Hyper-v we have two scenarios:

          • Giving Legacy Network Interfaces for PfSense VM

          • Give Real Interface for VM with full speed.

          Drawbacks

          • With Legacy Interface we don't have to install BIS/ Since its built in

          • With Legacy Interface Pfsense can control and discover the interface, but Mostly the IRQ will be wrong which reveals for no way to make transparent MODE

          • With dedicated Interface (Full Speed), Pfsense Can't control it until installing BIS (Since FreeBSD 10.2) it build in.

          Result:

          • Pfsense does not has Ports so no further drivers can be loaded.
            Example IBM Server RAID controller

          • Using transparent mode not working with hyper-v

          Suggestions
          have you ever make testing for this methodology?
          And what is yours suggestions?

          Wishes

          MAHMOUD KHALID ABURUB

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.