InGateway Series
User's manual
(Applicable to IG500, IG900 series products)
Version V1.0, June 2024
© 2024 InHand Networks All rights reserved.
The InHand logo is a registered trademark of InHand Networks.
The company reserves the right to change this manual, and the products are subject to subsequent changes without prior notice.We shall not be responsible for any direct, indirect, intentional or unintentional damage or hidden trouble caused by improper installation or use.
The InGateway series is an edge computing gateway for the industrial IoT sector from InHand. This series of products has rich interfaces and global cellular access capability. It supports users to use Python secondary development, and can be built-in InHand DeviceSupervisor™ Agent service, which supports hundreds of data collection protocols, and easily achieves device data collection, processing and cloud, and also supports InHand DeviceLive cloud management, helping enterprises to accelerate the process of digitisation.
The product models to which this manual applies are listed below:
Connect to the IG using the following default IP address (address information is also available from the device panel)
Select "Use the following IP address", enter the IP address (default is any value from 192.168.2.2 to 192.168.2.254), subnet mask (default is 255.255.255.0), default gateway (default is 192.168.2.1), and DNS server address, click <OK>.
Device factory default password:username: admpassword: check the nameplate on the device panel for initial password information
This page provides an overview of the gateway's system status, system performance, system storage, network connectivity, network flow, and other information. This page allows you to get a quick overview of the device basics.
This page shows the current cellular status and configuration information of the gateway. You can configure the cellular network parameters by using the "Enable Cellular" button.
The cellular network parameters are described below:
- Network Type: User selects the type of mobile network used by the device, GSM, CDMA can be selected.
- APN: APN (Access Point Name) is used to identify the service type of WCDMA/LTE network, and the WCDMA/LTE system provides corresponding services according to the APN of the user connecting to the WCDMA/LTE network. Provided by the operator (this item is not set for CDMA2000 series).
- Access Number: The dialling string used for dialling. The dialling string is provided by the operator, please obtain it from the operator.
- When the 3G/LTE data card supports WCDMA or LTE standard, the default dialling string is *99***1#.
- When the 3G data card supports the CDMA2000 standard, the default dialling string is #777.
- Auth Method
- Auto: automatically selects an authentication method
- PAP: Password Authentication Protocol, which provides a simple plaintext authentication method through two handshakes.
- CHAP: Challenge Handshake Authentication Protocol, which confirms the digest information through three handshakes for secure authentication.
- MS-CHAP: Microsoft's CHAP standard.
- MS-CHAPv2: An upgraded version of MS-CHAP, which requires two-way authentication.
- Username: Specifies the user name of the user accessing the external PDN network. Provided by the operator. The default username is gprs.
- Password: Specifies the password for users accessing the external PDN network. Provided by the operator. The default username is gprs.
- Select primary card: support SIM1, SIM2, random and sequence four ways
- Max Number of Redials: when SIM1 has not dialled successfully within the set maximum dialling times, the device will switch to SIM2 for dialling.
- Min Connected Time: When the device's dial-up connection success time is less than the set minimum connection time, the device's dial-up times are accumulated. When greater than the set minimum connection. The dialling times of the device will be cleared to zero. 0 is to disable this function
- Backup SIM Timeout: If the current card is a backup sim, after the successful dialling of the backup sim, the device will switch to the main card for dialling when the set timeout time of the spare card is reached.
- Enable SMS: enable/disable SMS function
- Reply result: When enabled, when the user configures the cellular via SMS, io or reboots the system, the device will reply with an SMS to inform whether the result of the configuration is successful or not.
- Query interval: the device will periodically query the received SMS, set the interval of periodic query here
- Mobile number whitelist: only mobile phone numbers in the whitelist can send SMS to set cellular parameters and other information.
Details of the SMS configuration are given below:
1、SMS set cellular dialling parameters
SMS format:
cellular slot=sim1 apn=hello username=abcd password=123456 network=4g dialnumber=*99*1 auth=pap
The cellular dialling parameters are configured as described below:
Caveats:
2、SMS to restart the system
SMS format:
system command=reboot
Reboot System Parameter Description:
3、SMS query dialling information
SMS format:
status object=cellular
Query Dialling Information Parameter Description:
After sending the enquiry SMS, you will receive an SMS with the following content:
cellular_status signal=none network=4g hostname=EdgeGateway uptime=150 ip=10.48.104.247
The response content parameters are described below:
4、SMS device digital output DO
SMS format:
io do0=1 do1=1 do2=0 do3=0
DO Setup Parameter Description:
5、Changes in DI for SMS reception
To use this feature, you need to configure the mobile phone number to receive SMS on the io page and add the mobile phone number to the whitelist on the dialling page.
The user's mobile phone number receives an SMS with the following content after the value of di changes:
io_status sn=GL5022221013941 di0=0 timestamp=2024-05-15T10:03:12+0000
Note: Currently, only the basic models IG502-FF53 and IG502-FQ58 support the SMS function, e.g. IG502-FQ58-W-G, IG502-FF53-IO-W-G. Please refer to the Ordering Information section in the datasheet for the specific models.
- Initial Commands: you can configure some AT commands to query the module status.
- RSSI Poll Interval: After the device dials up successfully, it will query the signal status regularly with the set query interval time, such as setting the RSSI Poll Interval as 60s. For example, if the RSSI Poll Interval is set to 60s, after the device dials up, unplug the device antenna and wait for 60s, the signal of the device should be lowered, and the signal of the device will not be changed within 60s. 0 means disabled.
- Dial Timeout: If the device does not dial successfully within the set Dial Timeout, it is considered as dialling timeout, and the device re-detects the module and re-dials.
- MRU: Maximum Receive Unit, in bytes.
- MTU: Maximum Transmission Unit, in bytes.
- Use Default Asyncmap: Enable/Disable the default Asyncmap
- Use peer DNS: Use the DNS servers assigned in the dial-up network connection when enabled
- LCP Interval: detects whether the dial-up connection is normal at specified intervals
- LCP Max Retries: number of retries after detection of connection disconnection
- Infinitely Dial Retry: when enabled, unlimited dialling retries if dialling fails
- Debug: The system log will print more detailed information when debug mode is enabled.
- Expert Options: You can configure the corresponding command parameters in the Expert Options.
The "Ethernet" page shows the configuration and status information of the Ethernet interface of the device, and you can configure the Ethernet interface parameters or view the detailed status information on this page. The steps to configure the Ethernet interface are as follows:
Take the IG902 as an example, the IG902 has two Gigabit Ethernet ports, the specific configuration and description are as follows
Configure dynamic address acquisition for the interface (network type selected as DHCP) as shown below:
Configure the interface with a static IP (network type is selected as static IP) as shown below:
If the interface type is WAN port, you can also set the gateway and DNS:
- Auto Negotiation
- 1000M Full Duplex
- 1000M Half Duplex
- 100M Full Duplex
- 100M Half Duplex
- 10M Full Duplex
- 10M Half Duplex
The "WLAN" page shows the IG's WLAN configuration and status information, where you can configure WLAN parameters or view detailed status information.
Note: Not all models of IG series support WLAN function, please refer to the official website Resource Centre for specific support, and go to the corresponding product list to check the "Ordering Guide" section in the product specification.
Configure the WLAN as the access point as shown below:
The parameters when configuring the WLAN as an access point are described below:
- SSID Broadcast: enable SSID broadcasting after the wireless client can scan the SSID, disable that is, hide the SSID, SSID hidden, the device sends a beacon frame does not contain SSID information, access to the client must be manually configured in the wireless client to access the device SSID identification
- Bridge: Bridges the WLAN to the bridge interface when enabled
- Band: the AP's wireless band, different equipment models support different situations, details can be found in the product specifications
- Radio Type: Different Radio types are supported by different wireless bands. Details can be found in the product datasheet
- 802.11b: operates in the 2.4G frequency band with a maximum speed of 11Mbps
- 802.11g: operates in the 2.4G band with a maximum speed of 54Mbps
- 802.11n: operates in the 2.4G band, but can also operate in the 5G band, with a theoretical maximum speed of 300Mbps.
- Channel: A channel is a data signal transmission channel that uses wireless signals as a transmission medium. There are 13 channels in the 2.4G band, each with a different carrier frequency.
- Channel 1, centre frequency 2.412 GHz;
- Channel 2, centre frequency 2.417 GHz
- Channel 3, centre frequency 2.422GHz;
- Channel 4, centre frequency 2.427 GHz
- Channel 5, centre frequency 2.432GHz;
- Channel 6, centre frequency 2.437GHz
- Channel 7, centre frequency 2.442GHz;
- Channel 8, centre frequency 2.447 GHz
- Channel 9, centre frequency 2.452GHz;
- Channel 10, centre frequency 2.457 GHz
- Channel 11, centre frequency 2.462GHz;
- Channel 12, centre frequency 2.467GHz
- Channel 13, centre frequency 2.472GHz
- SSID: Service Set Identifier. SSID technology can divide a wireless LAN into several sub-networks that require different authentication, each sub-network has to be independently authenticated, and only authenticated users can enter the corresponding sub-network, preventing unauthorised users from entering the network.
- Auth Method: Five authentication methods are available: OPEN, SHARED, WPA-PSK, WPA2-PSK, WPAPSK/WPA2PSK. encrypted authentication methods There are currently three authentication methods: WPA-PSK, WPA2-PSK, WPAPSK/WPA2PSK
- Encrypt Mode: Support TKIP and AES encryption
- WPA/WPA2 PSK key: authentication key, key length 8-63
- Bandwidth: Specify the channel bandwidth corresponding to the AP radio frequency, e.g. 20MHz, 40MHz for 2.4G band.
- Station Limit: Maximum number of clients the device can connect to at one time (up to 128)
- Wpa Group Rekey Time: the time interval (in ms) between authentication and key exchange required by a client device when attempting to access the encrypted network
Configure the WLAN as a client as shown below:
The parameters when configuring the WLAN as a client are described below:
- Client SSID: Fill in the name of the SSID that the gateway wants to connect to.
- Auth Method: consistent with the authentication method of the SSID to which you want to connect
- Encrypt Mode: consistent with the encryption method of the SSID to which you want to connect
- WPA/WPA2 PSK key: consistent with the key of the SSID to which you want to connect
- Network Type: Select the mode of obtaining IP address for the client, there are two kinds of static IP and dynamic address (DHCP).
A loopback interface is a logical, virtual interface on the device. After you create and configure a loopback interface, its address can be pinged or telnetted, which can be used to test network connectivity. You can configure or view the loopback interface parameters on the Loopback Interface page.
NOTE: A maximum of 10 slave IP addresses can be configured.
DHCP uses a client/server communication model, in which the client requests an address from the server, and the server returns the IP address assigned to the client and related information (such as the lease period) to enable dynamic configuration of IP addresses and other information. You can set and view the configuration of the DHCP server on the DHCP Server page.
Start the dhcp server function on the interface to assign addresses to the downstream devices on that interface
- Enable DHCP service: enable/disable DHCP service.
- Interface: select the corresponding interface, the type and number of interfaces supported by different devices are not the same, select according to the actual situation
- Starting Address: Sets the starting IP address assigned to the client device in the address pool.
- Ending Address: Sets the ending IP address assigned to the client device from the address pool.
- Lease: Set the lease period of the assigned IP address, after the expiration date, the DHCP server will recall the IP address assigned to the client and re-assign the IP address, it cannot be empty.
The Domain Name System (DNS) is a distributed database for TCP/IP applications that provides translation between domain names and IP addresses. With the DNS, users can use easy-to-remember, meaningful domain names for certain applications, and DNS servers in the network will resolve the domain names to the correct IP addresses. You can set up and view the domain name servers and DNS relay service in the "DNS Service" page.
Configure DNS servers to support up to two domain name servers, as shown in the following figure:
Configure the DNS relay service, as shown in the following figure:
Note: Enable the DNS relay service and do not disable the DNS relay service when DHCP server is enabled.
GNSS stands for Global Navigation Satellite System. Common GNSS systems include GPS (Global Positioning System) of the United States, GLONASS (GLONASS) of Russia, and BeiDou (BDS) of China. On the "GNSS" page, you can view the status of GNSS and configure GNSS.
Remarks:
Not all models of IG series support GNSS function, for details, please refer to the website Resource Centre, and enter the corresponding product list to check the "Ordering Guide" section in the product specification.
GNSS configuration
GNSS configuration page parameter descriptions:
- GPS: Global Positioning System
- BDS: China's Beidou Satellite Navigation System
- GLONASS: Russia's GLONASS satellite navigation system
GNSS IP Forwarding
The GNSS IP forwarding parameters are described below:
- Client
- Transmit Protocol: Two protocols available, TCP and UDP.
- Connection Type: two types are available: Long-Lived and Short-Lived. Needs to be consistent with the server side
- Keepalive Interval: when the TCP connection is successfully established, the time interval between the device and the server for one heartbeat message interaction to determine whether the connection status is normal or not
- Keepalive Retry: after the heartbeat timeout, the number of times the heartbeat continues to be sent, when the set number of times the heartbeat still times out, the device disconnects the TCP connection.
- Min Reconnect Interval: the connection interval used when the device establishes a TCP connection, incremented every 30 seconds until the maximum reconnect interval is reached
- Max Reconnect Interval: Maximum time between reconnections when the device establishes a TCP connection.
- Source Interface: When the device connects to the server, it uses the address of the source interface as the source address to establish a TCP connection.
- Reporting Interval: the time interval for the device to report GNSS information.
- Include RMC: Whether to send RMC data for GNSS data
- Include GSA: Whether to send GSA data for GNSS data
- Include GGA: Whether to send GGA data for GNSS data
- Include GSV: whether to send GSV data for GNSS data or not
- Message Prefix: user-defined header content for GNSS messages sent by the device
- Message Suffix: user-defined message endings for GNSS messages sent by the device
- Destination IP address: IP of the server and port of the server
- Connection Type: two types are available,Long-Lived and Short-Lived. Needs to be consistent with the client
- Keepalive Interval: when the TCP connection is successfully established, the time interval between the device and the client for one heartbeat message interaction to determine whether the connection state is normal or not
- Keepalive Retry: after the heartbeat timeout, the number of times the heartbeat continues to be sent, when the heartbeat timeout reaches the set number of heartbeat retries, the device disconnects the TCP connection
- Local Port: the service port number defined by the device when it is a TCP server.
- Reporting Interval: the time interval for the device to report GNSS information to the server.
- Include RMC: Whether to send PMC data for GNSS data
- Include GSA: Whether to send GSA data for GNSS data
- Include GGA: Whether to send GGA data for GNSS data
- Include GSV: Whether to send GSV data for GNSS data
- Message Prefix: user-defined header content for GNSS messages sent by the device
- Message Suffix: user-defined message endings for GNSS messages sent by the device
GNSS Serial Forwarding
The GNSS Serial Forwarding parameters are described below:
You can view information about the hosts connected to IG on the Host List screen.
Select "Network > Routing > Routing Status" to enter the "Routing Status" interface. You can view the detailed information of routes in this screen, as shown in the following figure:
You can manually set up a static route on the Static Routing page. After you set up a static route, messages to the specified destination will be forwarded in accordance with the path you specify.
Configure static routes as shown below:
The static route parameters are described below:
An ACL is an access control list that filters network interface data by configuring a series of matching rules to allow or disallow the passage of specified data streams (e.g., restricted source IP addresses, account numbers, etc.). You can set the filtering policy for network interface data in the "Access Control List" page.
Configure the standard access control policy, as shown in the following figure:
- ID: ACL rule ID, range 1-99, used to uniquely identify an access control policy
- Sequence Number: ACL rule serial number, the saller the value, the higher the priority
- Action: Permit/Deny messages to pass
- Source IP: the source address of the matching message of the ACL rule, if it is empty, it means any, that is, all network segments.
- Source Wildcard: The source address backmask of the ACL rule matching message, for example, if the source address segment is 192.168.2.0 and its mask is 255.255.255.0, then its backmask is 0.0.0.255.
- Log: When enabled, the system records logs about access control.
- Description: Used to provide a description of the ACL rule, making it easy to see at a glance what the ACL does.
Configure the extended access control policy as shown in the following figure:
- ID: ACL rule ID, range 100-199
- Sequence Number: ACL rule serial number, the smaller the value, the higher the priority
- Action: Permit/Deny the passage of the message
- Protocol: Access Control Protocol
- Source IP: the source address of the ACL rule matching message, when it is empty, it means any, that is, all networks.
- Source Wildcard: The source address backmask of the ACL rule matching message.
- Source Port: source port number, any means any source port of TCP/UDP message matches. The source port number can only be specified if the protocol is TCP or UDP.
- Destination IP: the destination address of the matching message of the ACL rule, if it is empty, it means any, that is, all networks.
- Destination wildcard: the backmask of the destination address of the ACL rule match message.
- Destination Port: Destination port number, any means any destination port of TCP/UDP message matches. The destination port number can only be specified if the protocol is TCP or UDP.
- Established: when enabled, it controls the messages of established TCP connections, not the TCP messages of unestablished connections; when not enabled, it controls both established and unestablished TCP messages. This parameter can be configured only when the protocol is TCP.
- Segment: Controls the message that is fragmented when the packet is sent out of the interface. (This is only available if the protocol type is IP.)
- Log: When enabled, the system records logs about access control.
- Description: Used to provide a description of the ACL rule, making it easy to see at a glance what the ACL does.
- Interface: the name of the interface that needs to set the access control policy
- In ACL: Select an ACL rule for messages that enter from this interface and are then forwarded by the device
- Out ACL: Select an ACL rule for messages forwarded through the device and whose egress is this interface.
- Admin ACL: Select an ACL control rule for messages coming in from this interface with a destination address on the device itself, usually used to restrict access to this machine
Network Address Translation (NAT) enables multiple hosts on a LAN to access the public network through one or more public IP addresses, i.e., using a small number of public IP addresses to represent a large number of private IP addresses, thus saving IP addresses on the public network. You can view and set the NAT rules in the Network Address Translation page.
As shown in the following configuration, configure the IG lower device to access the upper device through WAN:
The network address translation rule parameters are described below:
- SNAT: Source Address Translation, translates the source address of an IP packet into another address. Generally used for data sent from inside the gateway to the outside.
- DNAT: Destination Address Translation, converts the destination address of an IP packet to another address. Generally used for data sent from outside the gateway to the inside.
- 1:1NAT: Add one SNAT and one DNAT at the same time
- Internal: internal address
- External: external address
In this example, the WAN port is the converted outgoing interface, so set the type of WAN to "Outside" interface.
- IP to IP
- IP to INTERFACE
- IP PORT to IP PORT
- ACL to INTERFACE
- ACL to IP
- IP address: the IP address to be converted
- Port: the port number where the conversion needs to be done
- Access Control List: The access control lists that need to be converted are pre-configured in the "Access Control Lists".
- IP Address: converted IP address
- Interface: Converts data to that interface for forwarding
- Log: when turned on, logs related to network address translation will be printed in the log, which is turned off by default
- Description: describes this NAT rule
Layer 2 Tunneling Protocol L2TP is a type of Virtual Private Dial-up Network VPDN tunneling protocol that extends the application of Point-to-Point Protocol PPP and is an important VPN technology for remote dial-up users to access the corporate headquarters network.
Note: Detailed configuration of IPSEC, GRE, OPENVPN can be found in the catalogue " Advanced Functions > VPN".
- Name: Custom L2TP Class Name
- Authentication: Tap Enable to require authentication when connecting to the network.
- Hostname: the hostname of the local end of the network connection, can not be matched
- Challenge Secrets: The tunnel authentication key must be configured when the authentication point selection is enabled, otherwise it does not need to be configured.
- Name: Custom Pseudowire Class Name
- L2TP Class: The name of the defined L2TP Class.
- Source Interface: Select the source interface name
- Data Encapsulation Method: optional L2TPV2, L2TPV3
- Tunnel Management Protocol: L2TPV2, L2TPV3, NONE can be selected
- Enable: enables or disables L2TP Tunnel
- ID: L2TP virtual interface identification number
- L2TP Server: Set the IP address or domain name of the L2TP server.
- Pseudowire Class: the name of the defined Pseudowire Class.
- Authentication Type: Auto, PAP, CHAP can be selected
- Username: the legitimate user name set by the counterpart server
- Password: a legitimate password set by the counterpart server of the network.
- Local IP Address: Set the IP address of the L2TP virtual interface address, or leave it unassigned for the peer server to assign automatically.
- Remote IP Address: gateway to the server-side L2TP address pool, may or may not be assigned
- Enable: enables or disables L2TPV3 Tunnel
- ID: L2TPV3 virtual interface identification number
- Peer ID: Set the IP address or domain name of the L2TPV3 server.
- Pseudowire Class: the name of the defined Pseudowire Class.
- Protocol: IP, UDP optional
- Source Port: the source port used when establishing L2TP using the UDP protocol
- Destination Port: the destination port when L2TP is established using the UDP protocol
- Xconnect Interface: L2TPV3 Bridge Port
- Local Session ID: the local tunnel ID specified in the static configuration of L2TPV3, in the range 1-65535
- Remote Session ID: Remote tunnel ID specified in the static configuration of L2TPV3, in the range 1-65535
- Local Tunnel ID: the L2TPv3 tunnel identifier configured above
- Local Session IP Address: address of the statically configured L2TPV3 virtual interface
The L2TP server parameters are described below:
- Challenge Secrets: Tunnel key to be authenticated when L2TP is established, must be the same at both ends
- Server Name: Name of the server when establishing L2TP.
- Client Name: Specifies the name of the L2TP client for access.
The "Python Edge Computing" page shows information about the IG's Python secondary development environment and the app configuration and running status on the device. You can develop your customised Python App with the secondary development environment information on this page, and you can also configure and view the App status on this page.
The Python environment configuration steps are as follows:
App configuration steps are as follows:
App configuration features are described below:
- Start All: Starts all deactivated apps
- Stop All: stops all enabled apps
- Restart All: Restart all apps in the list
- Download: Download the runtime logs of the specified apps
- Delete: Empty the runtime log of the specified app
- View: View the runtime log of the specified App
- Stop: Stop running the specified app
- Restart: Restart the specified App
- Enable: Enable the App, the App will run automatically every time you reboot your device after you enable it
- Startup Parameters: You can configure the startup parameters of the app here.
- Export Configuration: Export App Configuration File
- Import Configuration: Import the App configuration file, after importing the configuration file and restarting the App it will run according to the imported configuration file.
- Uninstall: Uninstall the App
- Edit: Edit the size and number of App log files, as well as the App's startup parameters
- Add: Add App
IG supports hosted docker images, you can publish your docker images to IG to quickly deploy and run your self-developed applications.The steps to configure the Docker environment are as follows:
Note: Only IG902 and IG974 support Docker function.
Enable the Docker Manager as shown below:
The parameters of the Docker management page are described below:
The gateway supports both Azure IoT Edge and AWS IoT Greengrass edge computing components. They can be configured on the Edge Computing -> Cloud Edge Computing page. Note: Only the IG902 supports the Cloud Edge Computing function.
The configuration steps are as follows:
The configuration steps are as follows:
An I/O module (Input/Output Module) is a device or component used to implement input and output functions. It can input signals from external devices into the control system or output signals from the control system to external devices, thus realising the interaction between the system and the external environment.
Configure the IOs on the Edge Computing -> IO Module page. the gateway supports 4 input IOs and 4 output IOs.
Note: Support models IG502/IG504/IG532/IG902
Input IOs: 4 input IOs can be configured as "Digital Input" or "Counter".
Output IOs: 4 output IOs can be configured as "Digital Output", "Continuous Pulse Output" and "Fixed total Pulse Output".
Supports reading and writing IO data via Modbus TCP protocol when Modbus TCP slave function is enabled.
You can view Modbus coil status information and holding register information in the Modbus Mapping Table page.
Configure Telegraf functionality on the Edge Computing -> Telegraf page. Support for installing Telegraf sdk, importing and exporting configuration files and exporting log files
Note: Only IG502 supports this function.
In order for the IG to work better with other devices, the system time needs to be configured accurately. The configuration method and steps are as follows:
- Select "System > System Time" to enter the "System Time" interface.
- Select the time zone of the gateway in the "Time zone" of "System Time".
- Select and click "Apply".
- Select "System Management > System Time" to enter the "System Time" interface.
- The gateway automatically gets the PC's time as the local time
- Click "Synchronise" in the device time, the device time will be synchronised with the local time.
- Select "System Management > System Time" to enter the "System Time" interface.
- Manually set the device time directly in the "Set Time".
- Click "Apply" when you are done with the settings.
- Select "System Management > System Time" to enter the "System Time" interface.
- Tick "Enable SNTP Clients".
- Configure each parameter in turn
- Click "Submit" to apply the configuration.
The SNTP client parameters are described below:
- Server Address: SNTP server address (domain name/IP), you can fill in up to 10 servers. When setting up multiple SNTP servers, the system will poll all SNTP servers until it finds an available one.
- Port: SNTP service port of the SNTP server
The IG can also be used as an NTP server to synchronise time for other devices as follows:
The NTP server parameters are described below:
- Primary NTP Server: Set multiple NTP servers, when primary NTP server is ticked, it means our device synchronises time with this NTP server. Checking more than one will poll all the ticked NTP servers until we find an available one.
- Server Address: NTP server address (domain name/IP), up to 10 servers.
You can select "System > Log" to enter the "Log" page. This page contains a lot of information about the network and IG, including operational status, configuration changes, and so on.
In the "Configure" page, you can set the gateway to interface with the remote logging server, after the setup is completed, the gateway will upload all system logs to the remote logging server, which requires the cooperation of the remote logging software on the host computer (e.g., Kiwi Syslog Daemon).
Select "System > Configuration Management" to enter the "Configuration Management" interface. You can backup the configuration parameters, import the corresponding parameter configurations, and restore the IG to the factory settings in this screen.
- Autosave: when checked, the configuration in running-config will be automatically synchronised to startup-config every time the configuration is modified to ensure that the configuration is not lost after the device is powered off and on.
- Encrypted: When enabled, all parameters configured by the IG on the WEB with passwords will be displayed in the configuration in an encrypted way. Improve password security.
- Import Startup Config: Import the configuration file into startup-config, the imported configuration will be loaded after reboot. (Note: During this process, make sure that the imported configuration is legal and in order. When importing configurations, IG will filter the commands with illegal format and re-store the remaining correct configurations into startup-config, and then execute the legal configurations in order after system reboot. If the imported configuration is not in a valid order, the system will not be able to enter the desired configuration state.)
- Export Startup Config: Backup startup-config to the host. startup-config is the configuration of the gateway at boot time.
- Export Running Config: Backs up running-config to the host. running-config is the current running configuration of the gateway.
- Restore Factory Configuration: restores the IG to the factory configuration, all configurations of the gateway are restored to the default parameters. A restart of the IG is required for the factory restoration to take effect.
The device cloud platform developed by InHand supports monitoring IG status, remote maintenance of field devices, remote batch issuance of IG configurations and batch upgrade of IGs, helping users manage IGs and field devices conveniently and efficiently. At present, IGs support interfacing with InHand cloud platforms: InHand Connect Service, InHand Device Manager, InHand iSCADA Cloud, and InHand Device Live Manager.
Configure the IG to connect to the InHand Connect Service (InConnect) platform as shown below:
Connecting to the InHand Connect Service platform parameters are described below:
- Enable Secure Channel: Enable/Disable the secure channel; when this function is enabled, a dedicated, encrypted communication channel will be established to ensure the security, integrity and confidentiality of data transmission during remote access to the device.
- Location: Source of location information, either Cellular or GPS.
- LBS Upload Interval: time interval for LBS information reporting, legal value 60-86400, unit: sec.
- Heartbeat Interval: heartbeat interval with the cloud platform, legal value 30-3600, unit: second
- Data Upload Interval: time interval of traffic information report, legal value 3600-86400. unit: second.
Configure the IG to connect to the InHand Device Manager (DM) platform as shown below:
Connecting to the InHand Device Manager platform parameters are described below:
- Enable Secure Channel: Enable/disable the secure channel; when this function is enabled, a dedicated, encrypted communication channel will be established to ensure the security, integrity and confidentiality of data transmission during remote access to the device.
- Location: Source of position information, either Cellular or GPS.
- LBS Upload Interval: time interval for LBS information reporting, legal value 60-86400, unit: sec.
- Heartbeat Interval: heartbeat interval with the cloud platform, legal value 30-3600. unit: second.
- Data Upload Interval: time interval for reporting traffic information, legal value 3600-86400, unit: second
Connecting to the InHand iSCADA Cloud platform parameters are described below:
Configure the IG to connect to the InHand Device Live Manager (DeviceLive) platform as shown below:
Connecting to the InHand Device Live Manager platform parameters are described below:
You can upgrade the firmware version of IG to support new features or to get a better experience on the "Firmware Upgrade" page. The steps to upgrade the firmware version are as follows:
To manage and configure the IG, you can configure how to manage and access the IG in the "Access Tools" screen. The configuration steps are as follows:
The HTTPS parameters are described below:
The TELNET parameters are described below:
The SSH parameters are described below:
The developer mode parameters are described below:
You can add a new user or manage the user's account password and access rights in the "User Management" page to achieve multi-user access and management of IG.
In the "Reboot" page, you can reboot the device every day or immediately. As shown in the figure below, if you enable "Regularly Daily Reboot", the device will be rebooted at "00:00" every day, and this function is disabled by default.
Select "System > Network Tools" to enter the "Networks Tools" page. You can diagnose IG network problems on this page. You can enter some extended options in Expert Options, e.g. -s 100 for sending 100-byte packets in Expert Options Configuration in Ping tool.
Use the Ping tool to detect whether the network is reachable, as shown below:
Use the route probing tool to determine the path through which IP datagrams access the destination, as shown in the following figure:
Use the network packet capture tool to capture the data transmitted on the specified interface, as shown in the following figure:
Select "System> 3rd Party Notification" to enter the Third Party Software Notification page. You can view the third-party software notification of IG software here.
You can click on the InGateway logo in the upper left corner of any web interface of the gateway to quickly jump to the "Overview" page.
You can click on your username in the top right corner to log out.
You can click "Language" in the upper right corner to switch the language display of the WEB interface, the gateway supports both Simplified Chinese and English.
Here, you can view the system status and network status; in the system status section, you can view the name, model, serial number, MAC address, version information, device time, device startup time, performance, storage and other information, you can also click on the Synchronise Time button to set the system time; in the network status section, click on the interface of the "Settings" to enter the configuration page of the corresponding interface. Click "Settings" after the interface in the Network Status section to enter the configuration page of the corresponding interface.
The RADIUS protocol uses a client/server (C/S) mode of operation. the RADIUS protocol entity consists of three parts: the user side, the RADIUS client (NAS), and the RADIUS server. The authentication process is shown in the following figure:
The authentication steps are as follows:
1. When a user accesses the network, the user initiates a connection request and sends a username and password to the RADIUS client.
2. The RADIUS client sends an authentication request message containing user name and password information to the RADIUS server. (NAS and RADIUS server use a pre-shared key, and the user password is encrypted and hidden by MD5 encryption algorithm using this shared key, which increases the security of the password.)
3. The RADIUS server checks the legitimacy of the user's identity:
(1) If the user's identity is legitimate, the RADIUS server returns an authentication acceptance message to the RADIUS client, allowing the user to proceed to the next action. Since the RADIUS protocol merges the processes of authentication and authorisation, the authentication acceptance message also contains the user's authorisation information.
(2) If the user's identity is not legitimate, the RADIUS server returns an authentication denial message to the RADIUS client, denying the user access to the access network.
4. The RADIUS client informs the user whether the authentication is successful.
The Radius authentication configuration is shown below:
The Radius parameter is described below:
Tacacs+ (Terminal Access Controller Access Control System) is a security protocol with enhanced functionality based on the Tacacs protocol, which is similar in function to the RADIUS protocol. The protocol is similar to the RADIUS protocol, using a client/server model to achieve communication between the NAS and the TACACS+ server. TACACS+ holds independent authentication (Authentication), authorisation (Authorization) and billing (Accounting) functions.
The Tacacs+ authentication configuration is shown below:
The Tacacs+ parameters are described below:
Lightweight Directory Access Protocol LDAP is a directory access protocol based on TCP/IP, mainly used to store infrequent data, such as email addresses, contact lists, etc. LDAP defines a variety of operations, and user authentication and authorisation can be achieved through binding and query operations. LDAP is based on Client/Server structure, the directory information is stored on the server, and does not support billing.LADP authentication process is shown in the following figure:
LADP certification is described below:
1、When the user needs to access the LDAP server, the user enters the user name and password and initiates an authentication request to the device
2. The device obtains the user name and password of the user and sends an administrator binding request message to the LDAP server with the administrator DN and administrator password as parameters to obtain query privileges.
3. When the LDAP server receives the administrator binding request message, it verifies whether the administrator DN and administrator password are correct. If the administrator DN and administrator password are correct, the binding is successful and the LDAP server sends an administrator binding response message to the device.
4. When the device receives the binding response message, it constructs a filter condition with the parameter of the user name entered by the user and sends a user DN query request message to the LDAP server. For example, the filter condition is CN=User2.
5. After the LDAP server receives the user DN query request message, it looks up the user DN according to the query starting point, query range, and filter conditions in the message. If the query is successful, it sends a successful query response message to the device. The queried user DN can be one or more.
6. The device sends a user binding request message to the LDAP server based on the user DN obtained from the query and the password entered by the user as parameters.
7. After the LDAP server receives the user binding request message, it checks whether the password entered by the user is correct.
(1) If the password entered by the user is correct, a binding response message of successful binding is sent to the device.
(2) If the password entered by the user is incorrect, a binding failure response message is sent to the device. The device takes the next user DN queried as a parameter and continues to send binding requests to the LDAP server until one DN binds successfully. If all user DNs fail to bind, the device notifies the user of the authentication failure.
8、After successful authentication, the device notifies the user of successful login.
The LADP authentication configuration is shown below:
The LDAP parameters are described below:
The following authentication methods are supported:
NOTE: Authentication 1 and Authorisation 1 should be set up consistently; Authentication 2 and Authorisation 2 should be set up consistently; Authentication 3 and Authorisation 3 should be set up consistently.
Dynamic domain name is a service that bundles dynamically assigned IP addresses with fixed domain names. In networks, in many cases the IP address that users are given when they access the Internet changes dynamically. To access specific network services or devices through a domain name, a dynamic domain name service is required.
The dynamic domain name parameters are described below:
DDNS Method List:
- Disable: Indicates that the dynamic domain name function is disabled.
- DynAccess
- QDNS(3322)-Dynamic
- QDNS(3322)-Static
- DynDNS-Dynamic
- DynDNS -Static
- NoIP
- Custom: a customisation option that allows you to configure other dynamic domain name services not listed in the list according to your specific needs.
Note: Up to 4 dynamic domain name update methods can be configured
Specify A Method To Interface
Flow control is the process of managing and limiting network flow to ensure network stability, performance, and rational allocation of resources.IG can set limits for daily/monthly flow, and after the flow exceeds the set threshold, it can be set to only Reporting/Stop Forward/Shutdown Interface to remind users or disable the flow.
The configuration of flow control is shown below:
In order to maintain the stability of the network, in the network environment composed of devices, usually use some backup connections to improve the robustness and stability of the network, where the backup connection is also known as the backup link or redundant link.
InHand SLA Fundamentals: 1. Object tracking: the reachability of a specified object is tracked.2. SLA probe: the object tracking feature can be used to issue different types of probes to an object using the InHand SLA.3. using the static routing and tracking options.SLA Configuration Steps The SLA configuration steps are as follows:
The SLA parameters are described below:
The purpose of Track is to realise the linkage function, which consists of three parts: the application module, the Track module and the monitoring module. the Track module is located between the application module and the monitoring module, and its main function is to shield the differences between the different monitoring modules and provide a uniform interface for the application module.
The Track module parameters are described below:
Track Object:
Track Action:
- positive-start/negative-stop: When the result of IPSec-related probing or monitoring is "positive" (IPSEC tunnel status is normal), the corresponding operation or process will be started; and when the result is "negative" (IPSEC tunnel status is abnormal), the corresponding operation or process will be stopped. negative" (IPSEC tunnel status abnormal), the corresponding operation or process will be stopped.
- positive-stop/negative-start: When the result of IPSec-related probing or monitoring is "positive" (IPSEC tunnel status is normal), the corresponding operation or process will be stopped; and when the result is "negative" (IPSEC tunnel status is abnormal), the corresponding operation or process will be started. negative" (IPSEC tunnel status abnormal), the corresponding operation or process will be started.
Interface backup refers to the formation of a master-backup relationship between specified interfaces of the same device. When an interface fails or the bandwidth is insufficient and the service transmission cannot be carried out normally, the flow can be quickly switched to the backup interface, which will take over the service transmission or share the network flow, thus improving the reliability of the communication of data devices.
The interface backup parameters are described below:
VPN is a "virtual" private communications network built on top of a public network (such as the Internet). By "virtual", we mean that it does not have independent physical links and infrastructure like traditional private networks, but rather, through network technology, it establishes a logically isolated and dedicated communication channel on the public network to achieve functions and security similar to those of private networks.
By means of tunneling technology, encryption technology, etc., it makes users feel like they are communicating in an independent and secure private network when using a VPN, but in reality the data is transmitted on top of the public network and is only logically dedicated and private.
IPsec is a set of open network security protocols developed by IETF, which performs authentication and encryption operations on packets at the IP layer to ensure the integrity and security of communication data. It reduces the risk of data leakage and eavesdropping, and guarantees the security of user business data transmission.
The IPsec configuration parameters are described below:
- ID: Custom IKEv1 policy identifier
- Encryption: 3DES, DES, AES128, AES192, AES256 can be selected
- 3DES: encrypts plaintext using three 64bit DES keys
- DES: encrypts a 64bit block of plaintext with a 64bit key
- AES: Encrypts plaintext using the AES algorithm with a 128bit, 192bit or 256bit key length
- Hash: optional MD5, SHA1, SHA2-256, SHA2-384, SHA2-512
- MD5: Generate a 128bit message digest by entering a message of arbitrary length.
- SHA1: Input message length less than 128bit, generate 160bit message digest.
- SHA2-256: Output 256bit
- SHA2-384: Output 384bit
- SHA2-512: Output 512bit
- Diffie-Hellman Group: the Diffie-Hellman algorithm is a public key algorithm. The communicating parties compute a shared key by exchanging some data without transmitting the key. The prerequisite for encryption is that the two parties exchanging encrypted data must have a shared key. the essence of IKE is that it never transmits the key directly over an insecure network, but rather through a series of data exchanges, it eventually computes the key shared by the two parties. Even if a third party (e.g. a hacker) intercepts all the data exchanged between the two parties used to calculate the key, it will not be enough to calculate the real key.
- Lifetime: set the survival time of the IKE SA, another SA will be negotiated in advance to replace the old one before the set survival time is exceeded.
- ID: Custom IKEv2 policy identifier
- Encryption: 3DES, DES, AES128, AES192, AES256 can be selected
- 3DES: encrypts plaintext using three 64bit DES keys
- DES: encrypts a 64bit plaintext block with a 64bit key
- AES: Encrypts plaintext using the AES algorithm with a 128bit, 192bit or 256bit key length
- integrity: optional MD5, SHA1, SHA2-256, SHA2-384, SHA2-512
- MD5: Generate a 128bit message digest by entering a message of arbitrary length.
- SHA1: Input message length less than 128bit, generate 160bit message digest.
- SHA2-256: Output 256bit
- SHA2-384: Output 384bit
- SHA2-512: Output 512bit
- Diffie-Hellman Key Exchange: the Diffie-Hellman algorithm is a public key algorithm. The communicating parties compute a shared key by exchanging some data without transmitting the key. The prerequisite for encryption is that the two parties exchanging encrypted data must have a shared key. the essence of IKE is that it never transmits the key directly over an insecure network, but rather through a series of data exchanges, it eventually computes the key shared by the two parties. Even if a third party (e.g. a hacker) intercepts all the data exchanged between the two parties used to calculate the key, it will not be enough to calculate the real key.
- Lifetime: set the survival time of the IKE SA, another SA will be negotiated in advance to replace the old one before the set survival time is exceeded.
- Name: Sets the name of the IPSec policy. This parameter cannot be modified after the IPSec policy is successfully configured.
- Encapsulation: The AH protocol of the IPSec protocol defines the application method of authentication, providing data source authentication and integrity assurance; the ESP protocol defines the application method of encryption and optional authentication, providing data reliability assurance
- AH: Provides data source authentication, data integrity checking and message anti-replay. The sender performs discrete operations on the invariant part of the IP header and the IP net load to generate a digest field. The receiving end recalculates the digest field of the message according to the received IP message and determines whether the message has been tampered with during network transmission by comparing the digest fields.
- ESP: ESP Encapsulating Security Payload Protocol: provides all the features of the AH Authentication Header Protocol, but also encrypts the IP message payload. the ESP protocol allows the content of the IP header of an IP message to be protected.
- Encryption: 3DES, DES, AES128, AES192, AES256 can be selected
- 3DES: encrypts plaintext using three 64bit DES keys
- DES: encrypts a 64bit plaintext block with a 64bit key
- AES: Encrypts plaintext using the AES algorithm with a 128bit, 192bit, or 256bit key length
- Authentication: optional MD5, SHA1, SHA2-256, SHA2-384, SHA2-512
- MD5: Generate a 128bit message digest by entering a message of any length.
- SHA1: Input message length less than 128bit, generate 160bit message digest.
- SHA2-256: Output 256bit
- SHA2-384: Output 384bit
- SHA2-512: Output 512bit
- IPsec Mode: Encapsulation mode of the IPSec protocol
- Tunnel mode: Encapsulates an IPSec header (AH or ESP) outside the original IP header and then encapsulates the new IP header in the outermost layer, with the original IP message being protected by IPSec as part of the payload. Tunnel mode is typically used between two security gateways. A message encrypted at one security gateway can only be decrypted when it reaches the other security gateway.
- Transport mode: An IPSec header (AH or ESP) is inserted between the IP header and the upper layer protocol header. In this mode, the original IP header remains unchanged, except that the IP Protocol field is changed to AH or ESP and the IP header checksum is recalculated. Transport mode is used for communication between two hosts, or a host and a Security Gateway.
- Shared Key: user enters the shared key
- Certificate: Users need to import the corresponding valid certificates in the certificate management page.
- Main Mode: Main mode separates key exchange information from authentication information. This separation protects the identity information and thus provides a higher level of security
- Aggressive Mode: Aggressive mode lacks authentication, but can meet the needs of some specific network environments. If the initiator's address is not known in advance, or if the initiator's address is always changing, and both parties want to use pre-shared key authentication to create an IKE SA, then brute force mode can be used.
- IP Address: Fill in the address of the peer to establish the IPsec interface.
- FQDN: Use string as local identity
- User FQDN: Use the full domain name as the local identity.
- IP address: Use the IP address of the interface as the identity of the local end, and conduct IKE negotiation with the other end to interact with the identity information.
- FQDN: Set the name used for the identity of the peer device in IKE negotiation, which needs to be consistent with that set on the peer device.
- User FQDN: Same as the full domain name configured on the other end
- DPD Timeout: when the receiving end triggers a DPD query and actively sends a request message to the opposite end for detection and does not receive a DPD response message from the opposite end after the timeout time has elapsed, this IPsec SA will be deleted. legal value: 10-3600 Unit: sec.
- DPD Interval: used for the detection interval of IPSec neighbour status. After the DPD function is activated, when the receiving end does not receive the IPSec encrypted message from the opposite end within the time interval of triggering the DPD, it can trigger the DPD query to actively send a request message to the opposite end to detect the existence of IKE peers. Legitimate value: 1-60, unit: sec.
- Automatically: Automatically completes IKE negotiation to establish an IPSec tunnel after applying an IPSec policy. Commonly used in client mode
- Respond Only: Only passively receives IPSEC requests and does not actively initiate connections. Commonly used in server mode
- On-demand: IKE negotiation is completed and an IPSec tunnel is established only when an IPsec-defined packet passes through the interface.
- Send cert always: Some ipsec services do not send "request certificates" requests, but they do not store the peer's certificate locally, so the peer must be configured to "always send certificates" in order to establish IPSEC.
- Send Cert if asked: local certificate is sent only when the peer sends a request
- No certificates are sent: the local will send its own certificate to the other side, regardless of whether the other side sends a request or not
- ICMP Detect Server: address of the counterpart host for IPsec probes
- ICMP Detection Local IP: source address of IPsec-protected traffic
- ICMP Detection Interval: the time interval between ICMP probe messages sent by the device
- ICMP Detection Timeout: If no ICMP response packet is received within the set ICMP detection timeout, the ICMP detection timeout is considered to have expired.
- ICMP Detection Maximum Retries: Sets the maximum number of retries if an ICMP probe fails (the IPsec service will be restarted after the maximum number is reached)
The IPSec extension parameters are described below:
- Name: Sets the name of the IPsec Profile
- IKE vVersion: Set the version number of IKE protocol, IKEv1 and IKEv2 are supported.
- IKEv1 Policy: the policy identifier defined in the IKEv1 policy list.
- IKEv2 Policy: the policy identifier defined in the IKEv2 policy list.
- IPsec Policy: Policy identifiers that have been defined in the IPsec Policies list.
- Negotiation Mode: Sets the negotiation mode of IKEv1.
- Main Mode: Main mode separates key exchange information from authentication information. This separation protects the identity information and thus provides a higher level of security
- Aggressive Mode: Aggresive mode lacks authentication, but can meet the needs of some specific network environments. If the initiator's address is not known in advance, or if the initiator's address is always changing, and both parties want to use pre-shared key authentication to create an IKE SA, then brute force mode can be used.
- Authentication methods: Two authentication methods are available, Shared key and Certificate
- Shared Key: user enters the shared key
- Certificate: Users need to import the corresponding valid certificates in the certificate management page.
- Local ID: the local identifier corresponding to the selected local identifier type
- Remote ID: the end-user identification corresponding to the selected end-user identification type
- IKE Keepalive: Sets whether to enable the peer survival detection DPD function
- DPD Timeout: When the receiving end triggers the DPD query and actively sends a request message to the opposite end for detection, and does not receive the IPSec encryption message from the opposite end even after the timeout period, this ISAKMP Profile will be deleted.
- DPD Interval: used for the detection interval of IPSec neighbour status. After the DPD function is activated, when the receiving end does not receive the IPSec encrypted message from the other end within the time interval of triggering the DPD function, it can trigger the DPD query to send a request message to the other end to detect the existence of IKE peers.
- Perfect Forward Stratification (PFS): PFS is a security feature that means that the cracking of one key does not affect the security of the other keys because there is no derivation between these keys. the IPSec phase 2 key is derived from the phase 1 key, and when the phase 1 IKE key is stolen, it is possible for an attacker to gather enough information to derive the key for the phase 2 IPSec SA. The PFS secures the phase 2 keys by performing an additional DH exchange.
- IPsec SA Lifetime: sets the lifecycle of the IPSec SA. the IPSec negotiation establishes the SA with the smaller of the lifecycle set at the local end or the lifecycle at the peer end.
- Fail times to Restart Interface: when the number of tunnel connection failures reaches the set value, restart the physical interface on which the tunnel was established; the default is 0, i.e., the interface is not restarted even after a failure, legal value: 1-12 times
- Fail times to Reboot: when the number of tunnel connection failures reaches the set value, restart the current device; the default is 0, i.e., the device is not restarted even after the failure, legal value: 1-32 times
Description:
Generic Routing Encapsulation (GRE) defines a protocol that encapsulates any other network layer protocol over any other network layer protocol.GRE can be used as a Layer 3 tunneling protocol for VPNs, providing a transparent transmission channel for VPN data. Simply put, GRE is a tunneling technology that provides a pathway on which encapsulated data messages can be transmitted, and encapsulates and decapsulates the data messages at both ends of the tunnel.
The GRE parameters are described below:
- NHS IP Address: the address of the counterpart NHS server
- Authentication Key: NHRP's authentication key
- Hold Time: legal value 1-65535
- Purge Forbid: enable/disable
Description:
In OpenVPN, if a user accesses a remote virtual address (belonging to the address series assigned to the virtual NIC, different from the real address), the operating system will send data packets (TUN mode) or data frames (TAP mode) to the virtual NIC through the routing mechanism, and the service programme receives the data and processes them accordingly, and sends them out from the extranet through SOCKET, the remote The service programme receives the data from the extranet via SOCKET and processes it accordingly, then sends it to the virtual NIC, which can be received by the application software, completing a unidirectional transmission process, and vice versa.
The OpenVPN client parameters are described below:
- Virtual IP-start address: The client's virtual IP starting address is usually assigned and set by the server side.
- Netmask: Subnet Mask of the Virtual IP
- IP address number: the number of virtual IPs that can be assigned to the server
- Source Interface: the interface used to establish OpenVPN
- Interface Type: select the form of data sent out from this interface
- tun: Mostly used for IP-based communication.
- tap: Allows full Ethernet frames to pass through Openvpn tunnels, providing support for non-ip protocols.
- Network type: net30, p2p, subnet can be selected (this item can be ignored when the interface type is tap)
- net30: select 4 ips with mask 30 from the pool, use the larger of the two middle ips as the client's virtual NIC ip; use the smaller one as the client's peer ip.
- p2p: select an ip from the pool as the client's virtual NIC ip, and use your actual virtual NIC ip as the client's peer ip.
- subnet: select an ip from the pool as the client's virtual NIC ip, and use its own subnet mask as the client's subnet mask.
- Bridge Interface: used to connect multiple virtual machines or network devices so that they can communicate on the same network (this can be ignored when the interface type is configured in tun mode)
- Cipher: The encryption protocol used by OpenVPN to transmit data, must be consistent with the server
- HMAC: The checksum method used by OpenVPN to transmit data, data transmission fails if the checksum is not passed, and must be consistent with the server.
- Compression LZO: The form of compression used for OpenVPN data transmission.
- Redirect-Gateway: Directs the Client's default gateway to OpenVPN so that all Client traffic is forwarded through the OpenVPN interface.
- Remote Float: allows the remote end to change its IP address/port
- Link Detection Interval: The time to send connection detection messages after OpenVPN is successfully established.
- Link Detection Timeout Time: After OpenVPN connection detection fails, L2TP re-establishes the connection when the maximum number of failures is reached.
- MTU: Maximum Transmission Unit of the OpenVPN interface, in bytes
- Enable Debug: Tap Enable
- Expert Configuration: Configuring OpenVPN Extended Parameters
- Import Configuration: Select the OpenVPN configuration file to be imported.
The OpenVPN server parameters are described below:
- Authentication Type: Select the appropriate authentication type
- Local IP Address: virtual IP address of the OpenVPN server interface
- Remote IP Address: virtual IP address of the OpenVPN client
- Description: Description information of the OpenVPN tunnel
- Show Advanced Options: tap Enable
- Source Interface: Interface used to establish OpenVPN
- Interface Type: Select the form of data sent out of this interface.
- tun: Mostly used for IP-based communication.
- tap: Allows full Ethernet frames to pass through Openvpn tunnels, providing support for non-ip protocols.
- Network Type: net30, p2p, subnet can be selected (this item can be ignored when the interface type is tap).
- Bridge Interface: used to connect multiple virtual machines or network devices so that they can communicate on the same network (this can be ignored when the interface type is configured in tun mode)
- Protocol Type: consistent with the client
- Port: the port number used by the OpenVPN service
- Cipher: The encryption protocol used by OpenVPN to transmit data, which must be consistent with the client's
- HMAC: The checksum method used by OpenVPN to transmit data; data transmission fails if the checksum is not passed. Must be consistent with the client
- Compression lZO: The form of compression used for OpenVPN data transmission. Consistent with the client
- Link Detection Interval: The time to send connection detection messages after OpenVPN is successfully established.
- Link Detection Timeout Time: After OpenVPN connection detection fails, L2TP re-establishes the connection when the maximum number of failures is reached.
- MTU: Maximum Transmission Unit of the OpenVPN interface, in bytes
- TCPMSS: Maximum data length that can be transmitted in a single TCP message
- Fragment: When the length of a message in the network exceeds the MTU (Maximum Transmission Unit) in the path, it may be necessary to fragment the message into smaller pieces for transmission.
- Enable Debug: Tap Enable
- Expert Configuration: Configuring OpenVPN Extended Parameters
Scep (Simple Certificate Enrollment Protocol) is a communication protocol for device certificate management developed by cisco and Verisign. It utilises a combination of existing PKCS#7 and PKCS#10 protocol technologies and enjoys extensive support for client and CA implementations.
Certificate Management:
The certificate management parameters are described below:
- CRL URL: CRL is Certificate Revocation List, set the URL of the CRL issuing point.
- OCSP URL: Configure the URL of the OCSP server, which is usually the same as the URL of the certificate server.
Note: When using certificates, ensure that the device time is synchronised with the actual time
ROOT CA:
Import the pre-registered ROOT CA certificate
Set the parameters of the IG serial port according to the serial port parameters of the terminal device connected to the IG to achieve normal communication between the IG and the terminal device.
The serial port setting parameters are described below:
Attention:
The DTU 1 parameters are described below:
- Transparent transport and TCP-Server: if a transparent transport device is selected as client, a TCP server device is selected as server.
- RFC2217: No need to set up the serial port configuration after selecting this mode.
- IEC101 to 104: for the power industry, similar to TCP
- Long-Lived: TCP client and TCP server establish a connection and then keep the TCP connection.
- Short-Lived: After the TCP client and TCP server establish a connection, when there is no data transmission during the idle time, it will automatically disconnect from the server TCP connection.
- Parallel: simultaneous de-connection to the centre of the destination IP address list
- Polling: connect to the centre at the front of the list first, and if it is connected, then no more connections to the back; if it is not connected, then it is connected in descending order until it is connected to a centre.
- Heartbeat Interval: This is only required if ReportID is enabled Legal value: 1-65535, unit: sec.
- Heartbeat Packet Content: This is required to enable ReportID.
- Server Address: Customise the IP address of the server to which the device will connect.
- Server Port: customise the server port to which the device will connect
Description: Up to 10 destination IP addresses can be set.
Same as DTU1.