Overview

In TrueStack, network access is explicitly defined. Rather than allowing unrestricted access, you control exactly which servers or networks a computer can reach through the VPN, and optionally whether all internet traffic is routed through the tunnel.

This guide explains how the Network tab works, what each option does, and how network routes interact with computer settings to determine VPN behavior.

Network Access Model

TrueStack uses an allow-list approach to networking:

Remote Computer → TrueStack VPN → Allowed Network Routes → Internal Servers

Only destinations defined in the Network tab are eligible to carry traffic through the VPN.

Opening the Network Tab

From the TrueStack admin interface, click Network.

When the Network tab opens, you’ll see the form for creating a new network route at the top of the page, followed by the list of existing routes.

Server Name

The Server Name field defines how the route appears when assigning it to computers.

Use a clear, recognizable name so it’s easy to select the correct route later—especially in environments with multiple servers or networks.

Common examples:

  • Domain Controller
  • File Server
  • Internal Network
  • Application Server

This name is purely descriptive and does not affect routing behavior.

IP Address or Subnet

Each network route applies to either:

  • A single IP address, or
  • An entire subnet

This setting defines which destinations are allowed to receive traffic through the VPN.

Typical use cases:

  • A single IP for a specific server (for example, a domain controller)
  • A CIDR subnet when access to an entire network is required

Only traffic destined for the defined IP address or subnet is eligible to traverse the VPN.

DNS and WINS Server Options

When a route is configured as a single IP address, additional options appear:

DNS Server

When DNS Server is enabled, the server’s IP address is added as a DNS server on the TrueStack network adapter.

This allows connected computers to resolve:

  • Active Directory domain names
  • Internal hostnames
  • Other DNS-based resources over the VPN

The DNS Server option is required for:

  • Active Directory authentication
  • Group Policy processing
  • Resolving internal DNS names

WINS Server

When WINS Server is enabled, the server’s IP address is added as a WINS server on the TrueStack network adapter.

This option is typically only required in legacy environments that still rely on NetBIOS name resolution.

Adding the Route

After entering the required information, click Add Route.

The route will appear in the Network Routes list and is now available to be assigned to computers.

How Network Routes Are Used

Network routes are applied from the Computers tab.

When adding or editing a computer, you select which network routes that computer is allowed to use.

Only the selected routes are eligible to carry traffic through the VPN.

This makes it easy to:

  • Limit access on a per-device basis
  • Assign different network access to different systems
  • Avoid exposing unnecessary networks

Important VPN Behavior

VPN traffic behavior depends on two factors:

  1. Whether any network routes are selected
  2. Whether Route all traffic is enabled on the computer

The Network tab defines which internal destinations are allowed.

The computer settings determine whether:

  • Only those destinations are routed through the VPN, or
  • All traffic (including internet traffic) is sent through the VPN tunnel

Important Note

If no network routes are selected and Route all traffic is disabled, the VPN connection may appear active, but no traffic will flow through it.

Common Active Directory Configuration Example

A typical Active Directory setup includes:

  • A network route for the domain controller
  • DNS Server enabled on that route
  • Optional routes for file servers or application servers

Once assigned, remote computers can:

  • Authenticate to the domain
  • Apply Group Policy
  • Access internal resources securely

Summary

The Network tab defines:

  • Which internal destinations are allowed through the VPN
  • How access is controlled at the device level

It works together with computer settings to determine whether traffic is selectively routed or fully tunneled through TrueStack.