Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Network panel mistakes Clash TUN interface for Ethernet uplink
Reported by LIghtJUNction · filed Sep 28, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
What happened
With Clash Verge TUN enabled, the Omarchy network panel identifies the TUN device (Meta) as the active Ethernet connection. It shows Ethernet (10gbit), the TUN IP 198.18.0.1, and TUN gateway 198.18.0.2, even though the physical uplink is Wi-Fi.
omarchy-network-status --verbose reports iface=Meta, type=ethernet, and speed=10000 in this situation.
Why it happens
bin/omarchy-network-status selects the device with ip route get 1.1.1.1. A TUN policy route sends that lookup through Meta (in my case, table 2022). The script then categorizes every device without /sys/class/net/<device>/wireless as Ethernet. Meanwhile, the main routing table has a default route via wlan0.
Expected behavior
The panel should describe the physical uplink (wlan0 and its Wi-Fi connection), while the internet ping can still measure the current routed path through the TUN device.
Reproduction evidence
$ ip -j route get 1.1.1.1
[{"gateway":"198.18.0.2","dev":"Meta","table":"2022","prefsrc":"198.18.0.1"}]
$ ip -j route show table main default
[{"dst":"default","gateway":"10.175.255.254","dev":"wlan0","metric":600}]Omarchy 4.0.4, Clash Verge TUN, systemd-networkd/iwd uplink.
View raw text
### What happened
With Clash Verge TUN enabled, the Omarchy network panel identifies the TUN device (`Meta`) as the active Ethernet connection. It shows `Ethernet (10gbit)`, the TUN IP `198.18.0.1`, and TUN gateway `198.18.0.2`, even though the physical uplink is Wi-Fi.
`omarchy-network-status --verbose` reports `iface=Meta`, `type=ethernet`, and `speed=10000` in this situation.
### Why it happens
`bin/omarchy-network-status` selects the device with `ip route get 1.1.1.1`. A TUN policy route sends that lookup through `Meta` (in my case, table `2022`). The script then categorizes every device without `/sys/class/net/<device>/wireless` as Ethernet. Meanwhile, the main routing table has a default route via `wlan0`.
### Expected behavior
The panel should describe the physical uplink (`wlan0` and its Wi-Fi connection), while the internet ping can still measure the current routed path through the TUN device.
### Reproduction evidence
```text
$ ip -j route get 1.1.1.1
[{"gateway":"198.18.0.2","dev":"Meta","table":"2022","prefsrc":"198.18.0.1"}]
$ ip -j route show table main default
[{"dst":"default","gateway":"10.175.255.254","dev":"wlan0","metric":600}]
```
Omarchy 4.0.4, Clash Verge TUN, systemd-networkd/iwd uplink.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 20:01 UTC