On 05/15/2018 03:37 AM, 'Evastar' via qubes-users wrote:


Posting back to qubes-users...

Sorry for direct message. Now, I use web-based mail it set direct answer by 
default :(

A little more information. When it goes to "no network state" then I seeing at my ethervpn with "ip 
route list" (as I remember) that all vif+ interfaces show as "down". It is the problem. I do not know 
how to reconnect them and remove "down" mark.


Finally, if you find the solution involves restarting the ethervpn
client, you may want to run it with 'systemd-run --unit' to give you
better control over the process. You could even try running it with
qubes-tunnel using a drop-in file for the service (see 00_example.conf
and manpages for systemd.unit "overriding vendor settings").


Thanks. I will check this manpages. Maybe this will help.

If the vif interfaces are going down, that suggests a bug either in Qubes or in ethervpn. Since other Qubes users don't seem to be reporting this symptom, I'd guess that ethervpn is mistakenly including the vif interfaces with tun/tap whenever a link goes down or restarts. (The vif, tun and tap interfaces look similar in the sense that they're all virtual.) Its probably worth reporting this behavior on the ethervpn forum/list.

You might also try writing a small script to bring the vif interfaces up.

--

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/c4c6d117-e112-f398-30c7-f58bb79b5f40%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

Reply via email to