Oh sorry, not at all.
Mullvad vpn client issue [SOLVED]
Re: Mullvad vpn client issue
Which is good. So what's left, I assume, is to startup the daemon earlier
in the process before the network manager is up
Which means to have a little init.d script for the sturtup of either one of the above daemons.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
Re: Mullvad vpn client issue
Perhaps - at least for a test - try to start the daemon as this.
Do add those lines add the end of the file /etc/rc.local
Keep only one line un-commented either for mullvad-daemon or for qomui-service - not both.
Make sure the last line will be exit 0 followed by a new line.
So the file /etc/rc.local looks either like this
for mullvad-daemon
or like this for qomui-service
EDIT: and do reboot after those changes ...
Do add those lines add the end of the file /etc/rc.local
Keep only one line un-commented either for mullvad-daemon or for qomui-service - not both.
Make sure the last line will be exit 0 followed by a new line.
Code: Select all
# leave onle one line uncommented
/opt/mullvad-vpn/resources/mullvad-daemon -v --disable-stdout-timestamps
#
/usr/bin/env qomui-service
for mullvad-daemon
Code: Select all
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
/opt/mullvad-vpn/resources/mullvad-daemon -v --disable-stdout-timestamps
exit 0
Code: Select all
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
/usr/bin/env qomui-service
exit 0
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
Re: Mullvad vpn client issue
I think i've done it right, but nothing changed. BTW i'm testing it in vm, not to worry about bricking anything in my main system.fehlix wrote: ↑Tue Sep 25, 2018 11:45 am Perhaps - at least for a test - try to start the daemon as this.
Do add those lines add the end of the file /etc/rc.local
Keep only one line un-commented either for mullvad-daemon or for qomui-service - not both.
Make sure the last line will be exit 0 followed by a new line.So the file /etc/rc.local looks either like thisCode: Select all
# leave onle one line uncommented /opt/mullvad-vpn/resources/mullvad-daemon -v --disable-stdout-timestamps # /usr/bin/env qomui-service
for mullvad-daemonor like this for qomui-serviceCode: Select all
#!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # /opt/mullvad-vpn/resources/mullvad-daemon -v --disable-stdout-timestamps exit 0
EDIT: and do reboot after those changes ...Code: Select all
#!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # /usr/bin/env qomui-service exit 0
You do not have the required permissions to view the files attached to this post.
Re: Mullvad vpn client issue
Yeah, it's probably too late with rc.local at the end of the runlevel, it needs to be get started earlier.
So what is needed would be to have init.d start script to get it a bit earlier started.
You might look whether you can find any mullvad related service files, which we might convert
to inti.d scripts.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
Re: Mullvad vpn client issue
Look i'm not that stupid. I did what you said first and after that i started mullvad, but same thing happened.fehlix wrote: ↑Wed Sep 26, 2018 6:20 pmYeah, it's probably too late with rc.local at the end of the runlevel, it needs to be get started earlier.
So what is needed would be to have init.d start script to get it a bit earlier started.
You might look whether you can find any mullvad related service files, which we might convert
to inti.d scripts.
Re: Mullvad vpn client issue
I also trying to run mullvad through openvpn following the instructions from here :https://mullvad.net/en/guides/linux-ope ... tallation/
But when i go to 4. step i get [FAIL] Starting virtual private network daemon: mullvad_no failed!
But when i go to 4. step i get [FAIL] Starting virtual private network daemon: mullvad_no failed!
Re: Mullvad vpn client issue
OK, I meant if you look for mullvad servcice files within the systemd folder /etc/systemd/system.
And if you post those here we might convert them into alternative start files,
so they get started ealier than rc.local, which appreaas to be to late, when you start MX17 with the default SysVint start system.
I can't test this myself, as I have no mullvad vpn.
And if you post those here we might convert them into alternative start files,
so they get started ealier than rc.local, which appreaas to be to late, when you start MX17 with the default SysVint start system.
I can't test this myself, as I have no mullvad vpn.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
Re: Mullvad vpn client issue
There is a file named "mullvad-daemon.service" and that is inside:fehlix wrote: ↑Thu Sep 27, 2018 11:52 am OK, I meant if you look for mullvad servcice files within the systemd folder /etc/systemd/system.
And if you post those here we might convert them into alternative start files,
so they get started ealier than rc.local, which appreaas to be to late, when you start MX17 with the default SysVint start system.
I can't test this myself, as I have no mullvad vpn.
# Systemd service unit file for the Mullvad VPN daemon
[Unit]
Description=Mullvad VPN daemon
Wants=network.target
After=network-online.target
StartLimitBurst=5
StartLimitIntervalSec=20
[Service]
Restart=always
RestartSec=1
ExecStart=/opt/Mullvad\x20VPN/resources/mullvad-daemon -v --disable-stdout-timestamps
[Install]
WantedBy=multi-user.target
Re: Mullvad vpn client issue
Ah thats, looks nice. The path differs from the one I gave above.
What happens if you start from the command line this
Note the backslash before the space.
Would the daemon run ?
What happens if you start from the command line this
Code: Select all
/opt/Mullvad\ VPN/resources/mullvad-daemon -v --disable-stdout-timestamps
Would the daemon run ?
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB