Overlapping subnets with IPsec solution

From Teltonika Networks Wiki
Revision as of 16:00, 5 January 2022 by Karolist (talk | contribs) (prep for example config)

(diff) ← Older revision | Approved revision (diff) | Latest revision (diff) | Newer revision → (diff)
Main Page > General Information > Configuration Examples > VPN > Overlapping subnets with IPsec solution

Introduction

This article provides an extensive configuration example with details on how to solve overlapping subnets when using IPsec.

Configuration overview and prerequisites

Prerequisites:

  • Two RUTxxx routers of any type (excluding RUT850)
  • A SIM card with a Public Static or Public Dynamic IP address for the IPsec server
  • An end device (PC, Laptop, Tablet, Smartphone) to configure the routers

Configuration scheme:

Configuration examples ipsec subnet overlapping.png

Router configuration

If you have familiarized yourself with the configuration scheme and have all of the devices in order, we can start configuring the routers using instructions provided in this section.

Basic tunnel


First of, lets configure a simple connection between two IPsec instances, i.e., RUT1 and RUT2.

RUT1 configuration


IPsec1 config.png Ipsec2 config.png

  1. Enable - Enables IPsec instance
  2. Remote endpoint - IP address or hostname of remote IPsec instance, only one side of IPsec needs to have it configured
  3. Pre-shared key - Shared password used for authentication between the peers. The value of this field must match the other instance
  4. Type - select tunnel
  5. Local subnet - Virtual local IP address used to install IPsec tunnel
  6. Remote subnet - Virtual remote IP address used to install IPsec tunnel

RUT2 configuration


Ipsec3 config Overlapping subnets solution example .png Ipsec4 config Overlapping subnets solution example .png

  1. Enable - Enables IPsec instance
  2. Remote endpoint - IP address or hostname of remote IPsec instance, only one side of IPsec needs to have it configured
  3. Pre-shared key - Shared password used for authentication between the peers. The value of this field must match the other instance
  4. Type - select tunnel
  5. Local subnet - Virtual local IP address used to install IPsec tunnel
  6. Remote subnet - Virtual remote IP address used to install IPsec tunnel