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

    Make Remote Location available over VPN

    Scheduled Pinned Locked Moved OpenVPN
    12 Posts 4 Posters 1.1k 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
      conor
      last edited by conor

      9d5879a0-2ebe-4a64-aded-0f8fbfa4d200-image.png

      The above is where in your OpenVPN server settings for your remote VPN users where you need to add your Location 2 subnet.

      Also make sure that if the subnet for the remote VPN users is different from Location 1 & 2 that a firewall rule permits that subnet to pass from location 1 to location 2 and back.

      Also make sure that location 2 has the subnet route for the remote User VPN subnet added to its routing table. Location 2 needs to know how to send the packet back.

      200+ pfSense installs - best firewall ever.

      1 Reply Last reply Reply Quote 1
      • V
        verpfsense
        last edited by

        Thanks for your help.

        So i Setup the following Config:

        IpV4 Local Networks(your screenshot): 192.168.3.0/24,192.168.4.0/24

        Advanced options:
        push "route 192.168.3.0 255.255.255.0";
        push "route 192.168.4.0 255.255.255.0";
        push "dhcp-option DNS 192.168.3.2";

        And setup a Rule VPN Subnet to all but i somehow still cant reach the 4.0/24 subnet any ideas what im missing or see any mistakes?

        DerelictD 1 Reply Last reply Reply Quote 0
        • C
          conor
          last edited by

          What is your users vpn subnet? Is that route set up on Location 2 to point back to Location 1?

          200+ pfSense installs - best firewall ever.

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate @verpfsense
            last edited by

            You do not need to mess about with the advanced options there.

            IpV4 Local Networks(your screenshot): 192.168.3.0/24,192.168.4.0/24

            will already do this:

            push "route 192.168.3.0 255.255.255.0";
            push "route 192.168.4.0 255.255.255.0";
            

            If anything someone will see error messages about not being able to add a route (because it has already been added) confusing them into clicking away to try to fix what isn't really broken in the first place.

            push "dhcp-option DNS 192.168.3.2";
            

            will be added by setting the DNS Servers in the server configuration.

            The main benefit to using the server and client configuration fields instead of Advanced Options is pfSense configuration upgrades can make changes as OpenVPN requires without trying to build an advanced options parser where it will be up to you to track and make changes. It also lets pfSense know what networks might need to be included for things like automatic outbound NAT.

            @conor is on the right track. Location 2 also needs a route back to the tunnel network at Location 1.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 1
            • V
              verpfsense
              last edited by verpfsense

              Thanks for you help, so how do i configure the route from location 2 back to location 1 over vpn?

              I checked and set the Pass rules so all traffic is on vpn is allowed and i also removed advanced options you mentioned.

              Location1 is 192.168.3.0/24
              Location2 is 192.168.4.0/24
              VPN is 10.0.2.0/24 connected to location 1

              C 1 Reply Last reply Reply Quote 0
              • C
                conor @verpfsense
                last edited by

                @vertecpfsense

                At location 2 device.

                Goto: System > Routing > Static Routes

                Click Add

                Destination Network is the VPN off Location 1 network

                Gateway is the interface for the OpenVPN site to site tunnel.

                200+ pfSense installs - best firewall ever.

                1 Reply Last reply Reply Quote 0
                • DerelictD
                  Derelict LAYER 8 Netgate
                  last edited by

                  No.

                  Do NOT use static routes. Let OpenVPN add the routes to the routing table.

                  All you should have to do is add 10.0.2.0/24 to the Remote Networks in the OpenVPN configuration at Location 2.

                  Chattanooga, Tennessee, USA
                  A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                  DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                  Do Not Chat For Help! NO_WAN_EGRESS(TM)

                  1 Reply Last reply Reply Quote 1
                  • H
                    hagak
                    last edited by

                    I am attempting to have basically the same setup as the original poster. Also running into the same issue. I want my users VPN to direct ALL traffic through the vpn. As such you do not get the option to add the routes.

                    However even when I un-select the direct all traffic option and add the network subnets I still have the issue that OpenVPN users can not access the other end of the site-site vpn.

                    1 Reply Last reply Reply Quote 0
                    • DerelictD
                      Derelict LAYER 8 Netgate
                      last edited by

                      So post your configuration and explain exactly what you think should be working that isn't.

                      Be sure the other end of the site-to-site VPN has a route/traffic selector containing the remote access VPN tunnel network.

                      Chattanooga, Tennessee, USA
                      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                      Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

                        So the issue was I had on the far side Block BOGON networks turned on for the LAN interface.

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