এই পেজ এখনো বাংলা ভাষায় নেই। ইংরেজিতে দেখানো হচ্ছে।
VPN Manager
Free plan Beta
এই পেজে 12 সেকশন
- How it works
- Before you start
- Set up a network
- Create a network
- Add a device
- Start the client on the device
- Add the other devices and connect
- Client requirements
- Device details
- Change a virtual IP address
- LAN routes
- Firewall rules
- Monitoring and diagnostics
- Peer paths: direct or relay
- Recent events
- Example: reach an office PC and its LAN from a laptop
- Remove a device or delete a network
- Troubleshooting
- Related pages
VPN Manager joins your devices into a private network. Each device gets a virtual IP address, and the devices reach each other on those addresses as if they were on the same LAN, directly when possible and through a relay when not.
How it works #
- A network has a name, a subnet that Localtonet assigns, and a relay location that you choose.
- A device is one of your AuthTokens added to the network. The Localtonet client that signs in with that token brings up a VPN interface with the device's virtual IP address.
- The dashboard says it this way: Devices connect directly when possible. A relay is available when a direct path cannot be established.
- Optional LAN routes make a local subnet behind a device reachable from the other devices, and optional Firewall rules filter the traffic that arrives at a device from the other devices.
VPN Manager connects your own devices to each other. It is not the same thing as VPN Access on a proxy tunnel, which gives a WireGuard or OpenVPN profile whose traffic leaves through that proxy. See Proxy Server for that.
Before you start #
- One AuthToken per device. Each device needs its own token, and a token can be in one VPN network only. Create tokens under My Tokens; see AuthTokens.
- The Localtonet client installed on every device. See Install.
- Permission to create a network interface on the device: the client must run as administrator on Windows and as root on Linux and macOS. On Linux the
tunkernel module must be available. See Client requirements. - Your own account dashboard. The VPN Manager menu item is not shown while you work in a team dashboard.
Set up a network #
-
Create a network #
Open VPN Manager and select Create network.
Field What to enter Network name A name of up to 100 characters, for example Office network. Two of your networks cannot have the same name.Relay location The Localtonet server that relays traffic when two devices cannot connect directly. The dialog advises: Choose a location close to your devices. Direct P2P connections are preferred when available. Select Create network. The network appears in the Networks list with its Subnet and Relay. Localtonet assigns the subnet: your first network gets
10.11.0.0/16, and each further network gets the next free one (10.12.0.0/16,10.13.0.0/16, and so on). -
Add a device #
Select the network, then Add device. Under Choose the device’s auth token, pick the token that the device signs in with and select Add device. Tokens that are already in this network are listed as Already added and cannot be picked again. If the list is empty, create a token under Manage auth tokens, then select Reload tokens.
The device gets the next free address in the subnet. In a new
10.11.0.0/16network the first device is10.11.0.1and the second is10.11.0.2. The address is shown in the VPN address column. -
Start the client on the device #
Start the Localtonet client on the device with the same token, with administrator or root rights:
Terminal (administrator or root)localtonet --authtoken <YOUR_TOKEN>The client receives the VPN settings when it connects and shows a VPN row with the interface name and the virtual IP address. In the Localtonet app, the dashboard asks you to open the app with this token and enable VPN.
Back in the dashboard, the device changes to Online and its VPN health shows VPN ready.
-
Add the other devices and connect #
Repeat the two steps above for every device, each with its own token. Then use the virtual IP addresses between the devices, for example:
Bashping 10.11.0.1 ssh <USER>@10.11.0.1A path between two devices is established on demand, when one of them first sends traffic to the other's VPN address.
Client requirements #
| Platform | What the VPN needs |
|---|---|
| Windows | Start the client from a Command Prompt or PowerShell opened with Run as administrator. Without it the client shows Admin rights required. in its VPN row. |
| Linux, macOS | Run the client as root (for example with sudo). On Linux the tun module must be loaded. |
| Linux DEB and RPM packages | The packages ship two systemd services. localtonet.service runs without root and cannot create the VPN interface. For VPN, switch to localtonet-vpn.service, which runs as root and loads the tun module. Only one of the two services can run at a time. |
| Localtonet app | Sign in with the device's token and enable VPN in the app. |
To switch a packaged Linux installation to the VPN service:
sudo modprobe tun
sudo systemctl disable --now localtonet.service
sudo systemctl enable --now localtonet-vpn.service
journalctl -u localtonet-vpn.serviceThe service being active does not yet mean the VPN is ready: wait until the device shows VPN ready in the dashboard. Package installation and the token file are described in DEB and RPM packages.
Device details #
Select a device in the list to open Device details. The buttons at the top are:
| Button | What it does |
|---|---|
| Change IP | Sets another virtual IP address for the device. |
| LAN routes | Shares a local subnet behind the device with the other devices. |
| Firewall rules | Filters the traffic that arrives at the device from other VPN devices. |
| Copy auth token | Copies the token of the device. |
| Remove device | Removes the device from the network. Its LAN routes and firewall rules are removed too. |
Change a virtual IP address #
Select Change IP, enter the new Virtual IP address and select Save address. The address must stay inside the network's subnet: the first two numbers stay the same (for example 10.11), and you choose the last two. An address that another device in the network already uses is refused. Existing connections may briefly reconnect after the change.
LAN routes #
A LAN route makes a local subnet behind a device accessible to the other devices in the VPN. Use it to reach machines that cannot run the Localtonet client, such as a printer or a NAS, through a device that is on the same LAN.
Open the device, select LAN routes, then Add LAN route.
| Field | What it does | Values |
|---|---|---|
| Enable this route | Turns the route on. Turn it off later to pause access without deleting the settings. | On for a new route. A new route cannot be added switched off. |
| Local network address | The LAN address behind this device. | An IPv4 network address, for example 192.168.1.0 |
| Prefix length | The size of that LAN. | 16 to 24 (Supported range: /16–/24.). Each /24 route of a device gets its own VPN route. A route with a prefix length from 17 to 23 gets a VPN route only when it is the first route of that device. |
Select Save route. The route is listed with the LAN you entered and a second line, VPN route. That is the address range Localtonet assigned to the LAN inside the VPN. The other devices reach a host of the LAN through the VPN route, with the same host part. For example, with the LAN 192.168.1.0/24 and VPN route: 11.11.1.0, the LAN host 192.168.1.50 is reached at 11.11.1.50.
The device that owns the route forwards the traffic into its LAN, so it must stay online and must itself be able to reach the hosts you want to use.
Firewall rules #
Firewall rules belong to one device and filter the traffic that arrives at that device from other VPN devices. The dashboard summarizes the behaviour as follows:
- No active rules: the VPN firewall is off, and the device accepts traffic from every device in the network.
- With active rules: unmatched incoming traffic is blocked, Deny wins over Allow, and replies to the device's own outgoing connections are allowed.
Open the device, select Firewall rules, then Add firewall rule.
| Field | What it does | Values |
|---|---|---|
| Enable this rule | Turns the rule on or off without deleting it. | On or off |
| Action | What happens to matching traffic. | Allow, Deny |
| Protocol | The traffic the rule matches. | TCP, UDP, TCP + UDP, ICMP (ping), All (TCP, UDP, ICMP) |
| Source device | The device whose incoming traffic this rule matches. | All devices in this network, or one other device of the network |
| Apply to all ports | Matches every port. Turn it off to enter ports. | On or off. Not shown for protocols that include ICMP. |
| Ports | The destination ports on this device. | A single port, comma-separated ports, or a range, from 1 to 65535. Example: 443, 8080, 10000-10100 |
Select Save rule. Notes on the protocols:
- ICMP (ping) includes ping and network error messages. It does not use ports.
- All (TCP, UDP, ICMP) matches TCP, UDP and ICMP on all ports.
- ICMP rules require an updated VPN client.
The first active rule changes the default. As soon as a device has one active rule, everything that no rule allows is blocked for incoming traffic. If you allow only TCP port 22, a ping to that device stops working until you add an ICMP (ping) rule.
Saved settings are sent to the client. The VPN firewall · device report box in the device details shows what the client last reported: whether the firewall is enabled, the number of active rules, and how many packets were blocked since the last policy reload. This report is the last one the client sent; it does not confirm that your latest edit was applied. Firewall rules of the operating system are separate and still apply.
Monitoring and diagnostics #
The network header shows the counters Devices, Online and Need attention, and the time of the last status update. The device list refreshes on its own every few seconds; Refresh devices and status reloads it at once. Filter the list with All devices, Online, Needs attention and Offline, or search by name or IP.
Online means the device is reporting to the server. The VPN health column tells you whether its VPN interface works:
| VPN health | Meaning |
|---|---|
| VPN ready | Interface is running. Peer paths are established on demand. |
| Connecting | A peer tunnel is being established. |
| Connection issue | One or more peer paths need attention. |
| Interface error | VPN interface setup failed. Check VPN permission or the device service. |
| Firewall setup issue | Windows VPN interface permission could not be configured. Open device details for the firewall report. |
| Interface stopped | The device is online, but its VPN interface is not running. |
| Report expired | The device heartbeat is recent, but no fresh VPN diagnostic report has reached the dashboard. Current VPN health is unknown. |
| Diagnostics unavailable | No health report yet. Older clients need an update to send diagnostics. |
| No heartbeat | No recent device heartbeat. Check connectivity and whether the app is running. |
| Status unavailable | The status request failed. The dashboard retries automatically. |
Peer paths: direct or relay #
Under the health badge, a line such as 1 direct · 0 relay counts the connected paths of the device. The device details list them under Current peer paths with the columns Peer, State, Path, Latency and Traffic. The path is P2P for a direct connection or Relay when traffic goes through the relay location of the network. If a direct path does not respond, the existing relay is kept, so the devices stay connected.
If the list says No peer traffic has been attempted in this session, nothing is wrong: paths appear when a device sends traffic to another VPN address.
Recent events #
Recent events lists what happened on the paths of the device. The history includes failed attempts that later recovered (marked Recovered), so judge the current state by the peer paths above it.
| Event | What to check |
|---|---|
| Connection attempt exceeded its time limit. | Whether the other device is online and its network allows outgoing connections. |
| Relay connection could not be established. / Relay node could not be reached. | Outgoing connections from the device to the relay location. |
| The other device could not join the relay. | The network connection of the other device. |
| Neither relay nor direct connection succeeded. | Both devices: client running, online, VPN interface running. |
| Direct path did not respond; the existing relay was kept. | Nothing. Traffic keeps using the relay. |
| The VPN interface could not be started. | Administrator or root rights, and the tun module on Linux. |
| No device advertises a route for this IP. Check the destination device and its VPN address. | The address you are connecting to. It must be the VPN address of a device or inside a VPN route. |
Tunnel status shows transport health. It does not verify ping or application access: a firewall rule, the firewall of the operating system or a missing route can still block the traffic.
Example: reach an office PC and its LAN from a laptop #
You have an office PC and a laptop, and a NAS in the office LAN 192.168.1.0/24 at 192.168.1.50.
- Create two tokens under My Tokens, named
office-pcandlaptop. - In VPN Manager, create the network
Office networkwith a relay location close to the office. As your first network it gets the subnet10.11.0.0/16. - Add the device
office-pc. It gets10.11.0.1. Add the devicelaptop. It gets10.11.0.2. - Start the client with administrator or root rights on both machines, each with its own token. Wait for VPN ready on both.
- From the laptop, connect to the office PC on its VPN address:
Bash
ping 10.11.0.1 - Open
office-pc, select LAN routes and add Local network address192.168.1.0with Prefix length24. The route shows VPN route: 11.11.1.0. - From the laptop, reach the NAS through the VPN route:
Bash
ping 11.11.1.50 - To limit what the laptop may open on the office PC, open
office-pc, select Firewall rules and add a rule with Action Allow, Protocol TCP, Source devicelaptopand Ports22, 3389. From now on, incoming VPN traffic to the office PC that this rule does not allow is blocked, so the ping from step 5 no longer answers. Test the NAS again after adding rules, and add a rule for it if you still need it.
Always use the addresses your dashboard shows. They differ when this is not your first network or when addresses were already in use.
Remove a device or delete a network #
- Remove device in the device details removes the device from the VPN, together with its LAN routes and firewall rules. The VPN stops on that device.
- Network options › Delete network deletes the network and removes all its devices. This cannot be undone.
Troubleshooting #
The device stays Offline or shows "No heartbeat"
The client is not connected with the token you added. Start the Localtonet client on the device with exactly that token and check its internet connection. Use Copy auth token in the device details to compare the token.
The client shows "Admin rights required." or the health is "Interface error"
The client could not create the VPN interface. Close it and start it again as administrator (Windows) or as root (Linux, macOS). On a packaged Linux installation, switch from localtonet.service to localtonet-vpn.service as shown under Client requirements.
"Interface stopped": the device is online but the VPN is not running
The client is connected, but its VPN interface is down. Restart the client with administrator or root rights. On Linux, check that the tun module is loaded with sudo modprobe tun.
"Firewall setup issue" on Windows
The message in the device report is Windows VPN interface permission could not be configured. Check administrator permissions and Windows firewall policy on this device. Run the client as administrator, and check whether a company policy manages Windows Firewall on that PC.
Both devices are "VPN ready" but ping does not work
Check the firewall rules of the destination device first: with at least one active rule, everything that no rule allows is blocked, and ping needs a rule with the protocol ICMP (ping) or All (TCP, UDP, ICMP). The device report shows the number of blocked packets and the source of the last blocked one. Then check the firewall of the operating system, which is separate from the VPN firewall.
"This AuthToken is already used in a VPN network. Select a different AuthToken."
A token can be a device in one VPN network only. Create another token for the device, or remove the token from the other network first.
"Enter a valid IPv4 address within the same subnet." or "This address is already assigned to another device."
The new virtual IP address must keep the first two numbers of the subnet and must not be in use by another device of the network.
"Use ports from 1 to 65535, separated by commas, or a valid range."
Write ports as 22, 80, 443 or 10000-10100. In a range the first port must not be larger than the second.
"No relay locations are available. Close and reopen this dialog to retry."
The list of relay locations could not be loaded. Close the Create network dialog and open it again.
A host behind a LAN route does not answer
Connect to the address inside the VPN route, not to the original LAN address. Check that the route is Active, that the device owning the route is online, and that this device can reach the host itself.