feat: rebranded from vpn-router to linux-manager.

This commit is contained in:
slawek committed 2026-11-22 09:51:07 +01:00
1 parent 8efe21bfa6
commit 85a1ffa21f
238 files changed
+5010 -3761

No files matched your search

+7 -7
View File
@@ -1,6 +1,6 @@
# Azure example
Deploys `vpn-router` on an Azure VM: a two-NIC router (external/WAN and internal/protected),
Deploys `linux-manager` on an Azure VM: a two-NIC router (external/WAN and internal/protected),
a demo protected `workload` subnet routed through it, and cloud-init that installs and
configures the package on first boot. See the repository's top-level [README](../../README.md)
for what the package itself does.
@@ -10,10 +10,10 @@ for what the package itself does.
- An Azure subscription and `az login` (or another form of Azure credentials Terraform can pick
up).
- An SSH key pair for `admin_ssh_public_key`.
- A build of the `vpn-router` package published to the repository at `repo_url` (default: the
- A build of the `linux-manager` package published to the repository at `repo_url` (default: the
project's Gitea Debian registry). See [../../debian-package](../../debian-package) for
`build.sh`/`publish.sh`.
- That repository must allow anonymous reads, since the router pulls the package with no
- That repository must allow anonymous reads, since the server pulls the package with no
credentials configured. On Gitea this means the `debian` package registry under the
`slawek` account is set to public/anonymous-read; `publish.sh` still authenticates to
upload, only reads are anonymous. This is a one-time change made on the Gitea side, outside
@@ -28,7 +28,7 @@ export TF_VAR_psk='change-me' # keep secrets out of tracked files
```
`platform = azure` and `mode = auto` are hard-coded into the cloud-init template call in
`router.tf`: the router has exactly two NICs, the external one carries the default route (it is
`router.tf`: the server has exactly two NICs, the external one carries the default route (it is
marked `primary` and holds the public IP), which is exactly the case `mode = auto` is designed
to detect reliably - see the top-level README's "What mode decides" section.
@@ -36,10 +36,10 @@ to detect reliably - see the top-level README's "What mode decides" section.
```sh
ssh <admin_username>@$(terraform output -raw router_public_ip)
systemctl status vpn-router-setup
systemctl status linux-manager-setup
swanctl --list-sas
```
Set `deploy_workload_vm = true` and re-apply to add a VM on the `workload` subnet (no public
IP - reach it via the router or Azure Bastion) for confirming that its traffic to `remote_cidrs`
actually flows through the router.
IP - reach it via the server or Azure Bastion) for confirming that its traffic to `remote_cidrs`
actually flows through the server.