RipEX2-Remote Configuration


Print version

4. RipEX2-Remote Configuration

RipEX2-Remote settings

Fig. 4.1: RipEX2-Remote settings

The Settings menu is the same as on the Centre station except for the following:

  • Unit name: RipEX2-Remote

  • Radio IP:

  • ETH IP:

  • ARP Proxy & VLAN: On

ARP Proxy & VLAN menu must be opened and configured. Set the Alias IP address for the Ethernet interface. We simulate several subnets behind local RipEX’s Ethernet (or SLIP protocol).

That is not necessary for GRE functionality; it is just used to show this configuration option.

RipEX2-Remote ETH Alias/Subnet

Fig. 4.2: RipEX2-Remote ETH Alias/Subnet

To set and enable this alias, you need to click on the “Add Subnet” button and fill in the subnet into the “IP/MASK” field.

RipEX2-Remote GRE tunnel configuration

Fig. 4.3: RipEX2-Remote GRE tunnel configuration

Set the Peer IP to the RipEX1-Base Ethernet IP address – The GRE subnet must correspond to the Centre settings, i.e. choose the second IP address within a given subnet –

RipEX2-Remote routing rules

Fig. 4.4: RipEX2-Remote routing rules

The last step is to configure Routing rules.

  •, Gateway

    • This rule depends on your L3 infrastructure, but in our example, we use the rule to route data for network via local gateway.

  •, Gateway

    • The route using the GRE tunnel – packets for the Server ( are encapsulated into the GRE. You might configure other destinations within this subnet if required, but not (RipEX Ethernet – Peer IP, i.e. RipEX1-Base).

  • a, Gateway

    • Data for subnets behind RipEX4-Remote are routed to its Radio IP address (i.e. not using GRE tunnel).

©  2024 RACOM s.r.o. All Rights Reserved.