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:
+9
-7
@@ -3,8 +3,8 @@ title: QwenPaw
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-08-15
|
||||
updated: 2026-10-11
|
||||
verified_on: 2026-10-11
|
||||
updated: 2026-11-04
|
||||
verified_on: 2026-11-04
|
||||
confidence: high
|
||||
tags: [qwenpaw, ct465, agent, paseo]
|
||||
sources: [live-probe, config-reference]
|
||||
@@ -24,11 +24,13 @@ Multi-agent gateway platform. Runs on CT465 with its own workspace, agent profil
|
||||
|
||||
## Current State
|
||||
|
||||
- **Status:** Active — `paseo.service` active on CT465, verified 2026-10-11
|
||||
- **Status:** Active — `paseo.service` active on CT465, **re-verified 2026-11-04**
|
||||
- **Default chat model:** OmniRoute Smart Route (`auto/smart`)
|
||||
- **Config format:** JSON (`agent.json` per workspace)
|
||||
- **Daemon:** `paseo.service`
|
||||
- **Also listening on CT465:** PVE exporter (`100.96.150.69:9221`), a Python service on `:9876`, and local SMTP `:25`
|
||||
- **Daemon:** `paseo.service` — **system** unit on CT465 (distinct from the **user** unit `paseo-daemon.service` that runs on CT460; see [[systems/paseo]])
|
||||
- **CT465 listening ports (live 2026-11-04):** `0.0.0.0:6767` (Paseo), `*:13500`, `127.0.0.1:25463`, `127.0.0.1:11434` (Ollama), `127.0.0.1:38585`, `100.110.72.126:42510`, `:22`
|
||||
- ⚠ **Corrected 2026-11-04.** The old claim that "PVE exporter (`100.96.150.69:9221`), a Python service on `:9876`, and local SMTP `:25`" were listening **on CT465** was **wrong on all three counts**. Live `ss -ltn` inside CT465 shows **none** of them. `:9221` and `:9876` listen on the **`pve` hypervisor host itself** (`100.96.100.82`), not in the guest, and `100.96.150.69` is **CT200** (the Docker host), not the PVE exporter. `:25` is the hypervisor's own loopback SMTP, also not in CT465.
|
||||
- **Port 6767 has two live implementations — do not conflate them:** CT465's own `paseo.service` listens on `0.0.0.0:6767` and answers **HTTP 404** on `/` (the daemon is alive; `/` is not a route). The tailnet node `paseo` (`100.72.188.93`) is a **different guest** — CT1261 on `m93p` — also running `paseo.service` on `:6767`, and it answers **HTTP 200** on `/`. CT460's own user-unit daemon is a third instance (also `:6767`, **HTTP 404** on `/`; `/api/health` → 200).
|
||||
- **CT400/CT465 identity:** confirmed CT465 = `qwenpaw`, running
|
||||
|
||||
## Operating Layers
|
||||
@@ -60,8 +62,8 @@ qwenpaw daemon status
|
||||
|
||||
When adding an OpenAI-compatible provider from Proxmox:
|
||||
- Verify target by VMID and hostname before writing config
|
||||
- CT600/`omniroute` is the **live** OmniRoute service at `100.88.81.19:20128` — verified serving 2026-10-11
|
||||
- CT601/`omni` is a separate guest at `100.93.204.4` — **stopped**, do not use
|
||||
- CT600/`omniroute` is the **live** OmniRoute service at `100.88.81.19:20128` — verified serving 2026-10-11, still live 2026-11-04
|
||||
- ⚠ **Corrected 2026-11-04:** CT601/`omni` is **no longer present on either hypervisor** — `pct list` on both `pve` and `m93p` shows **no CT601 at all**, and the `omni` tailnet peer (`100.93.204.4`) has dropped out of the tailnet entirely. The guest was **removed**, not merely stopped. Use CT600.
|
||||
- A third instance `omniroute-1` at `100.78.63.20:20128` is also live; Hermes registers it as provider `omni-101`
|
||||
- Query `/v1/models` using the exact API key stored for QwenPaw, not a management key
|
||||
- See [[systems/omniroute]] for the full live node table
|
||||
|
||||
Reference in New Issue
Block a user