docs(deploy): the home end's check of the tunnel with nc's own timeout (ADR 0032)
Run on the home end, the check that nothing new from the tunnel reaches the instance's server failed at once with "missing port number" instead of trying. OpenBSD's nc, as the WireGuard image has it, ends the try with its own -w, without timeout or a shell around it; checked on the home end on 31 Oct 2026, where it gave up after 5 s. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>
This commit is contained in:
parent
82fa7aec1b
commit
4c78c7d2c5
1 changed files with 3 additions and 2 deletions
|
|
@ -242,8 +242,9 @@ home machine.
|
||||||
and on the home machine, in `deploy/home-jellyfin/`:
|
and on the home machine, in `deploy/home-jellyfin/`:
|
||||||
|
|
||||||
```sh
|
```sh
|
||||||
# Refused (nothing new from the tunnel reaches the host): times out.
|
# Refused (nothing new from the tunnel reaches the host): gives up after 5 s. The
|
||||||
docker compose exec -T wireguard sh -c 'timeout 5 nc 10.61.96.1 22 </dev/null' && echo LEAK
|
# image's nc is OpenBSD's, whose own -w ends the try.
|
||||||
|
docker compose exec -T wireguard nc -w 5 -z 10.61.96.1 22 && echo LEAK
|
||||||
```
|
```
|
||||||
|
|
||||||
Stopping the home end (`docker compose stop`) makes the site answer 502, and
|
Stopping the home end (`docker compose stop`) makes the site answer 502, and
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue