mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2024-12-25 15:29:29 -05:00
update 7-year-old test-bench machine setup
Updates the developer documentation for remote test bench
This commit is contained in:
parent
08eb959f6f
commit
0a6f37156e
@ -15,11 +15,25 @@ This guide shows how to set up simple test bench that automatically test your co
|
||||
|
||||
We will set up a spare machine (bare metal, not a virtual) that will be hosting our experimental Dom0. We will communicate with it via Ethernet and SSH. This tutorial assumes you are familiar with [QubesBuilder](/doc/qubes-builder/) and you have it set up and running flawlessly.
|
||||
|
||||
## Setting up the machine
|
||||
<div class="alert alert-warning" role="alert">
|
||||
<i class="fa fa-exclamation-triangle"></i>
|
||||
<b>Notice:</b>
|
||||
This setup intentionally weakens some security properties in the testing system. So make sure you understand the risks and use exclusively for testing.
|
||||
</div>
|
||||
|
||||
First, do a clean install from ISO you built or grabbed elsewhere.
|
||||
|
||||
You have to fix network, because it is intentionally broken. This script should reenable your network card without depending on anything else.
|
||||
## Setting up the Machine
|
||||
|
||||
### Install ISO
|
||||
First, do a clean install from the `.iso` [you built](/doc/qubes-iso-building/) or grabbed elsewhere (for example [here](https://qubes-os.discourse.group/t/qubesos-4-1-alpha-signed-weekly-builds/3601))
|
||||
|
||||
### Enabling Network Access in Dom0
|
||||
|
||||
Internet access is intentionally disabled by default in dom0. But to ease the deployment process we will give it access. The following steps should be done in `dom0`.
|
||||
|
||||
1. Remove the network card (PCI device) from `sys-net`
|
||||
2. Restart your computer (for the removal to take effect)
|
||||
3. The following script should enable your network card in dom0. *Be sure to adjust the script's variables to suit your needs.*
|
||||
|
||||
```bash
|
||||
#!/bin/sh
|
||||
@ -27,6 +41,9 @@ You have to fix network, because it is intentionally broken. This script should
|
||||
# adjust this for your NIC (run lspci)
|
||||
BDF=0000:02:00.0
|
||||
|
||||
# adjust this for your network driver
|
||||
DRIVER=e1000e
|
||||
|
||||
prog=$(basename $0)
|
||||
|
||||
pciunbind() {
|
||||
@ -50,22 +67,20 @@ pcibind() {
|
||||
}
|
||||
|
||||
pciunbind ${BDF}
|
||||
pcibind ${BDF} e1000e
|
||||
pcibind ${BDF} ${DRIVER}
|
||||
|
||||
dhclient
|
||||
sudo dhclient
|
||||
```
|
||||
|
||||
TODO: describe how to run this at every startup
|
||||
4. Configure your DHCP server so your testbench gets static IP and connect your machine to your local network. You should ensure that your testbench can reach the Internet.
|
||||
|
||||
Now configure your DHCP server so your testbench gets static IP and connect your machine to your local network. You should ensure that your testbench can reach the Internet.
|
||||
|
||||
Install `openssh-server` on your testbench:
|
||||
5. Install `openssh-server` on your testbench (since dom0 now has internet access the command `qubes-dom0-update` is not needed).
|
||||
|
||||
~~~
|
||||
yum install openssh-server
|
||||
sudo dnf install openssh-server
|
||||
~~~
|
||||
|
||||
Ensure that sudo works without password from your user account (it should by default).
|
||||
**Note:** You'll need to run the at every startup (TODO: describe how to run this at every startup)
|
||||
|
||||
## Development VM
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user