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.
Wired Internet Slow / DNS Hijacking After Install
Reported by krafi-code · filed Oct 5, 2025Closed upstream on 2025-10-06 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
🐞 Wired Internet Slow / DNS Hijacking After Install
Issue:
Fresh Omarchy Linux install → wired internet works but is slow/unreliable. ping google.com sometimes resolves to weird IPs (e.g. 192.178.x.x), not real Google addresses.
Cause:
Default systemd-networkd config accepts ISP DNS via DHCP, which can be slow or hijack requests.
Fix:
Edit /etc/systemd/network/20-ethernet.network:
[Match]
Name=en*
[Network]
DHCP=yes
DNS=1.1.1.1
DNS=8.8.8.8
Domains=~.
[DHCP]
UseDNS=falseThen:
sudo systemctl restart systemd-networkd systemd-resolved✅ After this, DNS is fast, secure, and resolves correctly.
Suggestion:
Set UseDNS=false by default in the live ISO’s network config to avoid this post-install pitfall.
View raw text
--- ### 🐞 Wired Internet Slow / DNS Hijacking After Install **Issue**: Fresh Omarchy Linux install → wired internet works but is **slow/unreliable**. `ping google.com` sometimes resolves to weird IPs (e.g. `192.178.x.x`), not real Google addresses. **Cause**: Default `systemd-networkd` config accepts **ISP DNS via DHCP**, which can be slow or hijack requests. **Fix**: Edit `/etc/systemd/network/20-ethernet.network`: ```ini [Match] Name=en* [Network] DHCP=yes DNS=1.1.1.1 DNS=8.8.8.8 Domains=~. [DHCP] UseDNS=false ``` Then: ```bash sudo systemctl restart systemd-networkd systemd-resolved ``` ✅ After this, DNS is fast, secure, and resolves correctly. **Suggestion**: Set `UseDNS=false` by default in the live ISO’s network config to avoid this post-install pitfall. ---
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.
No decision has been recorded yet.