vault-sync: 2026-10-06 06:01 (jimmy)

2026-10-06 06:01:04 -07:00
parent d7d743a8a1
commit 7589b73608
5 changed files with 155 additions and 9 deletions
@@ -275,3 +275,20 @@ stale tailnet identity corrected in memory (this box = `tonyb` @ 100.96.158.89,
 - T10 deeper fix → raise `memory.memory_char_limit` 2200→3000 in `/hermes/config.yaml`
  (global; affects all profiles) — one-line change, awaiting go.
 - T02 generic exit codes — noise bucket, monitored not fixed.
+
+
+### T29 root cause (2026-10-06)
+Recurring Telegram breakage = **IPv6 enabled but non-functional** on this box:
+`ms_tcpip6` binding True on Ethernet/Wi-Fi, **no global IPv6 address** (link-local only),
+**no `::/0` route** — yet DNS returns an AAAA for `api.telegram.org`. Every hostname connect
+burns a cycle on the black-holed IPv6 path (`ConnectError('')`) before falling back to IPv4
+(which works: `curl -4` 5/5, 302, 0.16 s). `logs/gateway.log` shows the flap loop; 294
+`telegram_network` events, 121 reconnects; clusters 09-01/02/05, 10-03/05.
+**Fix (admin/UAC, not applied):** `Disable-NetAdapterBinding -Name Ethernet -ComponentID ms_tcpip6`
+(+ `Wi-Fi`); keep the Tailscale adapter's IPv6. **Not a watchdog** — root-cause per the repo principle.
+Evidence: `curl -4/-6`, `Get-NetAdapterBinding`, `Get-NetRoute -AddressFamily IPv6 -DestinationPrefix '::/0'`.
+
+### T10 (2026-10-06)
+`memory.memory_char_limit` raised 2200 → 3000 in `/hermes/config.yaml` (backup:
+`config.yaml.bak-memlimit-20261005-235840`). Effective for NEW sessions; the running session
+cached 2200 at startup.