Files
claudetools/.claude/memory/infra_office_network.md
Mike Swanson cd80f5e447 feat: add wiki knowledge layer (Phase 0 + Phase 1 seed)
Implements LLM-compiled wiki layer between raw session logs and live
CONTEXT.md, inspired by Karpathy's knowledge base workflow. Adds wiki/
directory structure, article templates, spec docs, and seeds first two
articles (Cascades of Tucson, GuruRMM) from 60+ session logs.

Updates CLAUDE.md to check wiki first on all context-loading triggers.
Captures verified ACG IP/hostname map and Neptune physical-location
clarification (Dataforth D2, subnet overlap TODO) in memory.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-24 15:42:38 -07:00

2.3 KiB

name, description, metadata
name description metadata
infra-office-network ACG office LAN infrastructure — IPs, hosts, roles, and post-power-failure recovery
type
project

ACG office LAN is 172.16.0.0/22, routed via Tailscale through pfSense node pfsense-2 (100.119.153.74).

Key hosts:

Host IP SSH Role
pfSense 172.16.0.1 port 2248, user admin Router, DNS (Unbound), Tailscale subnet router
Jupiter 172.16.3.20 port 22, user root Unraid NAS — all VMs + Docker containers
Uranus 172.16.3.21 (no key) OwnCloud additional storage only — NOT a proxy
GuruRMM VM 172.16.3.30 port 22, user guru Linux VM on Jupiter — GuruRMM, Coord API, MariaDB, Gitea
Pluto 172.16.3.36 (Windows) Windows Server 2019 VM on Jupiter — MSI build server

Why: How to apply: check these IPs before assuming what's where. .21 is NOT the Seafile proxy — NPM on .20 is.

Docker on Jupiter (.20):

  • npm — Nginx Proxy Manager (ports 1880/7818/18443)
  • seafile + seafile-mysql + seafile-elasticsearch + seafile-memcached — Seafile stack (port 8082)
  • gitea — port 3000 (also accessed as 172.16.3.20:3000 or via SSH port forward from GuruRMM VM at .30:3000)

NPM → 443 routing: iptables PREROUTING on Jupiter: dpt:443 → 172.17.0.2:443 (NPM container). Persisted in /boot/config/go. DNS sync.azcomputerguru.com → 172.16.3.20.

VMs on Jupiter (virsh): GuruRMM, Unifi, OwnCloud, Claude-Builder (running); Windows 7, Windows Server 2016, Windows Server 2016_Template (shut off).

Neptune (ACG infra, physically at Dataforth D2):

  • neptune.acghosting.com | internal 172.16.3.11 | external 67.206.163.124
  • Exchange Server 2016 — active mail server for multiple ACG-hosted clients
  • Physically colocated at Dataforth's D2 facility, NOT at ACG office
  • Access from ACG office: must route through D2TESTNAS (192.168.0.9) because Dataforth's UDM runs a subnet overlapping ACG office LAN (both use 172.16.x.x range), making direct routing ambiguous
  • TODO: Resubnet Dataforth UDM to a non-overlapping range to fix routing and simplify Neptune access

Why: How to apply: see power-failure-runbook for full post-outage recovery steps. Neptune is NOT on ACG office LAN despite the 172.16.x.x IP — always route via D2TESTNAS or Dataforth VPN.