wiki: nightly audit 2026-11-05 window — network-map re-verified by live probe (9377=Camofox not Stratos, 8790/5174 gone, +9120/9222/7777/6767/8085/9900, full Tailscale Serve table, two dead routes 8769/9123); commit pending 11-04 stocktake re-verifications; log + skills-index

This commit is contained in:
hermes
2026-11-05 01:22:45 +08:00
parent e4086ec18e
commit 3b5daccb4d
15 changed files with 942 additions and 552 deletions
+33 -6
View File
@@ -3,8 +3,8 @@ title: Retained Research Answers
type: query
status: active
created: 2026-07-22
updated: 2026-10-12
verified_on: 2026-10-12
updated: 2026-11-04
verified_on: 2026-11-04
review_after: 2027-01-12
confidence: medium
tags: [query, research, vnc, remote-desktop]
@@ -18,11 +18,32 @@ Research answers worth keeping: what was asked, the answer, the evidence it rest
> The 2026-07-22 stub was filled on 2026-10-12 with the first retained answer (asked in the 2026-10-11
> interactive session `talaria-ios`, 41 messages).
>
> **2026-11-04 re-verification:** the answer's *framing* was wrong — it was written for "TigerVNC + Xtigervnc
> servers" that the estate does not run. The client-side advice remains valid for the one VNC server that does
> exist (x11vnc on CT460). See the correction note under the answer.
## Fastest VNC client (asked 2026-10-11)
**Answer for the CT460/CT200 TigerVNC + Xtigervnc servers:** use the **TigerVNC native viewer** with
AutoSelect and the defaults — free, and the fastest standard-RFB client. Lowest bandwidth is **KasmVNC**
**Answer for the CT460 VNC server:** use the **TigerVNC native viewer** with AutoSelect and the defaults —
free, and the fastest standard-RFB client.
> ⚠ **Corrected 2026-11-04 — the original question was framed against servers the estate does not run.**
> This answer was written on 2026-10-12 for "the CT460/CT200 TigerVNC + Xtigervnc servers". **Neither exists.**
> Live state, re-verified 2026-11-04:
> - **CT460** runs **x11vnc**, not TigerVNC and not Xtigervnc: `x11vnc -display :99 -forever -shared -rfbport 5901
> -rfbportv6 5901 -noxdamage -quiet -nopw` (PID 1290295), fronted by **websockify** → noVNC on
> `127.0.0.1:6080 → 5900` (a **dead** target — no listener on 5900) and `127.0.0.1:6081 → 5901` (**live**).
> The display itself is `Xvfb :99 -screen 0 1600x1200x24 -ac -nolisten tcp`.
> - **CT200** runs **no VNC server at all**. Its only X server is `Xvfb :495478600 -screen 0 800x680x24`, started
> 2026-10-30 — that is the Camofox browser's own headless Xvfb, and the Camofox VNC plugin tree lives on
> **CT460** (`/home/hermes/services/camofox-browser/plugins/vnc/`), not on CT200. No `x11vnc`, no `Xtigervnc`,
> no `vncserver`, and nothing listening on 5900/5901/6080/6081.
>
> **The advice itself still stands**, because x11vnc speaks standard RFB and TigerVNC's viewer is the right
> client for it — but it now applies to **one** host, and the page's "the estate's own VNC/Xtigervnc setup" pointer
> is wrong. The real setup is documented at [[systems/headless-server]], which already described x11vnc correctly
> back on 2026-10-20; this query page was the outlier. Lowest bandwidth is **KasmVNC**
(WebP, ~30 % less) but that is a *server* swap, not a client. **RealVNC Connect** is not a faster decoder, it is
a forked protocol (RFB 6, audio, no port-forwarding) and needs a RealVNC server. **TurboVNC** remains the
reference for lossless 3D/CAD. Genuinely low latency means leaving RFB entirely: **Parsec** or
@@ -66,8 +87,14 @@ software (a thin client with no SIMD headroom decodes slowly regardless of viewe
**Does NOT establish:** exact throughput multipliers on current hardware (the benchmark is 2012); no
end-to-end benchmark was run against Anthony's own hosts. If speed becomes a real complaint, measure the
existing server before changing clients.
existing server before changing clients. **It also does not establish anything about TigerVNC or Xtigervnc
*server*-side behaviour on this estate, because the estate runs neither** — x11vnc's own encoder settings
(`-compress`, `-quality`, `-encodings`) are the live lever on CT460, not the TigerVNC/TurboVNC encoder options
the report discusses. The compression-level and local-cursor levers above map onto x11vnc as
`-compress <level>` and the `x11vnc` cursor-shape options, but the specific numbers were tuned for a different
server and should be re-measured before being trusted on this one.
## Related
- [[systems/hermes-agent]] — the estate's own VNC/Xtigervnc setup lives under [[systems/headless-server]]
- [[systems/headless-server]] — **the estate's actual VNC setup** (x11vnc on `Xvfb :99`, noVNC via websockify) — re-verified 2026-11-04
- [[systems/hermes-agent]] — the agent host this answer was researched for
- [[log]] — audit entries