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

Why WAN interface needed DHCP option enabled?

General pfSense Questions
4
20
5.5k
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.
  • S
    stephenw10 Netgate Administrator
    last edited by Apr 1, 2019, 10:29 AM

    Hmm, if you have only on static IP in the 192.x.x.x range when you set the pfSense WAN to use it are you removing it from the host? Only one of those things can use that IP at a time.

    Steve

    F 1 Reply Last reply Apr 1, 2019, 11:00 AM Reply Quote 1
    • F
      Foertsch @stephenw10
      last edited by Foertsch Apr 1, 2019, 11:22 AM Apr 1, 2019, 11:00 AM

      @stephenw10 Yes, I am trying to use the same IP address for the host and the pfSense virtual machine. I'm sorry for wasting your time. Tell me, please, in my network pfSense filters only traffic addressed to virtual machines, right? Host not protected by pfSense? And can I implement NAT for pfSense in order not to buy an additional public IP?

      1 Reply Last reply Reply Quote 0
      • S
        stephenw10 Netgate Administrator
        last edited by Apr 1, 2019, 11:48 AM

        It is possible to do that, yes. However I'm not familiar with the exact terms used by Hyper-V to do it.

        You could just set the host to DHCP since that seems to work. But you might lose connectivity to it. You need to have some out-of-band connection to it to be sure you can revert that change if necessary.

        Steve

        F 1 Reply Last reply Apr 1, 2019, 12:16 PM Reply Quote 1
        • F
          Foertsch @stephenw10
          last edited by Apr 1, 2019, 12:16 PM

          @stephenw10 I'm sorry for disturbing you, will it be possible to implement such a network scheme using virtualized pfSense: Global Nework -> pfSense Firewall (virtualized) -> Host (192.xxx.xxx.xxx) -> Other VMs
          Is it realizable? Or required physical gateway on which pfSense installed?

          1 Reply Last reply Reply Quote 0
          • S
            stephenw10 Netgate Administrator
            last edited by Apr 1, 2019, 12:57 PM

            It is possible to do that.

            Pass the physical NIC through to the pfSense WAN interface or a switch connected to it without the host using that NIC directly. Then give the host a virtual NIC in the LAN subnet so it only has connectivity through pfSense.

            As I said though I'm not familiar with the exact way that might be done in Hyper-V.

            You should probably ask in the Virtualisation sub-forum.

            Steve

            F 1 Reply Last reply Apr 1, 2019, 1:00 PM Reply Quote 1
            • F
              Foertsch @stephenw10
              last edited by Apr 1, 2019, 1:00 PM

              @stephenw10 Thank you very much for help and advice!

              1 Reply Last reply Reply Quote 0
              • M
                marvosa
                last edited by marvosa Apr 1, 2019, 3:48 PM Apr 1, 2019, 3:15 PM

                To keep things straight, and for performance reasons, I'd recommend adding a 3rd NIC at a minimum (if not a 4th) and dedicating 2 NIC's to your PFsense VM. The configuration would look like this:

                4 NIC setup
                NIC 1 = Assign to vSwitch0, create vMkernel port group used for management, connect to switch
                NIC 2 = Assign to vSwitch1, create port group labeled "VM Network", connect to switch
                NIC 3 = Assign to vSwitch2, create port group labeled "PFsense WAN", connect to ISP modem
                NIC 4 = Assign to vSwitch3, create port group labeled "PFsense LAN", connect to switch

                3 NIC setup
                NIC 1 = Assign to vSwitch0, shared vSwitch for VMkernel port group (Management) and VM Network port group, connect to switch
                NIC 2 = Assign to vSwitch1, create port group labeled "PFsense WAN", connect to ISP modem
                NIC 3 = Assign to vSwitch2, create port group labeled "PFsense LAN", connect to switch

                I use ESXi, so you may have to translate the terms into Hyper-V speak.

                A 2 NIC setup will work as intended but has to be configured and addressed properly... much like stephenw10 mentioned.

                1 Reply Last reply Reply Quote 1
                • S
                  stephenw10 Netgate Administrator
                  last edited by Apr 1, 2019, 3:59 PM

                  This is going to be significantly more difficult because as understand it hyper-v is running on a hosted appliance. Access to it may be limited. Adding NICs is probably not an option.

                  Steve

                  1 Reply Last reply Reply Quote 1
                  • F
                    Foertsch
                    last edited by Apr 1, 2019, 5:14 PM

                    Thank you all. I setup network, it turned out pretty simple. I thought External Virtual Switch - its a network bridge in Hyper-V, but its works differently. Probably, i dont uderstand how it works - I watched IP conflict, because my public IP (192.xxx.xxx.xxx) belonged to host, at the same time pfSense tried to use it (because of this there was no network on pfSense VM). I delete ipv4 parametr from External VS, create Microsoft Network Bridge for External VS and Ethernet 2 (my physical adapter with public IP). And its works for me! Now i have internet on all my virtual machines. Also, NAT is work. pfSense routes all packets. Tracert gives me the: 10.10.10.1 -> ISP gateway -> google.com (example). Thank you guys! Without your help, I would hardly have succeeded. :) Very friendly forum!

                    1 Reply Last reply Reply Quote 0
                    • M
                      marvosa
                      last edited by marvosa Apr 1, 2019, 6:03 PM Apr 1, 2019, 5:20 PM

                      Glad it's working!

                      Just a note for down the road, eventually you will want to remediate your double NAT situation. In other words, have the ISP configure their modem in bridge mode, so PFsense gets a public IP.

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