From d127e29fac24a05e98c18a3e303059ccef0d388d Mon Sep 17 00:00:00 2001 From: Vuong Hoang Date: Sun, 23 Aug 2026 22:39:51 -0700 Subject: [PATCH] docs(ipv6): retire the next-candidates line now that all three are done Replaces it with why the remaining segments have no eligible hosts: two are appliance-only and three have no IPv6 enabled yet, pending the firewall-policy pass that SLAAC on a client segment would require. --- docs/pfi/ipv6-naming-scheme.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/pfi/ipv6-naming-scheme.md b/docs/pfi/ipv6-naming-scheme.md index 1cfab74..158503c 100644 --- a/docs/pfi/ipv6-naming-scheme.md +++ b/docs/pfi/ipv6-naming-scheme.md @@ -167,5 +167,8 @@ base64 because quoting a multi-line script through two SSH layers mangles it. Worth remembering as the general path for guests whose credentials are not vaulted. -Natural next candidates, both on `esh-server` and both real Linux hosts: -`esh-pve-nas` → `…:4411:b105:50:55`, `esh-vm-db` → `…:4411:b105:50:60`. +Every Linux host on `esh-server` now carries its name. The remaining ESH +segments have no eligible hosts: `esh-cameras` and `esh-iot` are appliances +with no shell, and `esh-mgmt`, `esh-userland` and `Default` are still +`ipv6_interface_type: none` pending the firewall-policy pass — enabling SLAAC +there gives every client a globally reachable address.