User manual

12: Static routes configuration
_______________________________________________________________________________________________________
12 Static routes configuration
Static routes can be added 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.
12.1 IPv4 routes
It is possible to define arbitary IPv4 routes on specific interfaces using route
sections. As for aliases, multiple sections can be attached to an interface. These
kind or routes are most commonly known as static routes.
A minimal example is shown below:
network.name_your_route=route
network.name_your_route.interface=lan
network.name_your_route.target=172.16.123.0
network.name_your_route.netmask=255.255.255.0
network.name_your_route.gateway=172.16.123.100
config 'route' 'name_your_route'
option 'interface' 'lan'
option 'target' '172.16.123.0'
option 'netmask' '255.255.255.0'
option 'gateway' '172.16.123.100'
Lan is the logical interface name of the parent interface.
172.16.123.0 is the network address of the route.
255.255.255.0 specifies the route netmask.
Legal options for IPv4 routes are described in the table below.
Name Type Required Default Description
interface string yes (none)
Specifies the logical interface name of the
parent (or master) interface this route is
belonging to, must refer to one of the
defined interface sections.
target ip address yes (none) Specifies the network address.
netmask netmask no (none)
Defines route netmask. If omitted,
255.255.255.255 is assumed which makes
the target a host address.
Gateway ip address no (none)
Network gateway. If omitted, the gateway
from the parent interface is taken. If set to
0.0.0.0 no gateway will be specified for the
_______________________________________________________________________________________________________
© Virtual Access 2015
GW1000 Series User Manual
Issue: 2.4 Page 69 of 255