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

[BUG] Random disconnects in Slackware-current #375

Open
BusinessKid opened this issue Nov 3, 2024 · 0 comments
Open

[BUG] Random disconnects in Slackware-current #375

BusinessKid opened this issue Nov 3, 2024 · 0 comments

Comments

@BusinessKid
Copy link

I'm getting random vpn disconnects, most often using qbittorrent. The fault is not, however, limited to qbittorrent.

It's difficult to describe how to 'provoke' a random event. That said, start a torrent download using qbittorrent or just surf. After some random period, (minutes to many days), it will go offline. Restart the VPN, and connection is restored.

Expected behavior
The connection should not drop.

Error Messages/Program Output/Log Messages (~/.pvpn-cli/pvpn-cli.log)
Last 100 lines of /root/.pvpn-cli/pvpn-cli.log attached. There's nearly 11,000 lines/2.6Meg.

Desktop (please complete the following information):

  • OS: Slackware-current 2024-09-09 with Mate-1.28.0
  • Python Version: [e.g. 3.7.4 (python3 --version)] Python3-3.11.101
  • ProtonVPN-CLI Version: [e.g. 2.0.0 (protonvpn --version)] 2.2.12

Additional context
Add any other context about the problem

Here's some output
`here.
dec@ebony:~$ cat /etc/resolv.conf

Generated by resolvconf

ProtonVPN DNS Servers. Managed by ProtonVPN-CLI.

nameserver 10.20.0.1
dec@ebony:$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.20.0.1 128.0.0.0 UG 0 0 0 proton0
default chateau.dec 0.0.0.0 UG 1002 0 0 eth0
10.20.0.0 0.0.0.0 255.255.0.0 U 0 0 0 proton0
128.0.0.0 10.20.0.1 128.0.0.0 UG 0 0 0 proton0
146.70.48.2 chateau.dec 255.255.255.255 UGH 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 1002 0 0 eth0
dec@ebony:
$ ping 10.20.0.1
PING 10.20.0.1 (10.20.0.1) 56(84) bytes of data.
64 bytes from 10.20.0.1: icmp_seq=1 ttl=64 time=39.0 ms
64 bytes from 10.20.0.1: icmp_seq=2 ttl=64 time=22.7 ms

--- 10.20.0.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 22.658/30.828/38.999/8.170 ms
dec@ebony:~$ ping 146.70.48.2
PING 146.70.48.2 (146.70.48.2) 56(84) bytes of data.
64 bytes from 146.70.48.2: icmp_seq=1 ttl=54 time=28.8 ms
64 bytes from 146.70.48.2: icmp_seq=2 ttl=54 time=30.4 ms

--- 146.70.48.2 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 28.768/29.600/30.432/0.832 ms`

The particular IPs vary, but with the fault occurring (It isn't now), the diagnostics are as described here:
[https://www.linuxquestions.org/questions/slackware-14/protonvpn-nuttiness-4175743576/
pvpn-cli.log
](url)
pvpn-cli.log

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

1 participant