User's Manual
Table Of Contents
- RipEX2 Radio modem & Router
- Table of Contents
- Important Notice
- 1. Quick guide
- 2. Product
- 3. Accessories
- 4. Installation
- 5. RipEX2 in detail
- 6. Web interface
- 7. Settings
- 7.1. Interfaces
- 7.1.1. Ethernet
- 7.1.2. Radio
- 7.1.3. COM
- 7.1.4. Terminal servers
- 7.1.5. Cellular
- 7.2. Routing
- 7.2.1. Static
- 7.2.2. OSPF
- 7.2.2.1. Description
- 7.2.2.2. Common - Common settings
- 7.2.2.3. Network - Areas and interfaces - Areas
- 7.2.2.4. Network - Areas and interfaces - Interfaces
- 7.2.2.5. Network - Areas and interfaces - Neighbors
- 7.2.2.6. Network - Areas and interfaces - Networks
- 7.2.2.7. Static rules
- 7.2.2.8. Import filter
- 7.2.2.9. Export filter
- 7.2.3. BGP
- 7.3. Firewall
- 7.4. VPN
- 7.5. Security
- 7.6. Device
- 7.7. Advanced
- 7.1. Interfaces
- 8. Diagnostics
- 9. Technical parameters
- 10. Safety, regulations, warranty
- 10.1. Frequency
- 10.2. Safety distance
- 10.3. High temperature
- 10.4. Battery disposal
- 10.5. Instructions for Safe Operation of Equipment
- 10.6. SW license
- 10.7. EU Compliance
- 10.8. Compliance Federal Communications Commission and Innovation, Science and Economic Development Canada
- 10.9. Compliance ANATEL Brasil
- 10.10. Warranty
- 10.11. RipEX2 Availability and service life time
- 10.12. RipEX2 maintenance
- Appendix A. Abbreviations
- Index
- Revision History
Fig. 5.6: Router - Flexible, Optimised addressing
The default gateway is also a very powerful routing tool, however be very careful whenever the default
route would go to the radio interface, i.e. to the radio channel. If a packet to non-existing IP destination
came to the router, it would be transmitted over the radio channel. Such packets increase the load of
the network at least, cause excessive collisions, may end-up looping etc. Consequently the default
route should always lead to the ETH interface, unless you are perfectly certain that a packet to non-
existing destination IP may never appear (remember you are dealing with complex software written
and configured by humans).
5.3. Combination of IP and serial communication
RipEX2 enables combination of IP and serial protocols within a single application.
Five independent terminal servers are available in RipEX2. Terminal server is a virtual substitute for
devices used as serial-to-TCP(UDP) converters. It encapsulates serial protocol to TCP(UDP) and vice
versa eliminating the transfer of TCP overhead over the radio channel.
If the data structure of a packet is identical for IP and serial protocols, the terminal server can serve as
a converter between TCP(UDP)/IP and serial protocols (RS232, RS485).
You can see an instructional video explaining the Terminal server functionality here:
https://www.racom.eu/ripex-terminal
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.
Examples of the use:
47© RACOM s.r.o. – RipEX2 Radio modem & Router
RipEX2 in detail