Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-10-01 01:25:40 -04:00
Code Issues Packages Projects Releases Wiki Activity

QubesFirewall changed

Browse Source 
Added info on reconnecting to netvms after they got rebooted
This commit is contained in:
Joanna Rutkowska 2013-11-16 12:08:41 +00:00
parent 7450f056f5
commit a4c8108acc
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
QubesFirewall.md
View File

@ -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 <appvm> -s netvm <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
--------------------------------------