Node HandbookNODE HANDBOOK中文
Clash Verge Rev · TUN

Clash Verge Rev: TUN is on, but was the adapter created?

A page that will not load and an exit IP that did not change are outcomes. Whether the operating system created and kept a virtual interface is an observation you can make directly, and it belongs before any conclusion about routes or nodes.

Node Handbook editorial team ·

Three observations that are not the same

ObservationWhat it meansWhat it does not mean
The TUN switch is onThe client has been asked to capture trafficThat a service installed, or an interface exists
The service reports runningThe helper process is aliveThat the adapter was created or that routes were changed
An interface appears in the OS listThe system enumerated itThat traffic is captured, DNS resolves, or nodes work

The failure “pages do not load” or “the exit IP did not change” sits downstream of all three. Until you know which of them holds, any fix is a guess.

Capture the interface list before and after

  1. Record client and core versions, OS version, the time TUN was enabled, and the first error in the log.
  2. Turn TUN off in the client and confirm plain networking works.
  3. Capture the interface list. Use the platform's own tool and save the complete output, not a filtered line.
  4. Enable TUN, wait for the client to report its state, then capture the same command again.
  5. Compare names, descriptions and status fields, then disable TUN and capture once more.
PlatformCommandWhat to keep
WindowsGet-NetAdapterName, InterfaceDescription, Status
macOSifconfigInterface names and flags
Linuxip linkInterface names, state and MTU

Interface naming varies with OS and driver, so searching for one fixed name is not a test. Microsoft documents the Get-NetAdapter fields; macOS and Linux use different fields entirely, and a Windows Status=Up criterion should not be transplanted.

Reading the comparison

ObservationWhat it establishesNext step
A new interface appears while TUN is on and disappears when it is offThe system enumerated it; nothing about routes, DNS or nodesKeep the fields, then test one fixed target through the TUN path
The interface appears but its status is not up, or it vanishes shortly afterIt was created; the link state or service lifetime still needs checkingSave service and core logs with the enable time; do not call the driver broken from the name alone
No identifiable new interface in either listThe list does not show one — which may also be timing or namingCheck whether the service is running and whether the TUN log reports an error, then repeat with the same command

When the interface is missing

  • Check the service state and the client log for installation or start errors. A missing interface with a service error is a service problem, not a routing problem.
  • Confirm the client actually attempted to enable TUN, rather than reporting an unrelated failure.
  • Re-run the capture after the client reports it is connected; a list taken mid-startup shows a different state.

Do not uninstall the driver, disable security software or reinstall repeatedly before you have those three pieces of evidence. Each of those removes a capability and none of them produces a diagnosis.

When the interface exists but pages still fail

That is where this page stops. Enumeration does not prove capture, routing, DNS or node reachability. Move to the general TUN path: one fixed target, a recorded request result, the route the packet took, and the DNS decision. If the log also shows reject loopback connection while every node reads as failed, use the loopback-specific path instead.

Scope

This page only covers whether the operating system created and retained a virtual interface after TUN was enabled. It is a diagnostic method, not a reproduction on any specific device. Interface presence, capture, DNS and node health are four separate facts and must be recorded separately.