Re: [qubes-users] reboot sys-net

2018-02-07 Thread Ivan Mitev



On 02/07/18 10:22, haaber wrote:

I remember some issues with reattaching in the past, but recently, the qvm-shutdown 
--wait --force sys-net && qvm-start sys-net seems to be working.

This sounded even more interesting than the script. But: It does not
work in my Q4rc4 install. last experience of this type was with
sys-whonix and anon-whonix. The latter running, the former did not power
off (even with --force); after some wait I kill it, but it won't reboot:
on boot it spills out "network device with MAC ... already exists"
before dying. I had to power off anon-whonix, then restart sys-whonix.

Same thing happen with the sys-net - sys-firewall - sys-whonix -
anon-whonix chain. I need to power off all of them to get sys-net to
rebbot, which is, frankly, annoying. So finally a script is a good idea,
even if Ilpo's did not work out of the box in my install (may be a Q3.2
- Q4 issue).


FWIW on R4.0rc4 I don't need to poweroff/boot any VM depending on 
sys-net: 'qvm-kill sys-net' (or clean shutdown) followed by 'qvm-start 
sys-net' works perfectly well, ie. network connectivity is automatically 
restored in sys-firewall and other dependent VMs.


Note that I ran 'qvm-prefs sys-firewall netvm sys-net' (once after a 
complete reboot) after reading Awokd's reply, where he pointed to the 
doc explaining how to reconnect sys-firewall after a sys-net crash [1]. 
So maybe that step is required to get "automatic" re-connection.


[1] https://www.qubes-os.org/doc/firewall/

--
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2685ee5f-5863-fcce-104d-f60eac9a8f9e%40maa.bz.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] reboot sys-net

2018-02-07 Thread haaber
> I remember some issues with reattaching in the past, but recently, the 
> qvm-shutdown --wait --force sys-net && qvm-start sys-net seems to be working. 
This sounded even more interesting than the script. But: It does not
work in my Q4rc4 install. last experience of this type was with
sys-whonix and anon-whonix. The latter running, the former did not power
off (even with --force); after some wait I kill it, but it won't reboot:
on boot it spills out "network device with MAC ... already exists"
before dying. I had to power off anon-whonix, then restart sys-whonix.

Same thing happen with the sys-net - sys-firewall - sys-whonix -
anon-whonix chain. I need to power off all of them to get sys-net to
rebbot, which is, frankly, annoying. So finally a script is a good idea,
even if Ilpo's did not work out of the box in my install (may be a Q3.2
- Q4 issue).

Best, Bernhard

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/688e1318-b7e4-f7e0-0b8a-b73b67a5c6b4%40web.de.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] reboot sys-net

2018-02-02 Thread Vít Šesták
I remember some issues with reattaching in the past, but recently, the 
qvm-shutdown --wait --force sys-net && qvm-start sys-net seems to be working. 
It can fail in some cases like when you have a paused VM (a feature that seems 
to cause various issues in 3.2) and it does nto work id the sys-net is shut 
dows from the VM itself.

You can do the same for both sys-net and sys-firewall at once. The qvm-shutdown 
command accepts multiple VM names. For qvm-start, you can just request start of 
sys-firewall, because the sys-net VM is started automatically in such case.

Regards,
Vít Šesták 'v6ak'

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ef9188b0-4402-45c8-85f6-1527a7e8b972%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] reboot sys-net

2018-02-02 Thread 'awokd' via qubes-users
On Fri, February 2, 2018 11:05 am, Bernhard wrote:
> On 02/02/2018 11:58 AM, Ilpo Järvinen wrote:
>
>> On Fri, 2 Feb 2018, Bernhard wrote:

>>> That would allow to confortably reboot sys-net

For a bit more blunt force approach, you could qvm-kill sys-net then use
the procedure "Reconnecting VMs after a NetVM reboot" on
https://www.qubes-os.org/doc/firewall/ to reconnect it. Have not
thoroughly tested.

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/289528855d40ca7fa0bff173a2a3d753.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] reboot sys-net

2018-02-02 Thread Bernhard
On 02/02/2018 11:58 AM, Ilpo Järvinen wrote:
> On Fri, 2 Feb 2018, Bernhard wrote:
>
>> Did by chance someone write a dom0-script that
>>
>> a) fetches a list of all (running) appvm's that use sys-net.
>>
>> b) setting their net-vm to "none"
>>
>> c) reboot sys-net
>>
>> d) undoes step (b)
>>
>> That would allow to confortably reboot sys-net (same ideas apply to
>> sys-firewall & sys-whonix) and could help many people in many
>> situations. I am not a bash hero, and before losing half a day on this
>> useful script, I prefer asking if someone did it already :)
> I didn't have it already but it wasn't too difficult to do so I wrote one 
> as it seems somewhat useful.

Awesome! Thank you very much. Bernhard

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/36c7f28f-90a7-f322-d5fc-3ff3a90af580%40web.de.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] reboot sys-net

2018-02-02 Thread Ilpo Järvinen
On Fri, 2 Feb 2018, Bernhard wrote:

> Did by chance someone write a dom0-script that
> 
> a) fetches a list of all (running) appvm's that use sys-net.
> 
> b) setting their net-vm to "none"
> 
> c) reboot sys-net
> 
> d) undoes step (b)
> 
> That would allow to confortably reboot sys-net (same ideas apply to
> sys-firewall & sys-whonix) and could help many people in many
> situations. I am not a bash hero, and before losing half a day on this
> useful script, I prefer asking if someone did it already :)

I didn't have it already but it wasn't too difficult to do so I wrote one 
as it seems somewhat useful.


-- 
 i.

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/alpine.DEB.2.20.1802021230410.15025%40whs-18.cs.helsinki.fi.
For more options, visit https://groups.google.com/d/optout.
#!/bin/sh

vm="sys-net"
[ $# -ge 1 ] && vm="$1"

echo "Restarting $vm..."

explicitlist=$(qvm-ls --raw-data state netvm name-raw | \
grep -e "^Running|$vm|" | cut -d '|' -f 3)

defaultlist=$(qvm-ls --raw-data state netvm name-raw | \
grep -e "^Running|[*]$vm|" | cut -d '|' -f 3)

for i in $explicitlist $defaultlist; do
qvm-prefs -s $i netvm none
done

qvm-shutdown --wait "$vm"
qvm-start "$vm"

for i in $explicitlist; do
qvm-prefs -s $i netvm "$vm"
done

for i in $defaultlist; do
qvm-prefs -s $i netvm default
done


[qubes-users] reboot sys-net

2018-02-02 Thread Bernhard
Did by chance someone write a dom0-script that

a) fetches a list of all (running) appvm's that use sys-net.

b) setting their net-vm to "none"

c) reboot sys-net

d) undoes step (b)

That would allow to confortably reboot sys-net (same ideas apply to
sys-firewall & sys-whonix) and could help many people in many
situations. I am not a bash hero, and before losing half a day on this
useful script, I prefer asking if someone did it already :)  Thank you,
Bernhard

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/dc35b472-0c8c-df87-a0d7-3705f9a2d1ce%40web.de.
For more options, visit https://groups.google.com/d/optout.