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

    Accessing IPsec an OpenVPN client

    Scheduled Pinned Locked Moved OpenVPN
    4 Posts 3 Posters 383 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
      mafpbiaggi
      last edited by mafpbiaggi

      Hello everybody, I have a scenario just like this:

      Re: Accessing IPsec branch office from an OpenVPN client

      IPSec Site A to Site B
      OpenVPN Site A, but I need to access Site B

      I already have 2 tunels (Phase2) pointing to correct networks, but I still can't access Site B over OpenVPN.

      The only difference i've found is my NAT Outbounding table. It's MANUAL.

      Can anybody help me with NAT settings? Do I need to assign my OpenVPN interface and create a GW?

      Thanks for now.

      V JKnottJ 2 Replies Last reply Reply Quote 0
      • V
        viragomann @mafpbiaggi
        last edited by

        I assume the OpenVPN is an access server, so have you pushed the route for the site B networks to the clients?

        @mafpbiaggi said in Accessing IPsec an OpenVPN client:

        I already have 2 tunels (Phase2) pointing to correct networks

        Show screenshots, please and provide more details about your networks.

        M 1 Reply Last reply Reply Quote 1
        • JKnottJ
          JKnott @mafpbiaggi
          last edited by

          @mafpbiaggi

          Given that VPN type is irrelevant, you have a routing or filter issue. Once a VPN is up, it's no different than any other IP connection.

          PfSense running on Qotom mini PC
          i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
          UniFi AC-Lite access point

          I haven't lost my mind. It's around here...somewhere...

          1 Reply Last reply Reply Quote 1
          • M
            mafpbiaggi @viragomann
            last edited by

            @viragomann and @JKnott , thanks for the repply, but I already solved the issue. The problem was wrong firewall rules in the other side of the ipsec tunel.

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