Skip to content
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

L2TP disconnects after timeout on Alpine Linux 3.8 #208

Open
jayavanth opened this issue Sep 28, 2020 · 1 comment
Open

L2TP disconnects after timeout on Alpine Linux 3.8 #208

jayavanth opened this issue Sep 28, 2020 · 1 comment

Comments

@jayavanth
Copy link

jayavanth commented Sep 28, 2020

After about 10-20 mins of idle time, xl2tp disconnects and therefore VPN disconnects. I saw right after it disconnected that the file /var/run/xl2tpd/l2tp-control was empty

When I populated the file with echo "c myvpn" > /var/run/xl2tpd/l2tp-control, the VPN connected again.

Who is writing into that file? Why is that file empty after some idle time?

@dkosovic
Copy link
Contributor

Although located on the file system, it isn't really a file, but a named pipe :

$ ls -l /var/run/xl2tpd/l2tp-control
prw------- 1 root root 0 Oct 31 08:59 /var/run/xl2tpd/l2tp-control

$ file /var/run/xl2tpd/l2tp-control
/var/run/xl2tpd/l2tp-control: fifo (named pipe)

With that named pipe which xl2tpd uses for accepting commands, nothing is written to the file system, but to kernel memory.

where are you seeing that /var/run/xl2tpd/l2tp-control is empty?

/usr/sbin/xl2tpd-control was introduced to send control commands to xl2tpd via the named pipe. You are using the older approach of redirecting stdout to the named pipe.

I suspect the issues is not with /var/run/xl2tpd/l2tp-control, but something else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants