Revise for clarity, terminology, and orthography

This commit is contained in:
Andrew David Wong 2017-01-11 19:50:31 -08:00
parent d95582f62b
commit fa46feae1e
No known key found for this signature in database
GPG Key ID: 8CE137352A019A17

View File

@ -203,13 +203,15 @@ Configure your AppVMs to use the VPN VM as a NetVM...
![Settings-NetVM.png](/attachment/wiki/VPN/Settings-NetVM.png) ![Settings-NetVM.png](/attachment/wiki/VPN/Settings-NetVM.png)
If you want to be able to use the qubes firewall, create a ProxyVM firewall and set it to use the VPN VM as NetVM. If you want to be able to use the [Qubes firewall](/doc/firewall), create a new FirewallVM (as a ProxyVM) and set it to use the VPN VM as its NetVM.
Then configure AppVMs to use *that* firewall as their NetVM. Then, configure AppVMs to use your new FirewallVM as their NetVM.
If you want to update your Templates through the VPN, configure the ProxyVM firewall so as to enable the qubes-updates-proxy service. If you want to update your TemplateVMs through the VPN, enable the `qubes-updates-proxy` service in your new FirewallVM.
You can do this using the services tab in the Manager or at the command line: You can do this in the Services tab in Qubes VM Manager or on the command-line:
`qvm-service -e <name> qubes-updates-proxy`
Then configure your templates to use the ProxyVM firewall as their NetVM. $ qvm-service -e <name> qubes-updates-proxy
Then, configure your templates to use your new FirewallVM as their NetVM.
Troubleshooting Troubleshooting