feat: rebranded from vpn-router to linux-manager.
This commit is contained in:
1 parent
8efe21bfa6
commit
85a1ffa21f
238 files changed
+5010
-3761
No files matched your search
@@ -1,6 +1,6 @@
|
||||
# GCP example
|
||||
|
||||
Deploys `vpn-router` on a GCE instance: a two-NIC router (external/WAN and internal/protected,
|
||||
Deploys `linux-manager` on a GCE instance: a two-NIC router (external/WAN and internal/protected,
|
||||
each its own VPC network), a demo protected `workload` subnet in the internal network 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, and
|
||||
@@ -11,9 +11,9 @@ repository's top-level [README](../../README.md) for what the package itself doe
|
||||
- A GCP project and credentials Terraform can pick up (`gcloud auth application-default login`
|
||||
or a service account).
|
||||
- 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
|
||||
`build.sh`/`publish.sh`. That repository must allow anonymous reads, since the server pulls
|
||||
the package with no credentials configured.
|
||||
|
||||
## Usage
|
||||
@@ -25,7 +25,7 @@ export TF_VAR_psk='change-me' # keep secrets out of tracked files
|
||||
```
|
||||
|
||||
`platform = gcp` and `mode = auto` are hard-coded into the cloud-init template call in
|
||||
`router.tf`: the router has exactly two NICs, and on GCP the system default route always goes
|
||||
`router.tf`: the server has exactly two NICs, and on GCP the system default route always goes
|
||||
out NIC0 (the external one here) while a secondary NIC only reaches its own subnet unless
|
||||
policy-routed - exactly the case `mode = auto` is designed to detect reliably. See the
|
||||
top-level README's "What mode decides" section.
|
||||
@@ -39,10 +39,10 @@ needs no separate subnet association - the route in `internal` already covers bo
|
||||
|
||||
```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 IAP) for confirming that its traffic to `remote_cidrs` actually
|
||||
flows through the router.
|
||||
IP - reach it via the server or IAP) for confirming that its traffic to `remote_cidrs` actually
|
||||
flows through the server.
|
||||
Reference in new issue
Block a user