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

    Planning to Transition to pfSense

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    5 Posts 3 Posters 926 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.
    • S
      simon_lefisch
      last edited by

      Hello everyone,

      First time poster here and as the title says, I am looking to transition to pfSense as my router/firewall but would like to get a little info first. I have poked around and setup pfSense as a VM for a virtual network I am running but would like to put this into my own LAN and make the transition as seamless as possible.

      My current setup is as follows:

      Arris SURFboard SB8200 modem >
      Netgear R7800 router w/ DD-WRT firmware (Kong) >
      Netgear GS728TPv2 managed switch >
      CentOS 7 server running KVM (this is where I would have pfSense running)

      • server has 2 onboard NICs and a 2-port PCIe NIC card
        Other devices connected to switch as well (Apple TV/etc)

      I will most likely use the PCIe card for pfSense (1-port (A) for WAN and 1-port (B) for LAN), and turn the R7800 into a wireless AP. Would the following connections be correct?

      modem > pfSense WAN port (A) <> pfSense LAN port (B) to switch, All other devices to switch (PCs/AP/etc)

      If so, how would I setup the WAN port of pfSense (static or DHCP)? I assume static? I know I can get to the modem UI via 192.168.100.1, but would that mean I need to set the pfSense WAN on the same subnet (192.168.100.x)? Thanks in advance for any info you can provide.

      1 Reply Last reply Reply Quote 0
      • chpalmerC
        chpalmer
        last edited by

        Set the pfSense WAN to DHCP. Reboot your cable modem between changes from one box to the other.

        You will get a public IP address on your pfSense WAN and should still be able to access your modem at 192.168.100.1

        Triggering snowflakes one by one..
        Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

        1 Reply Last reply Reply Quote 1
        • S
          simon_lefisch
          last edited by simon_lefisch

          Thanks for the reply @chpalmer. Sounds easy enough. Connection wise, everything else sounds good? Again just trying to make the transition as easy/seamless as possible. Thanks again for your time and patience.

          Raffi_R 1 Reply Last reply Reply Quote 0
          • Raffi_R
            Raffi_ @simon_lefisch
            last edited by

            @simon_lefisch said in Planning to Transition to pfSense:

            Thanks for the reply @chpalmer. Sounds easy enough. Connection wise, everything else sounds good? Again just trying to make the transition as easy/seamless as possible. Thanks again for your time and patience.

            Connection wise, what you laid out makes sense. That's the way I would do it as well. As suggested, if WAN is setup with DHCP and assuming the modem does its job of handing out a DHCP WAN address, it should just work.
            Good luck.

            S 1 Reply Last reply Reply Quote 1
            • S
              simon_lefisch @Raffi_
              last edited by

              @Raffi_ awesome, thanks for the info. I will most likely make the switch this weekend and update when complete. Thank you both for your time and info 😁

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