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

    New Install No Internet

    Scheduled Pinned Locked Moved General pfSense Questions
    11 Posts 4 Posters 1.2k 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.
    • A
      Authec
      last edited by

      Hi All,

      I'm a new PFSense user trying to figure my way out through this. I've setup my network, however on the LAN side of things I'm not receiving any internet.

      For context, my topology is as follows;

      2c4a213a-b1a0-446e-9d6d-9fa776d96138-image.png

      To clarify the image a little clearer, my goal was to set this up in a manner to retain the wireless network from the Modem/Router to be usable by smart devices (pre-firewall). Any further traffic that is not to be used by smart devices to be post PFSense.

      The Modem/Router is on 192.168.69 which then enters my nook PC running PFSense into the WAN allocated NIC. If it helps as well I've also set the DNS servers to 8.8.8.8 and 9.9.9.9

      From there the PFSense is configured to run on 192.168.69.250. From my understanding this allows the LAN port to allocate DHCP for 192.168.69.10-192.168.69.241 from what I can see in the DHCP leases.

      However, anything post LAN I am not receiving any internet and am unsure where to start looking. Any guidance would be greatly appreciated!

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @Authec
        last edited by

        @Authec said in New Install No Internet:

        The Modem/Router is on 192.168.69 which then enters my nook PC running PFSense into the WAN allocated NIC. If it helps as well I've also set the DNS servers to 8.8.8.8 and 9.9.9.9

        From there the PFSense is configured to run on 192.168.69.250. From my understanding this allows the LAN port to allocate DHCP for 192.168.69.10-192.168.69.241 from what I can see in the DHCP leases.

        So you have both, WAN and LAN in 192.168.69.0/24?
        This would make routing impossible at all. The subnets have to be different.

        1 Reply Last reply Reply Quote 1
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Yup the pfSense LAN needs to be a different subnet.

          1 Reply Last reply Reply Quote 0
          • A
            Authec
            last edited by

            Sorry apologies, I've typod there.

            The WAN is on 192.168.1.69

            Whilst the LAN is on 192.168.69.x

            So currently the WAN and LAN are in different subnets

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              If you can connect to the pfSense GUI check what pfSense itself can see.

              Try to resolve in Diag > DNS Lookup. Make sure all the configured server are responding.

              Try to ping out by IP and url in Diag > Ping.

              Steve

              A 1 Reply Last reply Reply Quote 0
              • A
                Authec @stephenw10
                last edited by

                @stephenw10 Thanks for the guidance.

                So I can access the pfSense GUI and was able to do both.

                DNS Lookup

                8469ed51-8f3f-4648-b8c1-061b976d0a77-image.png

                Ping

                URL
                048091d9-9c1d-4d87-877e-da8d9fee3ce9-image.png

                IP Address of Google
                a4a8e994-e5ef-477c-990a-d5db96e2bc76-image.png

                Interestingly on the home page, the LAN Gateway is coming up as Offline, Packetloss but I'm unsure if I've done that correctly. I've set it up as the gateway of the LAN connections from how I understand it, but this may have been a mistake on my part and I may not have done that correctly with the topology used and IP schema I've implemented. I'm wondering if this is the problem?

                ec99f25e-cdd2-4084-8095-5b02b1b15c36-image.png

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  Yes OK. You should not have a gateway on the LAN. You would only ever have that if you had other downstream routers behind pfSense.

                  The IPv4 system default gateway is still set to automatic and it's selected the invalid LAN gateway which is why you have no IPv4 connectivity.

                  Remove the LAN gateway and it should all start working as expected.

                  A 1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Ah, unless you actually are using that. 192.168.69.1 is the LAN side wireless router?

                    In which case go to System > Routing > Gateways and set the default IPv4 gateway to WAN_DHCP.

                    A 1 Reply Last reply Reply Quote 0
                    • A
                      Authec @stephenw10
                      last edited by

                      I do have a downstream router behind pfSense as I'm running on a nook and unfortunately not the Netgate pfSense gateway.

                      I'm currently running a Netgear ex7700 in access point mode for a router but I'm also not getting internet on the switch either

                      If that's the case would removing the LAN gateway rectify this and allow traffic to then pass?

                      johnpozJ 1 Reply Last reply Reply Quote 0
                      • johnpozJ
                        johnpoz LAYER 8 Global Moderator @Authec
                        last edited by

                        @Authec when you create a gateway on an interface, pfsense sees it as a wan.

                        if you did need/want to route downstream networks, you would create a gateway and route, but you wouldn't actually put it on the interface.

                        This is how you would do downstream router.

                        pfsense-layer-3-switch.png

                        But then again, that is not something you would do with a downstream natting router.. And if you were to have a downstream router, there should be no devices on your transit/connector network. See the above example.

                        An intelligent man is sometimes forced to be drunk to spend time with his fools
                        If you get confused: Listen to the Music Play
                        Please don't Chat/PM me for help, unless mod related
                        SG-4860 24.11 | Lab VMs 2.8, 24.11

                        1 Reply Last reply Reply Quote 0
                        • A
                          Authec @stephenw10
                          last edited by

                          @stephenw10 Thank you!

                          You're a legend, both of those combined are what restored the internet connection.

                          Thank you so much for all of your assistance over the past few days.

                          I greatly appreciate all of your help!

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