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

    2.5.1 VPN fix for those with virtual IP.

    Scheduled Pinned Locked Moved IPsec
    3 Posts 2 Posters 654 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.
    • D
      draconpern
      last edited by

      This is a better fix to my old post.

      I upgraded from 2.4.x to 2.5.1 and found all my vpn connections broken. To fix in your Phase 1, change 'My identifier' from 'My IP Address' to 'IP Address' and enter a real ip address.

      long story: after doing swanctl --list-conns I realized that the local ip of the connection was set to a virtual ip for the WAN port. So no wonder ike didn't find a corresponding config. Sure enough /var/etc/ipsec/swanctl.conf listed a different ip even though config.xml is using 'wan'.
      The issue is the local address of WAN in /var/etc/ipsec/swanctl.conf file is being filled with the first ipaddress in ifconfig, not from a config file. So if you have virtual ip on your WAN connection, your vpn may or may not work depending on the order in which ip addresses are being applied to your interface.

      M 1 Reply Last reply Reply Quote 0
      • M
        mfld LAYER 8 @draconpern
        last edited by

        @draconpern could this be related to this bug ?

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

        D 1 Reply Last reply Reply Quote 0
        • D
          draconpern @mfld
          last edited by

          @mfld It is indeed!

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