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

    Wireguard Site-to-Site Gateways disabled after reboot - service not starting

    Scheduled Pinned Locked Moved WireGuard
    35 Posts 9 Posters 4.8k 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
      Seeking Sense @michmoor
      last edited by Seeking Sense

      @michmoor said in Wireguard Site-to-Site Gateways disabled after reboot - service not starting:

      Have you tried disabling gateway monitoring?

      Sure have. Not only that but disabled take action as well.

      And just to be clear the WireGuard Interface fails to come online after reboot.

      B 2 Replies Last reply Reply Quote 0
      • B
        buzz2912 @Seeking Sense
        last edited by

        @Seeking-Sense
        The Solution is restarting dpinger after reboot.
        Search for my post in the solution for site to site gateway down after Reboot

        M S 2 Replies Last reply Reply Quote 0
        • M
          Misterb @buzz2912
          last edited by

          What Buzz said, restart dpinger and then start Wireguard.

          1 Reply Last reply Reply Quote 0
          • S
            Seeking Sense @buzz2912
            last edited by

            Thanks for the reply @buzz2912 I may have tried that in the past not exactly sure and just stumbled across the DISABLE & ENABLE Interface solution.

            I will reboot pfSense later and try your solution.

            Never the less I need an unattended automated method to implement your or my solution for the times that my internet connect flakes out or there is a power outage and yes I have pfSense on a UPS.

            Also WireGuard "is running" just not functioning when I DISABLE and ENABLE it's Interface.

            1 Reply Last reply Reply Quote 0
            • B
              buzz2912 @Seeking Sense
              last edited by buzz2912

              @Seeking-Sense
              install cron and service watchdog. Add wireguard to service watchdog. Create a cron job @reboot && sleep 30 for designer restart Here is the link

              S 1 Reply Last reply Reply Quote 0
              • S
                Seeking Sense @buzz2912
                last edited by Seeking Sense

                @buzz2912 are you saying to reinstall the WireGuard each time this happens? If so that is bonkers Or are you saying restart dpinger utilizing CRON and WATCHDOG?

                B 1 Reply Last reply Reply Quote 0
                • B
                  buzz2912 @Seeking Sense
                  last edited by buzz2912

                  @Seeking-Sense
                  At First i reinstalled. Now I am using dpinger restart

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    Misterb @buzz2912
                    last edited by

                    I've just installed 2.7.0-RELEASE and the same issue and fix exists.

                    L S 2 Replies Last reply Reply Quote 0
                    • L
                      lcbbcl @Misterb
                      last edited by

                      @Misterb wow really? The problem still exist? omg i won't even bother to install the new version.I just need to find a pfb replace and i am out.
                      Thanks you just save me some time, i had in mind a clean install.

                      1 Reply Last reply Reply Quote 0
                      • S
                        Seeking Sense @Misterb
                        last edited by

                        @Misterb thanks for being the guinea pig. 😀

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

                          Tried it too. 2.7.0 and the problem is still the same.

                          1 Reply Last reply Reply Quote 0
                          • L
                            lcbbcl
                            last edited by

                            Well i think that i might solved the problem after reboot. If someone can test and see if its working, i did several reboots and now my wg is coming up without the error for unknown gateway.
                            What i did is check the box Disable Negate rules under System/Advanced/Firewall & NAT.
                            But i still have the problem if my wan goes offline when it is coming back my wg connection will remain offline until i reboot the box.
                            This is a clean 2.7 install without restoring backup just to discard any errors.

                            1 Reply Last reply Reply Quote 0
                            • R rpotter28 referenced this topic on
                            • First post
                              Last post
                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.