Page 8
Development Canada ....................308 10.10. Compliance ANATEL Brasil ..................315 10.11. Warranty ........................315 10.12. RipEX2 Availability and service life time ..............316 10.13. RipEX2 maintenance ....................316 A. Security Hardening Procedure ....................318 A.1. Password and accounting .................... 318 A.2.
Page 10
). The ETH/USB contains a built-in DHCP server, so if you have a DHCP client in your PC as most users, you do not need to set anything up. The default IP address of RipEX2 unit, for access over the ETH/USB adapter, is 10.9.8.7.
Page 11
Section 2.2.9, “HW button”. 1.1. Bench testing Before installing a RipEX2 network in the field, a bench-test should be performed in the lab. The RipEX2 Demo case is great for this as it contains everything necessary: 3× RipEX2 unit, Power supply, dummy load antennas, etc.
Page 13
2. Product RipEX2 is a radio modem platform renowned for overall data throughput in any real-time environment. RipEX2 radio modems are native IP devices, Software Defined with Linux OS that have been designed with attention to detail, performance and quality.
Page 19
This rugged connector connects to a power supply and it contains control signals. A Plug with screw- terminals and retaining screws for power and control connector is supplied with each RipEX2. It is Tyco 7 pin terminal block plug, part No. 1776192-7, contact pitch 3.81 mm. The connector is designed for electric wires with a cross section of 0.5 to 1.5 mm...
Page 21
The SFP modules listed in Accessories are thoroughly tested by RACOM and are guaranteed to function with RipEX2 units. It is possible to use any other SFP module, but RACOM cannot guarantee they will be completely compatible with RipEX2 units.
Page 23
RipEX2 unit should be DTE (Data Terminal Equipment) and a straight-through cable should be used. If a DCE device is connected to the serial port of RipEX2, a null modem adapter or cross cable has to be used.
Page 24
If the RipEX2 unit is installed in the RipEX2-HS (Hot Standby chassis), the DI/DO interface is dedicated for the Hot Standby operation. Note “Extension module ‘C’ (as 3rd and 4th COM port) is not supported with RipEX2 var. F and O.“ 2.2.6. USB RipEX2 uses USB 3.0, Host A interface. USB interface is wired as standard: Tab.
Page 25
RipEX2 can be equipped with an internal G – Extension GPS (GNSS) module (see details). The GPS module is used for time synchronization of the NTP server inside RipEX2. In this case the EXT connector serves for connecting the GPS antenna: •...
Page 26
• Pull below 1.1 VDC to activate (1.1 VDC / 1.9 VDC threshold hysteresis) • Max. 30 VDC If the RipEX2 unit is installed in the RipEX2-HS (Hot Standby chassis), the DI/DO interface is dedicated for the Hot Standby operation.
Page 28
For the RipEX2 version with narrowband LTE (cellular modules 'M' and 'O'), the EXT connector is used to connect the antenna. 2.3.2. SIM cards Two SIM card holders for Micro SIM (3FF) are available under the screwed cover on the RipEX2 bottom side. Warning Disconnect RipEX2 unit from a power supply before opening the cover and manipulating with SIM cards.
Page 32
COM2 – enables COM2 interface, RipEX2e, RipEX2 variant ‘F’ and ‘O’ only; Part No.: RipEX2- SW-COM2 Ex - authorization for use RipEX2 in hazardous location II 3G Ex ic IIA T4 Gc. Part No.: RipEX2- Ex (Note: Ex keys are available only for units produced after 1st of January 2022) Region –...
Page 33
In the case of export from the country where the units were delivered by RACOM, the exporter must inform RACOM of the new country of delivery. X was under production until XII/2022 ** E, P, A cellular modules were under production until XI/2021 *** C, D were under production until VIII/2023 https://webservice-new.racom.eu/main/eshop.list?t=10...
Page 34
8. Ingress Protection IP52 https://www.racom.eu/eng/products/radio-modem-ripex.html#accessories_mounting 9. Dummy load antenna Dummy load antenna for RipEX2 is used to test the configuration on a desk. It is unsuitable for higher output – use transmitting output of 1.0 W only. https://www.racom.eu/eng/products/radio-modem-ripex.html#accessories https://www.racom.eu/eng/products/radio-modem-ripex.html#accessories_mounting https://www.racom.eu/eng/products/radio-modem-ripex.html#accessories_mounting...
Page 36
(recommended) or widthwise; in both cases with the RipEX2 lying flat. The choice is made by mounting the clips, one M4 screw per clip. RipEX2 is delivered with two clips, two screws and four threaded holes. Use solely the M4×5 mm screws that are supplied.
Page 39
. 4.3.4. IP52 mounting RipEX2 unit provides IP41 level of environmental protection. It is possible to reach higher level of pro- tection IP52 (Limited dust ingress protection and protection from water spray < 15 degrees from vertical).
Page 41
Use 50 Ω impedance cables only. The shorter the feed line, the better. If RipEX2 is installed close to antenna, the data cable can be re- placed by an Ethernet cable for other protocols utilizing the serial port, see Section 7.1.4, “Terminal servers”.
Page 42
Installation 4.9. Power supply We do not recommend switching on power supply of the RipEX2 unit before connecting the antenna and other devices. Connecting the RTU and other devices to RipEX2 while powered increases the likelihood of damage due to the discharge of difference in electric potentials.
Page 43
Ethernet ports The whole radio network build from RipEX2 radio modems behaves as a standard Ethernet bridge. An Ethernet bridge ("Network interface" in RipEX2) automatically learns which devices (MAC addresses) are located in the local LAN and which devices are accessible over the radio channel.
Page 44
The COM port needs to be Enabled and a Protocol needs to be selected to transfer any data. "Trans- parent" type of COM protocol is dedicated for Bridge mode purposes. This protocol transfers data between the COM port and the RipEX2 network transparently. Any other Protocol can be selected when needed.
Page 45
RipEX2 C and RipEX2 A send the received packet to their COM ports. Packet is addressed to RTU C, so only RTU C responds. RipEX2 A is set as a repeater, so it retransmits the packet on Radio channel. Packet is received by all RipEX2 units. Step 4 RipEX2 B sends repeated packet to its COM.
Page 46
You can see an example of IP addresses of the SCADA equipment and RipEX2 ETH interfaces in the picture below. In Bridge mode, the IP address of the ETH interface of RipEX2 is not relevant for user data communic- ation. However it is strongly recommended to assign a unique IP address to each RipEX2 Network in- terface, since it allows for easy local as well as remote service access.
Page 47
○ Install a duplexer (exact type for a given channel link). A recommended duplex distance is 75 dB and more. ○ Due to high duty cycle, proper cooling is required. We recommend to use RipEX2-RS For more details see RipEX2 PtP link tutorial video 5.2.
Page 49
As already mentioned, RipEX2 works as a standard IP router with multiple independent interfaces: Radio and Ethernets. Each interface has its own MAC address, IP address and mask. When Base driven protocol is used, Radio IP addresses for all RipEX2 units must share the same IP subnet.
Page 51
CSMA and TDMA; the Radio channel is deemed to be free when there is no noise, no interfering signals and no frames being transmitted by other RipEX2 stations. In this situation, a random selection of time slots follows and a frame is then transmitted on the Radio channel.
Page 52
RipEX2 1 receives this packet, checks data integrity and transmits the acknowledgement. At the same time packet is sent to RTU1 through COM. RipEX2 3 receives this packet too. It doesn’t react, because this packet is directed to RipEX2 1 only. Step 3 RipEX2 2 waits untill previous transaction on Radio channel is finished (anti-collision mechanism).
Page 53
Ethernet port. This helps to keep the routing tables clear and simple. Note Even if the IP addresses of all RipEX2 units in a radio channel share a single IP network, they may not be communicating directly as in a common IP network. Only the RipEX2 units that are within the radio range of each other can communicate directly.
Page 54
• Based on this record, all packets with addresses in the range from 192.168.2.1 to 192.168.2.254 are routed to 10.10.10.1 • Because RipEX2 50’s radio IP is 10.10.10.50/24, the router can tell that the IP 10.10.10.1 belongs to the radio channel and sends the packet to that address over the radio channel •...
Page 55
5.3.1. Detailed Description Generally, a Terminal server (also referred to as Serial server) enables connection of devices with a serial interface to a RipEX2 over the local area network (LAN). It is a virtual substitute for the devices used as serial-to-TCP(UDP) converters.
Page 56
Terminal server in RipEX2. User data are extracted from the TCP messages and processed as if it came from a COM port. When the data reaches the destination RipEX2, it can be transferred to the RTU either via the serial interface or via TCP (UDP), using the Terminal server again.
Page 57
(via LAN) or a high-speed WAN (e.g. Internet). The RipEX2 which you are logged-in to in this way is called Local. Then you can manage any remote RipEX2 in the network over-the-air in a throughput-saving way: all the static data (e.g. Web page graphic objects) is downloaded from the Local RipEX2 and only information specific to the remote unit is transferred over the Radio channel.
Page 58
Web interface Login page The login page informs you about the Unit name and IP address of the RipEX2 unit you are trying to log in. The login page allows to view and copy the password. The login page allows changing of the language of the whole web interface (English language is default).
Page 59
6.2. Changes to commit RipEX2 is capable of remembering changes, which were done in its configuration and collecting them in a Changes to commit "basket". All changes of configuration parameters are highlighted by different color.
Page 61
Web interface 6.3. Notifications With RipEX2 new way of showing important system events to the user is introduced. It is called Notific- ation Center and is used consistently throughout the interface. Notification Center is located on the top right corner of the interface. It exists in two forms: active notification display and full Notification Center.
Page 62
It is strongly recommended to change the default password. 6.5. Remote access RipEX2 unit management is designed to work smoothly even when the unit under configuration is connected via relatively slow channel. In case of locally connected unit - direct configuration of the unit (accessing the unit IP address directly from the web browser) works fine.
Page 63
Once the Remote access is successful, the IP address line changes its color to black together with the web page identification. The IP address of the currently connected RipEX2 unit is displayed as a part of the Remote access button. All the configuration settings are remotely available using standard web interface. Some of the Diagnostic features are available via local connection only.
Page 64
Refresh deletes all non-saved changes which were done in the client. 6.7. Status info area Status info area provides a general overview about RipEX2’s individual SETTINGS (or DIAGNOSTICS) section by displaying diagnostic data relevant to the section. To update the data it is necessary to click the Refresh button.
Page 66
7.1. Interfaces 7.1.1. Ethernet RipEX2 provides 5 physical Ethernet ports ETH1, ETH2, ETH3, ETH4 and ETH5. ETH1 - ETH4 ports are metallic. ETH5 port is an SFP port. There is a possibility to define an Ethernet bridge - a logical Network interface - by bridging (joining) together multiple physical Ethernet interfaces.
Page 75
Unit is repeater List box {On; Off}, default = "Off" Each RipEX2 may work simultaneously as a Repeater (Relay) in addition to the standard Bridge operation mode. If "On", every frame received from Radio channel is transmitted to the respective user interface (ETH, COM) and to the Radio channel again.
Page 76
MUST be set in all units in the network, including the Repeater units themselves. After transmitting to or receiving from the Radio channel, further transmission (from this RipEX2) is blocked for a period calculated to prevent collision with a frame transmitted by a Repeater. Further- more, a copy of every frame transmitted to or received from the Radio channel is stored (for a period).
Page 80
Number {70 – 1500}, default = 1500 B If a packet entering to an interface exceeds the maximum value, it is either discarded or fragmented. Minimum MTU value to establish TCP between RipEX2 units = 576 B. Minimum MTU value for IPv6 (Babel) = 1280 B.
Page 81
Resilience parameter controls this functionality. By default the Auto is set - when intereference holds, RipEX2 stays in High resilience mode of receiver operation and signals this state by turning the yellow RX LED on. Once the interfering signals fade away, RipEX2 automatically returns to its High sensitivity mode of receiver operation.
Page 82
Such UDP frames received by the RipEX2 unit from the RipEX2 network (based on the unit IP address and UDP port of the Protocol module) are translated into original frame format (by the Protocol module) and send out through the COM port.
Page 84
RTS/CTS (Request To Send / Clear To Send) hardware flow control (handshake) between the DTE (Data Terminal Equipment) and RipEX2 (DCE - Data Communications Equipment) can be enabled in order to pause and resume the transmission of data. If RX buffer of RipEX2 is full, the CTS goes down.
Page 85
UDP ports for COM or Terminal servers can be used or UDP port can be set manually. If the des- tination IP address belongs to a RipEX2 and the UDP port is not assigned to COM or to a Terminal server or to any other special SW module running in the destination RipEX2, the packet is discarded.
Page 88
The None protocol switches the COM port off. All incoming data will be thrown away, no data will be sent into the COM interface. 7.1.3.3.2. Transparent protocol Operates in Bridge mode only. All the traffic is bridged transparently to RipEX2 network (see Section 5.1, “Bridge mode” for details). 7.1.3.3.3. Async link Async link creates an asynchronous link between two COM ports on different RipEX2 or M!DGE3 units.
Page 89
Note The COMLI protocol in the RipEX2 or M!DGE3 is not fully compatible on COM port with RipEX and MR modems. RipEX2 implementation is not supporting “Intercharacter tx delay”. Mode of Connected device: MASTER Congestion timeout [ms] Number {0 –...
Page 90
Each frame in the DNP3 protocol contains the source and destination addresses in its header, so there is no difference between Master and Slave in terms of the RipEX2 configuration. The DNP3 allows both Master-Slave polling as well as report-by-exception communication from the remote units.
Page 91
Settings 7.1.3.3.6. DF1 Each frame in the Allen-Bradley DF1 protocol contains the source and destination addresses in its header, so there is no difference between Master and Slave in the Full duplex mode in terms of RipEX2 configuration. Duplex mode List box {Full duplex;...
Page 92
MARS-A was widely used by legacy RACOM radio modems in the MORSE system from the year 1999. The new implementation of this protocol in RipEX2 or M!DGE3 is limited to the parts of the complex protocol which can be used together with modern packet type of these routers: USER DATA (0x09) from router to the serial interface (e.g.
Page 93
7.1.3.3.9. Modbus RTU Modbus RTU is a serial polling-type communication protocol used by Master-Slave application. When RipEX2 radio network run in Router mode, more Modbus Masters can be used within one Radio network and one Slave can be polled by more Masters.
Page 102
Settings 7.1.3.3.13. SAIA S-Bus SAIA S-Bus protocol was widely used by legacy RACOM radio modems in the MORSE system. The S-Bus protocol is implemented as an access module for communication with the SAIA PCD device. The protocol is a MASTER/SLAVE type; the MASTER does not have its own address. There can be at most 254 SLAVEs, the address 255 is reserved for broadcast transmitting which is not acknowledged.
Page 106
7.1.4. Terminal servers Generally, a Terminal Server (also referred to as a Serial Server) enables connection of devices with serial interface to a RipEX2 over the local area network (LAN). It is a virtual substitute for devices used as serial-to-TCP (UDP) converters.
Page 107
Up to 5 independent Terminal servers can be set up. Each one can be either TCP or UDP Type, TCP Inactivity is the timeout in seconds for which the TCP socket in RipEX2 is kept active after the last data reception or transmission. As source IP address of a Terminal server will be used the IP address of the RipEX2 ETH interface (Local preferred source address if exists see Section 7.2.1, “...
Page 117
Various methods and protocols are used for this purpose. Babel, OSPF and BGP standard routing protocols are available in RipEX2 networks. Link management option was added allowing to set the switchover of the main link (in the event of its failure) to an existing backup link by automatic changes of routing rules.
Page 118
Destination IP / mask IP address, default = 0.0.0.0/0 Each IP packet, received by RipEX2 through any interface (Radio, ETH, COM, ...), has got a des- tination IP address. RipEX2 (router) forwards the received packet either directly to the destination IP address or to the respective Gateway, according to the Routing table.
Page 119
IP address, default = 0.0.0.0 Local IP address used as a source address for packets originating in the local RipEX2 unit being routed by this routing rule. It might be for example packets originating from the COM port or from the Terminal Server.
Page 120
7.2.1.1. Loopback addresses Table of loopback addresses contains IP addresses of RipEX2, which are set on the loopback interface as "support" addresses independent on specific interface. Maximum number of addresses is 256. Loopback addresses can be useful e.g. for specific routing purposes or specific user data traffic. For example using different routing rules for different traffic.
Page 126
Router ID IP address, default = 0.0.0.0 RipEX2 unit acts in the Babel network as a dynamic router. Every router is identified by an ID having the format of IP address. This IP address does not have to be ‘real’.
Page 137
IP address, default = 0.0.0.0 RipEX2 unit acts in the OSPF network as a dynamic router. Every router is identified by an ID having the format of IP address. This IP address does not have to be ‘real’. Router ID is shared across all dynamic protocols.
Page 156
List box {Off; On}, default = "Off" Relates to the first packet when a TCP connection starts (Request from TCP client to TCP server for opening a new TCP connection). Used e.g. for allowing to open TCP only from RipEX2 network to outside.
Page 158
Settings Relates to the first packet when a TCP connection starts (Request from TCP client to TCP server for opening a new TCP connection). Used e.g. for allowing to open TCP only from RipEX2 network to outside. Connection state Established List box {Off;...
Page 159
List box {Off; On}, default = "Off" Relates to the first packet when a TCP connection starts (Request from TCP client to TCP server for opening a new TCP connection). Used e.g. for allowing to open TCP only from RipEX2 network to outside.
Page 165
• MASQUERADE rule for Cellular connection has lower priority that user NAT (it is tested after the NAT), thus it is possible to create exceptions in NAT settings. • By using DNAT it is possible to intercept a passing connection and redirect it into the RipEX2 (similar to a proxy behavior).
Page 166
• IKE SA: IKE Security Association providing SA keys exchange with the peer. • CHILD SA: IPsec Security Association providing packet encryption. Every IPsec tunnel contains 1 IKE SA and at least 1 CHILD SA. In RipEX2 can be set maximum of 24 IKE_SA and 48 CHILD_SA (TS).
Page 170
The true time of expiration is randomly selected within the range of 90-110%. Unfortunately, the more frequent the key exchange, the higher the network and CPU load. Note If low capacity channel is used, the RipEX2’s channel load can affected during the key exchange process. IKE Post-quantum PSK (PPK) List box {On;...
Page 171
Note If low capacity channel is used, the RipEX2’s channel load can affected during the key exchange process. PSK (Pre-shared key) authentication is used for IKE SA authentication. The relevant peer is identified using it's "Peer ID".
Page 172
Unsupported characters are: ", `, \, $, ;. The full UTF-8 character set is available since FW 2.1.2.0. Note: If the password starts with the characters 0x or 0s, then the connection between RipEX2 with FW 2.1.2.0 (and newer) and RipEX2 with FW 2.1.1.0 (and older) will not be established.
Page 174
MTU of the L2 tunnel. Number {74 – 1500}, default = 1430 B Overhead of the L2 tunnel is 38 B, so it should be GRE MTU = Path MTU - 38. Minimum MTU value to establish TCP between RipEX2 units = 576 B. Note For traffic in bridged network (e.g.
Page 176
GRE packets will be discarded and ICMP report will be send back to the source of the original packet (Path MTU discovery). Minimum MTU value to establish TCP between RipEX2 units = 576 B. Key enabled Enables using key identification of the tunnel from/to the same peer.
Page 183
7.5.3. Credentials RipEX2 units feature a unified storage solution for keys, certificates and other credentials. This storage is secured and only accessible to users with Sectech permission and higher. Credentials are separate from configuration to improve security and it also is protected using checksum to prevent unauthorised modification.
Page 190
RADIUS accounts can be mapped to one of the four user roles. This is either managed by the server itself or by local RipEX2 settings. Local accounts are checked first and if the account does not exist, RADIUS accounts will be used. If the RADIUS server is not accessible, users may use the local username/password to “fall back”...
Page 191
Management-Privilege-Level the static account level option (for all users) has to be used. 7.5.6. Tamper reset Tamper is a detection service, which is triggered, when the RipEX2 chassis is physically opened. There are 2 contacts (securing top and bottom casing) and the event is triggered even if the unit is without power.
Page 195
Informational comment. 7.6.1.3. Sleep mode RipEX2 offers a mode which periodically switches between the full traffic mode and low power con- sumption mode. This mode is suitable e.g. for power-consumption sensitive applications. When in Sleep mode, RipEX2 has extremely low power consumption (10 mW). The time needed for a complete wake-up from the Sleep mode (booting time) is approx.
Page 196
7.6.1.3.1. Wake-up parameters Waking up the RipEX2 from Sleep mode is possible via setting the time of its awakening. It is also possible to set an interval during which the unit will be woken up regularly. Sleep mode time boundaries are counted in a set Time zone (SETTINGS >...
Page 197
7.6.1.3.2. Go to sleep parameters RipEX2 will go into the Sleep mode after the set time passes. It is possible to delay the Sleep mode to assure that all data transfer is complete. Connecting USB-ETH or USB-WIFI adapters to the service port will also delay the Sleep mode.
Page 198
SI is trigged/activated if it is pulled below 1.1 VDC. See more details in Pin assignment If the RipEX2 is in the Sleep mode and SI is triggered, the unit will wake up for the set awake period and go back to sleep. The Sleep Input signal is not monitored while RipEX2 is awake so any additional SI trigger does not increase the awake period.
Page 200
• Current configuration - displayed configuration, which is seen in the web client. • Running configuration - actual configuration, running in the RipEX2 unit. • Stored configuration - configuration stored in the RipEX2 unit. This configuration is stored in the unit, even when its turned off.
Page 204
Fig. 7.27: SETTINGS > Device > Events 7.6.4. SW keys Certain RipEX2 features needs to be activated by a SW key to be available. When the respective SW key is not present, the feature cannot be configured. If the feature is enabled in a configuration backup file and the file is loaded to a unit which is not equipped with the respective key, the configuration is refused (no changes are made in the unit).
Page 206
Radius Tamper detection Tamp *By defaults from 03/2024, if you've purchased RipEX2 before this date and want to use this function- ality, you will need to request the atomic key from the supplier. Note The newly added atomic keys are not included in the delivery of the previously ordered SW key (Link management for units dispatched before 07/2023, OpenVPN for units dispatched before 10/2023).
Page 207
4. Click the Upload firmware button to transfer the firmware file into the unit. The upload can take a long time – depending on the connection speed between the management PC and the RipEX2 unit. In case of slow connection and file transfer longer than 120 s, the web browser will shut down the connection and the action will not finish successfully.
Page 209
For successful activation a compatibility between the patch file and active firmware (or uploaded firmware) must be ensured. Patch files for RipEX2 can be downloaded from RACOM’s web site . FW versions stored in RipEX2 are dis- played in SETTINGS >...
Page 210
Settings Example: There are 2 older FW versions (2.0.8.0 and 2.0.10.0) stored in RipEX2 (picture above). For successful activation of newer FW version (e.g. 2.0.13.0) using patch file either: • Download patch files version upgrading from 2.0.8.0 to 2.0.13.0 or •...
Page 213
Distribution works over the radio network (FOTA - Firmware over the air) in form of multicast. Units must be available to each other within one IP hop. To set up FW distribution, RipEX2 unit must be set either as a sender or a receiver.
Page 218
List box {Default; User defined}, default = "Default" Engine ID serves for unique identification of the SNMP instance (i.e. the RipEX2 unit) according to RFC3411. When the "Default" Engine ID mode is selected the MAC address of the ETH1 interface is used for the unique part of the Engine ID (the whole Engine ID example: 800083130302a92006ef).
Page 221
(numerical codes 16 to 23) can be set. Consult with your Syslog server administrator about which facility will be used for individual groups of units. 7.7.4. SMS RipEX2, fully connected into the cellular network (status CONNECTED), is capable of receiving and sending SMS. • Receiving and sending SMS is provided by a linux service.
Page 224
RipEX2 User manual and section "Switching over" Ripex2-HS Important The communication between individual RipEX2 units and HS controller use DI/DO interfaces, so other use of these interfaces is not possible. Note HW option RipEX2e (product variant ‘C' and 'D’) cannot be used in Hot standby configuration.
Page 225
Settings Virtual ETH MAC MAC address of shared LAN interface. It should be same for both individual RipEX2 units. This MAC address has to differ from other MAC addresses used in unit. It is possible to use e.g. VRRP type of addresses: 00:00:5E:00:01:XX.
Page 233
Error, Critical, Alert, Emergency 8.2. Overview The Overview section serves to give general information about the RipEX2. 8.2.1. Measurements Section Overview - Measurements contains current data measurement (obtained from sensors). • Card Temperature - provides data about temperature (on CPU, modem and radio).
Page 234
• 15-min interval is collected by taking 14 mins from history + seconds passed from current minute. 8.3. Information This section provides more detailed information (data extract) about settings of RipEX2 unit. It provides also a deeper explanation about some of set values and interfaces. Diagnostic data are provided as well.
Page 235
Fig. 8.1: DIAGNOSTICS > Information > Interfaces > Ethernet Intefaces used in RipEX2 units are in general either Bridged ports (BP-L2) or Routed interfaces (RI- L3). All interfaces used by the linux router (internal interfaces excluded) are displayed in the following list.
Page 243
This menu serves for collecting data, either from local or remote station and storing them into a package (file). Diagnostic package serves primarily as a help tool, for RACOM’s technical support in case of any potential unit issues. Minimum size of a package is 5kB. Maximum size depends on the amount of radio links contained in the statistics.
Page 245
Debug 8.5. Statistics RipEX2 unit permanently monitors various system 'channels'. There are several types of those channels: Physical interfaces (Ethernet ports, serial ports, radio interface, additional module interface (e.g. LTE module) when installed), virtual interfaces (e.g. VLAN interfaces) and HW sensors (CPU temperature, supply voltage, ...).
Page 249
(unlike "Radio protocol statistics" where the Link address is an address of the unit where the packet entered the RipEX2 network). There is a special address 'RELAY' to indicate frames coming from the re-translation unit in case of Base Driven Protocol operation.
Page 250
'Correct' and 'Drop' Bytes provides the total amount of Bytes on the physical interface. Rx direction: from the connected (at the COM or ETH port) external device to the RipEX2 unit (i.e. from the COM port module or Terminal server module to the Router module). Tx direction: from the RipEX2 unit to the external device.
Page 251
Only correctly received frames are handled. The counters correspond to the specific IP protocol types. Rx direction: from the physical Ethernet port to the RipEX2 unit (i.e. to the Router module). Tx direction: from the RipEX2 unit to the physical Ethernet port.
Page 252
Rx direction: from the Cellular module to the Router module. Interface – “cell-ext” interface is used for RipEX2 optional extension cellular module. UDP, TCP, ICMP, ARP - Packet count and amount of data in Bytes [B] for different protocol types. Amount of data is summed over the whole Layer 2 Ethernet frame (i.e.
Page 253
Diagnostics 8.5.9.2. Cellular state statistics Interface – “cell-ext” interface is used for RipEX2 optional extension cellular module. SIM [%] – information about using the individual SIM cards during the time displayed in %. Services [%] – N/A (not available), 2G (e.g. GPRS, EDGE), 3G (e.g. UMTS), 4G (e.g. LTE) services usage dis- played in % of time.
Page 254
Monitoring is an advanced on-line diagnostic tool, which enables a detailed analysis of communication over any of the RipEX2 router interfaces. In addition to all the physical interfaces (RADIO, EXT, ETHs, COMs, TSs), some internal interfaces between software modules can be monitored when such advanced diagnostics is needed.
Page 255
Terminal Server) and vice versa. When an external interface (e.g. Interface COM) is monitored, the Tx also means packets being transmitted from the RipEX2 over the respective interface (Rx means "received"). Understanding the directions over the internal interfaces may not be that...
Page 256
List box {LOW; NORMAL; HIGH; UNLIMITED}, default = "NORMAL" Monitoring bandwidth limit to prevent overload of management link between client PC and the RipEX2 unit. LOW (up to ~300 kb/s), NORMAL (up to ~800 kb/s), HIGH (up to ~2 Mb/s), UNLIMITED (up to ~8 Mb/s) Source port (from) / Source port (to) TCP/UDP source port to be enabled/disabled in the monitoring output.
Page 258
When Promiscuous mode is enabled, the unit is capable to monitor (receive) frames from the other RipEX2 units even if the other unit(s) is(are) working in the other Unit mode (Bridge versus Router). Frames transmitted under another Unit mode may not be properly 'analyzed'. In such a case frames are displayed in raw data format.
Page 262
Output format of different type (other than radio) of hops is similar to ICMP ping. Destination IP Destination IP address. This address must belong to a RipEX2 unit as the RSS ping can be initiated only between two RipEX2 units.
Page 265
Radio Settings before using this feature. 8.7.5. Antenna detection The RipEX2 is equipped with circuits and algorithms that make it possible to monitor the state of its output transmission circuits, including the antenna and its cable. To evaluate the situation, the data...
Page 272
HW tamper Case opening evidence When full-duplex with full power (40 dBm PEP) and the surrounding temperature above + 60°C the external passive cooler should be used (e.g. RipEX2-RS 19" Rack chassis Diagnostic and Management Link testing ICMP ping, RSS ping...
Page 298
10.0 10.3. High temperature If the RipEX2 is operated in an environment where the ambient temperature exceeds 55 °C, the RipEX2 must be installed within a restricted access location to prevent human contact with the enclosure heatsink. 10.4. Battery disposal Battery Disposal - This product may contain a battery (e.g.
Page 299
• The unit must be powered with an intrinsically safe power source. • The antenna has to be installed outside the hazardous zone. • Do not manipulate the RipEX2 (e.g. plug or unplug connectors) unless powered down or the area is known to be non-hazardous.
Page 303
Everyone can copy and spread word-for-word copies of this license, but any change is not permitted. The program (binary version) is available for free on the contacts listed on https://www.racom.eu. This product contains open source or another software originating from third parties subject to GNU General Public License (GPL), GNU Library / Lesser General Public License (LGPL) and / or further author li- censes, declarations of responsibility exclusion and notifications.
Page 305
• any requirements for authorisation of use. Fig. 10.5: EU restrictions or requirements The RipEX2 radio modem predominantly operates within frequency bands that require a site license be issued by the radio regulatory authority with jurisdiction over the territory in which the equipment is being operated.
Page 306
С настоящото RACOM s.r.o. декларира, че този тип радиосъоръжение RipEX2 е в съответствие с Директива 2014/53/ЕС. Por la presente, RACOM s.r.o. declara que el tipo de equipo radioeléctrico RipEX2 es conforme con la Directiva 2014/53/UE. Tímto RACOM s.r.o. prohlašuje, že typ rádiového zařízení RipEX2 je v souladu se směrnicí 2014/53/EU.
Page 307
Με την παρούσα ο/η RACOM s.r.o., δηλώνει ότι ο ραδιοεξοπλισμός RipEX2 πληροί την οδηγία 2014/53/ΕΕ. Hereby, RACOM s.r.o. declares that the radio equipment type RipEX2 is in compliance with Directive 2014/53/EU. Le soussigné, RACOM s.r.o., déclare que l'équipement radioélectrique du type RipEX2 est conforme à...
Page 308
Safety, regulations, warranty RACOM s.r.o. týmto vyhlasuje, že rádiové zariadenie typu RipEX2 je v súlade so smernicou 2014/53/EÚ. RACOM s.r.o. potrjuje, da je tip radijske opreme RipEX2 skladen z Direktivo 2014/53/EU. RACOM s.r.o. vakuuttaa, että radiolaitetyyppi RipEX2 on direktiivin 2014/53/EU mukainen.
Page 315
The serviced equipment shall be returned by RACOM to the customer by prepaid freight. If circumstances do not permit the equipment to be returned to RACOM, then the customer is liable and agrees to reim- burse RACOM for expenses incurred by RACOM during servicing the equipment on site. When equipment does not qualify for servicing under warranty, RACOM shall charge the customer and be reimbursed for costs incurred for parts and labour at prevailing rates.
Page 316
The Availability depends on specific network design and Service availability. Availability can be increased by decreasing MTTR. Availability calculation needs to be done for each network element separately. RipEX2 redundant solution within Field Replaceable Units fully achieving the level availability and reli- ability for the Core elements.
Page 318
You create user accounts (local authentication or remote RADIUS) and assign them roles via which they can access RipEX2/M!DGE3 GUI or API. • There are four different levels of user access privileges – they are bound with four different user...
Page 319
Cellular networks are in control of operators and public APNs are connected to the public Internet. Any data sent or received by RipEX2 (EXT) or M!DGE3 (MAIN, EXT) can be captured by experienced hackers. If such data are not encrypted, sensitive data can be read by these hackers and misused.
Page 320
(Radio, cellular MAIN/EXT, ETH, GRE L3, …). A.6. Exchange of certificates It is recommended to change certificates for certificates trusted by the RipEX2 user. The default certificates are part of installation of all units, so the replacement for your own certificates will increase the security of all processes and services (e.g.
Page 321
Protect the unit via Firewall settings • SETTINGS > Firewall > L2 / L3 / NAT • Especially important if RipEX2/M!DGE3 has a public IP address! Limit access to RipEX2/M!DGE3 GUI • Only allow authorized IPv4 addresses to access your network. Each piece of hardware connected to a network has an assigned IPv4 address.
Page 322
Utilize USB flash drive - for FW upgrade via USB disk - this service is on by default, it can be disabled. • SETTINGS > Device > Firmware > USB Utilize Firmware distribution for RipEX2 networks in a bandwidth optimized way. • FW distribution uses the authentication key during the process - the key is the same in all manufac- tured units - you can generate and use your own.
Need help?
Do you have a question about the RipEX2 and is the answer not in the manual?
Questions and answers