-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NetworkManager[pid]: xl2tpd[pid]: Maximum retries exceeded for tunnel [number]. Closing. #189
Comments
I'm not sure which version of NetworkManager you are using, but if it is >= 1.36 you might be experiencing one of the routing bugs introduced with the newer NetworkManager. e.g. spurious route with no metric (i.e. metric 0) and/or spurious IP address. See: |
NetworkManager --version I tried setting "ipv4.ignore-auto-routes" to yes / no Still behaves exactly the same. Routing table before bringing up the connection:
After bringing up the connection:
|
Regarding the sudo sed -e '/blacklist l2tp_netlink/s/^b/#b/g' -i /etc/modprobe.d/l2tp_netlink-blacklist.conf
sudo sed -e '/blacklist l2tp_ppp/s/^b/#b/g' -i /etc/modprobe.d/l2tp_ppp-blacklist.conf See the following for more details: |
I dont have those files:
I dont have those modules (l2tp_ppp, l2tp_netlink) in Linux 5.10.104 kernel. I loaded that module and got same results |
On RedHat and Fedora the L2TP kernel modules are in the kernel-modules-extra package (PPPoX isn't specifically PPP over L2TP, but does provide support for the l2tp_ppp kernel module to do so). Not sure if there other Linux distros that don't package the L2TP kernel modules in the main kernel package. Theses are the L2TP kernel modules I see after xl2tpd is run with NetworkManager-l2tp : $ lsmod | grep l2tp
l2tp_ppp 28672 0
l2tp_netlink 28672 1 l2tp_ppp
l2tp_core 32768 2 l2tp_ppp,l2tp_netlink
pppox 16384 1 l2tp_ppp
ppp_generic 45056 2 pppox,l2tp_ppp
ip6_udp_tunnel 16384 1 l2tp_core
udp_tunnel 16384 1 l2tp_core I was also going to suggest trying go install "github.com/katalix/go-l2tp/...@latest"
sudo mkdir /usr/local/sbin
sudo cp go/bin/kl2tpd /usr/local/sbin NetworkManager-l2tp will use kl2tpd by default and fall back to xl2tpd if it can't find kl2tpd. |
Thing is that once the connection is made it works perfectly fine .. for 20 seconds. Question is - how do I debug this and figure the cause ? log doesn't seem to provide any information. |
Well, I got the connection to last much longer with this disgusting hack (not my finest work ever):
I hope this helps somebody |
Thanks for the bug report. I've added an Will look into adding a GUI option in the future. |
Connection is lost after about 20 seconds after being up and working.
When I bring up the connection with "nmcli c up vpn":
At this point the connection is working just fine, but after about 20 seconds I get this:
StrongSwan 5.9.2
nm-l2tp 1.20.4
xl2tpd 1.3.14
Connection configuration file:
The text was updated successfully, but these errors were encountered: