search

tasket / Qubes-vpn-support

VPN configuration in Qubes OS
GNU General Public License v3.0
126 stars 28 forks source link

unable to perform DNS lookups for the VPN provider's domain #47

Closed initCCG closed 4 years ago

initCCG commented 4 years ago

For this particular user, it's Proton vpn.

ProxyVM is built on Debian-9-minimal, on a new install of latest Qubes.

Openvpn link test worked until running the install script.

setenv in config doesn't fix it. Neither does installing resolvconf and putting external servers in resolv.conf. (Putting in ISP provider's DNS seems best to avoid, because user lives on totalitarian territory, with only government DNS servers, and sets static DNS servers in other places.)

Enabling vpn-handler-egress is not possible, because that service doesn't exist in VPN VM.

Considering that this is supposed to be the easy way to set up Qubes VPN VM's, after couple of days of spare time, now mainly trying to decide if it's worth spending more time hacking on this, or giving up on it as a work-in-progress, and going back to the old difficult way to set up qubes vpn we did for other users.

Please advise. Thank you for your efforts.

tasket commented 4 years ago

vpn-handler-egress can be added to the VM by simply typing it into the dropdown list area and clicking '+' (also, deactivate the entry for vpn-handler-openvpn). I suggest trying this first.

initCCG commented 4 years ago

Thanks. With that, we can get openvpn to work from command line again, but qubes-vpn-handler.service still fails with code 123 on qubes-vpn-setup --pre-start.

I think we are not advanced enough yet to figure out this easy Qubes vpn installation method. So, it's hard to trust that its features would work better for us than the difficult, manual configuration we were able to make work previously.

Maybe we'll have more luck if we try it in the future. Thank you for your work.