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

    pf sense going down

    Scheduled Pinned Locked Moved General pfSense Questions
    11 Posts 3 Posters 876 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
      bluecovenant
      last edited by

      my ISP modem is connected to a protectli vault running pf sense, which is connected to a router

      the router is set to auto reboot at a specific time daily

      when the reboot occurs, pfsense goes down and is no longer accessible via browser even though the router network is up and running

      the only way to get pfsense back up is to physically power down the protectli and then turn back on

      why does this occur and is there a solution?

      thanks

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

        It actually crashes? Kernel panic?

        Does it respond to pings?

        Is it still responding at the console?

        How are you testing? Where are you testing from?

        what pfSense version are you running?

        Steve

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

          @bluecovenant All of the above, but also try a switch between pfSense and the ISP router.

          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!

          1 Reply Last reply Reply Quote 0
          • B
            bluecovenant @stephenw10
            last edited by

            @stephenw10 said in pf sense going down:

            It actually crashes? Kernel panic?

            how do i determine this?

            Does it respond to pings?

            how do i check this?

            Is it still responding at the console?

            what is the console?

            How are you testing? Where are you testing from?

            after rebooting the router, i cannot load the pfsense page on my browser (192.168.1.1)

            what pfSense version are you running?

            2.7.0

            Steve

            this occurs whether i manually reboot the router or set a scheduled reboot, both from the router's browser interface from a computer

            if i manually power down the protectli by pressing the power button, then powering backup up, i am able to load the pfsense page and login, and the internet service to the network returns as well

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

              What is the router you're rebooting here?

              The console is a direct connection to the firewall. So either a serial cable or a keyboard/monitor directly.

              It sounds like you have either some subnet conflict or maybe a default route changing.
              In pfSense what is shown in System > Routing > Gateways?

              B 1 Reply Last reply Reply Quote 1
              • B
                bluecovenant @stephenw10
                last edited by

                @stephenw10 said in pf sense going down:

                What is the router you're rebooting here?

                gl.inet GL-MT6000

                The console is a direct connection to the firewall. So either a serial cable or a keyboard/monitor directly.

                It sounds like you have either some subnet conflict or maybe a default route changing.
                In pfSense what is shown in System > Routing > Gateways?

                there are three lines, with an anchor symbol on the first line, whose name is "WAN_DHCP" and the description is "Interface WAN_DHCP Gateway". the second line's name is "WAN_DHCP6 ", and the third line "VPN1_VPNV4"

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

                  Is the default IPv4 gateway set to WAN_DHCP?

                  B 1 Reply Last reply Reply Quote 0
                  • B
                    bluecovenant @stephenw10
                    last edited by

                    @stephenw10 it is set to automatic. should it be set to WAN_DHCP?

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

                      Yes set it to WAN_DHCP.

                      Because you have a VPN gateway present that may be becoming the default gateway if the WAN goes down.

                      B 1 Reply Last reply Reply Quote 0
                      • B
                        bluecovenant @stephenw10
                        last edited by

                        @stephenw10 this seems to have solved the problem

                        what would cause this problem to occur on this router, whereas i did not need to change this setting on my previous router (netgear orbi)?

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

                          Unclear. By 'router' here you mean the gl.inet GL-MT6000? And that is connected to the pfSense LAN?

                          I can only imagine that device drops the link to the LAN when it reboots and the other device does not. However that should not affect the WAN. The other possibility is that during boot it comes up with a subnet that conflicts with the WAN causing the default to flip.

                          But however it's doing it you should definitely set WAN_DHCP as default to prevent it trying to use the VPN as default.

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