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

    Routing Openvpn Client to Site connections over an IPSEC S2S

    Scheduled Pinned Locked Moved IPsec
    4 Posts 2 Posters 310 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.
    • W
      wspence
      last edited by

      Hello all, I am new to the pfsense community and i have 2 SG-2100's
      Site A 10.10.10.0/24 - has a C2S OpenVPN setup using 10.10.50.0/24
      |
      -=Site to Site IPsec =-
      |
      Site B 10.10.20.0/24

      I have the Site 2 Site connections between site A and B and traffic flowing fine. I also have an OpenVPN setup for Client 2 Site connections attached to Site A

      what i am trying to figure out is how to allow those Client to Site VPN connection to route over the IPSEC connection to allow communication to Site B

      1 Reply Last reply Reply Quote 0
      • V
        viragomann
        last edited by

        Add a phase 2 to the IPSec to connect the site B's LAN with the OpenVPN clients tunnel network.
        So on site B you have
        local network: 10.10.20.0/24
        remote network: 10.10.50.0/24
        and on A the other way round.

        In the OpenVPN access server settings add the site B's LAN to the local networks to push the proper route to the clients.

        Ensure that you have firewall rules allowing that access on all involved interfaces.

        1 Reply Last reply Reply Quote 1
        • W
          wspence
          last edited by wspence

          @viragomann Thank you for the quick reply, i have it setup as the following below but appears to still not be working, i did add the Phase 2 entries as you suggested.

          1 Reply Last reply Reply Quote 0
          • W
            wspence
            last edited by

            @viragomann Actually just did a reboot and it appears to be working now, thank you.

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