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

    IPSEC and 2.2.6

    Scheduled Pinned Locked Moved IPsec
    4 Posts 3 Posters 1.2k 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.
    • N
      nexxous
      last edited by

      HI, we have had some issues with this new release 2.2.6 mainly only on one box. We have three site to site tunnels running we have had no issues but now seems since we went to 2.2.6 I can't get one tunnel to sync even though it was for about a day then for no reason it will not connect. I tried many different configurations but still won't sync up but yet with the same box two other tunnels work fine? What would cause this? I thought firewall so I checked rules, etc. all good and even redid the rules just in case but still won't go?

      any suggestions on this would be greatly appreciated.

      Ron

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        What's in the IPsec logs?

        1 Reply Last reply Reply Quote 0
        • P
          peterclark4
          last edited by

          I think that I've just stumbled upon the same issue.

          I have a 2.2.5 install locally and remotely I have a 2.2.6 (this was upgraded to 2.2.6 between Christmas and New Year). I came in this morning and couldn't bring the tunnel up, Phase1 was fine but Phase2 never completed. Re-starting IPSEC on both side made no difference and on the 2.2.5 end (local) we had other tunnels working fine. In the end I had to re-boot the remote 2.2.6 to bring the tunnel back up.

          Strange, working again now so I will monitor and see what happens. I'm sorry but due to time restraints I didn't get chance to pull the logs. If this happens again I will make sure that i do this.

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            There are endless different reasons you can have the same symptoms with IPsec. Please start a new thread with your logs and status output if it happens again, as it's almost certainly not the same root cause so that's the best bet for getting help.

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