Overview
- This article explains how to configure a Subnet Linker for Mesh Network administrators.
Notes
- Mesh Network administrator privileges are required to view the actual screens or make configuration changes.
- At the initial login, only the initial administrator registered at the time of application can log in to Mesh Network.
- The content of this article is based on the product specifications as of August 2026 and may be changed without prior notice.
- For an overview and role of the Subnet Linker, please refer to the following service overview.
[Mesh Network] Service Overview - The following are the supported targets for configuring a Subnet Linker:
- Windows Server (resources installed via CLI)
- Linux Server (resources installed via CLI)
- Windows PC (devices installed via client installer)
Procedure
- Access the Mesh Network login page from the URL below and log in with an administrator user.
https://login.hennge.runetale.com - After logging in to the Administration, go to [Linkers] - [Subnet Linker] and click [Create New Subnet Linker].
-
Enter the following fields and click [Create].
Field Description Linker Name The name of the Subnet Linker. Advertised Routes Specify the local network you want to access via the Subnet Linker.
You can also specify a host by setting the subnet as [/32].
* You can add up to 2 routes. - Associate resources and devices with the created Subnet Linker.
From the list of Subnet Linkers, click [Node Integration] for the target Subnet Linker. - Select the resources and devices to associate with the Subnet Linker and click [Next].
- If the content is correct, click [Connect].
- Log in to the resources and devices associated as Subnet Linkers.
-
[Windows Server] Launch PowerShell and run the following command.
runetale up --snat-subnet-routes=true -
[Linux Server] Launch the shell and run the following commands.
echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.conf echo 'net.ipv6.conf.all.forwarding =1' | sudo tee -a /etc/sysctl.conf sudo sysctl -p /etc/sysctl.conf runetale up --snat-subnet-routes=true -
[Windows PC] Launch PowerShell and run the following commands.
* If you changed the client installation folder, specify the installation directory in the first command and execute it.cd "c:\Program Files\runetale" runetale up --snat-subnet-routes=true
-