"TUN mode is connected but nothing loads" is one symptom with five different causes, which is why
threads about it go in circles. Each layer fails identically from the user's point of view: the
toggle is on, the status says connected, every request times out.
The layers are ordered by frequency and by cost-to-check, so going top-down finds the fault
faster than any other order.
Layer 1 — did the interface actually come up
Creating a virtual network adapter requires elevated privileges. If the background service isn't
installed or was started without admin/root, the core runs in userspace, reports "connected" in
the UI, and never creates an adapter.
# Linux / macOS
ip link show | grep -i -E "tun|utun|mihomo"
ifconfig | grep -A2 utun
# Windows
ipconfig | findstr /i "Mihomo utun"
You want an interface holding an address in 198.18.0.0/16 or 172.19.0.0/16.
If there's no interface, stop. Nothing below matters. This is a permissions problem, and no
amount of config editing will fix it. On Windows that means the service component; on Linux it
means the binary needs CAP_NET_ADMIN.
Layer 2 — is traffic entering the tunnel
Interface exists but packets still leave through the physical NIC. Usually a competing default
route from another VPN client, Hyper-V, WSL2, or Docker.
traceroute 1.1.1.1 # first hop should be the TUN gateway
route print # Windows: check the metric on 0.0.0.0
ip route get 1.1.1.1 # Linux: which interface wins
First hop = your router's LAN IP means the route wasn't taken over. Two TUN drivers on one
machine is a coin flip; uninstall the other one rather than fighting route metrics.
Layer 3 — DNS
The most common after permissions, and the most misdiagnosed. The tell: nothing resolves, but a
raw IP works in the browser.
nslookup example.com
ping 1.1.1.1
-
nslookuptimes out,pingworks → DNS isn't going through the tunnel. Eitherdns.enableis false, or the client's own DNS override panel is winning over your YAML. Several clients have a separate override layer that takes precedence and isn't obvious in the UI. - Resolves to a real IP but pages still fail → in fake-ip mode the answer should be
198.18.x.x. A real IP means fake-ip isn't active regardless of what the config says. - Browser's "secure DNS" / DoH enabled → it bypasses the system resolver entirely. Turn it off before concluding anything about the tunnel.
Layer 4 — the node
TUN can be perfectly healthy and the node dead. This is the one that makes people reinstall the
client for no reason.
Check the delay test in the dashboard, and open the connections view while loading a page — it
tells you instantly whether the request even reached the core, and which rule matched.
A node that completes a handshake but returns nothing (expired subscription, rotated UUID,
server-side port block) looks exactly like a broken TUN from the browser.
Layer 5 — the application
Some apps bypass the system proxy, and a few bypass TUN as well. UWP apps on Windows are
sandboxed and need loopback exemption. Game clients with their own network stack ignore the route
table. Anything with a bundled network library may read its own proxy config.
curl -I https://example.com
Terminal works, app doesn't → it's the app.
The part that actually saves time
Notice that "reinstall the client" doesn't appear in the list, yet it's the most common advice in
every forum thread about this. It's almost never the fix.
The habit that pays off: keep the connections panel open while you reproduce the problem. It
disambiguates layer 4 from layers 1–3 in one glance, which is otherwise the hardest split to make.
Rough split from the cases I've logged: permissions ~30%, DNS ~35%, dead node ~20%, competing
route ~10%, app-level the rest.
Longer writeup with the exact menu paths per client:
jiedianshouce.com.
Top comments (0)