Cut over remaining service references to Nebula overlay addresses or mesh DNS #23

Open
opened 2026-07-01 16:17:21 +01:00 by nimmo · 0 comments
Owner

Goal

Complete Phase 5 of the Nebula rollout by replacing remaining hardcoded LAN addresses with Nebula overlay addresses or mesh hostnames.

Context

projects/nebula-mesh-network.md records Phases 0–4 and 2.5 as complete. The remaining open work is the service cutover phase.

Acceptance Checklist

  • Identify the remaining service configs that still use 192.168.8.x addresses.
  • Replace them with 10.10.0.x overlay addresses or mesh hostnames where appropriate.
  • Confirm the affected services continue to work both on-LAN and off-LAN through the mesh.
  • Prefer the Nebula path only where it improves portability and resilience; do not churn working configs without a reason.

Candidate Targets Called Out In The Note

  • Ollama
  • NFS consumers
  • other service configs still pinned to LAN IPs

Verification

End-to-end checks should confirm that existing service access still works after the address change, including at least one cross-host access path over the mesh.

## Goal Complete Phase 5 of the Nebula rollout by replacing remaining hardcoded LAN addresses with Nebula overlay addresses or mesh hostnames. ## Context `projects/nebula-mesh-network.md` records Phases 0–4 and 2.5 as complete. The remaining open work is the service cutover phase. ## Acceptance Checklist - Identify the remaining service configs that still use `192.168.8.x` addresses. - Replace them with `10.10.0.x` overlay addresses or mesh hostnames where appropriate. - Confirm the affected services continue to work both on-LAN and off-LAN through the mesh. - Prefer the Nebula path only where it improves portability and resilience; do not churn working configs without a reason. ## Candidate Targets Called Out In The Note - Ollama - NFS consumers - other service configs still pinned to LAN IPs ## Verification End-to-end checks should confirm that existing service access still works after the address change, including at least one cross-host access path over the mesh.
Sign in to join this conversation.
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
nimmo/nixos-config#23
No description provided.