VPN basics: subscriptions, nodes, routes, protocols, and split tunneling

A beginner’s guide to subscription links, node and route types (IEPL dedicated lines, relayed, and direct), common protocols, traffic rules, and global vs. rule-based mode.

When you first use a VPN, it helps to understand subscriptions, nodes, routes, protocols, and split tunneling separately. A subscription delivers configuration settings; a node is a connection option; a route describes the path your traffic takes; a protocol defines how the two ends communicate; and split tunneling determines which traffic uses a node. Proxy apps are sometimes called VPN clients, but importing a proxy configuration does not mean every app on your device will use the proxy.

Subscription links: importing configuration

A plan subscription is a billing arrangement; a subscription link is the address a client uses to fetch configuration. They are not the same thing. The client retrieves a list of nodes through the link, and some configurations also include node groups and traffic rules. A successful import only means the client can read the configuration. It does not mean a node has been selected or that your system traffic is being routed through the client.

The same subscription URL may not work with every client. Some clients can read the full configuration, while others import only a node list; some may fail because they do not recognize the format. If you see “Invalid format” or the list is empty after importing, first check that the link is complete and that the format provided in the dashboard is supported by your client. If you see a permissions error, check the subscription status in the dashboard. When the provider updates nodes, use the client’s update feature to refresh the list instead of adding them one by one.

Nodes and routes: the exit isn't the whole path

A node is a connection option in your client, usually containing a server address and connection parameters. Traffic may first pass through a relay before exiting from another location, so the point of connection and the exit location may be in different regions. Two nodes labeled with the same region may also take different routes. If a service offers region-specific content, check the actual exit location before comparing performance.

Direct nodes, relays, and IEPL dedicated lines: what’s the difference?
Type What the route means What to consider
Direct node The client connects to the proxy server directly over the public internet, without first passing through the provider’s relay entry point. Test on your own ISP connection and during your usual usage hours; don’t rely only on the node’s latency test.
Relayed route Traffic first connects to an entry point, which forwards it to the exit. The term “relay” alone does not tell you whether a dedicated line is used in between. Compare how smoothly the same app connects, and watch for interruptions during extended use.
IEPL dedicated line IEPL stands for International Ethernet Private Line. In network setups, it is typically used to connect specific access points; it does not mean the entire path from your device to the destination website uses a dedicated line. A dedicated line describes only one part of the route. You still need to consider performance from your location to the entry point and from the exit to the destination service.

Note the two meanings of “direct.” Selecting a “direct node” still routes traffic through a proxy server; a “direct” split-tunneling rule means traffic does not use a proxy node. A client’s latency test may only check a designated probe address, so it cannot replace real-world tests such as video playback, conference calls, or file uploads.

Protocols: check compatibility at both ends

A protocol defines how the client and server exchange data. It does not determine the exit region or indicate a route’s quality tier. The server configuration usually determines which protocol a node uses. Even if your client offers a different option, changing only the protocol name will not connect you to the same server. The address, authentication, transport method, and related encryption settings must all match the server.

  • Shadowsocks: An encrypted proxy protocol. The client must support both the node configuration and its specified encryption method.
  • VMess and VLESS: Two distinct proxy protocols with incompatible configurations. VLESS does not provide traffic encryption by itself; actual protection depends on the accompanying transport security settings.
  • Trojan: Typically establishes connections over TLS. Along with the authentication details, check that the server name matches and the certificate is verified. Do not disable verification just to pass a connection test.
  • Hysteria2 and TUIC: Both are based on QUIC and communicate over UDP, but they are not interchangeable. If your network restricts UDP, the app may fail to connect or become unstable; that alone does not mean the subscription is invalid.

Beginners should start by importing the configuration provided by the service provider. To compare protocols, keep the network, exit region, and use case as consistent as possible. If you change the protocol, node, and local network at the same time, it is difficult to tell which change made a difference.

Split tunneling: choosing global or rule-based mode

Rule-based mode uses conditions such as domain names and IP ranges to decide whether traffic goes through the proxy, connects directly, or follows another policy. For example, you can send a local network printer’s traffic directly and route specific websites through the proxy, while unmatched traffic follows the fallback rule in the configuration. Many clients apply rules in order and use the first match; a broad rule near the top may override more specific rules below it. A website’s pages, images, sign-in, and video may also use different domains, so loading the homepage does not mean every part of the service took the same route.

Global mode generally applies a global policy to traffic the client has already taken over. That does not mean every app is covered: the system proxy mainly affects apps that honor the system proxy settings, while virtual network interface mode can usually capture more traffic, subject to routing and exclusions. Apps with their own network or DNS settings may behave differently from your browser.

Use rule-based mode for everyday use and global mode as a troubleshooting comparison. If a site works on the same node only after switching to global mode, first check which rule matched and what the fallback policy is. If it fails in both modes, check whether the traffic is being captured, whether the node is available, and whether DNS resolution is working.

Verify after importing: from configuration to real-world access

  1. Make sure the configuration is readable. Use a subscription format supported by your client. After importing, check the node list and select a node. If the list is empty, troubleshoot subscription retrieval or parsing first.
  2. Check which route your browser actually uses. In the same browser, open my IP before and after connecting. In rule-based mode, first confirm whether the test page is supposed to use the proxy. A change in exit IP only shows that this web request used a different exit; it says nothing about other apps.
  3. Test again in the app you’re troubleshooting. If the browser works but an app does not, check whether it follows the system proxy settings or is excluded, then compare rule-based and global mode on the same node. If your client has connection logs, check which policy matched the request.
  4. Check DNS separately from the exit IP. A normal exit IP does not mean DNS is being handled as expected. If a query that should go through a designated resolver is actually sent to a different one, a DNS leak may occur. Queries that are meant to resolve locally under your rules do not automatically count as leaks. Check your client’s DNS settings, then see whether your browser has its own encrypted DNS enabled.

Follow this troubleshooting order: if there are no nodes, check the subscription; if you can select a node but cannot connect, check configuration compatibility and the route; if only a specific app or website has problems, check traffic capture, split tunneling, and DNS. Change one setting at a time and retest the same destination so you can tell what fixed the issue.

Start Free