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

    How to pass internet to host from hyper-v pfsense instance

    Scheduled Pinned Locked Moved Virtualization
    2 Posts 2 Posters 553 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.
    • W
      WolfRam
      last edited by

      I have a small itx rig that has 2 built in nics in the motherboard, I'm using hyper-v to run a pfsense instance, having the machine act as my router, and the host is also my Plex Machine.

      One port connects to the ethernet cable coming in from the ONT, designated WAN, not shared with the host, while the other port goes to my LAN, switches and other devices. The LAN port is shared with the host.

      I'm not sure if this is the proper way to do it, but I couldn't find any other way to do it. I did think of creating a virtual switch in the hyper-v and trying to pass a connection from pfsense to the host that way, but couldn't figure out how to get it working.

      With the current setup, everything downstream from the host works perfectly, getting the full half gigabit symmetric speeds my isp advertises, all local connections to the host work great as well.

      The issue: The host itself, while gets the same download speeds to the WAN, is unable to eke out more than 1Mbps upload speeds to WAN. I ran 2 speed tests to the same server back to back, a downstream device has 500Mbps symmetric, host gets 500Mbps down, 1 Mbps up.

      My guess is sharing the LAN port is not the way to get my host connected, sharing the WAN port is definitely not it either, so any advice on how to do so securely will be appreciated

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

        @wolfram There is a problem with Hyper-V, see here. It will be fixed in the next release.

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