IPSec IKEv2 connection with LANCOM

In dieser Seite werden die Variablen für unterschiedliche Sprachen definiert.
Diese Seite wird auf folgenden Seiten eingebunden

• UTM (← liens)

{{var | Remote Host / Gateway ID--pfad

| Authentifizierung → $NAME → Entfernte Identität

Wenn dieser gesetzt wird, muss in jedem Fall auch der lokale Identitätstyp gesetzt werden!

| Authentication → $NAME → Remote identity

If this is set, the local identity type must also be set in any case!}

---

Instructions for setting up an IPSec IKEv2 connection with LANCOM routers

New article: 06.2024

notempty

This article refers to a Beta version

-

Access: UTM-IP:Port or UTM-URL:Port
Port as configured at Network / Appliance Settings / Webserver
Default-Port: 11115
i.e.: https://utm.ttt-point.de:11115
Default: https://192.168.175.1:11115 VPN IPSec

---

Preliminary remark

The following shows how to configure an IPSec IKEv2 connection with LANCOM routers and where to find the relevant settings in the router web interface.

The following local example networks should be accessible via the S2S connection:

Local router network	172.30.0.0/24
Shared UTM networks	172.31.2.0/24 & 192.168.250.0/24

---

Configuration of the UTM

notempty

The connection is set up on the UTM as described in the wiki article IPSec Site-to-Site.
The following configurations are then adjusted:

Phase 1 Edit UTMuser@firewall.name.fqdnVPNIPSec

Fig.1

The following configurations must be adjusted under VPN IPSec Area Connections button Phase 1:

• MOBIKE must be deactivated
• It is also recommended with regard to gateway IDs:
  • with fixed, public IPs on both sides: IP addresses
  • in all other cases: Email addresses

When using an email address as an ID, it is essential to pay attention to the double @ in front of the email address! (Example: @@mail@anyideas.de)

Phase 2 Edit UTMuser@firewall.name.fqdnVPNIPSec

Fig.2

Under VPN IPSec Area Connections button Phase 2 the grouping of subnet combinations must be switched off.

---

Configuration of the LANCOM router

The connection parameters are then configured on the LANCOM router.

To do this, the various data records must first be created. This is done in the web interface of the router, mainly under Configuration → VPN → IKEv2/IPSec, exceptions are the IPv4-Rules and the Routing.

The data records can always be edited by clicking on the name highlighted in blue and new data records can be created using the Add button, which can be found at the bottom center.

Under no circumstances should DEFAULT data records be deleted!

---

Checking/troubleshooting

You can see whether a configured connection has been established in the dashboard in the "VPN" line (scroll down a little if necessary).	[[Datei: ]] Dashboard
In addition, the actions of the router can be tracked under System information → Syslog to identify possible problems.	[[Datei: ]] Syslog

---

Location of relevant settings in the router web interface

The following table shows where the settings known from the UTM can be configured in the web interface of the Lancom router. notempty $NAME is a placeholder for the name of a data record that must be opened by clicking on it.
Phase 1 General General
Bezeichnung Securepoint UTM	Bezeichung Lancom
Local Gateway	No suitable counterpart available
Local Gateway ID	Configuration → VPN → IKEv2/IPSec → Authentication → $NAME → Local identity If this is set, the remote identity type must also be set in any case!
Remote Host / Gateway	Configuration → VPN → IKEv2/IPSec → Connection list → $NAME → Remote gateway
Remote Host / Gateway ID	Configuration → VPN → IKEv2/IPSec →
Authentication method	Configuration → VPN → IKEv2/IPSec → Authentication → $NAME → Local authentication Configuration → VPN → IKEv2/IPSec → Authentication → $NAME → remote authentication
Pre-Shared Key	Configuration → VPN → IKEv2/IPSec → Authentication → $NAME → Local password Configuration → VPN → IKEv2/IPSec → Authentication → $NAME → Remote password
Starting behavior: Incoming	Configuration → VPN → IKEv2/IPSec → Connection list → $NAME → Hold time: 0
Starting behavior: Outgoing	Configuration → VPN → IKEv2/IPSec → Connection list → $NAME → Hold time: 9999
Dead Peer Detection / DPD Interval	Configuration → VPN → IKEv2/IPSec → Connection-parameters → $NAME → Dead Peer Detection
IKE IKE
Encryption	Configuration → VPN → IKEv2/IPSec → Encryption → $NAME → IKE-SA encryption list
Authentication	Configuration → VPN → IKEv2/IPSec → Encryption → $NAME → IKE-SA hash list
Diffie-Hellman Group	Configuration → VPN → IKEv2/IPSec → Encryption → $NAME → Allowed DH groups
IKE Lifetime	Configuration → VPN → IKEv2/IPSec → Validity period → $NAME → IKE SA
Phase 2 General General
Encryption	Configuration → VPN → IKEv2/IPSec → Encryption → $NAME → Child-SA encryption list
Authentication	Configuration → VPN → IKEv2/IPSec → Encryption → $NAME → Child-SA hash list
DH Group (PFS)	Configuration → VPN → IKEv2/IPSec → Encryption → $NAME → Allowed DH groups → PFS: Yes
Key service life	Configuration → VPN → IKEv2/IPSec → Validity period → $NAME → Child SA
Subnet Subnet
Local network	Configuration → VPN → General → IPv4 rules → $NAME → Remote networks
Remote network	Configuration → VPN → General → IPv4 rules → $NAME → Local networks
notempty Local on one side is always remote on the other side!