MakerFLOSS_Troubleshooting/incidents/README.md
sjat 9ff12700ae Initial troubleshooting workspace: access, network map, runbooks
Scaffold for troubleshooting MakerFLOSS hosts at the makerspace.
Reference + thin runbooks model — authoritative data stays in the
source repos (AnsibleBaobabV4, MakerFLOSS_Mikrotik, MakerFLOSS).

- access.md: reach paths for mamba-on-LAN and fisi-tunneling-in
  (netbird on-demand, VPS bastion, ProxyJump via kuku->mamba),
  with the isolation rule.
- network-map.md: subnet pointers + open question on makerspace
  addressing (10.2.30/172.17.3/10.0.0).
- runbooks/switch-crs310.md: CRS310 connectivity + lockout recovery.
- incidents/: dated log scaffold.
- CLAUDE.md: operating rules for this repo.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-09 13:24:26 +02:00

33 lines
546 B
Markdown

# 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
```markdown
# 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
_(none yet)_