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

    Unstable VPNs since 2.2 and even worse with 2.3.2

    IPsec
    2
    2
    839
    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
      nippertje
      last edited by

      I have been having the same issues with IPSEC tunnels since 2.2 that many have been having on this forum. Although my tunnels (to various devices pfsense, fortigate, draytek) come up, they frequently disconnect and reconnect, sometimes instantly but sometimes after several minutes have passed. Draytek 2850/2860s are the worst and disconnect/reconnect every 20 or so seconds giving a second or two of dropped packets.

      I was hoping that later builds would improve things, but if anything it is getting worse with every release. With the exception of pfsense to pfsense, our tunnels are all over the place and none stays up for more than an hour.

      Does anybody have any advice on how to get stable tunnels between pfsense 2.2/2.3 and third party devices or should I consider rolling back to 2.1 and good ol' racoon, which was very reliable.

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        IPsec has gotten nothing but better between 2.2 and 2.3.2.

        The answers to what is ailing you lie in the configurations on both sides and the logs on both sides. It is impossible to make a recommendation without seeing those.

        In VPN > IPsec, Advanced set all the logging to Control except IKE SA, IKE Child SA, and Configuration backend. Set those to Diag.

        Then look at Status > System Logs, IPsec and match up the logs with a failure and see what it complained about.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

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