Page 4 of 5
Re: Mullvad vpn client issue
Posted: Fri Sep 28, 2018 1:21 pm
by fehlix
Hooten wrote: ↑Fri Sep 28, 2018 11:22 am
Phew... you scared me for a moment.
Fine.
Would you please add [Solved] to the subject line of your first post, just in case others seeking for a similar clue.
Thanks
Re: Mullvad vpn client issue [SOLVED]
Posted: Sun Dec 23, 2018 10:55 am
by mystic
I went through the same issue yesterday when I switched to Mullvad, luckily Wireguard works flawlessly in MX which Mullvad provides.
Re: Mullvad vpn client issue [SOLVED]
Posted: Sun Dec 23, 2018 11:24 am
by Hooten
mystic wrote: ↑Sun Dec 23, 2018 10:55 am
I went through the same issue yesterday when I switched to Mullvad, luckily Wireguard works flawlessly in MX which Mullvad provides.
Yes you can use Wireguard ofcourse, but if you want to use their client, follow the instructions that fehlix wrote in this thread. Works like a charm.
Re: Mullvad vpn client issue
Posted: Wed May 22, 2019 9:58 am
by flugzeit
fehlix wrote: ↑Thu Sep 27, 2018 12:53 pm
Command:
Code: Select all
/opt/MullvadVPN/resources/mullvad-daemon -v --disable-stdout-timestamps
If need to run this automatically after login,
we can prepare this later...
Hi there,
Thanks for this fix. I used it to successfully get Mullvad working on MX-18.
How can I set this up to run automatically after boot/login? Do I need a bash script and use /etc/init.d/.
Any advice would be much appreciated.
Thanks
-flugzeit
Re: Mullvad vpn client issue
Posted: Wed May 22, 2019 12:24 pm
by fehlix
flugzeit wrote: ↑Wed May 22, 2019 9:58 am
How can I set this up to run automatically after boot/login? Do I need a bash script and use /etc/init.d/.
Please try the attached init-script for Mullvad VPN.
Download the attached tar file mullvad-daemon.init.tgz
Extract the init.d script:
Code: Select all
sudo tar -C / -xvzf mullvad-daemon.init.tgz
update init-service links
Code: Select all
sudo update-rc.d mullvad-daemon defaults
Check status:
Code: Select all
sudo service mullvad-daemon status
Note: Actually I leave now the original install directory within '/opt/Mullvad VPN'
and to avoid "space" issue within the path I add an additional symlink like this
Code: Select all
ln -s '/opt/Mullvad VPN' /opt/MullvadVPN
Re: Mullvad vpn client issue
Posted: Fri May 24, 2019 3:32 am
by flugzeit
fehlix wrote: ↑Wed May 22, 2019 12:24 pm
Check status:
Code: Select all
sudo service mullvad-daemon status
Followed these steps and all worked perfectly!
fehlix wrote: ↑Wed May 22, 2019 12:24 pm
Note: Actually I leave now the original install directory within '/opt/Mullvad VPN'
and to avoid "space" issue within the path I add an additional symlink like this
Code: Select all
ln -s '/opt/Mullvad VPN' /opt/MullvadVPN
Yes, I've implemented this, also.
Thanks so much for the help! Very much appreciated, and I hope to spend more time on the forum now that I've committed to MX Linux.
-flugzeit
Re: Mullvad vpn client issue
Posted: Fri Feb 28, 2020 2:30 am
by bogleg
fehlix wrote: ↑Wed May 22, 2019 12:24 pm
Please try the attached init-script for Mullvad VPN.
Thank you for this!! How do I get the required permissions to see the file?
Re: Mullvad vpn client issue [SOLVED]
Posted: Fri Feb 28, 2020 2:31 am
by bogleg
Nevermind - it showed up right after I posted. :)
Re: Mullvad vpn client issue
Posted: Fri Feb 28, 2020 7:45 am
by fehlix
bogleg wrote: ↑Fri Feb 28, 2020 2:30 am
fehlix wrote: ↑Wed May 22, 2019 12:24 pm
Please try the attached init-script for Mullvad VPN.
Thank you for this!! How do I get the required permissions to see the file?
Meanwhile you can install Mullvad VPN this way:
MX Tools -> MX Package Installer -> Populare Apps -> Network -> Mullvad VPN
Re: Mullvad vpn client issue
Posted: Sat Mar 07, 2020 2:49 pm
by blankotadi
Hooten wrote: ↑Tue Sep 25, 2018 9:16 am
Actually it's a systemd thing. Everything works when i boot in MX with systemd. <Mod deleted URL> Is it possible to enable only one program to use systemd (like mullvad client) without booting in MX with systemd?
I haven't find any solution online like "apt-get install -f". I've reinstalled MX in the end to remove it and contacted Mullvad support but they didn't find a solution to this issue. Is any chance to be a fixed from the OS itself?