Description:
In 2019 the IETF (Internet Engineering Task Force) has designated IKEv1 as deprecated and insecure and therefore it should not be used anymore. LANCOM Systems instead recommends to use the current standard IKEv2.
The IKEv1 functionality in LANCOM devices remains intact and can still be used for scenarios where devices without IKEv2 support are used. However LANCOM Systems will not provide any support regarding the troubleshooting of connection problems with IKEv1 connections. Also there won't be any bug fixes or new features for IKEv1.
In rare cases a disconnect can occur during rekeying. In such a case it can be useful to increase the lifetimes, so that the disconnects occur less often.
The configuration of an IPv6 based IKEv2 connection between two LANCOM routers with IPv6 Internet connection is described in this Knowledge Base article.
Requirements:
- LCOS as of version 9.20 (download latest version)
- LANtools as of version 9.20 (download latest version)
Scenario:
- A company wishes to interconnect the local IPv6 networks at their headquarters and at a branch office by means of an IKEv1 site-to-site VPN connection.
- Both sites have a LANCOM router as their gateway and an Internet connection with a public IPv6 address. The public IPv6 address of the Headquarters is fd00::a, and the branch office is fd00::b.
- The VPN connection is established from the branch office to the headquarters.
- The local IPv6 network at the headquarters has the IP address range 2001:db8:a::/64, and the branch office uses the local IPv6 address range 2001:db8:b::/64.


From the list of proposals, the first IKE proposal that matches at both ends of the VPN connection is used to establish the IKE Phase 1.

From the list of proposals, the first IPSec proposal that matches at both ends of the VPN connection is used to establish the IPSec Phase 2.

- Name: Enter the name here.
- Local identifier type: Select the identifier type used on the router at the headquarters. In this example, the identity type was set to E-Mail address (FQUN) .
- Local identifier: Set the local identifier. In this example, the LANCOM router at the headquarters uses the local identity headquarter@test.de.
- Remote identifier type: Select the identifier type used on the router at the branch office. In this example, the identity type was set to E-mail address (FQUN).
- Remote identifier: Set the remote identifier. In this example, the LANCOM router at the branch office uses the remote identity office@test.de.

- Enable the VPN feature of the LANCOM router.
- Set the option Establ. of net relationships (SAs) to the value Collectively with KeepAlive.



- The LANCOM router at the headquarters will be accepting the VPN connection, so the value for the short-hold time must be set to 0 seconds here.
- The Dead Peer Detection is used for monitoring the VPN connection. Enter the value of 60 seconds here. For more information about the Dead Peer Detection, see the following KnowledgeBase article
.
- In the field for the remote Gateway, you need to enter the public IPv6 address of the LANCOM router at the branch office. In this example it is fd00::b.
- Set the Connection parameters to OFFICE.
- The Rule creation is carried out automatically in this example.
- The IKE exchange mode needs to be set to the option Main mode.


- As the IPv6 address, enter the address of the local IPv6 network at the branch office. In this example it is 2001:db8:b: : /64.
- For the Router field, select the identification of the VPN remote station (in this case: OFFICE).



This firewall rule is required in order for data transmission via the VPN connection from the remote station (in this case OFFICE) to be allowed.
- Set the Priority to the value 1.
- Set the Action to ACCEPT.
- In the field Server services, set the object to ANY.
- In the field Source stations, enter the name of the VPN connection to the office.

Make sure that the same IKE proposals are entered into this list as those used by the LANCOM router at the headquarters (see step 1.3).
2.4) Click the IPSec proposal lists button.

Make sure that the same IPSec proposals are entered into this list as those used by the LANCOM router at the headquarters (see step 1.5).
2.6) Click the IKE keys and identities button.

- Name: Enter the name here.
- Local identifier type: Select the identifier type used on the router at the headquarters. In this example, the identity type was set to E-mail address (FQUN).
- Local identifier: Set the local identifier. In this example, the LANCOM router at the branch office uses the local identity office@test.de.
- Remote identifier type: Select the identifier type used on the router at the branch office. In this example, the identity type was set to E-mail address (FQUN).
- Remote identifier: Set the remote identifier. In this example, the LANCOM router at the headquarter uses the remote identity headquarter@test.de.

- Enable the VPN feature of the LANCOM router.
- Set the option Establ. of net relationships (SAs) to the value Collectively with KeepAlive.



- The LANCOM router at the branch office will be actively establishing the VPN connection to the headquarters, so the value for the short-hold time must be set to 9,999 seconds here.
- The Dead Peer Detection is used for monitoring the VPN connection. Enter the value of 60 seconds here.
- In the field for the remote Gateway, you need to enter the public IP address of the LANCOM router at the HEADQUARTERS. In this example it is fd00::a.
- Set the Connection parameters to HEADQUARTER.
- The Rule creation is carried out automatically in this example.
- The IKE exchange mode needs to be set to the option Main mode.


- As the IPv6 address, enter the address of the local IPv6 network at the headquarters. In this example it is 2001:db8:a::/64.
- For the Router field, select the identification of the VPN remote station (in this case: HEADQUARTERS).



This firewall rule is required in order for data transmission via the VPN connection from the remote station (in this case HEADQUARTERS) to be allowed.
- Set the Priority to the value 1.
- Set the Action to ACCEPT.
- In the field Server services, set the object to ANY.
- In the field Source stations, enter the name of the VPN connection to the headquarters.

If problems occur during connection establishment, or if the established VPN connection does not work properly, a VPN Status Trace can help with the diagno sis. Information is available in this Knowledge Base article .