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

lan-discovery true does not persist after reboot - Ubuntu 22.04 #371

Open
sgrseanIT opened this issue Apr 18, 2024 · 2 comments
Open

lan-discovery true does not persist after reboot - Ubuntu 22.04 #371

sgrseanIT opened this issue Apr 18, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@sgrseanIT
Copy link

I worked with the very fine support staff on this: conversation Ticket ID is 15990481

I have nordvpn running on ubuntu 22.04 (not in a vm). I've tried nordvpn v1.0.0 and v3.17.4.

What I think are relevant settings:
autoconnect true
killswitch true
lan-discovery true

I'm also mounting a local network drive via /etc/fstab

On reboot, the lan-discovery true setting seems to not function as expected.

How I narrowed this down:
When I log into the gnome desktop environment it will hang while trying to mount the network drive. If I switch to command line and log in I cannot ping anything on the LAN. If I disable killswitch and disconnect nordvpn, then log out of command line and into gnome, the drive will mount. I can then re-enable killswitch and reconnect nordvpn and the lan-discovery:true setting works as expected until reboot.

This is annoying.

How I resolved the issue:
sudo nordvpn set lan-discovery false
sudo nordvpn allowlist add subnet "mysubnet"

Now on subsequent reboots nordvpn connects as expected and the drive mounts as expected.

Here is an example of another person having this issue, seemingly on a pi: https://www.reddit.com/r/nordvpn/comments/1abm1q0/pi_nords_landiscovery_functionality_does_not/

@keliramu keliramu added the bug Something isn't working label Apr 18, 2024
@keliramu
Copy link
Collaborator

Hi, thank you for a feedback. We were able to reproduce the problem and registered an issue in our internal task management system. We will fix it asap.

@sgrseanIT
Copy link
Author

Amazing, thanks!

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

2 participants