Git-Mirrors/qubes-mirage-firewall
1
0
Fork 0
mirror of https://github.com/mirage/qubes-mirage-firewall.git synced 2024-07-01 08:31:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #48 from talex5/update-readme

Browse Source 
Remove Qubes 3 instructions from README
This commit is contained in:
Mindy Preston 2019-04-04 12:05:06 -05:00 committed by GitHub
commit 88b55acaed
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@ -42,22 +42,6 @@ If you want to deploy manually, unpack `mirage-firewall.tar.bz2` in dom0, inside
The tarball contains `vmlinuz`, which is the unikernel itself, plus a couple of dummy files that Qubes requires.
### Qubes 3
To configure your new firewall using the Qubes 3 Manager GUI:
- Create a new ProxyVM named `mirage-firewall` to run the unikernel.
- You can use any template, and make it standalone or not. It doesn’t matter, since we don’t use the hard disk.
- Set the type to `ProxyVM`.
- Select `sys-net` for networking (not `sys-firewall`).
- Click `OK` to create the VM.
- Go to the VM settings, and look in the `Advanced` tab:
- Set the kernel to `mirage-firewall`.
- Turn off memory balancing and set the memory to 32 MB or so (you might have to fight a bit with the Qubes GUI to get it this low).
- Set VCPUs (number of virtual CPUs) to 1.
### Qubes 4
Run this command in dom0 to create a `mirage-firewall` VM using the `mirage-firewall` kernel you added above:
```
@ -75,6 +59,8 @@ qvm-create \
mirage-firewall
```
To upgrade from an earlier release, just overwrite `/var/lib/qubes/vm-kernels/mirage-firewall/vmlinuz` with the new version and restart the firewall VM.
### Configure AppVMs to use it
You can run `mirage-firewall` alongside your existing `sys-firewall` and you can choose which AppVMs use which firewall using the GUI.