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

    IPSec troubles

    Scheduled Pinned Locked Moved 2.2 Snapshot Feedback and Problems - RETIRED
    22 Posts 3 Posters 26.5k 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.
    • M
      miken32
      last edited by

      @cmb:

      That's this. https://redmine.pfsense.org/issues/4129

      I only have the single phase 2 entry; does it still apply to me? Thanks.

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

        No it doesn't in that case, I mis-read your last post. I'm doing some IPsec testing with an ASA right now, will see if that's replicable.

        1 Reply Last reply Reply Quote 0
        • M
          miken32
          last edited by

          @cmb:

          No it doesn't in that case, I mis-read your last post. I'm doing some IPsec testing with an ASA right now, will see if that's replicable.

          Any luck with this? Anything more I can do to help narrow it down?

          1 Reply Last reply Reply Quote 0
          • E
            eri--
            last edited by

            Did you test new snapshots?
            There have been fixes put in place for various issues especially on IPsec.

            1 Reply Last reply Reply Quote 0
            • M
              miken32
              last edited by

              @ermal:

              Did you test new snapshots?
              There have been fixes put in place for various issues especially on IPsec.

              No improvements with this morning's build. Tunnels have to be manually started or the wrong traffic selector is sent.

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

                What's wrong about it? It looks like it's sending what you have configured and the ASA is rejecting it. The only issue with interoperability with Cisco IPsec that I'm aware of is this. https://redmine.pfsense.org/issues/4178 Which only applies to IKEv1 and isn't what you're seeing here.

                1 Reply Last reply Reply Quote 0
                • M
                  miken32
                  last edited by

                  @cmb:

                  What's wrong about it? It looks like it's sending what you have configured and the ASA is rejecting it.

                  Please reread my earlier post at https://forum.pfsense.org/index.php?topic=84934.msg469407#msg469407. When pfSense tries to bring up the tunnel automatically, it sends a different traffic selector than when the tunnel is manually started from the status page.

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

                    The latest strongswan release (5.2.1->5.2.2) went into today's snapshots, please retry after upgrading to something from the 7th or newer and report back.

                    1 Reply Last reply Reply Quote 0
                    • M
                      miken32
                      last edited by

                      @cmb:

                      The latest strongswan release (5.2.1->5.2.2) went into today's snapshots, please retry after upgrading to something from the 7th or newer and report back.

                      Just updated. Tunnel still does not come up on boot, but a subsequent ping test from the pfSense did eventually bring up P1 and P2 successfully. Will do further testing and advise tomorrow, but looks like it's usable now. Thanks a lot!

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

                        Glad to hear. Tunnels never come up unless there is traffic triggering them, or you have the "Automatically ping host" set in the P2, so sounds like that's the expected end result.

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