Chris Laprise:
> On 4/20/20 9:31 AM, taran1s wrote:
>>
>>
>> Chris Laprise:
>>> On 4/20/20 8:12 AM, taran1s wrote:
>>>>
>>>>
>>>> Chris Laprise:
>>>>> On 4/17/20 7:12 AM, taran1s wrote:
>>>>>>
>>>>>>
>>>>>> Chris Laprise:
>>>>>>> On 4/15/20 6:35 AM, taran1s wrote:
>>>>>>>> In the point 3 of https://github.com/tasket/Qubes-vpn-support/
>>>>>>>> guide
>>>>>>>> there is the cd Qubes-vpn-support command as the first one. This
>>>>>>>> assumes
>>>>>>>> that the file is unzipped already, right? So I unzip it in the
>>>>>>>> /home/user folder, than cd to the unzipped Qubes-vpn-support-1.4.3
>>>>>>>> and
>>>>>>>> execute sudo bash ./install. Than proceed to the restart. Is this
>>>>>>>> how it
>>>>>>>> was meant?
>>>>>>>
>>>>>>> Yes, if you're installing it in the Proxy VM (VPN VM) itself.
>>>>>>> Otherwise,
>>>>>>> installing it in a template means you have to do step 4 also.
>>>>>>
>>>>>> Yes, I install it in the ProxyVM. Is my procedure right? The
>>>>>>
>>>>>>>
>>>>>>> Hmmm. Its not showing the full "Options error" lines. Try
>>>>>>> redirecting
>>>>>>> the output to a text file instead:
>>>>>>>
>>>>>>> sudo journalctl -u qubes-vpn-handler >log.txt
>>>>>>>
>>>>>>
>>>>>> See the log attached please.
>>>>>>
>>>>>
>>>>> It doesn't look like the same error as before. This one says the
>>>>> config
>>>>> has no "dev" specified. Can you check '/rw/config/vpn/vpn-client.conf'
>>>>> to see if it has a line like "dev tun"?
>>>>>
>>>>
>>>> If I go to the /rw/config/vpn/ there is no vpn-client.conf file but
>>>> vpn-client.conf-example only. This is content of the
>>>> vpn-client.conf-example:
>>>
>>> OK, it looks like you skipped the part of Step 2 where you copy or link
>>> your config file so that "vpn-client.conf" exists. For example:
>>>
>>> sudo cp US_East.ovpn vpn-client.conf
>>>
>> I created another ProxyVM ovpn and do it from the scratch. Can you
>> please check if this is the right procedure?
>>
>> [user@ovpn ~]$ sudo mkdir -p /rw/config/vpn
>> [user@ovpn ~]$ cd /rw/config/vpn
>> [user@ovpn vpn]$ ls
>> [user@ovpn vpn]$ sudo unzip ~/mullvad_openvpn_linux_all_all.zip
>> Archive:  /home/user/mullvad_openvpn_linux_all_all.zip
>>     creating: mullvad_config_linux/
>>   extracting: mullvad_config_linux/mullvad_ae_all.conf
>>   extracting: mullvad_config_linux/mullvad_al_all.conf
>>   extracting: mullvad_config_linux/mullvad_at_all.conf
>>   extracting: mullvad_config_linux/mullvad_au_all.conf
>>   extracting: mullvad_config_linux/mullvad_be_all.conf
>>   extracting: mullvad_config_linux/mullvad_bg_all.conf
>>   extracting: mullvad_config_linux/mullvad_br_all.conf
>>   extracting: mullvad_config_linux/mullvad_ca_all.conf
>>   extracting: mullvad_config_linux/mullvad_ch_all.conf
>>   extracting: mullvad_config_linux/mullvad_cz_all.conf
>>   extracting: mullvad_config_linux/mullvad_de_all.conf
>>   extracting: mullvad_config_linux/mullvad_dk_all.conf
>>   extracting: mullvad_config_linux/mullvad_es_all.conf
>>   extracting: mullvad_config_linux/mullvad_fi_all.conf
>>   extracting: mullvad_config_linux/mullvad_fr_all.conf
>>   extracting: mullvad_config_linux/mullvad_gb_all.conf
>>   extracting: mullvad_config_linux/mullvad_gr_all.conf
>>   extracting: mullvad_config_linux/mullvad_hk_all.conf
>>   extracting: mullvad_config_linux/mullvad_hu_all.conf
>>   extracting: mullvad_config_linux/mullvad_ie_all.conf
>>   extracting: mullvad_config_linux/mullvad_il_all.conf
>>   extracting: mullvad_config_linux/mullvad_it_all.conf
>>   extracting: mullvad_config_linux/mullvad_jp_all.conf
>>   extracting: mullvad_config_linux/mullvad_lu_all.conf
>>   extracting: mullvad_config_linux/mullvad_lv_all.conf
>>   extracting: mullvad_config_linux/mullvad_md_all.conf
>>   extracting: mullvad_config_linux/mullvad_nl_all.conf
>>   extracting: mullvad_config_linux/mullvad_no_all.conf
>>   extracting: mullvad_config_linux/mullvad_nz_all.conf
>>   extracting: mullvad_config_linux/mullvad_pl_all.conf
>>   extracting: mullvad_config_linux/mullvad_pt_all.conf
>>   extracting: mullvad_config_linux/mullvad_ro_all.conf
>>   extracting: mullvad_config_linux/mullvad_rs_all.conf
>>   extracting: mullvad_config_linux/mullvad_se_all.conf
>>   extracting: mullvad_config_linux/mullvad_sg_all.conf
>>   extracting: mullvad_config_linux/mullvad_us_all.conf
>>   extracting: mullvad_config_linux/mullvad_userpass.txt
>>   extracting: mullvad_config_linux/mullvad_ca.crt
>>   extracting: mullvad_config_linux/update-resolv-conf
>> [user@ovpn vpn]$ sudo cp mullvad_config_linux/mullvad_ch_all.conf
>> vpn-client.conf
>> [user@ovpn vpn]$ sudo openvpn --cd /rw/config/vpn --config
>> vpn-client.conf --auth-user-pass
>> mullvad_config_linux/mullvad_userpass.txt
>> Mon Apr 20 15:27:43 2020 Note: option tun-ipv6 is ignored because modern
>> operating systems do not need special IPv6 tun handling anymore.
>> Options error: --up script fails with '/etc/openvpn/update-resolv-conf':
>> No such file or directory (errno=2)
>> Options error: Please correct this error.
>> Use --help for more information.
>> [user@ovpn vpn]$ cd ~
>> [user@ovpn ~]$ sudo openvpn --cd /rw/config/vpn --config vpn-client.conf
>> --auth-user-pass mullvad_config_linux/mullvad_userpass.txt
>> Mon Apr 20 15:28:29 2020 Note: option tun-ipv6 is ignored because modern
>> operating systems do not need special IPv6 tun handling anymore.
>> Options error: --up script fails with '/etc/openvpn/update-resolv-conf':
>> No such file or directory (errno=2)
>> Options error: Please correct this error.
>> Use --help for more information.
> 
> You'll need to put the files in the vpn directory, not a subdirectory
> like "mullvad_config_linux".

Is there any particular comand, instead of unzip, to not create the
sub-directory but unzip it in the vpn directory directly?

> 
> That particular error, however, indicates that the config expects
> "update-resolv-conf" to be in "/etc/openvpn". You can copy it there for
> the test, but this part of the config is overridden by Qubes-vpn-support
> so in the end you won't need it there.

Should the Qubes-vpn-support be unzipped and installed in /home/user/ or
an another path or it doesn't matter?

BTW this is the log from debian-10 based ProxyVM. The error seems to be
different:

user@open:~$ sudo mkdir -p /rw/config/vpn
user@open:~$ cd /rw/config/vpn
user@open:/rw/config/vpn$ sudo unzip ~/mullvad_openvpn_linux_all_all.zip
Archive:  /home/user/mullvad_openvpn_linux_all_all.zip
   creating: mullvad_config_linux/
 extracting: mullvad_config_linux/mullvad_ae_all.conf
 extracting: mullvad_config_linux/mullvad_al_all.conf
 extracting: mullvad_config_linux/mullvad_at_all.conf
 extracting: mullvad_config_linux/mullvad_au_all.conf
 extracting: mullvad_config_linux/mullvad_be_all.conf
 extracting: mullvad_config_linux/mullvad_bg_all.conf
 extracting: mullvad_config_linux/mullvad_br_all.conf
 extracting: mullvad_config_linux/mullvad_ca_all.conf
 extracting: mullvad_config_linux/mullvad_ch_all.conf
 extracting: mullvad_config_linux/mullvad_cz_all.conf
 extracting: mullvad_config_linux/mullvad_de_all.conf
 extracting: mullvad_config_linux/mullvad_dk_all.conf
 extracting: mullvad_config_linux/mullvad_es_all.conf
 extracting: mullvad_config_linux/mullvad_fi_all.conf
 extracting: mullvad_config_linux/mullvad_fr_all.conf
 extracting: mullvad_config_linux/mullvad_gb_all.conf
 extracting: mullvad_config_linux/mullvad_gr_all.conf
 extracting: mullvad_config_linux/mullvad_hk_all.conf
 extracting: mullvad_config_linux/mullvad_hu_all.conf
 extracting: mullvad_config_linux/mullvad_ie_all.conf
 extracting: mullvad_config_linux/mullvad_il_all.conf
 extracting: mullvad_config_linux/mullvad_it_all.conf
 extracting: mullvad_config_linux/mullvad_jp_all.conf
 extracting: mullvad_config_linux/mullvad_lu_all.conf
 extracting: mullvad_config_linux/mullvad_lv_all.conf
 extracting: mullvad_config_linux/mullvad_md_all.conf
 extracting: mullvad_config_linux/mullvad_nl_all.conf
 extracting: mullvad_config_linux/mullvad_no_all.conf
 extracting: mullvad_config_linux/mullvad_nz_all.conf
 extracting: mullvad_config_linux/mullvad_pl_all.conf
 extracting: mullvad_config_linux/mullvad_pt_all.conf
 extracting: mullvad_config_linux/mullvad_ro_all.conf
 extracting: mullvad_config_linux/mullvad_rs_all.conf
 extracting: mullvad_config_linux/mullvad_se_all.conf
 extracting: mullvad_config_linux/mullvad_sg_all.conf
 extracting: mullvad_config_linux/mullvad_us_all.conf
 extracting: mullvad_config_linux/mullvad_userpass.txt
 extracting: mullvad_config_linux/mullvad_ca.crt
 extracting: mullvad_config_linux/update-resolv-conf
user@open:/rw/config/vpn$ sudo cp
mullvad_config_linux/mullvad_ch_all.conf vpn-client.conf
user@open:/rw/config/vpn$ sudo openvpn --cd /rw/config/vpn --config
vpn-client.conf --auth-user-pass mullvad_config_linux/mullvad_userpass.txt
Mon Apr 20 16:03:58 2020 Note: option tun-ipv6 is ignored because modern
operating systems do not need special IPv6 tun handling anymore.
Options error: --ca fails with 'mullvad_ca.crt': No such file or
directory (errno=2)
Mon Apr 20 16:03:58 2020 WARNING: file
'mullvad_config_linux/mullvad_userpass.txt' is group or others accessible
Options error: Please correct these errors.
Use --help for more information.

-- 
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/6d68bb4d-7f30-c147-0aec-8cd90308d106%40mailbox.org.

Attachment: 0xA664B90BD3BE59B3.asc
Description: application/pgp-keys

Reply via email to