Logo

Documentation v1.3.1

VPN Manager

Localtonet VPN Manager — Quick Start

Create a private mesh network in minutes. Add VPN servers, attach clients using existing Tokens, optionally bridge their LAN subnets into the VPN, and control access with fine-grained Firewall Rules. 

Note: Require administrative privileges.

1. Create (or Sign In to) Your Account

  1. Register at localtonet.com/register or sign in to your Dashboard.

2. Create a VPN Server

  1. Open VPN Manager → New VPN.
  2. Enter a VPN Name (e.g., MyVpnServer).
  3. Select a Server Relay Node (e.g., 🇪🇸 ES-Madrid).
  4. Click Create.

After creation, the server appears in the list with an assigned subnet (e.g., 10.14.0.0/16) and status Active.

3. Add VPN Clients

  1. In the server row, click Add Client.
  2. Pick a previously created Token Name that is installed on a device (e.g., vpn3).
  3. Click Add.

Each client gets a Virtual IP (e.g., 10.11.0.3). When the device is online, its status changes to Online.

4. (Optional) Bridge a Local LAN via the Client

You can bring a client’s on-prem LAN into the VPN so other VPN members can reach it. For example, if the client sits on 192.168.100.0/24 and its LAN IP is 192.168.100.2:

  1. On the client row, click LAN.
  2. Set Local Subnet to 192.168.100.0/24.
  3. Click Save.

The VPN will route traffic between the VPN subnet (e.g., 10.11.0.0/16) and the bridged LAN (192.168.100.0/24). LAN hosts can optionally receive mapped virtual IPs to appear as part of the VPN.

5. Add Firewall Rules

Control who can reach what, by protocol and port.

  1. Click a client’s Firewall button (or open global rules if available).
  2. Configure:
    • Action: Allow or Deny
    • ProtocolType: All, TCP, UDP, ICMP, …
    • Target VPN Client: All Clients or a specific client
    • Ports(toggle off “All Ports” to specify):
      • Single: 22
      • Multiple: 80, 443, 8080
      • Range: 1000-1500
  3. Click Save.

Examples

# Allow SSH to a single client
Action: Allow
Protocol: TCP
Target: vpn3
Ports: 22

# Allow all traffic between all clients
Action: Allow
Protocol: All
Target: All Clients
Ports: All Ports

6. Monitor & Manage

  • Status: Online / Offline indicators for each client.
  • Virtual IP: Click to copy; use it to reach services inside the VPN.
  • Process: Open Firewall and LAN dialogs for quick edits.

7. End-to-End Example

  1. Create MyVpnServer on ES-Madrid.
  2. Add clients vpn3 and vpn4.
  3. Bridge vpn3’s LAN:
    • Local Subnet: 192.168.100.0/24
  4. Add a firewall rule to allow TCP 22, 80, 443 for All Clients.

Result: vpn3 (10.11.0.3) and vpn4 (10.11.0.4) can reach each other and the bridged LAN at 192.168.100.0/24 through the VPN. Access policies are enforced by the rules above.

Troubleshooting

  • Client shows Offline: ensure the Localtonet app is running with the selected Token.
  • No access to bridged LAN:
    • Verify Gateway is the client’s real LAN IP.
    • Confirm the Local Subnet (CIDR) is correct (e.g., /24).
    • Review firewall rules; try a temporary Allow / All / All Ports to test.
  • Port blocked: add or adjust a rule for the required protocol/port.

Tip: Use the client’s Virtual IP (e.g., 10.11.0.3) to SSH/RDP/HTTP into services securely over the VPN.

support