How to Use OpenClash Dashboard: Speed Test Nodes and Switch Policy Groups

Mental model: LuCI + Dashboard both drive the same core

Think about OpenClash as layered plumbing. Below is the Mihomo lineage core (depending on bundled package), enforcing domain lists, GEOIP calls, sniffers, UDP tunables, DNS listeners, fake-ip quirks, tun versus redirect modes—all the gritty pieces we covered territorially inside OpenWrt + OpenClash install and whole-home proxy. Above that sits LuCI wrapping init scripts plus optional helper apps. Highest is the Dashboard (YaCD derivatives, newer Meta dashboards) that behaves like lightweight frontends targeting the same API your desktop Mihomo forks expose locally.

Because every layer can restart or rewrite config, disciplined operators capture two artifacts before exploratory clicking: exported subscription YAML snippets and snapshots of firewall tables. Screenshots decay; text files remain admissible when DNS suddenly stops resolving after swapping proxy modes midday.

Opening LuCI shortcuts versus the Dashboard

In LuCI, look under Services → OpenClash (some builds localize labels but keep the casing). Tabs cluster around configs, updater intervals, mixin toggles, custom rules, watchdog settings, cron refresh—basically infra work. Operational switching usually happens quicker once you open the Dashboard hyperlink embedded beside “Open Dashboard” wording; it targets http://router-lan-ip:9090/ui style endpoints or newer packaged static bundles fetched from CDN mirrors.

First launch frustrations usually trace to mismatched binds: Mihomo listens on LAN address but iptables nft input defaults reject non-LuCI HTTPS ports unless you punched an allowance. Another classic is forgetting that smartphone browsers autocomplete http while some bundles ship strict HTTPS stubs after local certificate trust is installed. Narrow failures by curling from LAN SSH (curl http://127.0.0.1:9090/version proxyless). If localhost answers but VLAN clients cannot reach the LAN IP variant, revise OpenWrt’s zone ingress.

LuCI-only controls dashboards skip

Before obsessing strictly over flashy charts, skim the LuCI tabs that babysit housekeeping functions: force-restart daemons without entire router reboot cycles, reschedule subscription downloads when upstream CDNs choke at midnight cron windows, tweak DNS hijacking toggles that silently rewrite queries before any Dashboard hears them, tune watchdog thresholds reviving stalled cores independent of flashy UI pings. Operators chasing “why did OpenClash stop last Tuesday” seldom find breadcrumbs inside React bundles—LuCI rotates textual trails earlier.

Packet capture shortcuts also hide here alongside IPv6 coexistence knobs not mirrored verbatim inside portable dashboards authored upstream. Memorize mapping between LuCI wording and Mihomo equivalents so teammates troubleshooting through SSH correlate instructions with GUI screenshots circulated in chats. Translating nomenclature across languages adds latency to incident response whenever firmware locales diverge unexpectedly after community package bumps.

Export buttons deserve ritual usage: zipped archives bundle running YAML, plugin metadata, sanitized secrets placeholders—lifesavers migrating across router generations or diffing regressions spanning multiple release candidates. Waiting until catastrophic flash corruption proves painful when history files vanish concurrently.

Node latency versus group latency

Inside the Proxies sidebar, leaf nodes expose per-outbound pings or URL-style delays when you click lightning icons (latency test semantics echo Clash terminology). Interpret these numbers as heuristic ordering signals: they seldom equal streaming throughput megabits, yet correlate with TLS setup speed and jitter when health targets align with CDN edges you routinely hit.

Nested selectors—think “Hong Kong trio,” “US media,” auto fallbacks chaining url-test wrappers—bubble metrics upward so you visualize which subtree currently wins arbitration. Operators chase two failure classes: artificially low latency masking packet loss bursts, which url-test tolerances swallow until streaming buffers stall, versus inflated latency attributable to probing through saturated Wi-Fi—not the WAN hop.

Exploring selectors, fallback chains, relay stacks

Policy groups split into familiar archetypes ported from YAML: Selector for manual branching, Url-Test for continual winners, Fallback for degraded ordering, relays that chain outbound SOCKS layers, balances if your profile author enabled them OpenClash-side. Understanding YAML definitions still matters—even gorgeous dashboards flatten nuance—for example distinguishing lazy url-test probing from immediate mass fan-out stressing CPU on low-end MT7621 boards.

When you reorder by latency inside UI, Mihomo persists selection into runtime memory and usually mirrors into local database files under /etc/openclash/history/-style folders (precise pathname varies across releases). Persisted histories survive minor reloads yet still defer to authoritative subscription merges when providers refresh nightly. Operators who lament “everything reset overnight” collide with cron subscription updates without dedicated stash overlays—documented intimately in YAML-first references like our Meta url-test, fallback tolerance guide if you escalate beyond UI toggling.

Goal	UI knob	Gotcha
Instant region hop	Manual selector dropdown	Rules above may bypass group if GEOIP directs elsewhere
Self-healing upstream	Fallback / Url-Test	Thrashing if tolerance too narrow or health URL blocked
Audit auto picks	Latency sort + Connections	WAN IPv6 leakage can ignore IPv4-heavy winners

Switching proxy modes responsibly

OpenClash proxy modes typically mirror Mihomo nomenclature: Rule defers routing to YAML hierarchy, while Global funnels tolerated TCP flows through chained tunnels unless exclusions exist, and Direct trims overlays for debugging chokepoints (OpenClash overlays sometimes rename toggles subtly—read inline help snippets). Household operators flip Global when diagnosing suspicious blocks, revert to Rule for daily stability, temporarily choose Direct isolating WAN path issues referencing ISP DNS breakage.

Each mode interacts with LAN DNS rewriting: fake-ip answers may stall if you jump Direct absent compatible upstream resolvers—symptoms aligning with troubleshooting pages such as our DNS versus fake-ip explainer. Document mode toggles correlating timestamps inside logs for cross-team retrospectives spanning several nights.

Reading the Connections inspector

Connections overlays mirror desktop tray analytics with router twist: LAN clients identifiable through IP leases, VLAN tags if you expanded bridges, hashed hostnames surfaced through sniff domains. Inspect columns for rule engines selecting policy groups—not only final outbound egress—because misaligned selector picks often disguise themselves as GEOIP leaps earlier upstream.

Operators hunting intermittent stalls filter by outbound name, pinning flows during voice calls discovering UDP weirdness absent from ICMP-only dashboards. Clearing tables mid-debug erases breadcrumbs; screenshot instead.

Digesting Logs without drowning routers

OpenClash logs fan into LuCI log readers plus optional remote syslog sinks. Verbosity ladders matter: informational lines highlight subscription downloads, WARN surfaces handshake failures tracing CA misconfigurations, DEBUG multiplies chatter unsuitable flash logging long term. Searching for RULE-MATCH, DNS- hijack confirmations, GEOIP rejects shortens RCA sessions.

Correlate log timestamps across OpenWrt logread and Mihomo overlays when crashes loop—daemon watchdog may restart cleanly while nft leftovers linger until cold reboot clears states.

YAML sync clashes with nimble UI explorers

Upstream authors embed comments, anchors, ephemeral provider metadata—OpenClash’s merge subsystem occasionally rewrites ordering when LuCI watchers detect drift. Operators who freestyle-edited proxies through Dashboard without converting into mixin fragments risk losing deltas after remote profile refresh. Institutionalize repeatable patterns: dedicate override files for handcrafted nodes, annotate subscription intervals, stash manual selections through export buttons when shipped.

Large household deployments script Git-backed YAML merges tested on VMs before SCP pushing into router overlays—beyond casual UI editing but worth acknowledging when reproducibility dominates household harmony.

Ground-truth verification checklist

• Router CPU load acceptable post mass latency sweep.
• Two LAN subnets each resolve expected DNS server IP.
• Dashboard secret rotated after firmware upgrades resetting defaults.
• Backup archives include both LuCI-exported configs and Mihomo caches.
• Guest SSIDs incapable of dashboards remain isolated deliberately.

FAQ

Why does Dashboard latency disagree with browsing throughput?

Measurements aim at deterministic health probes; webpages blend TLS resumes, QUIC, multiplexed HTTP/3, asymmetric congestion, intermittent Wi-Fi retransmits. Lean on comparative ordering: if Node A dominates Node B repeatedly, downstream streaming likely benefits—even if Mbps charts fluctuate midday.

Chosen nodes disappeared after nightly subscription refresh?

Providers rebuild remote YAML lists; absent local pinning, merges drop manual leaf entries. Persist stable sets either off-subscription clones or mixin-only manual definitions plus slower refresh cadences.

Guests cannot launch Dashboard bookmarks?

Mesh isolation often blocks intra-LAN management IPs. Decide intentionally: carve management VLAN unrestricted or accept mobile admin tasks only wired.

Why laptop Clash stays handy after router mastery

Router dashboards democratize whole-home throughput, yet road warriors juggling captive portals or corporate VPN killswitches still ache for brittle browser-only admins that demand constant WAN reachability to same LAN IP anchors. Lightweight desktop clients regain per-process fidelity, draggable latency charts exporting CSV, quicker rule experiments without reloading entire household NAT tables.

Clash’s native apps trim that wandering friction stack: iterative profile tuning on a notebook, syncing validated YAML outward only when commits prove stable mirrors how seasoned operators hedge firmware regressions silently bricking dashboards mid-flight.

Port your refined policies confidently between router and workstation—download Clash for free and keep tactile control when OpenWrt maintenance windows stretch longer than impatient family movie nights tolerate.