From a4c8108acc7ab6e9268acfbcf8733aa8da9aad8a Mon Sep 17 00:00:00 2001 From: Joanna Rutkowska Date: Sat, 16 Nov 2013 12:08:41 +0000 Subject: [PATCH] QubesFirewall changed Added info on reconnecting to netvms after they got rebooted --- QubesFirewall.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/QubesFirewall.md b/QubesFirewall.md index ddd448e0..30d5a276 100644 --- a/QubesFirewall.md +++ b/QubesFirewall.md @@ -28,6 +28,21 @@ Note that if you specify a rule by DNS name it will be resolved to IP(s) *at the Alternatively, one can use the `qvm-firewall` command from Dom0 to edit the firewall rules by hand: +Reconnecting AppVMs after a NetVM reboot +---------------------------------------- + +Normally Qubes doesn't let the user to stop a NetVM if there are other AppVMs running which use it as their own NetVM. But in case the NetVM stops for whatever reason (e.g. it crashes, or the user forces its shutdown via qvm-kill via terminal in the netvm), then there is an easy way to restore the connection to the netvm by issuing: + +``` {.wiki} +qvm-prefs -s netvm +``` + +Normally AppVMs do not connect directly to the actual NetVM which has networking devices, but rather to the default FirewallVM first, and in most cases it would be the NetVM that would crash, e.g. in response to S3 sleep/restore or other issues with [WiFi?](/wiki/WiFi) drivers. In that case it is necessary to just issue the above command once, for the FirewallVM (this assumes default VM-nameing used by the default Qubes installation): + +``` {.wiki} +qvm-prefs firewallvm -s netvm netvm +``` + Enabling networking between two AppVMs --------------------------------------