virtual access GW1000M Series - 19 Configuring Static Routes; Configuration Package Used; Configuring Static Routes Using the Web Interface

19: Configuring static routes
_______________________________________________________________________________________________________
_____________________________________________________________________________________________________
© Virtual Access 2017
GW1000 Series User Manual
Issue: 1.9 Page 139 of 350
19 Configuring static routes
It is possible to define arbitrary IPv4 routes on specific interfaces using route sections.
As for aliases, multiple sections can be attached to an interface. These types of routes
are most commonly known as static routes.
You can add static routes to the routing table to forward traffic to specific subnets when
dynamic routing protocols are not used or they are not configured for such subnets.
They can be created based on outgoing interface or next hop IP address.
19.1 Configuration package used
Package
Sections
network
route
19.2 Configuring static routes using the web interface
In the top menu, select Network -> Static Routes. The Routes page appears.
Figure 75: The routes page
In the IPv4 Routes section, click Add.
Web Field/UCI/Package Option
Description
Web: Interface
UCI: network.@route[0].interface
Opt: Interface
Specifies the logical interface name of the parent or master
interface this route belongs to. It must refer to one of the defined
interface sections.
Web: target
UCI: network.@route[0].target
Opt: target
Specifies the route network IP address.
Web: netmask
UCI: network.@route[0].netmask
Opt: netmask
Defines the route netmask. If omitted, 255.255.255.255 is
assumed, which makes the target a host address.