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

    Just upgraded from 22.01 to 22.05 on my Netgate 2100 MAX, cant reach internet now?

    Scheduled Pinned Locked Moved General pfSense Questions
    29 Posts 4 Posters 2.6k 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
      SteveITS Galactic Empire @robmontreal
      last edited by

      @robmontreal OK so that's a public IP at least. If you can't ping the .1 gateway then either that gateway doesn't respond to pings, or there's some weird routing going on, or there's a firewall rule blocking your ping, etc. That shot shows the gateway online though so it seems like the monitoring did ping it...

      Is anything set in System/Routing/Static Routes?

      Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
      When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
      Upvote 👍 helpful posts!

      R 1 Reply Last reply Reply Quote 0
      • R
        robmontreal @SteveITS
        last edited by

        @steveits Ok, so I can ping the gateway just to confirm.

        Nothing in static routes, its empty.

        This is getting weird.

        S 1 Reply Last reply Reply Quote 0
        • S
          SteveITS Galactic Empire @robmontreal
          last edited by

          @robmontreal said in Just upgraded from 22.01 to 22.05 on my Netgate 2100 MAX, cant reach internet now?:

          I can ping the gateway

          tracert 8.8.4.4

          and see how far you get. If you can get to the gateway it ought to be working.

          It's not a DNS issue is it?

          Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
          When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
          Upvote 👍 helpful posts!

          R 2 Replies Last reply Reply Quote 0
          • R
            robmontreal @SteveITS
            last edited by

            @steveits if i cant ping anything, i figure dns is not an issue

            here is a tracert from my windows box

            12faac6e-f6be-4e5c-8a75-2a7ac371c63e-image.png

            1 Reply Last reply Reply Quote 0
            • R
              robmontreal @SteveITS
              last edited by robmontreal

              @steveits Is it easy to revert back to 22.01 version?

              This issue is getting annoying... :)

              S 1 Reply Last reply Reply Quote 0
              • S
                SteveITS Galactic Empire @robmontreal
                last edited by

                @robmontreal You can reinstall:
                https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/reinstall-pfsense.html

                192.168.0.1 is the LAN of your pfSense? It sounds like it doesn't want to route out. Does Diagnostics/Routes show a default route? Yet, the gateway is pingable...which might make sense if there is no default route.

                Does System/Routing have a default gateway set? (black globe icon)
                c3185eb6-471b-4a16-a242-6a38f35cfc95-image.png

                Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                Upvote 👍 helpful posts!

                R 1 Reply Last reply Reply Quote 0
                • R
                  robmontreal @SteveITS
                  last edited by

                  This post is deleted!
                  1 Reply Last reply Reply Quote 0
                  • R
                    robmontreal
                    last edited by

                    This post is deleted!
                    S 1 Reply Last reply Reply Quote 0
                    • S
                      SteveITS Galactic Empire @robmontreal
                      last edited by

                      @robmontreal said in Just upgraded from 22.01 to 22.05 on my Netgate 2100 MAX, cant reach internet now?:

                      rather than leave as automatic in gateway i selected WAN_DHCP

                      I vaguely recall having to do that several years ago somewhere due to a bug, but it's not normal. The docs talk about it selecting the wrong gateway...

                      Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                      When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                      Upvote 👍 helpful posts!

                      R 1 Reply Last reply Reply Quote 0
                      • R
                        robmontreal @SteveITS
                        last edited by robmontreal

                        @steveits

                        Just to complete this post, as I deleted some screenshots with IP in them.

                        This problem is SOLVED

                        "I ended up setting the WAN gateway to WAN_DHCP as it was set to none."

                        And then everything started working as it should.

                        Thanks to all that helped me out.

                        Have a great day!

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