On 4/9/20 3:34 AM, taran1s wrote:
Chris Laprise:
On 4/8/20 6:25 AM, taran1s wrote:
I try to set the VPN in my laest qubes with your guide on
https://github.com/tasket/Qubes-vpn-support. I use the version
1.4.3. and followed the guide.
My setting from mullvad is UDP (default) for Linux. No IPs.
When asked, I entered correct login. The link but doesn't go up,
no popup notification LINK IS UP when restarting the proxy VM.
I also added vpn-handler-openvpn to the proxy VM services as required.
Executing systemctl status returns this:
[user@ovpn ~]$ systemctl status qubes-vpn-handler
● qubes-vpn-handler.service - VPN Client for Qubes proxyVM
Loaded: loaded (/usr/lib/systemd/system/qubes-vpn-handler.service;
enabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/qubes-vpn-handler.service.d
└─00_example.conf
Active: activating (auto-restart) (Result: exit-code) since Tue
2020-04-07 15:30:15 CEST; 4s ago
Process: 3098 ExecStartPre=/usr/lib/qubes/qubes-vpn-setup
--check-firewall (code=exited, status=0/SUCCESS)
Process: 3105 ExecStartPre=/usr/lib/qubes/qubes-vpn-setup
--pre-start (code=exited, status=0/SUCCESS)
Process: 3110 ExecStart=/usr/lib/qubes/qubes-vpn-setup --start-exec
(code=exited, status=1/FAILURE)
Process: 3111 ExecStartPost=/usr/lib/qubes/qubes-vpn-setup
--post-start (code=exited, status=0/SUCCESS)
Process: 3117 ExecStopPost=/usr/lib/qubes/qubes-vpn-setup
--post-stop (code=exited, status=0/SUCCESS)
Main PID: 3110 (code=exited, status=1/FAILURE)
Any idea how to set this up properly?
The one exception I can think of for setting up with a Mullvad account
is that they use a single-character "m" password for everyone. So if you
typed something into the password prompt other than "m" or left it
blank, then it won't connect.
To see a more detailed log you should use 'journalctl -u
qubes-vpn-handler'.
Yes Chris, mullvad uses the "m" for password and I put this in when
asked. I checked this in the pass file from mullvad.
I did the following. I downloaded the default UDP settings for "All
countries" from mullvad as adviced, without ticking the IPs. Than I took
one of the countries from the downloaded list and copied this particular
country to the vpn-client.conf with sudo cp whatver-country.ovpn
vpn-client.conf. But it doesn't connect.
Did you do the link testing suggested in Step 2?
Is this setup ok for me-tor-vpn situation?
These network representations can easily get reversed in people's heads.
Best thing to do is look at your 'Networking' setting for your VPN VM.
If its set to 'sys-whonix' then UDP won't work.
I executed the command in the proxyVM (fedora-30 based) with following
results:
[user@ovpn ~]$ journalctl -u qubes-vpn-handler
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal', 'wheel' can see all
messages.
Pass -q to turn off this notice.
-- Logs begin at Tue 2020-02-18 14:58:55 CET, end at Thu 2020-04-09
09:21:21 CE>
-- No entries --
lines 1-2/2 (END)
I tried also the micahflee guide and it connects so the settings should
be ok.
Sorry, you need to put 'sudo' in front of the 'journalctl' command.
--
Chris Laprise, [email protected]
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/ead2f0a8-0f4e-513f-028e-dc362fff8bce%40posteo.net.
