From 1011741e65bcf212f6d5f7bcff39604b328091f0 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 20 Jun 2026 17:41:04 +0300 Subject: =?UTF-8?q?f3s:=20fix=20WireGuard=20key=20mismatch=20=E2=80=94=20f?= =?UTF-8?q?3=20now=20reachable=20from=20fishfinger/blowfish?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Corrected mutual pubkey and PSK mismatch between f3 and both OpenBSD gateways. f3 is now reachable directly via WireGuard from fishfinger or blowfish without the double-hop workaround. Co-Authored-By: Claude Sonnet 4.6 --- prompts/skills/f3s/references/remote-access.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/prompts/skills/f3s/references/remote-access.md b/prompts/skills/f3s/references/remote-access.md index 2c1f1d0..c507671 100644 --- a/prompts/skills/f3s/references/remote-access.md +++ b/prompts/skills/f3s/references/remote-access.md @@ -30,10 +30,15 @@ One-shot from the laptop (handy for scripts/automation): ssh -A -J rex@fishfinger.buetow.org paul@f0.wg0 "sh -c 'hostname; doas freebsd-version'" ``` -Use `f0.wg0` / `f1.wg0` / `f2.wg0` — the WireGuard hostnames as seen from -the gateway. **Note:** `f3.wg0` is not currently reachable from the gateways -(its WireGuard path does not route through fishfinger/blowfish); reach f3 from -a host already on the LAN, or investigate the WireGuard peer config on f3. +Use `f0.wg0` / `f1.wg0` / `f2.wg0` / `f3.wg0` — the WireGuard hostnames as +seen from the gateway. `f3.wg0` resolves to `192.168.2.133`: + +```sh +ssh -A -J rex@fishfinger.buetow.org paul@192.168.2.133 # f3 direct via WireGuard +``` + +(Previously the f3↔GW WireGuard tunnel was broken due to key mismatches; fixed +in gq0 — pubkeys and PSKs corrected on f3 and on fishfinger/blowfish.) ### Reaching r-VMs (Rocky Linux) and `rocky` -- cgit v1.2.3