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

Post-quantum "kills" the connection to the VPN about every 2-3 hours #705

Open
noisecode3 opened this issue Dec 4, 2024 · 6 comments
Open
Labels
bug Something isn't working

Comments

@noisecode3
Copy link

I can now confirm that Post-quantum don't work on Slackware-current or Arch Linux with recent kernel.
It just disconnect the traffic leaving only like a ping coming from the server, that I could see in tcpdump.

Nordvpn status still say its up, NetworkManager is not down or anything like that, just a ping left from the server.
The killswitch is always on if it matters. No other settings, just pq on will do this.

If this is my Internet service provider, I don't know. I thought you should know. Maybe we can go around it? You can reproduce?

Its normal UDP with NORDLYNX all default settings, except auto-connect and killswitch;

I don't really need Post-quantum I was just messing around...

@noisecode3
Copy link
Author

Actually tcpdump is completely silent when this happens on Slackware current exactly 2h 42min of up time then I have to use the command nordvpn c again.. It was different with Arch I think... I could see the VPN still trying...

@devzbysiu
Copy link
Contributor

Hi @noisecode3, thank you for reporting 🙇

We tried to reproduce this on supported distros and we can't reproduce it. Unfortunately we are not supporting Slackware and Arch directly, so we are not checking those distros.

While it's possible that some recent developments in the kernel cause this, we'll stumble upon it when we'll be testing supported distros with those kernel changes and then we'll address this if it turns out to be affecting the app

@hectorj102
Copy link

Having the same issue since I enabled post-quantum a few days ago - connection becomes unusable after a few hours and requires disconnect/reconnect to restore but the restoration is only temporary and issue recurs in approximately the same time frame again and again.
Running Linux Mint 21.3 Cinnamon (Cinnamon version 6.0.4, kernel 5.1.5.0-130-generic).

@alaingad
Copy link

alaingad commented Jan 24, 2025

Same here.
Disconnect silently after a while. Started after last NordVPN "upgrade".
I have just disabled Post-quantum VPN to see if the connection will now stay up.

EDIT: After 21 hours, the connection is still up.

The message that was constantly being displayed in the log before disabling Post-Quantum VPN
Jan 24 09:43:48 OptiPlex nordvpnd[787]: 2025/01/24 09:43:48 [Warning] TELIO(v5.1.5): ThreadId(10) "telio_pq::conn":95 Failed to perform PQ rekey: TIMEOUT(8s)

System:
Kernel: 6.8.0-50-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc
Desktop: Cinnamon v: 6.2.9 tk: GTK v: 3.24.41 wm: Muffin v: 6.2.0 vt: 7 dm: LightDM v: 1.30.0
Distro: Linux Mint 22 Wilma base: Ubuntu 24.04 noble

NordVPN Version 3.20.0
Technology: NORDLYNX
Firewall: enabled
Firewall Mark: 0xe1f1
Routing: enabled
Analytics: disabled
Kill Switch: disabled
Threat Protection Lite: disabled
Notify: enabled
Tray: disabled
Auto-connect: disabled
IPv6: disabled
Meshnet: disabled
DNS: disabled
LAN Discovery: enabled
Virtual Location: enabled
Post-quantum VPN: disabled

@noisecode3
Copy link
Author

Sorry for not being specific here but my problem was(still had the log):

nordvpnd[655]: 2024/11/24 03:08:41 [NC] connection lost:  pingresp not received, disconnecting
nordvpnd[655]: 2024/11/24 03:08:41 [NC] start connection loop
nordvpnd[655]: 2024/11/24 03:08:46 [NC] failed to connect: timeout

and that it would not disconnect the connection in the app or anything like that just make the udp flow stop like the kill-switch was triggered. That was my problem, right now don't have time to test.

@mariusSincovici
Copy link
Contributor

Hi,

thanks for your feedback. We've reproduced and fixed the issue. A fix will be provided into the next application release.

@mariusSincovici mariusSincovici added the bug Something isn't working label Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants