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

    WIFI home router working with pfSense

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    10 Posts 3 Posters 4.0k 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.
    • B
      bimmerdad
      last edited by

      Hi All,

      I've played around a little (very little) with pfSense in the past but, now I've taken the plunge and set up a pfSense router for my home. But, I haven't gotten online yet because I have a few questions.

      Here is how my home network is currently setup:

      I have a Netgear (WGR614v10) wifi router that I have a few wired devices attached to it and it also serves as our wireless AP. It get's it's IP from TWC and is set with a network IP of 192.168.1.1. It serves as our DHCP.

      What I would like to do is to add the pfSense router with the Netgear router behind it to act as a switch since I have a few wired connections and as an AP for my internal network.

      I would like to not have to change anything with the devices that are currently within my network. ex. most are DHCP devices getting their info from the Netgear which is 192.168.1.1.

      Here is where my train of thought is:

      pfSense
      WAN interface -  DHCP from TWC
      LAN interface - 192.168.1.1, some how have it act as DHCP for internal network. (unless I can keep the Netgear acting as the internal DHCP)

      Netgear
      set with a static IP (192.168.1.2), GW - 192.168.1.1

      connect the WAN port to the LAN port on the pfsense.

      The question is with this setup work?

      If I haven't explained my situation clearly or I need to give additional info, please let me know.

      I tried a search to see if this type of question has been asked before but I have yet to find anything that addressed my issue specifically. If there is a link to the information that will help me please share.

      Thank You guys in advance

      Mark

      1 Reply Last reply Reply Quote 0
      • B
        bimmerdad
        last edited by

        oh, BTW, I installed version 2.2.2 and upgraded to 2.2.3.

        Mark

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

          https://forum.pfsense.org/index.php?topic=81014.msg442131#msg442131

          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 0
          • B
            bimmerdad
            last edited by

            Thanks for the link. I tried to get it to work but I could not.  I was able to set the pfSense LAN interface to 192.168.1.1, it tok some time but I was able to get the Netgear router set to 192.168.1 2 but then I got a message saying I had an IP conflict with the WAN. After trying several things and eventually a few factory resets on the Netgear, I gave up. I know I'm missing an understanding between the pfSense WAN/LAN and it's relationship with the Netgear LAN but am at a loss right now.  Any ideas or directions?

            Mark

            @Derelict:

            https://forum.pfsense.org/index.php?topic=81014.msg442131#msg442131

            1 Reply Last reply Reply Quote 0
            • P
              phil.davis
              last edited by

              I was able to set the pfSense LAN interface to 192.168.1.1, it tok some time but I was able to get the Netgear router set to 192.168.1 2 but then I got a message saying I had an IP conflict with the WAN.

              With which WAN? pfSense or Netgear?

              Follow that link to the diagram by Derelict - it will work.

              Do NOT connect the Netgear WAN port to anything.

              What is the pfSense WAN IP?
              If you the upstream TWC device is giving out a private IP like 192.168.1.x/24 that conflicts with your LAN then there will be trouble.

              Make sure to turn off DHCP on the Netgear.

              Do you have any other device using 192.168.1.2? Or 192.168.1.1?

              What is the pfSense LAN DHCP range?
              It needs to NOT start from 192.168.1.2

              As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
              If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

              1 Reply Last reply Reply Quote 0
              • B
                bimmerdad
                last edited by

                With which WAN? pfSense or Netgear?
                I was trying to configure the Netgear at the time so I;m guessing it was the Netgear WAN.

                Follow that link to the diagram by Derelict - it will work.
                I thought I did.  8-)

                Do NOT connect the Netgear WAN port to anything.
                I didn't, I left it empty

                What is the pfSense WAN IP?
                If you the upstream TWC device is giving out a private IP like 192.168.1.x/24 that conflicts with your LAN then there will be trouble.

                Make sure to turn off DHCP on the Netgear.
                I did but my Netgear WEBGUI is not that straight forward to me. It's kinda old. (I did do a firmware update when I did a factory reset)

                Do you have any other device using 192.168.1.2? Or 192.168.1.1?
                Well, the Netgear was 192.168.1.1 then, while it was still connected, I changed the PFS LAN IP to 192.168.1.1 and at the same time tried to set the Netgear to 192.168.1.2. I'm sure I didn't do something in the right order.

                What is the pfSense LAN DHCP range?
                I set that to 192.168,1.100 - 192.168.1.200

                It needs to NOT start from 192.168.1.2
                It didn't

                1 Reply Last reply Reply Quote 0
                • B
                  bimmerdad
                  last edited by

                  Okay,

                  After thinking about this overnight, I have more questions.

                  In what order should I change IP addreses? for example, my Network is going through the Netgear that has an IP of 192.168.1.1.

                  Just to see the pfSense on my network, I gave the LAN interface an IP of 192.168.1.2, and I can connect to it.

                  I also have 1 or 2 device with static IP's that have the GW of the Netgear (192.168.1.1).

                  So, if I change the the Netgear's IP to say 192.168.1.2 (the current pfsense IP), will I be able to get into the pfsense to change it's LAN IP to 192.168.1.1?

                  If I can get some guidance of how to do this then I can leave the devices with the static IP's alone and they still should work.

                  Can someone give me some advice on this please?

                  Thanks

                  Mark

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

                    No, if you have two devices on the network with the same IP you can't guarantee being able to get into one or either of them.

                    Just set the netgear to something else that's unused then set pfSense to .1

                    The only time you will ever use the netgear's IP address is to get into it to manage it.

                    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 0
                    • B
                      bimmerdad
                      last edited by

                      So, are you saying that if I just change the netgear to say 192.168.1.3, I can still log into the pfSense (192.168.1.2) and change it to 192.168.1.1 ( so that the static devices GW settings can stay the same), then everything should work?  (as long as I've done everything else correct)

                      BTW, on the Netgear, the static GW should be the IP of the pfsence LAN correct? That way the wireless/wired devices that connect through the Netgear will pass through the Netgear –> pfSense LAN(pickup IP from here) --> WAN --> TWC router -->  "The world"

                      Sorry for the newbie questions but my wife works from home and if I screw up the network, she has to go into work and I do have anywhere to stay...

                      Mark

                      @Derelict:

                      No, if you have two devices on the network with the same IP you can't guarantee being able to get into one or either of them.

                      Just set the netgear to something else that's unused then set pfSense to .1

                      The only time you will ever use the netgear's IP address is to get into it to manage it.

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

                        The only reason to have a default gateway in the netgear is so the netgear device itself can route to the internet.  You might or might not be able to even set a default gateway on the LAN side of that device.

                        The wireless clients should have the IP address of pfSense as their default gateway either from DHCP or static.  The Netgear simply bridges the wireless clients with the wired network.  The netgear/AP is not a layer 3 hop.  You are putting wireless and wired clients on the same segment.

                        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 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.