Description:

This article describes how a route-based IKEv2 connection can be set up between two LANCOM R&S®Unified Firewalls.

Setting up a policy-based IKEv2 VPN connection between two Unified Firewalls is described in the following knowledge base article:

Setting up a policy-based IKEv2 VPN connection (site-to-site) between two LANCOM R&S®Unified Firewalls (as of LCOS FX 10.4)


The differences between policy-based and route-based IPSec are described in the following Knowledge Base article:

Differences between policy-based and route-based IPSec with LANCOM R&S®Unified Firewalls

Requirements:

 

Scenario:

The Unified Firewalls are connected directly to the Internet and have a public IPv4 address:

If the Unified Firewall uses an upstream LANCOM router to connect to the Internet, then the upstream device has to be set to forward its inbound UDP ports 500 and 4500 to the WAN IP address of the Unified Firewall. If the router is from a different manufacturer, the ESP protocol must also be forwarded to the Unified Firewall.


Procedure:

1) Configuration steps on the Unified Firewall at the headquarters:

1.1) Configuring the VPN connection on the Unified Firewall at the headquarters:

1.1.1) Connect to the configuration interface of the Unified Firewall and go to the menu VPN → IPsec → IPsec Settings.

1.1.2) Enable IPsec using the slider and then click Save.


1.1.3) Go to the menu VPN → IPsec → Connections and click on the “+” icon to create a new IPsec connection.

1.1.4) Modify the following parameters:

If you have created your own template or security profile, you can use it here.

Do not use the ready-made security profile IKEv2 Suite-B-GCM-256 (RFC 6379) as both the IKE and the IPsec lifetime values (SA lifetime) are set to 0. This can lead to connection problems.

1.1.5) Go to the Tunnels tab and modify the following parameters:


1.1.6) Go to the Authentication tab and modify the following parameters:

The local and remote identifiers must not match!

1.1.7) Go to the Routing tab and enable the option Route-based IPsec. Then click Create.


1.2) Create the routing entry for the VPN connection: 

The following steps must be repeated for each additional local or remote network.

1.2.1) Go to the menu Network → Routing → Routing Tables and, in Table 254, click on the “pencil” icon to edit the table.


1.2.2) Click on the “+” icon to create a routing entry.


1.2.3) Modify the following parameters and click OK:


1.2.4) Click Save.


1.2.5) Acknowledge the warning message by clicking Save Anyway.



1.3) Allow communications using firewall rules:

1.3.1) In the menu bar for the desktop objects, click the icon to create a new VPN network.


1.3.2) Modify the following parameters and then click Create:


1.3.3) For the VPN network created in step 1.3.2, click the “connection tool” and then click on the network object for the local network with which you want to communicate via the VPN connection.

Repeat this step for each additional network with which you want to communicate via the VPN connection.


1.3.4) Use the “+” icon to assign the required protocols to the connection, and then click Create.

A Unified Firewall uses a deny-all strategy. You therefore have to explicitly allow communication.

1.3.5) Finally, implement the configuration changes by clicking Activate in the firewall.

1.3.6) This concludes the configuration steps on the Unified Firewall at the headquarters.



2) Configuration steps on the Unified Firewall at the branch office:

2.1) Configuring the VPN connection on the Unified Firewall at the branch office:

2.1.1) Connect to the configuration interface of the Unified Firewall and go to the menu VPN → IPsec → IPsec Settings.

2.1.2) Enable IPsec using the slider and then click Save.

2.1.3) Go to the menu VPN → IPsec → Connections and click on the “+” icon to create a new IPsec connection.

2.1.4) Modify the following parameters:

If you have created your own template or security profile, you can use it here

Do not use the ready-made security profile IKEv2 Suite-B-GCM-256 (RFC 6379) as both the IKE and the IPsec lifetime values (SA lifetime) are set to 0. This can lead to connection problems.

2.1.5) Change to the Tunnels tab and modify the following parameters:

 

2.1.6) Go to the Authentication tab and modify the following parameters:

The local and remote identifiers must not match!

2.1.7) Go to the Routing tab and enable the option Route-based IPsec. Then click Create.



2.2) Create the routing entry for the VPN connection:

2.2.1) Go to the menu Network → Routing → Routing Tables and, in Table 254, click on the “pencil” icon to edit the table.

2.2.2) Click the “+” icon to create a routing entry.


2.2.3) Modify the following parameters and click OK:


2.2.4) Click Save.


2.2.5) Acknowledge the warning message by clicking Save Anyway.



2.3) Allow communications using firewall rules:

2.3.1) In the menu bar for the desktop objects, click the icon to create a new VPN network.

2.3.2) Modify the following parameters and then click Create:

 

2.3.3) For the VPN network created in step 2.3.2, click the “connection tool” and then click on the network object for the local network with which you want to communicate via the VPN connection.

Repeat this step for every network that the branch should be able to access.

2.3.4) Use the “+” icon to assign the required protocols to the connection, and then click Create.

A Unified Firewall uses a deny-all strategy. You therefore have to explicitly allow communication.

2.3.5) Finally, implement the configuration changes by clicking Activate in the firewall.

2.3.6) This concludes the configuration steps on the Unified Firewall at the branch office.


Thank you for your feedback! You can also send us constructive suggestions for improving our knowledge base or ideas for new articles by email to knoweldgebase@lancom.de.