**Chat log** from Bead: Simtable Network · [canonical source](https://redfish.acequia.io/guerin/.agents/40a28642-b4bb-4a6d-93c3-c6f1ce1af361/2026-06-14/chats/2026-06-14-simtable-network.md) · session 2026-06-14 · discussion: Talk: Simtable Network *Verbatim chat log: immutable provenance. The bead's copy is ground truth; wiki edits here are a fork, never the record.*
Bead `40a28642-b4bb-4a6d-93c3-c6f1ce1af361` · 2026-06-14 · animator CV `my-claude-vscode` · parciante Stephen. Hatched mid-thread from the office-move discussion in the home-port-forward bead `7049c694`; upstream context lives in that bead's chat log.
**Pre-bead context (back-captured):** Stephen moved the host machine from home to the office. Established: office has **5 static IPs** `50.243.20.250–.254`; `node.redfish.com` → `.250`; this machine egresses via `.254`; NordVPN installed but **off**. Then: **Stephen (verbatim):** > check what servers are responding to the 250-254 on 80 and 443 **Assistant:** scanned the block from inside (egress `.254`) on 80/443, with TLS cert subjects: `.250` = node.redfish.com (Apache/2.4.48 Ubuntu, LE cert, **up**; nephele `:3334` down); `.251` = **Axis camera** (`CN=axis-accc8ef2e6c9`); `.252/.253/.254` = `000` internally (**NAT-hairpin** — external reachability unconfirmed; `.254` is the local Caddy box, definitely listening). Flagged the hairpin caveat: need an off-network probe to judge `.252/.253/.254`. **Stephen (verbatim):** > start-bead simtable-network **Assistant:** opened this bead (`40a28642`, slug `simtable-network`) and seeded it with the scan as [00-simtable-office-network.md](../notes/00-simtable-office-network.md) — the office static-IP inventory + LAN topology + open items (external probe of `.252/.253/.254`; confirm which static inbound-NATs to `192.168.1.19` for `stephenguerin.live`; node.redfish.com `:3334` down; build the Caddy ingress table). Distinct from sibling `7049c694` (the hosting *runbook*); this bead is the network *map*.