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

    pfSense on Hyper-V, but can't ping virtual LAN switch NIC from host network.

    Scheduled Pinned Locked Moved OpenVPN
    2 Posts 2 Posters 1.1k 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.
    • C
      CoyoteKG
      last edited by

      Probably need to create route. I don't know how.

      I followed this link
      https://www.netgate.com/docs/pfsense/virtualization/virtualizing-pfsense-with-hyper-v.html

      Created WAN which is real NIC on Host machine where cable from office router is plugged.
      Also created LAN like "Private network". Hm... I'm thinking now that maybe I needed to set Internal network...?

      So VPN is successfuly installed.
      receiving IP address from TPLink router, and I assigned it to MAC like static and it is 192.168.1.20

      I set LAN to 10.9.9.1/24

      I could not access to webinterface from Host machine, but I already have one Windows 10 Virtual Machine, set that LAN NIC to it, and it works.
      Windows 10 properly getting IP. 10.9.9.100 because I set DHCP from 100-150. Also that VM have access to internet.

      Afterwards I installed OpenVPN using this guide
      https://www.netgate.com/docs/pfsense/vpn/openvpn/openvpn-remote-access-server.html

      But now I need to set port forwarding on my TPLINK from 1194 probably to WAN address which is 192.168.1.20?

      Problem is that I can't ping not even 192.168.1.20, neither 10.9.9.1.

      Sorry for long post, I want to be detailed, to help you to understand my problem.
      Can you direct me with instructions or link what I missed?

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        By default pfSense passes nothing into WAN. You need firewall rules to pass traffic into WAN. Even pings.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

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