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

    Route traffic to specific IP over a separate VPN tunnel

    OpenVPN
    2
    2
    634
    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.
    • R
      rterren
      last edited by

      Hi

      I'm hoping someone can figure this out.

      I have two colo locations each with their own public facing IP's, each protected by a pfsense.  They are also connected via an internal dark fiber connection provided by the datacenter company, one location is my DR.

      Since I have this internal link I configured both locations to use the same IP space 10.0.0.0/24.  My VPN connection to the main colo is secured with a shared key.

      I want to create a second connection which takes all traffic destined for a specific jump host at 10.0.0.70 and sends it over a separate 2nd VPN connection to the external IP in DR.  I want this to act as my backdoor into the DR

      So effectively I have the following

      10.0.0.1 colo
      10.0.0.2 dr
      10.0.0.0/24 both sites
      10.0.0.70 for the VPN going to the external IP of the DR

      Is there any way in which to do this?

      The reason for using the same IP range in each was because when I had different ranges at each end the datacenter dark link was very slow as it tried to route traffic.  Before having VPN configured I would just RDP across the public internet to exposed RDP servers (AWFUL!! lol)

      Thank you

      Ron

      1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator
        last edited by

        "10.0.0.70 for the VPN going to the external IP of the DR"

        This is confusing me..

        So you have an extended layer 2 via dark fiber that is using the same network 10.0.0/24  See below drawing.

        Why would you not just use a vpn into location A, and another Vpn into local B.  If you source natted your vpn connection then you be able to access whatever you wanted on your extended vlan no matter what vpn you were connected to..  So if vpn A is down, you just vpn into vpn B.

        The use of source nat so you either look like .1 or .2 would remove the need of host routing or any sort of hairpin issues..  If you don't want to source nat then your devices on your 10.0.0 network would need host routing to know who to talk to .1 or .2 depending on the tunnel network your using on each vpn connection.

        extendedvlan-darkfiber.png_thumb
        extendedvlan-darkfiber.png

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.7.2, 24.11

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