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.
    • CourierdogC
      Courierdog @rcoleman-netgate
      last edited by

      @rcoleman-netgate There is a removal button in the Package Manager, I do not see an Uninstall method.
      In my understanding of past operations, there is a difference between the "Uninstall" and "Removal"
      I come from a MacOS experience where Removal, Uninstall and Move to Trash are very distinctly different operations.
      Sorry for any confusion.
      Also I am extremely new to pfsense (2022-04-20)

      R 1 Reply Last reply Reply Quote 0
      • R
        rcoleman-netgate Netgate @Courierdog
        last edited by

        @courierdog https://docs.netgate.com/pfsense/en/latest/packages/manager.html#uninstalling-packages

        Ryan
        Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
        Requesting firmware for your Netgate device? https://go.netgate.com
        Switching: Mikrotik, Netgear, Extreme
        Wireless: Aruba, Ubiquiti

        CourierdogC 1 Reply Last reply Reply Quote 0
        • R
          robmontreal @rcoleman-netgate
          last edited by

          @rcoleman-netgate

          It shows status as up, it has a gateway IP, no errors , no collisions, in/out packets 1/2(264 B/168B)

          Suggestions?

          Thanks for the prompt reply.

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

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

            upgraded to 22.05 on my Netgate 2100 MAX, rebooted and now no internet

            You rebooted or it rebooted itself? Upgrades will reboot automatically but it can take 10+ minutes sometimes, just wait it out.

            tried pfsense ping

            You can't ping the pfSense or the pfSense can't ping out to the Internet?

            LAN should not have a gateway, only WAN.

            192.168.1.69
            2001:56a:f1e1:c500:92ec:77ff:fe20:724

            The IPv4 is a private IP, do you have another router in front of your pfSense? Can you ping that router?

            Can you ping using IPv6? In Windows:
            ping -6 ipv6.google.com
            or
            ping -6 2607:f8b0:4009:81b::200e

            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 Thanks for the reply.... I had to reconnect old router so they can do some work, old router works as expected.

              I will reply in a bit when everyone goes to lunch i will switch over to Netgate again and troubleshoot

              After the upgrade it rebooted itself. I lost connectivity drove to the office(45 mins) and it was up, but could not get to the internet.

              I'll reply again in a bit
              Thanks..

              R 1 Reply Last reply Reply Quote 0
              • CourierdogC
                Courierdog @rcoleman-netgate
                last edited by

                @rcoleman-netgate OK we are on the same page.
                Thanks for the reference.
                I removed the Package and Re-Installed the PFBlocker.
                Now the CPU Usage is moving from 15% to 26% this is somewhat more normal from my observations.

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

                  @steveits

                  Ok i plugged modem back into netgate, i have a gateway under wan, but i cannot ping it, using ping under diags menu

                  Under status>gateways it says Pending everywhere?? Is this normal?

                  Thanks

                  S 1 Reply Last reply Reply Quote 0
                  • R
                    robmontreal @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 The pending status is probably because it can't ping the gateway either (?). In System/Routing you can edit the gateway and check "Disable Gateway Monitoring" but that's a bit of a hack. Does the ISP router normally respond to pings?

                      Is your WAN DHCP?

                      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 Hey Steve, i do not think my isp router normally responds to ping, i would have to reconnect the old router to check as everything works with old router.

                        My WAN is DHCP.
                        The pending was because i had the wan disconnected, my bad... it shows good now....
                        Can i provide more screen shots for you?

                        Thanks..

                        1 Reply Last reply Reply Quote 0
                        • 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.