IPsec Commands

remote-external-ip-address

When NAT Traversal (NAT_T) is enabled, the remote VPN’s public external IPv4 or IPv6 address or FQDN. If you want to accept a VPN connection from any host/network, you can enter %any in this field.

remote-host-nextwork

The IPv4 or IPv6 address of a specific host or the network address that the IOLAN will provide a VPN connection to. If the IPsec tunnel is listening for connections (Boot Action set to Add), and the field value is left at 0.0.0.0, any VPN peer with a private remote network/host that conforms to RFC 1918 (10.0.0.0/8, 172.16.0.0./12, 192.168.0.0/16) will be allowed to use this tunnel if it successfully authenticates.

remote-ip-address

The IPv4 or IPv6 address or FQDN of the remote VPN peer. If you want to accept a VPN connection from any VPN peer, you can enter %any in this field.

remote-next-hop

The IPv4 or IPv6 address of the router/gateway that will forward data packets to the IOLAN (if required). The router/gateway must reside on the same subnet at the remote VPN.

remote-validation-criteria

Any values that are entered in the remote validation criteria must match the remote X.509 certificate for a succsessful connection; any fields left blank will not be validated against the remote X.509 certificate. Note that all validation criteria must be configured to match the X.509 certificate. An asterick (*) is valid as a wildcard.

country

A two character country code; for example, US. This field is case sensitive in order to successfully match the information in the remote X.509 certificate. An asterisk (*) works as a wildcard.

state-province

Up to a 128 character entry for the state/province; for example, IL. This field is case sensitive in order to successfully match the information in the remote X.509 certificate. An asterisk (*) works as a wildcard.

locality

Up to a 128 character entry for the location; for example, a city. This field is case sensitive in order to successfully match the information in the remote X.509 certificate. An asterisk (*) works as a wildcard.

organisation

Up to a 64 character entry for the organisation; for example, Accounting. This field is case sensitive in order to successfully match the information in the remote X.509 certificate. An asterisk (*) works as a wildcard.

organisation-unit

Up to a 64 character entry for the unit in the organisation; for example, Payroll. This field is case sensitive in order to successfully match the information in the remote X.509 certificate. An asterisk (*) works as a wildcard.

common-name

Up to a 64 character entry for common name; for example, the host name or fully qualified domain name. This field is case sensitive in order to successfully match the information in the remote X.509 certificate. An asterisk (*) works as a wildcard.

114

IOLAN SDS/SCS/STS CLI Reference Guide, Version 3.6

Page 118
Image 118
Perle Systems CSS manual Remote-external-ip-address, Remote-host-nextwork, Remote-ip-address, Remote-next-hop

CSS specifications

Perle Systems, a well-established provider of networking and IoT solutions, offers the innovative Perle CSS (ClearSky Services) platform, designed to facilitate efficient and secure device management. This powerful solution aims to address the challenges of managing a diverse range of devices connected to the Internet, particularly in enterprise, industrial, and M2M (Machine-to-Machine) environments.

One of the main features of the Perle CSS is its robust device management capabilities. Administrators can remotely monitor, configure, and control devices in real-time. This means that troubleshooting can be conducted without the need for physical access, significantly reducing operational downtime. Additionally, the platform supports bulk provisioning, allowing organizations to onboard multiple devices simultaneously, which streamlines the deployment process.

Another notable feature is its security architecture. Perle Systems has integrated advanced security protocols to ensure the integrity and confidentiality of data transmitted between devices. The use of virtual private networks (VPNs), secure socket layer (SSL) encryption, and secure shell (SSH) protocols ensures that sensitive information remains protected from unauthorized access while in transit.

The Perle CSS also stands out for its compatibility with various communication protocols, including MQTT, RESTful APIs, and others. This interoperability allows organizations to integrate the CSS platform seamlessly with their existing systems, facilitating efficient data exchange and interoperability between different devices and applications.

Moreover, Perle CSS adopts a cloud-based architecture, which provides users with the flexibility to access device information from any location. This cloud integration enhances scalability, allowing businesses to expand their network capabilities without the need for extensive infrastructure investments.

The platform's user-friendly interface simplifies navigation, allowing users to manage devices effectively without requiring extensive technical expertise. With customizable dashboards and real-time analytics, administrators can gain valuable insights into device performance, network status, and usage patterns.

In summary, Perle Systems' CSS offers a comprehensive solution for managing connected devices in a secure and efficient manner. Its key features, including robust device management, advanced security, protocol compatibility, and a cloud-based architecture make it an ideal choice for enterprises looking to enhance their IoT capabilities and streamline operations in an increasingly connected world.