ccnet-WI: reconcile hostnames across WI systems #27

Open
opened 2026-07-14 07:45:46 +00:00 by claude-bot · 0 comments
Collaborator

docs/ccnet-wi-site.md flags that ccnet-wi-fw's runtime hostname (literally '2') doesn't match its configured hostname (copper-wi-fw), which itself doesn't match the device's actual name used everywhere else — DNS, this repo's docs, etc. (ccnet-wi-fw). Worth checking whether the same drift exists on the other WI systems (trixie, jump, qnap, pbs) while at it.

Scope: set the OS-level hostname on every ccnet-WI system to match its documented/DNS name consistently. Cosmetic, low priority — doesn't affect routing, the WireGuard tunnel, or backups — but worth a single pass so logs and hostname-based tooling aren't confusing later.

Related: docs/ccnet-wi-site.md's ccnet-wi-fw section.

docs/ccnet-wi-site.md flags that ccnet-wi-fw's runtime hostname (literally '2') doesn't match its configured hostname (copper-wi-fw), which itself doesn't match the device's actual name used everywhere else — DNS, this repo's docs, etc. (ccnet-wi-fw). Worth checking whether the same drift exists on the other WI systems (trixie, jump, qnap, pbs) while at it. Scope: set the OS-level hostname on every ccnet-WI system to match its documented/DNS name consistently. Cosmetic, low priority — doesn't affect routing, the WireGuard tunnel, or backups — but worth a single pass so logs and hostname-based tooling aren't confusing later. Related: docs/ccnet-wi-site.md's ccnet-wi-fw section.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
copper/ccnet-prod-devops#27
No description provided.