Node HandbookNODE HANDBOOK中文
Karing · cross-platform

Karing: from import to a verified connection

Cross-platform clients tend to accept several formats, which is convenient and also the first source of confusion: the wrong entry silently produces an empty list.

Node Handbook editorial team ·

Order of work

  1. Install from the project's own release channel, matching your platform.
  2. Import the subscription in the form the provider documents for this client.
  3. Confirm the node count is plausible and update reported no error.
  4. Select a node, so that a connection has something to use.
  5. Enable system proxy, then verify with one real request.
  6. Only if an application needs broader capture, enable the tunnel mode and record the pre-change state.

Format before settings

Input shapeProducesIf the entry is wrong
Subscription URL returning a listMany nodesEmpty list or a parse error
Single share linkOne nodeAn unexpectedly short list
Configuration file for another client familyDepends on the parserEmpty list, or fields silently ignored

“Fields silently ignored” is the dangerous case: the list looks populated, but behaviour does not match what the configuration intended. When something behaves unexpectedly, compare the original file against what the client displays.

Capture modes

ModeCoversNotes
System proxyApplications that read proxy settingsFewer variables, simpler rollback
TunnelBroader, subject to routes and exclusionsNeeds a tunnel interface and permissions; can conflict with other VPNs

The four contrasts when pages fail

  • Client off, ordinary site: establishes the base network.
  • Another node: separates one node from the whole subscription.
  • Another network: separates the current path from the service.
  • One app versus Safari: separates capture scope from forwarding.

Why a populated list can still behave oddly

A list with entries proves that nodes were produced. It does not prove that every field in the configuration was understood. Cross-format import is where this happens: a client may accept the file, create the nodes, and ignore a transport option it does not implement. The symptom is a node that connects and carries nothing, or one that behaves differently from the same node in another client.

When behaviour differs from the source configuration, compare the two rather than adding settings: what the file declared for that node, and what the client shows for it. A field silently ignored is not a field you can fix by changing DNS.

What to record

  • App version, platform and the time.
  • The input shape and what the address actually returned.
  • Whether the node list was empty, partial, or complete.
  • Mode used, and the result of each contrast.
  • Observed exit, if region matters.

Scope

This page describes an order of checks. Interface wording and supported formats follow the installed version and the project's documentation. Nothing here evaluates a provider or claims compatibility with a particular subscription.