VPN issues after upgrading to fed26?

[Stumpy]

I recently upgraded to fedora 26 from 24 and since then I have not been
able to get my VPN NetVM to work.
I have tried some things mentioned in other posts to restart my vpnvm
like
qvm-run -u root my_vpn_vm "/rw/config/rc.local"
Which does get a "VPN: Starting..." notification but that is it, it
never actually starts/runs.
As I am feeling a bit naked w/o my VPNvm I'd really appreciate any
suggestions!

[Chris Laprise]

Are you using the regular or minimal fedora template? The newest minimal
template may require additional packages.

--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886

[Stumpy]

Sorry, that is an important/relevant detail I forgot to mention.

No. I am using the full template, not minimal.

[Chris Laprise]

On 01/24/2018 06:10 PM, Chris Laprise wrote:
> On 01/24/2018 05:58 PM, Stumpy wrote:
>> I recently upgraded to fedora 26 from 24 and since then I have not
>> been able to get my VPN NetVM to work.
>> I have tried some things mentioned in other posts to restart my vpnvm
>> like
>> qvm-run -u root my_vpn_vm "/rw/config/rc.local"
>> Which does get a "VPN: Starting..." notification but that is it, it
>> never actually starts/runs.
>> As I am feeling a bit naked w/o my VPNvm I'd really appreciate any
>> suggestions!
>>
>
> Are you using the regular or minimal fedora template? The newest minimal
> template may require additional packages.

I re-tested on regular f26 (installed from qubes-template-fedora-26) and
it works. (Just remember that Qubes 4.0rc still needs a
'qubes-ip-change-hook' symlink that points to
`qubes-firewall-user-script` in the same /rw/config dir.)

You can try using the Qubes-supplied f26, otherwise my suggestion is to
troubleshoot by changing the top lines in rc.local to:

---
#!/bin/bash
VPN_CLIENT='openvpn'
VPN_OPTIONS='--cd /rw/config/vpn/ --config openvpn-client.ovpn'
[[ $1 == 'test' ]] || VPN_OPTIONS="$VPN_OPTIONS --daemon"
---

Then you can see the status messages in the CLI when you manually run it
like so:

$ sudo pkill openvpn
$ sudo /rw/config/rc.local test