From c923727cf2301732885e0100419d4f40f94d7be1 Mon Sep 17 00:00:00 2001 From: Vuong Hoang Date: Fri, 25 Sep 2026 23:30:03 -0700 Subject: [PATCH] memory: AMT follow-ups parked until the MS-03s arrive; OOB path through nh3-scale noted --- persistent-memory.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/persistent-memory.md b/persistent-memory.md index 70b8f5f..a74457e 100644 --- a/persistent-memory.md +++ b/persistent-memory.md @@ -139,8 +139,14 @@ hermes-gateway, Booth, ttyd, zellij-web and dev-backup are running. `scripts/amt-wsman.py`. - Root cause earlier tonight: Linux had the port down (the `igc` PHY was off). Fixed with `auto enp88s0`, IPv6 off and `arp_ignore=8`. - - **Open:** Prime's first MeshCommander session, then a dummy HDMI plug, then - move the NanoKVM to the gx10. + - ⏸ **AMT follow-ups PARKED (Prime, 2026-09-25 2326)** until the two new MS-03s + arrive and esh-pve's MS-01 is also on AMT. Parked items: + - MeshCommander test. + - Dummy HDMI plug, then the NanoKVM → gx10 move. + - An OOB path that does not run through nh3-pve. Today ANA/ESH → NH3 goes via + nh3-scale, CT 107 on nh3-pve, so remote AMT dies with the host. Recommended + fix: route 10.100.250.0/24 over the FortiGate↔UDM IPsec `pfi-ana-nh3`. + - Adding AMT to TRMM's MeshCentral (rmm-mesh, public IP; wants 2FA). - Found and fixed: **lxc-pve 6.0.0-1 broke Docker in the CT** (runc 1.5 sysctl reopen denied). Upgraded that one package to 6.0.0-2 (Proxmox fix #7006), and `gpu-lxc.yaml` now does this itself.