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

    IPSEC using CARP IP error

    IPsec
    2
    6
    1.1k
    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.
    • E
      emil
      last edited by

      Is there a known problem with IPSEC VPN?

      When I use CARP IP for IPSEC tunnel wont come ip and receive this error: there is no IKE config found, and ERROR: notification NO-PROPOSAL-CHOSEN received in unencrypted informational exchange.
      If I use WAN interface address all is good and tunnel is up. How should I make it work on CARP interface? Thanks.

      1 Reply Last reply Reply Quote 0
      • dotdashD
        dotdash
        last edited by

        Did you check the identifier per this post?
        https://forum.pfsense.org/index.php?topic=91107.0

        1 Reply Last reply Reply Quote 0
        • E
          emil
          last edited by

          Yes I did. But not luck.  :-\

          1 Reply Last reply Reply Quote 0
          • dotdashD
            dotdash
            last edited by

            I'm running a Tunnel from 2.2.1 on an CARP to a 2.15 on a CARP right now, didn't change the identifier from 'My IP address'
            Works fine. I did make sure prefer old SAs was off (set to 0, per the sticky)

            1 Reply Last reply Reply Quote 0
            • E
              emil
              last edited by

              I have reconfigure it and now it works. Only issue I have is that I am not able communicate over OPT1 interface that I want to use for pfSync, no ping or any traffic passing. I had to use LAN interface for pfsync and all is good and than CARP is working. Any idea why OPT1 on pfsense1 is not able to ping OPT1 in pfsense2 if they are on the same network? Odd. I am running those two pfsense VMs on Hyper-V 2012R2.

              1 Reply Last reply Reply Quote 0
              • E
                emil
                last edited by

                I was able to fix the issue by removing virtual network adapter for VM in hyper-v and add new one. After that all works. For some reason OPT1 was using difference MAC address than virtual NIC assigned in hyper-v. All is good now and working correctly.

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