On 6/1/19 1:46 PM, Stumpy wrote:
I upgraded to v30 fedora minimal, installed all the packages I installed
on v28, and tried using the vpn vm but nada, its acting like its not
even there? the vpn appvm has not been changed, same configuration, and
as far as i can tell the same packages installed in the new template as
the old template but when I try to use an appvm that uses the vpn vm as
a net-sys and check (ifconfig.co) it shows me the same thing as if i
wasnt using the vpn at all?
When set my vpn appvm to use the old fed 28 min template it goes back to
working fine...
If you're using qubes-vpn-support or qubes-tunnel, I'm looking into it
now. I think its happening on fedora-29/30 and debian-10.
There is a difference in systemd that requires a different startup
approach. But also, there is a bug in notify-send that causes it to hang
for a while, which causes the vpn scripts to hang for the same period.
Current workaround is to run it with debian-9.
Issue:
https://github.com/tasket/Qubes-vpn-support/issues/39
--
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/f111fe3c-8725-6289-e90f-23d47e7f7baf%40posteo.net.
For more options, visit https://groups.google.com/d/optout.
