From 503372614597440f704b28ebd9e52b9ae45a15f6 Mon Sep 17 00:00:00 2001 From: Matti Airas Date: Wed, 5 Aug 2026 15:15:34 +0300 Subject: [PATCH] docs(remote-access): name the config file up front The two-part summary at the top described what to change without saying where it lives. Co-Authored-By: Claude Opus 5 (1M context) --- docs/user-guide/remote-access-vpn.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/remote-access-vpn.md b/docs/user-guide/remote-access-vpn.md index fcfbb42..96077fe 100644 --- a/docs/user-guide/remote-access-vpn.md +++ b/docs/user-guide/remote-access-vpn.md @@ -4,7 +4,7 @@ To reach HaLOS from outside the LAN, the device's canonical hostname must resolv Enabling remote access has two parts: -1. Change the canonical from `${hostname}.local` to a fully-qualified domain name (FQDN, a name with at least one dot in it, like `halos.example`) that resolves on your LAN. +1. Change the canonical from `${hostname}.local` to a fully-qualified domain name (FQDN, a name with at least one dot in it, like `halos.example`) that resolves on your LAN. The canonical is the first line of `/etc/halos/hostnames.conf`. 2. Make the same FQDN resolve from the remote network. You'll also need a VPN connecting the remote network to the device's LAN. Configuring the VPN itself is out of scope for this page.