Specifications

There are no limitations to setting up routing in this case. The only rule is that the range of radio
and Ethernet IP addresses must not overlap.
B. If you can only set the IP address, network mask and gateway, not the routing table in the
IP device connected to RipEX
In this case destination addresses must not be on the same network (i.e. the destination address
must always be outside of the network mask). A destination address is the IP address of one of
the devices connected to RipEX's which mutually communicate over the radio channel.
C. If the connected device allows neither network mask, nor gateway to be set up
Router mode cannot be used at all; use Bridge mode instead.
1.3. Ethernet addressing
If you can set up IP addresses of the end devices connected over Ethernet, you can simplify routing
by hierarchic division into subnets, either complete or for routing purposes only. An example of such
network layout follows.
The centre and main repeater form distinct networks with mask 255.255.255.0 (/24), the sub-networks
narrow down towards the end devices 255.255.255.192 (/26) and then 255.255.255.248 (/29). Routing
tables are only given for a single branch of the network for clarity. They will be similar for other RipEX's.
Only Master Slave type applications are presumed without any direct communication between
Slave devices.
9© RACOM s.r.o. – RipEX Application notes
Address planing