NORD VPN Wireguard Implementation "NordLynx"

Suggestions for features and software you would like to see in DietPi, goes here.
Post Reply
Posts: 1
Joined: Thu Apr 16, 2020 6:11 am

NORD VPN Wireguard Implementation "NordLynx"

Post by LvsDark »

First off, i just wanna say thank you to the diet-pi team, for their amazing contributions! My requiest is it add wireguard to your current Dietpi-NordPVN. Just like how you can use the command ‘nordvpn set technology nordlynx’ to switch to wireguard protocol from openvpn. Thanks!
Posts: 1
Joined: Wed Nov 11, 2020 5:37 am

Re: NORD VPN Wireguard Implementation "NordLynx"

Post by maxdiamond »

I would also like to thank the DietPi team for building and supporting this awesome platform... thanks everyone!

I agree with Lvsdark that this would be an awesome function. It would be great to use the cool "edit up' and "edit down" script feature (which ensures privacy for other services is the VPN fails), to access the Nordlynx service.

Whether that is using the current NordVPN app or separate one (if OpenVPN and Wireguard can't co-exist)...

Any support on this would be awesome!

Posts: 4
Joined: Sun Dec 06, 2020 10:03 am

Re: NORD VPN Wireguard Implementation "NordLynx"

Post by Treejumping »

i'm far far far from an expert, but i have managed to throw together the following script as a pseudo if-up/down script for using nordlynx

Code: Select all


# Check vpn-tunnel "nordlynx" and ping google DNS if internet connection work
if  [ "$(ping -I nordlynx -q -c 1 -W 1 | grep '0% packet loss' )" != "" ]; then
# if-up commands	
	echo "vpn up"
#if-down commands
       echo "vpn down"
(its a modified code shared by joulinar on a spereate thread)

i made it executable (chmod +x) then popped it in /etc/cron.minutely/nordlynx (no .sh at the end or dietpi-cron won't execute it)

If you wanted a more frequent interval than minutely then i don't see why you couldn't repeat the code with "sleep 1" (or however many seconds you want between checks).

not perfect, but good enaough for me. i'm just using it to kill deluged (which runs socks5 anyway so if it takes a minute to notice then i can live with that).

By putting a 'systemctl start deluged' in the if-up command then it should relaunch deluged when the vpn s back up
Post Reply