sjat/MakerFLOSS_Troubleshooting
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
10 commits 1 branch 0 tags 92 KiB
Find a file
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
docs/superpowers plan: TaPPaaS-side publishing (sendable, self-contained) 2026-06-28 13:47:38 +02:00
incidents access: rewrite for the ubongo era; srv07 incident; refresh network map 2026-07-17 17:23:18 +02:00
runbooks runbook: swap flossfw wg1 peer public key on operator onboarding 2026-06-28 13:57:53 +02:00
.gitignore Initial troubleshooting workspace: access, network map, runbooks 2026-06-09 13:24:26 +02:00
access.md access: rewrite for the ubongo era; srv07 incident; refresh network map 2026-07-17 17:23:18 +02:00
CLAUDE.md access: rewrite for the ubongo era; srv07 incident; refresh network map 2026-07-17 17:23:18 +02:00
network-map.md access: rewrite for the ubongo era; srv07 incident; refresh network map 2026-07-17 17:23:18 +02:00
README.md Initial troubleshooting workspace: access, network map, runbooks 2026-06-09 13:24:26 +02:00

README.md

MakerFLOSS Troubleshooting

A working repo for troubleshooting and fixing hosts at the Orange Makerspace that are part of the MakerFLOSS project.

This repo is reference + thin runbooks: it does not duplicate authoritative data (IPs, topology, secrets). Those live in the source repos below. Here we keep access procedures, runbooks, and an incident log, with pointers back to source.

Source repos (authoritative)

Repo Path What it owns
AnsibleBaobabV4 ~/Projects/AnsibleBaobabV4 Canonical infra-as-code. The makerfloss VPS, makerfloss1, mf04, the makerfloss WireGuard plane (wg1), the Netbird control plane, and all containerised services. This is where most fixes land.
MakerFLOSS_Mikrotik ~/Projects/MakerFLOSS_Mikrotik The CRS310 switch (crs310-maker) — Ansible-managed RouterOS config. The "new switch" at the makerspace.
MakerFLOSS ~/Projects/MakerFLOSS Documentation site (docs.makerfloss.eu) and slides. Docs-only; the human-readable hardware/service catalog.

Note: AnsibleBaobabV4 is a separate (homelab) project that also happens to manage the MakerFLOSS infrastructure — early MakerFLOSS work started there and stayed. Its git remote is the baobab Forgejo, not the MakerFLOSS one.

Where fixes go

Fixes land in the relevant source repo's main branch (per decision 2026-06-09). Switch/live-infra changes still follow that repo's own lockout-safety and idempotency rules (e.g. run device-touching plays twice; enable VLAN-filtering last). This repo only holds runbooks and the incident log.

Layout

.
├── access.md            # HOW to reach makerspace hosts (read this first)
├── network-map.md       # thin network overview + pointers + open questions
├── runbooks/            # task-focused troubleshooting guides
│   ├── README.md
│   └── switch-crs310.md
└── incidents/           # dated log of issues worked + outcomes
    └── README.md

Quick start for a troubleshooting session

  1. Read access.md — pick a reach path for where you are (makerspace with mamba, or tunneling in from fisi).
  2. Check network-map.md for the host/subnet you're after.
  3. Find or create a runbook in runbooks/.
  4. Apply fixes in the source repo; log what happened in incidents/.