AT Modem Emulator - implementation of emulation telephone modem behavior
The AT Modem Emulator user module emulates a telephone modem’s behavior. The modem can receive a dial-up request via the serial port and convert it to a TCP/IP connection. Any device connected to the router’s serial interface sees the router as a HAYES-compatible modem.
DNP3 Outstation - implementation of DNP3 protocol
The DNP3 Outstation module allows the router to use DNP3 protocol (Distributed Network Protocol v3), which is intended for reading data from the router. The primary purpose of this protocol is the mutual communication between devices in a network.
Easy VPN Client - provides secure (encrypted) LAN connections
The Easy VPN Client module provides secure (encrypted) LAN connections for both our router products and Cisco routers.
pppGateway - allows the router to establish connection via PPP
This module allows the router to establish connection via PPP (a data link protocol commonly used in establishing a direct connection between two networking nodes) between the router and any device connected to the router through a serial port. This provides Internet access for older devices which do not have this ability, but do have serial connectivity.
Protocol ALPHA-MODBUS - communications protocol with Mitsubishi ALPHA
ALPHA-MODBUS protocol is binary transparent serial communications protocol for the Mitsubishi ALPHA controllers. The Mitsubishi ALPHA controllers use a proprietary protocol, while network connectivity to/from the automation control room uses MODBUS-TCP protocol. With this module, the router performs a real-time two-way conversion transparent scroll via the data.
Protocol BGP - implementation of a routing protocol between autonomous systems
These autonomous systems are basically collections of IP networks and routers under the control of one or more network operators that present a common, clearly defined routing policy (only one of the interior gateway protocols). The routing information is exchanged between these autonomous systems via a border gateway. The BGP user module is based on a software program called Quagga. This software provides TCP/IP based routing services with routing protocols that support RIP, OSPF and BGP.
- User Module – Protocol BGP (497 kB, TGZ)
- BGP Application note 20141007 (1 671 kB, PDF)
Protocol IEC 101-104 - bi-directional conversion between IEC101 and IEC104 protocols
This user module enables bi-directional conversion between IEC101 and IEC104 protocols specified by the IEC 60870-5 standard. The IEC101 serial communication protocol is converted to the IEC104 TCP/IP communication protocol and vice versa. Some parameters are configurable.
Protocol IS-IS - allows your router to use the IS-IS protocol
This module allows your router to use the IS-IS (Intermediate System – Intermediate System) routing protocol, which is designed for the exchange of routing information between routers. This protocol belongs to a family of IGP (Interior Gateway Protocol) protocols, which are designed to distribute routing information within a single autonomous system (AS). It is a link-state protocol, which means that information about the topology is exchanged between the nearest neighbors in a “flood way“ (flooding).
Protocol MODBUS-RTUMAP - periodically read stored values from the buffer
With this module, you can periodically read stored values from the buffer. This protocol is used for meter reading applications. Each meter is assigned a certain number of registers (or coils). The ranges are sequential, so the RTUMAP module reads the data from a total number of assigned registers (or coils) from the specified start address.
Protocol MODBUS-TCP2RTU - converts MODBUS TCP protocol to MODBUS RTU protocol
This user module converts the MODBUS TCP protocol to the MODBUS RTU protocol, which is typically run through the serial port. The router can use either PORT1 or PORT2 as a serial expansion port for RS-232 or RS-422/485.
Protocol NHRP - implement a dynamic Multipoint VPN
This user module enables you to implement a dynamic Multipoint VPN (DMVPN). The concept behind DMVPN is to increase the security of your network by allowing remote routers (called spokes) to exchange data without needing to pass through the headquarters virtual private network (VPN) router (hub). Instead, each spoke is permanently connected to the headquarters using a VPN tunnel. If two spokes need to communicate with each other, a temporary VPN tunnel is created between them while the headquarters retains the role of an NHRP server). The temporary tunnels are canceled after the spokes finish communicating. The DMVPN allows the port addresses to be assigned dynamically between the routers for the VPN tunnels. This is not possible when using “classical” site-to-site VPN. The DMVPN essentially creates a topology that could be called a (full) mesh VPN. This means that each remote router (spoke) can connect directly with all other remote routers, no matter where they are located.
Protocol OSPF - OSPF routing protocol
This protocol is designed for exchanging routing information within an autonomous system. The OSPF is a link state protocol, which means that routers maintain a map of the network (link state database) that is updated after any change to the network topology. To compute the shortest (least cost) path between the router and the rest of the network, the Dijkstra’s Algorighm is used. Then this data is used to fill in the routing table. The OSPF user module is based on a software program called Quagga, a routing package that provides TCP/IP based routing services with routing protocols to support RIP, OSPF, and BGP.
Protocol PIM-SM - Protocol Independent Multicast
- The module offers the PIM-SM (Protocol Independent Multicast – Sparse Mode) protocol. This commonly used multicast routing protocol is designed with the assumption that the recipients for a particular multicast routing group will be sparsely distributed throughout the network. In order to receive multicast data, routers must explicitly tell their upstream neighbors about their interest in the particular groups or sources. By default, PIM-SM uses shared trees, which are multicast distribution trees rooted in a specific node called the Rendezvous Point, RP. The router designated as the Rendezvous Point is used by all sources sending to the multicast group.
Protocol SuiteHT - implementation of SuiteHt protocol
This module allows the router to send queries from the AMR system to a meter through an IP network using the router as a gateway. The AMR system sends commands that will not be encoded or encapsulated, but will be sent “in clear” over a TCP connection. The router, upon receiving this command, will send it to the meter, following established timing and handshake processes. Once the router has received the response message from the meter, it sends it back to the AMR system and waits for another command. If AMR has no more commands to send, it will close the TCP session and the router will end the communication with the meter.
RIP Protocol - RIP routing protocol
The RIP routing protocol is a standard for the exchange of routing information among routers that will respond to changes in the network topology. RIP is a distrance-vector protocol, which means that routers transmit updated routing tables. To compute the shortest (least cost) path between the router and the balance of the network, the Bellman-Ford algorithm is used. The deciding factor is the number of routers through which data must pass between source and destination. The maximum number allowed for the RIP protocol is 15. This maximum, however, also limits the size of networks that the RIP can support. The RIP user module is based on the Quagga software. Quagga is a software package that provides the TCP/IP based routing services with protocols that support RIP, OSPF and BGP.
Transparent Mode - implements Transparent Mode
With this user module, the router becomes “invisible” for remote devices. It is available only for a device which is located behind the router. The default IP address of the router is 192.168.1.1 and configuration can only be performed by a logged in user (default name and password isroot). All communication with the device located behind this router runs directly. For example, if a user enters the IP address of the SIM card in the router, it will communicate with the interface of the device behind this router.
Stunnel - allows the router to create an encrypted network tunnel
Stunnel is primarily designed for adding SSL encryption to communication channels that cannot natively support it. This results in a significant increase in communication security within these channels. The data input is either encrypted on input; then decrypted on output, or vice versa. It is often used to improve security on commonly used servers, running inetd daemon (linux daemon which listens to communication on the network interface). These include POP2, POP3 or IMAP. With this module, it is also possible to add SSL encryption to NNTP, SMTP, HTTP services which are run by standalone daemons or to PPP tunnels.
Serial2TCP - Connects serial port devices with the TCP Server or Servers
With this module, serial communication is two-way: serial to TCP and TCP to serial. Often used in data collection and measurement applications including metering and remote asset management, the router can receive data and send commands or control data to any connected meters or serial port devices remotely via TCP.
SCEP Client - implements Cisco System’s Simple Certificate Enrollment Protocol
SCEP (Cisco System’s Simple Certificate Enrollment Protocol) is a PKI communication protocol which leverages existing technology by using PKCS#7 and PKCS#10. SCEP is the evolution of the enrollment protocol developed by Verisign, Inc. for Cisco Systems, Inc. It now enjoys wide support in both client and CA implementations.