MakerFLOSS_Troubleshooting/incidents
sjat 2194a26970 access: rewrite for the ubongo era; srv07 incident; refresh network map
fisi is decommissioned and boma retired Netbird (ADR-036), so the old
Claude-on-fisi/Netbird access doctrine is gone. New order: VPS bastion
ProxyJump onto wg1 (primary, isolation-clean), via mamba over the boma hub
when on-site. Netbird control plane kept but demoted to legacy (operator
decision, not an access path). Network map refreshed from live probing
2026-07-17: rack LAN is 10.0.0.0/24, wifi 172.17.3.0/24 does not route to
it, 10.2.30.0/24 likely gone. Incident log covers the srv07/mf04 identity
fix and re-established access.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-17 17:23:18 +02:00
..
2026-07-05-mamba-loses-netbird-on-switch-cable.md incidents: mamba loses netbird when switch cable plugged in 2026-07-05 17:50:20 +02:00
2026-07-17-srv07-access.md access: rewrite for the ubongo era; srv07 incident; refresh network map 2026-07-17 17:23:18 +02:00
README.md incidents: mamba loses netbird when switch cable plugged in 2026-07-05 17:50:20 +02:00

Incidents

Dated log of issues we troubleshoot and how they resolved. One file per incident: YYYY-MM-DD-short-slug.md. Keep them short and factual — symptom, what we found, what we changed (and in which source repo), outcome.

Suggested template

# YYYY-MM-DD — <short title>

- **Host(s):** 
- **Reported by / observed:** 
- **Reach path used:** (access.md §...)

## Symptom

## Investigation

## Root cause

## Fix
- Source repo + commit: 
- Live action taken: 

## Verification

## Follow-ups

Log