A.M.P.
Hōʻike — Network Operations Center
📋 MOPs
📡 ISP Watch
🔗 Links
Tailscale-Gated · Internal Only
Refresh in
60
s
Infrastructure
Loading...
Loading...
Loading...
Fleet Overview
Gateway Status
Loading...
Subscribers
▦ Open Subs
✕ CLOSE
Active Users
✕
Loading…
▶
Puka Setup Checklist
Reset
Setting up:
Puka 20 — Kent, WA
Puka 21 — Waimea, HI
Puka 22 — Nanakuli, HI
Puka 23 — Waianae, HI
1 · Physical Boot
Plug in puka (ethernet or power)
Ethernet first if WiFi not yet configured
Puka appears on Tailscale and shows
ONLINE
on Hōʻike
Allow ~2 minutes for boot + heartbeat
Confirm node ID and serial match expected puka
ssh -i ~/.ssh/amp-deploy pi@<TS-IP> "cat /etc/amp/serial"
2 · WiFi Setup (skip if on ethernet)
SSH into puka via Tailscale
ssh -i ~/.ssh/amp-deploy pi@<TS-IP>
Scan for home WiFi network
sudo nmcli device wifi rescan && sudo nmcli device wifi list
Connect to home WiFi
sudo nmcli device wifi connect "SSID" password "PASSWORD" ifname wlan0
Verify connection and confirm puka still reachable
nmcli connection show --active
3 · WireGuard Tunnel
Confirm WireGuard service is running on puka
sudo systemctl status wg-quick@wg0 --no-pager
Check handshake from BT (should be < 3 minutes)
wg show wg<N> latest-handshakes
Confirm route table is pointing to correct interface
ip route show table <N>
Should show: default dev wg<N> (not wg20 or wg_aikai)
4 · Subscriber Onboarding
Subscribers assigned to this gateway in DB
Verify in Subscribers section below — should show "not connected"
Share WireGuard QR code with each subscriber
Subscriber installs WireGuard app and scans QR code
Subscriber enables VPN — verify
● online
appears on Hōʻike within 3 minutes
5 · Health Sign-off
No
wifi_driver_reload
events in last hour
Failover state: Tier 1, not flapping
cat /var/lib/amp/failover-node<N>.json
Puka shows
ONLINE
on Hōʻike with green WireGuard status
Update DR backup zip after any DB or config changes