Skip to main content
日本語 简体中文 繁體中文

[Mesh Network] Procedure List

Overview

This article describes the procedure for customers introducing Mesh Network to begin using Mesh Network.

Notes

  1. Please review the items required according to the services and intended use.
  2. The content of this article is based on the product information as of September 2026 and is subject to change without notice.

Table of Contents

  1. Preparation
  2. Initial Setup / Operation Check
  3. End User Prerequisites for Initial Setup
  4. Start of Operations

Preparation

  1. Organize requirements 
    Please organize the operations you intend to implement using Mesh Network.
  • Internal services and systems to be accessed from outside
  • Source devices
  • Destination servers
  • Communication type when connecting
  1. Verify devices to be deployed
    Please verify the devices, servers, and other equipment that will use Mesh Network from the following perspectives.
  • Information about destination servers, etc.
    • OS type and version
    • Number of devices
    • Tools used when connecting (browser, Explorer, etc.)
    • Connection method (specifying an IP address, specifying an internal domain FQDN, etc.)
  • Source clients

  1. Verify the existing network environment

    Mesh Network requires TCP/443 communication from devices with the client/agent installed to Mesh Network to be allowed. For details, please refer to the following article.
    HENNGE One Network Requirements (FQDNs and IP Addresses)

  2. Mesh Network routing design
    Please design the ACL (Access Control List) with reference to the tips below.

・When the Mesh Network agent cannot be installed on destination servers, etc.

・When destination servers, etc. cannot meet the Mesh Network network requirements

Communication relaying using a Subnet Linker is required.

[Mesh Network] What is Subnet Linker?

When an internal FQDN is specified to access a destination server

Internal domain name resolution using Split DNS is required.

[Mesh Network] About DNS in Mesh Network

When communication from destination servers or source devices to Mesh Network passes through network security products such as a proxy

If communication using Mesh Network cannot be established, please isolate the issue by checking whether operation improves by bypassing the network security product, etc.

Initial Setup / Operation Check

  1. Edit Access Policy Group
    To allow administrators to log in to Mesh Network, permit login to Mesh Network in the HENNGEAccessControl access policy group settings.
    [Access Control] Create / Edit Access Policy Group
  2. Set Up Mesh Network Client Devices
    Depending on the design, install the client, log in, and configure the required settings on the necessary devices.
  3. Set Up Servers
    Depending on the design, install the agent on the necessary servers and configure the required settings.
  4. Configure ACL
    Configure an ACL for administrators to perform functionality testing.
  5. Mesh Network Functionality Test
    Verify that the ACL configured for functionality testing operates according to the requirements.
    [Mesh Network] Functionality Test

End User Tasks for Company-Wide Deployment

To configure ACL（AccessControlList）settings in the Mesh Network management console, the client must be installed and logged in to on each user's device.

Users and devices that have completed their initial login can be specified as ACL communication sources and destinations in the management console.
  1. Edit Access Policy Group
    To allow all users to log in to Mesh Network, permit login to Mesh Network in the HENNGEAccessControl access policy group settings.
    [Access Control] Create / Edit Access Policy Group

The conditions for permitting login to Mesh Network are defined in the HENNGEAccessControl access policy group.

Therefore, if you want to control devices using Mesh Network, perform the necessary device controls, such as using HENNGEAccessControl device certificates.
  1. Notify End Users to Install and Log In to the Client
    Install the client and perform the initial login on each device
    [Mesh Network] User Help
  2. Install the Client and Perform the Initial Login on Each Device
    End users install the client and perform the initial login according to the notification.

Start Operations

  1. Notification Regarding the Start of Operations
    Please inform end users about how to use Mesh Network, the start date for use, and the systems that will be accessed using Mesh Network.
    Content to Notify End Users When Starting to Use HENNGE One
  2. Configure ACLs for production operations.
    [Mesh Network] Editing a Group
    [Mesh Network] Editing an ACL (Access Control List)
  3. Mesh Network Functionality Test
    Please confirm that the ACLs configured for production operate according to the requirements.
    [Mesh Network] Functionality Test

This completes the Mesh Network implementation process.

Translation Disclaimer

This article has been automatically translated from the original Japanese version for your convenience.
While we strive to ensure accuracy, we cannot guarantee its reliability or completeness.

In the event of any discrepancies or questions regarding the content, the official Japanese version shall prevail.