Connectors
Basic Concepts
The Connector is a core service component provided by our platform. Deployed as software within your network, it enables access connections from external sources to resources inside your network. Running on containers or Linux systems, the Connector can be downloaded, installed, and automatically launched by executing platform command lines.
Once the Connector is online, it automatically establishes an outbound encrypted TCP persistent connection from your internal network to the VTN gateway.
Configuration Recommendations
Currently, the Connector supports three deployment methods:
- Docker
- RPM (RedHat / CentOS)
- DEB (Debian / Ubuntu)
Configuration recommendations are as follows:
| CPU | Memory | Available Disk | Estimated QPS | |
|---|---|---|---|---|
| Minimum Configuration | 4 cores or more | 8 GB or more | 100 GB or more | 5000 QPS |
| Recommended Configuration | 8 cores or more | 8 GB or more | 200 GB or more | 20000 QPS |
Connector Deployment
Following the deployment guidelines in the Quick Start, after obtaining the Connector configuration and commands, you can proceed to configure it in the prepared Linux system environment.
Questions
How many Connectors can be deployed in one network?
There is no upper limit to the number of Connectors that can be created in a network (subject to your plan restrictions), but a maximum of 8 Connector devices can provide services simultaneously in one network.
Can multiple Connectors be deployed on one device?
If using Docker deployment, multiple Connectors can be created on one device. Other deployment methods do not support this.
Can one installation command be used to deploy multiple Connectors?
One installation command can only be used for one device. If you need to install Connectors on other devices, please create new Connectors on the platform and obtain new installation commands.
Can a Connector device be switched to another network?
Connector devices cannot be switched to other networks. If migration is required, please create and deploy a new Connector in the target network.
