Qubes/Create Gateway ProxyVMs
From Whonix
< Qubes
Qubes-R3.2
Qubes VM Manager → VM → Create AppVM
Qubes-R4.0
Qubes VM Manager → Qube → Create new qube
Footnotes[edit]
- ↑
- Create Whonix-Gateway ™ ProxyVM (Qubes-R3.2).
- Name and label: Name your ProxyVM. Don't include any personal information (if the AppVM is compromised, the attacker could run
qubesdb-read /nameto reveal the VM name). Name the ProxyVM something generic, for example:sys-whonix. - Color: Choose a color label for the Whonix-Gateway ™ ProxyVM.
- Use this template: Choose the Whonix-Gateway ™ TemplateVM. For example:
whonix-gw-15. - Standalone: Leave the Standalone field unchecked, unless a persistent root filesystem is desired.
- Type: Choose the type
ProxyVM. - Allow networking: Choose the desired clearnet ServiceVM from the list. For example:
sys-firewall - Press:
OK.
- Name and label: Name your ProxyVM. Don't include any personal information (if the AppVM is compromised, the attacker could run
- Create Whonix-Gateway ™ ProxyVM (Qubes-R3.2).
- ↑
- Create Whonix-Gateway ™ ProxyVM (Qubes-R4).
- Name and label: Name your VM. Don't include any personal information (if the AppVM is compromised, the attacker could run
qubesdb-read /nameto reveal the VM name). Name the ProxyVM something generic, for example:sys-whonix. - Color: Choose a color label for the Whonix-Gateway ™ ProxyVM.
- Type: Choose the type
AppVM. - Template: Choose Whonix-Gateway ™ TemplateVM. For example:
whonix-gw-15. - Networking: Choose desired clearnet ServiceVM from the list. For example:
sys-firewall - Advanced: Place a check mark in the "provides network" box. This will allow the Whonix-Gateway ™ ProxyVM to provide networking for other AppVMs.
- Press:
OK.
- Name and label: Name your VM. Don't include any personal information (if the AppVM is compromised, the attacker could run
- Create Whonix-Gateway ™ ProxyVM (Qubes-R4).