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.

116

IOLAN SDS/SCS/STS/MDC CLI Reference Guide, Version 3.7

Page 116
Image 116
Perle Systems SDS, MDC manual Remote-external-ip-address, Remote-host-nextwork, Remote-ip-address, Remote-next-hop

SDS, MDC specifications

Perle Systems is a leading provider of connectivity solutions, renowned for its robustness and reliability in networking hardware. Among its expansive product offerings, the MDC (Multiport Device Converter) and SDS (Serial Device Server) stand out as pivotal solutions for industries requiring seamless data communication and device management.

The Perle MDC serves as a powerful multi-port device converter, providing the ability to connect multiple serial devices to a computer network without needing a separate connection for each device. This is particularly useful in environments with limited computing resources or high device density, such as railways, manufacturing plants, or remote field operations. It is designed to convert serial communication, which is commonly used in legacy devices, into Ethernet/IP or TCP/IP protocols, ensuring that older devices can integrate into modern networks.

Main features of the MDC include its robust design for industrial environments, support for a variety of serial protocols, and multiple device connections. It supports data rates of up to 115200 bps and provides easy monitoring and configuration via a web-based interface. Additionally, the MDC incorporates advanced security features including SSL and SSH encryption, ensuring data integrity and protection against unauthorized access.

On the other hand, the Perle SDS model exemplifies advanced serial device hosting capabilities, allowing users to connect Ethernet networks to serial devices. It acts as a bridge, enabling remote devices to be configured and managed over IP networks. The SDS series is known for its versatility, supporting a range of serial communication protocols, including RS-232, RS-422, and RS-485, making it suitable for various applications such as point-of-sale systems, industrial automation, and remote monitoring.

The SDS boasts several characteristics that enhance its functionality, such as automatic device discovery, real-time monitoring, and local or cloud-based management options. Its feature set also includes traffic management capabilities, allowing the optimization of device communication by controlling the flow of data, which is critical for applications requiring high reliability and low latency.

Both the MDC and SDS benefit from a strong emphasis on ease of deployment and management. They support a range of network topologies, facilitating seamless integration into existing infrastructures. Furthermore, these devices are backed by Perle Systems' reputation for customer support and a commitment to ongoing innovation, ensuring that organizations can rely on these solutions for future growth and technological advancement.