Domnev: Difference between revisions

Revision as of 10:51, 22 March 2023

The information on this page is updated in accordance with the 00.07.4 firmware version .

Introduction

Configuration overview and prerequisites

Before we begin, let's take a look at the configuration that we are attempting to achieve and the prerequisites that make it possible.

Prerequisites:

Two RUT/RUTX series routers with RUTOS firmware;
An end device (PC, Laptop) for configuration;

If you're having trouble finding any page or some of the parameters described here on your device's WebUI, you should turn on "Advanced WebUI" mode. You can do that by clicking the "Basic" button under "Mode," which is located at the top-right corner of the WebUI.

Topology

RUT1 - RUTX12 as a hub. A hub is a server, to which our spoke will be connecting (IPsec responder). It will be our "default gateway" for the spoke device. RUTX12 has a LAN subnet of 192.168.11.0/24 configured on it, which should be reachable by the spoke.

RUT2 - RUT955 as a spoke. A spoke is a client, that will be connected to the spoke (IPsec initiator). It will be connected to a hub for basic internet access. RUT955 has a LAN subnet of 192.168.9.0/24 configured on it.

RUT1 (Hub) configuration

Start by configuring the hub (RUT1) device. Login to the WebUI, navigate to Services → VPN → IPsec and add a new IPsec instance. Configure everything as follows.

Note: Not specified fields can be left as is or changed according to your needs.

Instance configuration


Enable instance; Authentication method - Pre-shared key; Pre-shared key - your desired password;

Connection configuration


Mode - Start; Type - Tunnel; Local subnet - 0.0.0.0/.0; Key exchange - IKEv2;


Enable Local firewall; Remote source IP - 10.20.30.0/24; Remote DNS 9.9.9.9;

Proposal configuration


Encryption - AES256; Authentication - SHA512; DH group - ECP521;


Encryption - AES128; Authentication - SHA256; DH group - ECP521;

RUT2 (Spoke) configuration

Login to the RUT2 WebUI, navigate to Services → VPN → IPsec and add a new IPsec instance. Configure everything as follows.

Instance configuration


Enable instance; Remote endpoint - RUT1 public IP; Authentication method - Pre-shared key; Pre-shared key - the same password you have set on RUT1 when configuring HUB instance;

Connection configuration


Mode - Start; Type - Tunnel; Enable default route; Key exchange - IKEv2;

Proposal configuration


Encryption - AES256; Authentication - SHA512; DH group - ECP521;


Encryption - AES128; Authentication - SHA256; DH group - ECP521;

Testing the configuration

After we establish the tunnel, we may observe the following information:

RUT1 (Hub) side

ipsec status all

root@Teltonika-RUTX12:~# ipsec statusall
Status of IKE charon daemon (strongSwan 5.9.2, Linux 5.4.231, armv7l):
  uptime: 74 minutes, since Mar 21 08:52:39 2023
  worker threads: 11 of 16 idle, 5/0/0/0 working, job queue: 0/0/0/0, scheduled: 2
  loaded plugins: charon aes des sha2 sha1 md4 md5 random nonce x509 revocation constraints pubkey pkcs1 pkcs8 pgp pem openssl gmp xcbc hmac kernel-netlink socket-default stroke vici updown eap-identity eap-mschapv2 xauth-generic
Virtual IP pools (size/online/offline):
  10.20.30.0/24: 254/1/0
Listening IP addresses:
  84.xxx.xxx.xxx
  192.168.11.1
  fd93:51e6:6fe8::1
Connections:
   HUB-HUB_c:  %any...%any  IKEv2
   HUB-HUB_c:   local:  uses pre-shared key authentication
   HUB-HUB_c:   remote: uses pre-shared key authentication
   HUB-HUB_c:   child:  0.0.0.0/0 === dynamic TUNNEL
Security Associations (1 up, 0 connecting):
   HUB-HUB_c[2]: ESTABLISHED 74 minutes ago, 84.xxx.xxx.xxx[84.xxx.xxx.xxx]...88.xxx.xxx.xxx[192.168.86.197]
   HUB-HUB_c[2]: IKEv2 SPIs: ded11f31c20352dc_i 58ebc8d96264c21e_r*, pre-shared key reauthentication in 89 minutes
   HUB-HUB_c[2]: IKE proposal: AES_CBC_256/HMAC_SHA2_512_256/PRF_HMAC_SHA2_512/ECP_521
   HUB-HUB_c{3}:  INSTALLED, TUNNEL, reqid 1, ESP in UDP SPIs: c27cb140_i c7382615_o
   HUB-HUB_c{3}:  AES_CBC_128/HMAC_SHA2_256_128/ECP_521, 215536 bytes_i (1981 pkts, 1s ago), 126021 bytes_o (499 pkts, 1s ago), rekeying in 14 minutes
   HUB-HUB_c{3}:   0.0.0.0/0 === 10.20.30.1/32

 /tmp/ipsec/ipsec.conf

root@Teltonika-RUTX12:~# cat /tmp/ipsec/ipsec.conf
# generated by /etc/init.d/ipsec
version 2

conn HUB-HUB_c
  left=%any
  right=%any
  leftfirewall=yes
  rightfirewall=no
  ikelifetime=3h
  lifetime=1h
  margintime=9m
  keyingtries=3
  dpdaction=none
  dpddelay=30s
  dpdtimeout=90s
  leftauth=psk
  rightauth=psk
  rightsourceip=10.20.30.0/24
  auto=start
  leftsubnet=0.0.0.0/0
  rightdns=9.9.9.9
  aggressive=no
  forceencaps=no
  type=tunnel
  keyexchange=ikev2
  esp=aes128-sha256-ecp521!
  ike=aes256-sha512-ecp521!

RUT2 (Spoke) side

root@Teltonika-RUT955:~# ipsec statusall
Status of IKE charon daemon (strongSwan 5.9.2, Linux 5.4.229, mips):
  uptime: 23 hours, since Mar 20 12:21:06 2023
  worker threads: 11 of 16 idle, 5/0/0/0 working, job queue: 0/0/0/0, scheduled: 9
  loaded plugins: charon aes des sha2 sha1 md4 md5 random nonce x509 revocation constraints pubkey pkcs1 pkcs8 pgp pem openssl gmp xcbc hmac kernel-netlink socket-default stroke vici updown eap-identity eap-mschapv2 xauth-generic
Listening IP addresses:
  192.168.86.197
  192.168.9.1
  fd35:98cd:61f0::1
Connections:
passth_SPOKE_ph2_1_lan:  %any...%any  IKEv1/2
passth_SPOKE_ph2_1_lan:   local:  uses public key authentication
passth_SPOKE_ph2_1_lan:   remote: uses public key authentication
passth_SPOKE_ph2_1_lan:   child:  192.168.9.0/24 === 192.168.9.0/24 PASS
SPOKE-SPOKE_c:  %any...84.xxx.xxx.xxx IKEv2
SPOKE-SPOKE_c:   local:  uses pre-shared key authentication
SPOKE-SPOKE_c:   remote: [84.xxx.xxx.xxx] uses pre-shared key authentication
SPOKE-SPOKE_c:   child:  dynamic === 0.0.0.0/0 TUNNEL
Shunted Connections:
passth_SPOKE_ph2_1_lan:  192.168.9.0/24 === 192.168.9.0/24 PASS
Security Associations (1 up, 0 connecting):
SPOKE-SPOKE_c[431]: ESTABLISHED 77 minutes ago, 192.168.86.197[192.168.86.197]...84.xxx.xxx.xxx[84.xxx.xxx.xxx]
SPOKE-SPOKE_c[431]: IKEv2 SPIs: ded11f31c20352dc_i* 58ebc8d96264c21e_r, pre-shared key reauthentication in 77 minutes
SPOKE-SPOKE_c[431]: IKE proposal: AES_CBC_256/HMAC_SHA2_512_256/PRF_HMAC_SHA2_512/ECP_521
SPOKE-SPOKE_c{14}:  INSTALLED, TUNNEL, reqid 1, ESP in UDP SPIs: c7382615_i c27cb140_o
SPOKE-SPOKE_c{14}:  AES_CBC_128/HMAC_SHA2_256_128/ECP_521, 136768 bytes_i (536 pkts, 6s ago), 235975 bytes_o (2169 pkts, 1s ago), rekeying in 13 minutes
SPOKE-SPOKE_c{14}:   10.20.30.1/32 === 0.0.0.0/0

root@Teltonika-RUT955:~# cat /tmp/ipsec/ipsec.conf
# generated by /etc/init.d/ipsec
version 2

conn passth_SPOKE_ph2_1_lan
  type=passthrough
  leftsubnet=192.168.9.1/24
  rightsubnet=192.168.9.1/24
  auto=route

conn SPOKE-SPOKE_c
  left=%any
  right=84.xxx.xxx.xxx
  leftsourceip=%config
  leftfirewall=yes
  rightfirewall=no
  ikelifetime=3h
  lifetime=1h
  margintime=9m
  keyingtries=3
  dpdaction=none
  dpddelay=30s
  dpdtimeout=90s
  leftauth=psk
  rightauth=psk
  rightsubnet=0.0.0.0/0
  auto=start
  aggressive=no
  forceencaps=no
  type=tunnel
  keyexchange=ikev2
  esp=aes128-sha256-ecp521!
  ike=aes256-sha512-ecp521!

@@ Line 1: / Line 1: @@
-<p style="color:red">The information in this page is updated in accordance with [https://wiki.teltonika-networks.com/view/FW_%26_SDK_Downloads'''00.07.4'''] firmware version .</p>
+<p style="color:red">The information on this page is updated in accordance with the [https://wiki.teltonika-networks.com/view/FW_%26_SDK_Downloads'''00.07.4'''] firmware version .</p>
 ==Introduction==
@@ Line 15: / Line 15: @@
 ==Topology==
-RUT1 - RUTX11 as a hub. It will be our "default gateway" for spoke device. RUTX11 has a LAN subnet of 192.168.11.0/24 configured on it, which should be reachable by the spoke.
+'''RUT1''' - RUTX12 as a '''hub'''. A hub is a server, to which our spoke will be connecting (IPsec responder). It will be our "default gateway" for the spoke device. RUTX12 has a LAN subnet of 192.168.11.0/24 configured on it, which should be reachable by the '''spoke'''.
-RUT2 - RUT955 as a spoke. It will be connecting to a hub for basic internet access. RUT955 has a lan subnet of 192.168.9.0/24 configured on it, which should be reachable by the hub.
+'''RUT2''' - RUT955 as a '''spoke'''. A spoke is a client, that will be connected to the spoke (IPsec initiator). It will be connected to a '''hub''' for basic internet access. RUT955 has a LAN subnet of 192.168.9.0/24 configured on it.
 ==RUT1 (Hub) configuration==
-Start by configuring HUB (RUT1) device. Login to the WebUI, navigate to '''Services → VPN → IPsec''' and add a new IPsec instance. Configure everything as follows.
+Start by configuring the hub (RUT1) device. Login to the WebUI, navigate to '''Services → VPN → IPsec''' and '''add a new IPsec instance'''. Configure everything as follows.
-'''Note:''' '''''Not specified fields can be left as-is or changed according to your needs.'''''
+'''Note:''' '''''Not specified fields can be left as is or changed according to your needs.'''''
 ===Instance configuration===
 ----
@@ Line 105: / Line 105: @@
 ==RUT2 (Spoke) configuration==
-Login to the RUT2 WebUI, navigate to '''Services → VPN → IPsec''' and add a new IPsec instance. Configure everything as follows.
+Login to the RUT2 WebUI, navigate to '''Services → VPN → IPsec''' and '''add a new IPsec instance.''' Configure everything as follows.
 ===Instance configuration===
 ----
@@ Line 141: / Line 141: @@
 </table>
-===Proposalconfiguration===
+===Proposal configuration===
 ----
 <table class="nd-othertables_2">
@@ Line 172: / Line 172: @@
 </table>
-==Testing configuration==
+==Testing the configuration==
 After we establish the tunnel, we may observe the following information:
 ===RUT1 (Hub) side===

Domnev: Difference between revisions

Revision as of 10:51, 22 March 2023

Introduction

Configuration overview and prerequisites

Topology

RUT1 (Hub) configuration

Instance configuration

Connection configuration

Proposal configuration

RUT2 (Spoke) configuration

Instance configuration

Connection configuration

Proposal configuration

Testing the configuration

RUT1 (Hub) side

RUT2 (Spoke) side

See also

External links