Titan – NA50: Using MTX-Titan-Router as a datalogger of serial frames for proprietary protocols.
Scenario Details Titan routers have all the typical features of a 2G/3G/4G router but also have a series of additional features that make it one of the routers with the most features on the market. One of the additional features is the ability to store data from a serial device connected to an RS485 or […]
Titan – AN49: LoRa server with slave LoRa gateway
Scenario Details MTX-StarLora is featured as LoRa-4G gateway packet forwarder using external LoRa Server. Check our app note 39. MTX-StarLora is also featured with ChirpStack integrated Lora Server inside and we’ll add more remote gateways and nodes Check our app note 48. This is our implementation block of our TITAN-Router with LoraServer. In a regular […]
Titan – AN48: Internal LoRa server
Scenario Details MTX-StarLora is featured as LoRa-4G gateway using external LoRa Server. Check our app note 39. MTX-StarLora is also featured with integrated Lora Server inside. That means that MTX-StarLora does not depend on external LoRa Servers, like TTN & among others, all the control over other gateways and external Lora devices is done internally. […]
Titan – AN47: IPSEC – Client-Server IKEv1 – Authentication with PSK
Scenario Details You need to implement a secure network between 3 PLCs, so that they can communicate with each other. For this, an IPSec tunnel will be created, where a Titan router connected to the PLC3 will act as the IPSec Master. This Titan router will have a SIM card with a fixed IP address […]
Titan – AN46: IPSEC – Server IKEv1 – Authentication with certificate
Scenario Details From two locations it is intended to remotely access the configuration of a Titan 4G router and the configuration of a PLC that is connected to the Ethernet port of said Titan router. All this through a secure IPSec type connection. It is intended to use digital certificate authentication. Description of the Example […]
Titan – AN45: IPSEC – Server IKEv1 – PSK Authentication
Scenario Details From a PC it is intended to remotely access the configuration of a Titan 4G router and the configuration of a PLC that is connected to the Ethernet port of said Titan router. All this through a secure IPSec type connection. It is intended to use IKEv1 and PSK authentication. Description of the […]
Titan – AN44: IPSEC – Client-Server IKEv2 – Authentication with certificate
Scenario Details We need to implement a secure network between 3 PLCs, so that they can communicate with each other. For this, an IPSec tunnel will be created, where a Titan router connected to the PLC3 will act as the IPSec Master. This Titan router will have a SIM card with a fixed IP address […]
Titan – AN43: IPSEC – Server IKEv2 – Authentication with certificate
Scenario Details From two locations it is intended to remotely access the configuration of a Titan 4G router and the configuration of a PLC that is connected to the Ethernet port of said Titan router. All this through a secure IPSec type connection. It is intended to use digital certificate authentication. Description of the Example […]
Titan – AN42: IPSEC – Server IKEv2 – PSK Authentication
Scenario Details From a PC it is intended to remotely access the configuration of a Titan 4G router and the configuration of a PLC that is connected to the Ethernet port of said Titan router. All this through a secure IPSec type connection. It is intended to use IKEv2 and PSK authentication. Description of the […]
Titan – AN41: IPSEC – Server IKEv2 – EAP Authentication
Scenario Details From a PC it is intended to remotely access the configuration of a Titan 4G router and the configuration of a PLC that is connected to the Ethernet port of said Titan router. All this through a secure IPSec type connection. It is intended to use IKEv2 and EAP authentication. Description of the […]
Enter the “ethernet” or “modem” connection type:
For an ethernet configuration, make sure the IP parameters are compatible with server access according to the concentrator local network configuration. For an ethernet connection, the configuration must be compatible with the concentrator’s local network topology so that it can access the servers. This configuration is done from the “Networks” configuration page (see section 3.2.2.3: “Networks”).
For a modem connection, the modem configuration must be correct before a connection can be set up. This configuration is done from the “Modem” configuration page (see section 3.2.2.4: “Modem”).
The parameters for the servers to be configured are at least the following:
Therefore the following fields need to be configured: “Interface”, “Type”, “Server type”, “Address”, “Port”, “Login” and “Password”.
The other fields can be left at the default values subject to the directories having been properly created beforehand. See section 3.1.2: “Configuration files” for more details.
Wait. The concentrator will reboot using its factory configuration.
