Wheelhouse

Support#

There is no support channel yet, and no plan includes support. What to collect before writing in, and what the documentation covers.

Read the documentation What is finished, and what is not

What a plan includes#

No plan includes support, and support is not sold separately. Homelab, Lab and Business buy the same software with different router counts and use rights (Pricing); none carries a response time, a ticket count or an agreement to answer. What every subscriber has is the documentation — this site, the wiki and the docs/ tree, versioned with the code — and, once it is published, a mailbox read on a best-effort basis with nothing promised about when.

A lapsed subscription is not a brick. A router whose key has expired signs you in, shows every page, counter, log and audit entry, and refuses only to change configuration.

Before you write in#

There is no support-bundle command. Collect these by hand. Everything except /health needs authentication; use an API token with the viewer role rather than a copied session cookie, which also needs the X-Wheelhouse-CSRF header on any request that changes something.

bash
R=https://<router>:8443
T=wh_...                                    # an API token with the viewer role

curl -sk  $R/health                                               # liveness, no auth
curl -sk -H "Authorization: Bearer $T" "$R/api/audit?limit=300"   # who changed what, when
curl -sk -H "Authorization: Bearer $T" "$R/api/history"           # commit revisions

The agent's log is the journal on an appliance:

bash
sudo journalctl -u wheelhouse-agent --since '1 hour ago'

What to include#

  • Both versions. The console banner carries them on two lines: the first line is Wheelhouse <version> -- <hostname>, and further down, under the rule, is Built on VyOS <version>. The About page in the interface has the same pair.
  • What you did and what happened. For a configuration problem, the exact set or delete path the editor showed you, and the router's own error text if it refused.
  • How to reproduce it. wheelhouse-agent --demo starts the agent with no router credentials, so the interface loads and the API answers without a router in front of it. It ships no fixture data: every router read fails until you give it --api-url and --api-key. That is enough to reproduce a sign-in, a layout or an API-shape problem, and not enough to reproduce anything that depends on router state.
  • The audit entries and the journal lines around the timestamp.

A security flaw does not go to support#

It goes through the disclosure process, which has its own windows. Please do not open an ordinary support thread describing a vulnerability.

Known gaps that generate tickets#

Listed so nobody spends an afternoon proving one.

  • A failed upgrade is not self-service. There is a documented recovery order and no rescue boot entry.
  • No administrator can reset another account's second factor, and there are no recovery codes. A lost phone means console access and a hand-edited state file.
  • App images are pinned, so they age. An install today is the bytes that were reviewed — and it stays those bytes until we re-pin the catalogue and ship a release, upstream security fixes included.
  • A capture keeps running with the page closed. Diagnostics → Capture starts a real tcpdump on the router; only its limits stop it, at most 300 seconds.

The whole list is on the status page.

Read on#