NetworkManager failed to connect: 'Timeout was reached' (Manjaro) #220
Comments
|
I see bypass policy in the logs, unlike many other Linux distros, Manjaro enables experimental strongswan plugins that can be problematic, try to disable loading them with: You will also need to reboot as kernel modules used by some of the strongswan plugins might also be loaded. |
|
I have the same issue when I try to connect to a VPN. My colleagues don't have this problem on other distros. I'm pretty sure that my VPN connection settings are correct. |
|
I don't currently have a VM with either Manjaro or Arch Linux. As they are cutting edge distros, they are typically the distros that first encounter issues with kernel updates that break the L2TP kernel modules and have issues with changes to NetworkManger. I'll try and spin one up this week. One other thing I forgot to suggest is that the following services should be stopped and preferably disabled :.
Some Arch Linux doco for L2TP suggests running the strongswan service, but they most definitely should not be run as NetworkManger is not compatible with it. It is compatible with strongswan-starter, but there is no need to have it running. NetworkManger-l2tp starts its own instance of strongwan, so doesn't need either of the above two services. Although I don't think these strongswan services are an issue in these cases. |
|
Regarding the 10 second timeout, that is not something from this repository, the IPsec connection has a 16 sec timeout as does the xl2tpd/pppd connection: NetworkManager-l2tp/src/nm-l2tp-service.c Lines 92 to 93 in 8760535 From memory, NetworkManager had a 50 second timeout for VPN connections, maybe it has been reduced on Manjaro? I'm not about to reproduce as my VPN connection takes less than 10 seconds. |
|
@dkosovic Thank you for your assistance. I've checked that the source code of nm and nm-l2tp is taken directly from their actual repositories and has no mentions related to "timeout" in pacman build configuration(even if this parameters don't exist). I think this issue can be closed as it's not related to nm directly. |
|
You could try replacing strongswan with libreswan from AUR : It is built with But from the libreswan AUR comments, looks like there are some issues with building/running it at the moment and there are some workarounds. Hopefully libreswan might be quicker in connecting. |
|
I didn't mention it, but I have tried both strongswan and libreswan. The result was the same. I want to try to build strongswan with increased timeout. |
|
I'll leave this issue open in case other Manjaro and Arch Linux users come along with the same issue, that way they know something is wrong. |
|
This is where the In that warning, it looks like
|
|
You could use strongswan on the command-line with the generated ipsec config file for further debugging and for removing NetworkManager from the equation. The below ( If strongswan isn't able to connect, you could post the ipsec.conf file contents and the command-line output to the strongswan issues page: They might be able to help you resolve the issue. |
As I'm jealous of my colleague who uses the l2tp connection on his Linux Mint machine successfully, I gave it a try on two different Manjaro systems.
I installed
networkmanager-l2tpandstrongswan:Created a new
l2tpconnection entry with the network manager, which resulted in thisnmconnectionfile:When trying to connect using this connection,
journalctl -f -u NetworkManager.servicegives:Looks like there is a
10 stimeout indicated by this line:Does anybody have a clue where the problem is?
The text was updated successfully, but these errors were encountered: