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

    IPSEC becomes unresponsive

    Scheduled Pinned Locked Moved IPsec
    5 Posts 4 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.
    • H
      hsb
      last edited by hsb

      Current build 22.01 (updated from 2.2.4)

      I am having issue on pfsense + hosted on AWS after updating, from 2.2.4 to 22.01, every now and then vpn tunnels stops working and ipsec service cannot be restarted, ipsec is totally unresponsive, i have to reboot the firewall to fix the issue.

      I have 50 VPN tunnels running with various sites.

      Any help would be appreciated.

      M T abliznoA 3 Replies Last reply Reply Quote 1
      • M
        mr.ortizx @hsb
        last edited by

        @hsb I am having the same issue. which a site with lots of site to site vpns setup.

        1 Reply Last reply Reply Quote 1
        • T
          Topogigio @hsb
          last edited by

          @hsb same issue on pfSense 2.6.0 on VMWARE.

          needed a whole pfSense reboot to restore tunnels

          1 Reply Last reply Reply Quote 0
          • abliznoA
            ablizno @hsb
            last edited by ablizno

            @hsb
            https://forum.netgate.com/topic/172075/my-ipsec-service-hangs/38

            https://redmine.pfsense.org/issues/13014

            There is some reading for you, If you run pgrep -f charon then kill -9 the PIDs, start IPSEC then restart IPSEC and it will come back up. You can do that as it's less disruptive than rebooting. It is a frustrating issue without much movement.

            T 1 Reply Last reply Reply Quote 0
            • T
              Topogigio @ablizno
              last edited by

              @ablizno "frustrating"? it's a blocking problem that simply makes pfSense unfit for many scenarios (in fact, all of my firewall scenarios)

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