Overview
- This article provides Mesh Network administrators with an overview of the Subnet Linker features.
Notes
- The content of this article is based on the product specifications as of August 2026 and is subject to change without notice.
- When configuring an ACL for a Subnet Linker, the unit of specification is the Subnet Linker, and you must specify all necessary ports for all servers you want to allow access to.
For details about ACLs, please refer to the following article.
[Mesh Network] Overview - Since you may need to open unused ports, we recommend using this feature only when there are devices on which the agent absolutely cannot be installed.
Overview of Subnet Linker
The Subnet Linker allows access to servers under its control via the Mesh Network, targeting servers where the Runetale agent cannot be installed for various reasons.
Components of Subnet Linker
The Subnet Linker consists of two components.
- Subnet Linker
- A server or client PC with the Subnet Linker role enabled.
- Advertised Route
- The destination IP address (network range) specified as the forwarding destination.
- By associating an Advertised Route with a Subnet Linker, you can enable access via the Subnet Linker.
- The maximum number of Advertised Routes that can be associated with a single Subnet Linker is 2.
Subnet Linker Configuration Procedure
For instructions on how to create a Subnet Linker, please refer to the following article.
[Mesh Network] How to Configure a Subnet Linker