On 04/19/18 14:04, Chris Laprise wrote:
On 04/19/2018 07:26 PM, john wrote:
I installed this in a App/proxy 4.0 VM, as I am familiar with the 3.2
CLI VPN creation.
I don't really understand how installing it in a Template or The
Template(not cloning it 1st) would allow me to swich between
geolocations ...
So, I used the AppVM, then I simply cloned the 1st one created with
the script and went into the PIA config file area ....and did rm -f ln
-s to the network manager thing.
and then recreated the ln -s to a new config file, which works , and
Even wakes up from suspend (where in 3.2 it never did) ; However,
If the AppVM using one of the VPN-foo as a netvm, and it is started,
and I want to switch to another VPN-foo1 it doesn't work on the fly,
I have to go and qvm-shutdown the AppVM and open it again, which is
a big pain. I am often running out of RAM, and so try to just use
one App-proxy-vpnVM , however ,
is this the expected behavior no switching vpn appvms on the fly ?
IIRC this is a bug in the versions of Linux kernel that Qubes 4.0 uses.
There is an issue but I can't locate it at the moment.
So, I guess I'll learn to live with it , and try not to change VPNs buy
buying some more expensive RAM :)
But, I'm curious , If I install the new script in the Template/s , how
would I switch VPN locations?
Or would every AppVM based on that Template be locked into whatever
geolocation's config file was symlinked to ?
--
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/2571bdf5-8e73-71ea-0c9c-825b909889bc%40riseup.net.
For more options, visit https://groups.google.com/d/optout.
