vh/esh-pfi-infrastructure
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

docs(ipv6): retire the next-candidates line now that all three are done

Browse Source 
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.
This commit is contained in:
vh
2026-08-23 22:39:51 -07:00
parent 4e83395ddf
commit d127e29fac
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/pfi/ipv6-naming-scheme.md
+5 -2
View File
@@ -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 Worth remembering as the general path for guests whose credentials are not
vaulted. vaulted.
Natural next candidates, both on `esh-server` and both real Linux hosts: Every Linux host on `esh-server` now carries its name. The remaining ESH
`esh-pve-nas` → `…:4411:b105:50:55`, `esh-vm-db` → `…:4411:b105:50:60`. 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.