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

    IPSEC tunnels monitor issue after updating to 2.5.0

    IPsec
    ipsec monitor status
    3
    8
    936
    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
      bashuis
      last edited by

      hi,

      i have a few pfsense firewalles connected by IPSEC tunnels.

      since the update to 2.5.0 the tunnels are up (functioning) but in the monioring they are down.

      Monitoring overview:
      8089c78e-b246-420c-b428-4e50ed54cae0-image.png

      IPSEC Status
      28da3f21-6493-4d62-9991-dc3a041f2ff7-image.png

      Is there any solution available?

      B 1 Reply Last reply Reply Quote 1
      • B
        bennyc @bashuis
        last edited by

        @bashuis
        did you install the 6 patches for IPSec? See post from Jimp:
        https://forum.netgate.com/topic/161291/sg-5100-21-02-ipsec-tunnels-duplicate-incorrect-status

        4x XG-7100 (2xHA), 1x SG-4860, 1x SG-2100
        1x PC Engines APU2C4, 1x PC Engines APU1C4

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

          I have the exact same issue and have applied all six of the patches that @jimp called out in the linked thread. All the functionality works with regards to the site-to-site VPN connectivity on the IPSec Tunnels, but the dashboard widget for IPSec is not displaying the correct status.

          Screen Shot 2021-03-22 at 11.25.05 PM.png Screen Shot 2021-03-22 at 11.25.29 PM.png Screen Shot 2021-03-22 at 11.27.39 PM.png Screen Shot 2021-03-22 at 11.28.01 PM.png

          B 1 Reply Last reply Reply Quote 0
          • B
            bennyc @lbthe3rd
            last edited by

            @lbthe3rd
            strange... did you restart the firewall after patching?
            IIRC that solved it for me.

            4x XG-7100 (2xHA), 1x SG-4860, 1x SG-2100
            1x PC Engines APU2C4, 1x PC Engines APU1C4

            L 1 Reply Last reply Reply Quote 0
            • L
              lbthe3rd @bennyc
              last edited by lbthe3rd

              @bennyc I can confirm that a reboot does not clear this issue up for me. I tried again this afternoon just to be sure. Thankfully this appears to be just cosmetic but I want to make sure it is being tracked for a 2.5.1 release, or minimally as a patch for 2.5.1.
              Netgate_Forum_Reply_IPSec_Widget.png

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

                I installed 2.5.1 RC, but this does not solve the problem

                2adeeaa8-de65-4f50-a511-b4522899d934-image.png

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

                  i updated an test pfsense to 2.6 dev version and the problem is solved.

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

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