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

    IPsec mobile client problems: no virtual IP found for %any …

    Scheduled Pinned Locked Moved 2.2 Snapshot Feedback and Problems - RETIRED
    24 Posts 4 Posters 14.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.
    • C
      charliem
      last edited by

      @ermal:

      Well try using a different subnet for the rightsourceip rather than peer ip address.

      SAD and SPD entries can be created if I comment out 'rightsubnet=192.168.3.0/24' from ipsec.conf (not sure that's possible with the current webgui code).  But I still cannot pass any traffic through the tunnel.

      I will start from scratch and take a close look over the weekend, thanks.

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

        This strongswan bug https://wiki.strongswan.org/issues/586 was properly rejected because it was not a strongswan issue, but rather a FreeBSD 10.0 issue.

        Symptoms seem to match what I'm seeing … Was or is this a valid bug?  I can't immediately find a similar patchset in FreeBSD sources, but I can't believe a bug like this would still be around.

        1 Reply Last reply Reply Quote 0
        • H
          hege
          last edited by

          FYI:

          i have the same issue.
          https://forum.pfsense.org/index.php?topic=81657.msg446613#msg446613

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

            @charliem:

            This strongswan bug https://wiki.strongswan.org/issues/586 was properly rejected because it was not a strongswan issue, but rather a FreeBSD 10.0 issue.

            Symptoms seem to match what I'm seeing … Was or is this a valid bug?  I can't immediately find a similar patchset in FreeBSD sources, but I can't believe a bug like this would still be around.

            The fix is already present in FreeBSD 10 afaik.
            So that patch is already merged!

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