Switches the rule on / off
Destination IP / mask
Each IP packet, received by M!DGE3 through any interface (Radio, ETH, COM, ...), has got a
destination IP address. M!DGE3 (router) forwards the received packet either directly to the destin-
ation IP address or to the respective Gateway, according to the Routing table. Any Gateway has
to be within the network defined by IP and Mask of one of the interfaces, otherwise the packet is
discarded.
Each item in the routing table defines a Gateway (the route, the next hop) for the network (group
of addresses) defined by Destination IP and Mask. When the Gateway for the respective destination
IP address is not found in the Routing table, the packet is forwarded to the Default gateway, when
Default gateway (0.0.0.0/0) is not defined, the packet is discarded.
The network (Destination and Mask) is written in CIDR format, e.g. 10.11.12.13/24.
Note
Networks defined by IP and Mask for Radio and other interfaces must not overlap.
Mode
{Static}Used for static IP routing rules. If the next hop on the specific route is over the radio channel,
the Radio IP is used as a
Gateway
. If Base driven protocol is used and the destination Remote is
behind a Repeater, the destination Remote Radio IP is used as a Gateway (not the Repeater ad-
dress).
Local preferred source address
Local IP address used as a source address for packets originating in the local M!DGE3 unit being
routed by this routing rule. It might be for example packets originating from the COM port or from
the Terminal Server. If the address is set to 0.0.0.0 it is not considered active. The IP address has
to belong to some of the following interfaces: Radio interface, Network interfaces.
Note
You may add a name to each route with your comments up to 16 characters (UTF8 is supported)
for your convenience.
7.2.1.1. Loopback addresses
Table of loopback addresses contains IP addresses of M!DGE3, 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.
M!DGE3 Cellular Router – © RACOM s.r.o.
76
Settings
Содержание M!DGE3
Страница 2: ......
Страница 11: ...2 1 Dimensions Fig 2 1 M DGE3 dimensions 11 RACOM s r o M DGE3 Cellular Router Product...
Страница 116: ...M DGE3 Cellular Router RACOM s r o 116 Settings...
Страница 134: ...Tab 7 3 Configuration versions FW version CNF version 2 0 13 0 1 M DGE3 Cellular Router RACOM s r o 134 Settings...