Westermo RedFox Series - Manual (Page 591)

Westermo OS Management Guide
Version 4.17.0-0
26.1.4.1 Using Static Route with Next-Hop or Interface as target
When defining a static route, the target is typically an IP address, e.g., ”route
192.168.5.0/24 192.168.1.1” where ”192.168.1.1” would be the IP address
of the next-hop router towards the destination.
In other situations you could define the target as a network interface of your unit,
e.g., ”route 192.168.5.0/24 ssl0” where all traffic towards ”192.168.5.0/24”
would be sent via your SSL VPN interface (
chapter 36 ).
Note
Using an interface as target of a static route is almost only used on point-
to-point interfaces, e.g., SSL or GRE interfaces. In rare cases it can be used
on LAN interfaces when you have multiple subnets on a VLAN, but in those
cases it is often simpler to use a secondary IP address on that LAN interface,
see
section 19.2.5 .
26.1.4.2 Floating Static Routes - Administrative Distance for Static Routes
Floating static routes are static routes with higher administrative distance (see
section 26.1.3 ) than routes learnt dynamically, e.g., via routing protocols such as
OSPF and RIP, or via dynamic configuration protocols such as DHCP or IPCP (PPP).
An example where a default route acquired via DHCP is given precedence over a
floating static (default) route is given in
section 19.2.6 . To complement this, an
example where routes learnt via OSPF is given precedence over a floating static
route is illustrated in
fig. 26.1 .
In this example, the user could have used OSPF over the low-speed backup link,
but has instead chosen to use a floating static route. Relevant parts of the con-
figuration at routers 1, 2 and 3 are shown below.
Router 1 injects a default route into the OSPF area, a defines a floating static
route towards 192.168.35.0/24 via Router2.
➞ 2015 Westermo Teleindustri AB 591