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

    Creating fake nics in Hyper-V.

    Scheduled Pinned Locked Moved Virtualization
    6 Posts 3 Posters 1.0k 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.
    • nerlinsN
      nerlins
      last edited by

      I would love to be able to set up Pfsense in a VM only as test box, set it up completely, save the config file, then upload the config to my real Protectli box.

      The roadblock is that the Hyper-V machine would only have one nic, so I assume. The Protecli has four: em0, em1, em2, and em3. Is there a way I could create fake adapters in Hyper-V, with the actual device ID's exactly like the names above so I can finally put more time into setting up Pfsense?

      I don't have a great homelab environment. I have to keep plugging Pfsense on and off, tinker, then revert back to my Netgear router so the home network is still functional.

      KOMK 1 Reply Last reply Reply Quote 0
      • KOMK
        KOM @nerlins
        last edited by

        @nerlins https://letmegooglethat.com/?q=how+to+add+virtual+network+adapters+to+hyperv

        1 Reply Last reply Reply Quote 0
        • nerlinsN
          nerlins
          last edited by nerlins

          My question was whether I can and how do I make Pfsense see them as those device IDs...em0, em1, etc.

          It can't be as simple as the name I actually give the virtual adapter in hyper-v, can it? I've never had the need to create more than one virtual adapter for a virtual machine so I have not delved that deep into it. If you have a link to how I can change the internal device IDs to match the protectli router then I'd appreciate it.

          KOMK 1 Reply Last reply Reply Quote 0
          • Bob.DigB
            Bob.Dig LAYER 8
            last edited by

            Hyper-v adapters are hn, not em. I don't think that you can change that, but I am no expert.

            1 Reply Last reply Reply Quote 0
            • KOMK
              KOM @nerlins
              last edited by

              @nerlins Ah sorry, that's different altogether. Normally when this is an issue when moving an installation, all you have to do is modify your config file to replace the NIC types as Bob.Dig below alluded to. Find & replace all em0, em1 with hn0, hn1 etc. Install fresh, do a basic config so you can get to WebGUI then restore your modified config file.

              1 Reply Last reply Reply Quote 0
              • nerlinsN
                nerlins
                last edited by

                @KOM I appreciate the insight. I think that will be my backup plan.

                I realized my office computer has a wifi adapter. I never used it. I'm thinking I will connect it to my current Netgear router so that network is not taken down. I'll connect my ethernet to Pfsense. I found a program called ForceBindIP, which I'm thinking could force Firefox to use the ethernet adapter, so I can configure PFsense in the web gui. I have to make sure the WAF is stable...😁

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