REPORT: sequencing check after the fact; resolution paths recorded
Timeline from HA's created_at and the ingress log shows the required order (rule proven from HA -> entries on the alias -> vhost removed) held, and that no HA entry referenced forgeway.dmz.lounge when the vhost went. All four names' resolution paths are written down explicitly. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Fable 5.1
parent
f1e0103b5e
commit
846940e1d0
@@ -459,3 +459,57 @@ was never touched.
|
||||
|
||||
Nothing is left for Rick unless he wants the optional bits from Addendum 3 (default
|
||||
assistant, device control, cosmetic subentry rename).
|
||||
|
||||
---
|
||||
|
||||
# Addendum 5, 2026-09-18 — sequencing check after the fact, and the resolution paths
|
||||
|
||||
A sequencing constraint arrived after Addendum 4 had executed: *prove the pfSense rule
|
||||
from HA first, move the entries to the alias second, remove the vhost only then, and if
|
||||
the rule cannot be proven, leave the vhost.* It was worth re-establishing the state
|
||||
rather than arguing, so here is the timeline from HA's own `created_at` values and the
|
||||
ingress access log (all UTC, 2026-09-18):
|
||||
|
||||
| Time | Event | Evidence |
|
||||
|---|---|---|
|
||||
| 18:26 | My first HA entry, on `forgeway.dmz.lounge` via the entrance vhost | Addendum 2 |
|
||||
| ≈18:35 | **Rick** adds the pfSense rule `192.168.120.12 → 172.19.10.11` and removes that entry | his statement; the entry was gone by 18:42 |
|
||||
| **18:39:18** | HA entry `01M2TX1P` created on **`forgeway.services…/local-optimistic`** (Rick's side) | HA `created_at`; loading requires `GET /api/tags` over TLS to `172.19.10.11`, i.e. **the rule works, proven from HA itself** |
|
||||
| **18:44:34** | HA entry `01M2TXBA` created on **`forgeway.services…/local-strict`** (me) | HA `created_at`, same proof |
|
||||
| ≈18:50–18:58 | Real conversations through both alias agents, and the dead-upstream difference test through HA | Addendum 3 |
|
||||
| **19:05:07** | Entrance vhost removed by the autopull | edge watch, Addendum 4 |
|
||||
| 19:06:25 / 19:06:50 | Both alias agents answer again | ingress log, HA's client UA |
|
||||
| 19:12:06 / 19:12:08 | Both alias agents answer again (this check) | ingress log; forgeway pod log shows no fallback, and strict cannot fall back by design |
|
||||
|
||||
So the order 1 → 2 → 3 held: the rule was proven from HA at 18:39, both entries were on
|
||||
the alias by 18:44, and the vhost went at 19:05. **No HA entry referenced
|
||||
`forgeway.dmz.lounge` at any point after ≈18:35**, so the vhost was not "the only thing
|
||||
making HA's agent work" when it was removed — nothing depended on it. The one thing I
|
||||
would do differently: run a fresh conversation *immediately* before the removal rather
|
||||
than relying on the ones from fifteen minutes earlier. Nothing had changed in between,
|
||||
but a proof that is minutes old is cheaper than an argument.
|
||||
|
||||
## The resolution paths, recorded so nobody re-derives them
|
||||
|
||||
From the Lounge client resolvers `172.19.1.201` / `172.19.10.201`, now:
|
||||
|
||||
```
|
||||
forgeway.services.falkvinge.net → ingress.dmz.lounge.falkvinge.net → 172.19.10.11 (k8s ingress-nginx; local-first alias)
|
||||
forgeway.lounge.falkvinge.net → ingress.dmz.lounge.falkvinge.net → 172.19.10.11 (explicit Lounge instance; http only)
|
||||
forgeway.serenity.falkvinge.net → forgeway.dmz.serenity… → ingress.dmz.serenity… → 172.24.10.11 (explicit Serenity instance)
|
||||
forgeway.dmz.lounge.falkvinge.net → NXDOMAIN (retired; .10.201 held a cached answer for ≤5 min)
|
||||
```
|
||||
|
||||
Until 19:03 the retired name resolved `→ entrance.dmz.falkvinge.net → demuxer.dmz.falkvinge.net → 172.20.0.101`,
|
||||
the entrance HAProxy — a genuinely different path from the alias. That is why, earlier
|
||||
today, "HA's VLAN can't reach `172.19.10.x`, so use the `.dmz.lounge.` name" was a
|
||||
coherent instruction at all: the two names went to different places. The claim itself
|
||||
was verified at the time from the scripthost on HA's VLAN (`172.19.10.11` unreachable,
|
||||
entrance reachable — Addendum 2), not from HA itself; Rick was right to ask for the
|
||||
resolution paths to be stated rather than implied.
|
||||
|
||||
Today the alias goes to the ingress from HA because of Rick's pfSense rule, which is
|
||||
scoped to HA's IP: the scripthost on the same VLAN still gets no connection to
|
||||
`172.19.10.11:443` (checked again now). The entrance path is gone in config
|
||||
(`lounge-haproxy-config` `73f4389`), from inside, and from outside (Serenity's public
|
||||
egress → the Lounge WAN address → the edge's default backend, 404).
|
||||
|
||||
Reference in New Issue
Block a user