49 lines
2.0 KiB
Markdown
49 lines
2.0 KiB
Markdown
# Remote tests
|
|
|
|
`run.py` installs the newest `out/linux-manager_*_all.deb` into LXD instances of a remote and
|
|
checks the router and VPN components in three scenarios:
|
|
|
|
- `core`: one interface, router and VPN off;
|
|
- `nat`: VPN on, router off, one interface; WireGuard and OpenVPN clients reach a target through
|
|
NAT, then the VPN is switched off;
|
|
- `s2s`: router and VPN on, two sites with two interfaces each, a site-to-site connection with a
|
|
pre-shared key, and a routed WireGuard client; the router is then switched off while
|
|
`site_to_site` is set, which setup refuses.
|
|
|
|
Servers are virtual machines, clients and LAN hosts containers, all from `ubuntu:26.04`. Each
|
|
scenario is a module in `scenarios/` whose `run(lab)` uses the `Lab` class of `run.py`.
|
|
`wireguard_peer.py` and `echo.py` are copied into the instances: the first gives the test user a
|
|
WireGuard peer on the server, the second answers HTTP with the client's address.
|
|
|
|
```sh
|
|
export LXD_REMOTE=...
|
|
export LXD_POOL=...
|
|
```
|
|
|
|
```sh
|
|
./build.sh
|
|
tests/remote/run.py core nat s2s
|
|
```
|
|
|
|
```sh
|
|
tests/remote/run.py all
|
|
```
|
|
|
|
Options:
|
|
|
|
| Option | Variable | Default | Meaning |
|
|
|---|---|---|---|
|
|
| `--remote` | `LXD_REMOTE` | required | The `lxc` remote |
|
|
| `--pool` | `LXD_POOL` | required | The storage pool of the project's root disks |
|
|
| `--project` | `LXD_PROJECT` | `lm-test` | The project the instances live in; it must not exist |
|
|
| `--image` | `LXD_IMAGE` | `ubuntu:26.04` | The image of every instance |
|
|
| `--keep` | | off | Leaves the project and the networks in place; run one scenario then |
|
|
|
|
Each scenario creates the project and its networks (`lmt-<scenario>-<net>`) and removes them at
|
|
its end. The administrator password and the pre-shared key are generated per run and written to
|
|
`tmp/remote-test.env`. The run prints PASS, FAIL or SKIP per check and exits non-zero on a
|
|
failure; WireGuard is skipped when the host kernel has no WireGuard module.
|
|
|
|
Not covered: IKEv2 client access, HTTPS with Let's Encrypt, the OpenID Provider and passkeys,
|
|
PowerDNS answering from outside, and the Azure and GCP platform modules.
|