ReliaGATE/DynaGATE 10-14

The ReliaGATE 10-14 is a Multi-service IoT Gateway that has been designed to deliver LTE and 2G/3G connectivity to industrial and lightly rugged applications.

The DynaGATE 10-14 is a Road Vehicle certified, IoT Gateway for Public Transport and Road Vehicles that enables a fast transition to ITxPT both in existing and new deployments.

GPS Configuration

Ordering codes from REGATE-10-14-35 to REGATE-10-14-37 come equipped with an internal GPS receiver integrated within the modem. The default configuration for the ESF PositionService works seamlessly upon installation. To ensure proper operation, please enable the modem's GPS in the network configuration section.

Ethernet Configuration

The default configuration of the Ethernet interfaces for a ReliaGATE 10-14 is the following:

Wireless Configuration

The ReliaGATE 10-14 has a WiFi interface, named wlan0.
By default, the interface is disabled.

Firewall Configuration

Following the ESF firewall configuration for the ReliaGATE 10-14:

Modem Support

The REGATE variants from REGATE-10-14-35 to REGATE-10-14-37 come equipped with an internal modem, which is supported by ESF right out of the box.

Tamper Detection

Reliagate and DynaGATE 10-14 feature tamper detection capabilities, ensuring the device can generate an event if the external enclosure is removed or if the service panel is opened. For additional information, please consult the device manual.

ESF offers a TamperDetectionService implementation that maintains a persistent tamper status based on EL tamper events (refer to Tamper Detection for further details). Once a tamper event is detected by EL, the device is marked as tampered by ESF until the user takes action to clear the tamper status.

Furthermore, the 10-14 TamperDetectionService is seamlessly integrated with the DiagnosticsService, which will publish the following tamper-related notifications:

• An alert for each tamper event.
• A new last_tamper_event_timestamp indicating the timestamp of the last tamper event, as recorded by the device RTC (see the device manual for more information).

🚧

Warning

If the service panel needs to be open for maintenance, the operator should reset the tamper status in the Security -> Tamper Detection section of the Web Console. This action requires the kura.admin permission.

AIDE Tamper Detection

On Everyware Linux 40.x, after a reboot the AIDE Integrity Check can report that the device has been tampered. This is caused by some files written by the operating system. To avoid that, add these exceptions in the AIDE Tamper Detection configuration:

!/etc/NetworkManager/system-connections/*
!/etc/rauc/central-status.raucs

Journald persistence

EL 27.0.0 uses in RAM journal
EL 27.1.0 uses persisted journal

Clock Service

The Chrony advanced option in the Clock Service is only supported in EL 27.1.0.

Docker integration

Installing ESF on EL 27.1 will disable Docker by default, in order to use ESF Docker integration, Docker must be enabled manually with the following command, and then the gateway must be restarted:

systemctl enable docker.service docker.socket

Serial Configuration

ESF provides a Serial Port Configurator configurable component that allows to configure the desired modes for the COM0 (/dev/ttymxc0) and COM1 (/dev/ttymxc1 on ReliaGATE 10-14 and /dev/ttymxc3 for DynaGATE 10-14) gateway serial ports.

As reported in Gateway Manual, the serial ports share a multi-function line driver which allows for numerous combinations of RS-232, RS-422 and RS-485 between the two serial ports; however, some combinations are not supported.

In ESF 7.5.x and before ESF Serial Port Configurator allowed to configure only the mode for COM1 port through the com1.mode property, setting COM0 in RS232 mode.

ESF 7.6.0+ provides a new Serial Port Configurator that allows to configure both serial ports, in this version the com1.mode property is replaced by a new com.modes property with the following values, that cover all modes supported by the line driver:

• COM0=HiZ COM1=HiZ
• COM0=RS232 COM1=RS232
• COM0=RS232 COM1=RS422
• COM0=RS232 COM1=RS485
• COM0=RS422 COM1=RS422
• COM0=RS485 COM1=RS485
• COM0=Loop COM1=Loop

The component also allows to configure the following parameters for each serial port:

• com0.rts.after.send and com1.rts.after.send: Set SER_RS485_RTS_AFTER_SEND bit [0,1].
• com0.rts.on.send and com1.rts.on.send: Set SER_RS485_RTS_ON_SEND bit [0,1].
• com0.delay.after and com1.delay.after: Insert RS485 wait after send in ms [0..100].
• com0.delay.before and com1.delay.before: Insert RS485 wait before send in ms [0..100].
• com0.termination and com1.termination: Insert termination resistor. Only applies to RS485 or RS422 modes.

📘

Note

Serial port configuration might fail if the configured serial port is in use. In this case the configuration change will be applied at next device reboot.

Upgrade and snapshot compatibility

If ESF is upgraded via RPM from 7.5.x and previous versions, the com.modes property will be automatically generated basing on the value of the com1.mode property as described in the following table, preserving the existing serial port mode configuration.

🚧

Warning

Please note that the com1.mode property is no longer supported by ESF 7.6.0+ Serial Port Configurator. Uploading a configuration snapshot or submitting a configuration update request that specifies com1.mode instead of com.modes will not change the current serial port modes. Existing snapshots and configuration update requests that reference com1.mode must be manually updated as described in the table above. The only case when the transition from com1.mode to com.modes is performed automatically by ESF is durning RPM upgrade.

Network Threat Manager

The flooding protection and fail2ban features are enabled by default.