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

    access pfsense web in Hyper-V on Windows 10 for testing purposes

    Scheduled Pinned Locked Moved Virtualization
    11 Posts 2 Posters 2.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.
    • provelsP
      provels @imthenachoman
      last edited by provels

      @imthenachoman Have you allowed your V-host to share the LAN V-Switch interface for management? Does the WAN get DHCP from your modem/router/ISP?
      9551887b-7a05-4150-b790-46e57331dd14-image.png

      Peder

      MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
      BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

      1 Reply Last reply Reply Quote 0
      • I
        imthenachoman
        last edited by

        So for LAN I use external and select the network adapter my host is connected on?

        I don't need/want the rest of my network to access the pfsense. I just want access from my host for testing.

        provelsP 1 Reply Last reply Reply Quote 0
        • provelsP
          provels @imthenachoman
          last edited by

          @imthenachoman Yes, all switches must be external to see the world. Private allows a VM to see another VM only, Internal allows VMs to see the Host, and External allows connectivity outside the Host (what you want).

          Peder

          MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
          BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

          1 Reply Last reply Reply Quote 0
          • I
            imthenachoman
            last edited by

            I am not following.

            I only want to access this pfsense VM from my host. It is only for test. I don't want my router to be aware of it so I do not have it set for the WAN to get DHCP from the modem/router/ISP.

            So I think for LAN it would/should be private, right? And for WAN it should be internal so the host machine can connect to the web configuration of the pfsense VM. But that combination does not work.

            provelsP 1 Reply Last reply Reply Quote 0
            • provelsP
              provels @imthenachoman
              last edited by provels

              @imthenachoman Delete your Private switch and recreate as Internal. As long as your LAN interface IP of the pf is on the same net as the Host (and you have allowed the Host to share the switch) it should work. Without an External switch for WAN, you won't go anywhere anyway. You don't want to manage from your WAN.

              Peder

              MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
              BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

              I 1 Reply Last reply Reply Quote 0
              • I
                imthenachoman @provels
                last edited by

                @provels There is no option for host to share internal switch.

                provelsP 1 Reply Last reply Reply Quote 0
                • provelsP
                  provels @imthenachoman
                  last edited by provels

                  @imthenachoman Sorry, then, I'm out of options. I run on 2012R2. Sorry x2.

                  EDIT - Sure about that?
                  http://www.troubleshootwindows.com/windows-10/how-to-make-a-virtual-switch-in-windows-10/

                  Peder

                  MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
                  BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

                  I 1 Reply Last reply Reply Quote 0
                  • I
                    imthenachoman @provels
                    last edited by

                    @provels Oh. I thought you said to make LAN = internal.

                    However, I think I got it working.

                    I made:

                    • WAN = private virtual switch
                    • LAN = internal virtual siwtch (not "Default Switch")
                    • In Windows 10 (the host), in "Network and Sharing Center", for "vEthernet (internal)", I gave it a static IP of 10.20.30.41 and subnet of 255.255.255.0
                    • In pfsense:
                      • ignore if WAN can't get an IP via DHCP since it doesn't matter for my purposes
                      • set LAN IP to 10.20.30.1 and enable DHCP (10.20.30.100 to 10.20.30.150)

                    Now I can connect to 10.20.30.1 from my host to access pfsense. Woot!

                    provelsP 1 Reply Last reply Reply Quote 0
                    • provelsP
                      provels @imthenachoman
                      last edited by

                      @imthenachoman x2!

                      Peder

                      MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
                      BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

                      1 Reply Last reply Reply Quote 1
                      • I
                        imthenachoman
                        last edited by

                        Thanks for your help!

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