For backwards compatibility with most L2TP/IPsec VPN servers out there, network-manager-l2tp 1.2.16 no longer uses the strongSwan and libreswan default set of allowed algorithms, instead algorithms that are a merge of Windows 10 and macOS/iOS/iPadOS L2TP/IPsec clientsâ IKEv1 proposals are used instead. The weakest proposals that were not common to both Win10 and iOS were dropped, but all of the strongest ones were kept.
So I suspect youâll have more luck with the newer version.
Update to ânetwork-manager-l2tp 1.2.16â as advised
Tried to connect.
However, the following error appears and the connection cannot be made.
$ sudo / usr / lib / NetworkManager / nm-l2tp-service --debug
nm-l2tp [xxxx] nm-l2tp-service (version 1.2.16) starting âŠ
nm-l2tp [xxxx] uses default --bus-name âorg.freedesktop.NetworkManager.l2tpâ
:
generating QUICK_MODE request xxx [HASH SA No KE ID ID NAT-OA NAT-OA]
sending packet: from yyy.yyy.yyy.yyy [4500] to xxx.xxx.xxx.xxx [4500] (xxx bytes)
received packet: from xxx.xxx.xxx.xxx [4500] to yyy.yyy.yyy.yyy [4500] (xxx bytes)
parsed QUICK_MODE response xxx [HASH SA No KE ID ID NAT-OA NAT-OA]
received netlink error: Function not implemented (38)
unable to add SAD entry with SPI xxx (FAILED)
From the error message
For example, the kernel does not support encryption
Is it the cause?
I canât see the âreceived proposalsâ log output which has the list of Quick Mode proposals offered by the VPN server. Looks like your kernel canât handle one of the selected proposals. I canât tell from that snippet of log output which one.
Youâll need to manually enter the Phase 2 Algorithms in the IPsec Option dialog box based on the received proposals till you get a combination that works with your kernel. It is currently set to the following default internally:
aes256-sha1,aes128-sha1,3des-sha1!
you might like to first try entering the above without aes256-sha1, then if it doesnât work, only keep 3des-sha1!.
but if the received proposals has others that werenât in the default I mentioned, you can see the keywords for all strongswan algorithms on the following page:
Forgot to mention, you might also want to check you have the crypto plugin packages installed, e.g. libstrongswan-standard-plugins and libstrongswan-extra-plugins.
3des-sha1!
parsed INFORMATIONAL_V1 request 158090692 [HASH N (NO_PROP)]
received NO_PROPOSAL_CHOSEN error notify
2.aes256-sha1, aes128-sha1,3des-sha1!
received packet: from xxx.xxx.xxx.xxx [4500] to yyy.yyy.yyy.yyy [4500] (xxx bytes)
parsed QUICK_MODE response xxxxx [HASH SA No ID ID NAT-OA NAT-OA]
selected proposal: ESP: AES_CBC_128 / HMAC_SHA1_96 / NO_EXT_SEQ
received netlink error: Protocol not supported (93)
unable to add SAD entry with SPI xxx (FAILED)
received netlink error: Protocol not supported (93)
unable to add SAD entry with SPI xxx (FAILED)
unable to install inbound and outbound IPsec SA (SAD) in kernel
establishing connection âxxxâ failed
Looking at the results, â2.â seems to be the correct setting
âProtocol not supported (93)â and the connection could not be established.
This was because the kernel module needed by strongswan was insufficient.
I enabled the following settings and built a kernel to make an L2TP IPsec connection.
below setting at .config
CONFIG_INET_AH = y
CONFIG_INET_ESP = y
CONFIG_INET_IPCOMP = y
Thank you for various advice.
It was very helpful.