TCR100 Routing

Main Page > TCR Routers > TCR100 > TCR100 Manual > TCR100 WebUI > TCR100 Network section > TCR100 Routing

The information in this page is updated in accordance with firmware version TCR1_R_00.07.11.3.

Summary

The Routing page is used to set up static routes, routing tables and rules.

This manual page provides an overview of the Routing windows in TCR100 devices.

If you're having trouble finding this page or some of the parameters described here on your device's WebUI, you should turn on "Advanced WebUI" mode. You can do that by clicking the "Advanced" button, located at the top of the WebUI.

Static Routes

Routes ensure that network traffic finds its path to a specified host or network, both in local and remote network scenarios. Static routes are simply fixed routing entries in the routing table(s).

This section provides the possibility to configure custom static routes.

Static IPv4 Routes

The Static IPv4 Routes section displays a list of user defined static IPv4 routes and provides the possibility to add and configure new ones. The list is empty by default.

To add a new route and begin editing, simply click the 'Add' button. Refer to the table below for information on static route configuration fields.

Field	Value	Description
Interface	network interface; default: lan	Network interface of the target network.
Target*	ip4; default: none	Destination network address.
IPv4-Netmask*	netmask; default: none	A netmask is used to divide an IP address into sub-networks (subnets). Combined together, the 'Netmask' and 'Target' values define the exact destination network or IP address to which this route applies.
IPv4-Gateway	ip4; default: none	A gateway can be any machine in a network that is capable of serving as an access point to another network. Traffic that matches this route will be directed over the IP address specified in this field.
Metric	integer [0..255]; default: none	The metric value acts as a measurement of priority. If a packet about to be routed matches two or more rules, the one with the lower metric is applied.
MTU	integer [64..9000]; default: 1500	Sets the maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction.
Route Type	unicast \| local \| broadcast \| multicast \| unreachable \| prohibit \| backhole \| anycast \| -- custom -- ; default: unicast	Selects route type. Each type specifies a different behavior for the route: unicast - most common type of route, simply describes a path to a destination. local - routes of this type are added to the 'local' routing table and used only for locally hosted IPs. broadcast - routes of this type are added to the 'local' routing table and used by link layer devices that support the broadcast address principle. multicast - used for distribution of multicast traffic. unreachable - sends an ICMP "unreachable" response to the source address when a request for a routing decision returns a "destination with an unreachable route type" message. prohibit - used to prohibit traffic to specified host or network. When a destination is prohibited, the kernel sends a 'Network is unreachable' response the source address. blackhole - packets that match this type of route are discarded without any response. anycast - provides a possibility to route incoming requests to multiple different network locations. -- custom -- - does not use any of the predefined route types.

*Additional notes on 'Target' & 'Netmask' fields:

You can define a rule that applies to a single IP like this:

Target: some IP
Netmask: 255.255.255.255

Furthermore, you can create target/netmask combinations that apply to a range of IPs. Refer to the table below for examples.

Target	Netmask	Network range
192.168.2.0	255.255.255.240	192.168.2.0 - 192.168.2.15
192.168.2.240	255.255.255.240	192.168.2.240 - 192.168.2.255
192.168.2.161	255.255.255.0	192.168.2.0 - 192.168.55.255
192.168.0.0	255.255.0.0	192.168.0.0 - 192.168.255.255
192.168.2.161	255.255.255.255	192.168.2.161

Static IPv6 Routes

The Static IPv6 Routes section displays a list of user defined static IPv6 routes and provides the possibility to add and configure new ones. The list is empty by default.

To add a new route and begin editing, simply click the 'Add' button. Refer to the table below for information on static route configuration fields.

Field	Value	Description
Interface	network interface; default: lan	Network interface of the target network.
Target	ip6; default: none	Destination network address.
IPv6-Gateway	ip6; default: none	A gateway can be any machine in a network that is capable of serving as an access point to another network. Traffic that matches this route will be directed over the IP address specified in this field.
Metric	integer [0..255]; default: none	The metric value acts as a measurement of priority. If a packet about to be routed matches two or more rules, the one with the lower metric is applied.
MTU	integer [64..9000]; default: 1500	Sets the maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction.
Route Type	unicast \| local \| broadcast \| multicast \| unreachable \| prohibit \| backhole \| anycast \| -- custom -- ; default: unicast	Selects route type. Each type specifies a different behavior for the route: unicast - most common type of route, simply describes a path to a destination. local - routes of this type are added to the 'local' routing table and used only for locally hosted IPs. broadcast - routes of this type are added to the 'local' routing table and used by link layer devices that support the broadcast address principle. multicast - used for distribution of multicast traffic. unreachable - sends an ICMP "unreachable" response to the source address when a request for a routing decision returns a "destination with an unreachable route type" message. prohibit - used to prohibit traffic to specified host or network. When a destination is prohibited, the kernel sends a 'Network is unreachable' response the source address. blackhole - packets that match this type of route are discarded without any response. anycast - provides a possibility to route incoming requests to multiple different network locations. -- custom -- - does not use any of the predefined route types.

Policy Based Routing

The Policy Based Routing section is used to configure policy-based routing infrastructures, which are usually used in more complex or specific networking scenarios.

Routing Tables

Routing Tables store network routes. Tables are checked before every routing decision until a matching route is found. Having multiple tables allows the user to set up a policy routing infrastructure. Policy-based routing is a technique where routing decisions are based on policies (rule) set by the user.

The 'Routing Tables' section displays user created routing tables. By default, the list is empty.

To create a new table, look to the 'Add New Routing Table' section below. Enter an ID for the new table in the range of [1..252], enter a custom name and click the 'Add' button. The new table should appear in the 'Routing Tables' list. Click the 'Edit' button next to it to begin editing.

Refer to the table below for information on configuration fields for routing tables.

Field	Value	Description
Name of Table	string; default: none	A custom name for the table. A table can be invoked by the both its ID or name.
ID of Table	integer [1..252]; default: none	Unique numerical identifier for the table. A table can be invoked by the both its ID or name.

Routing Rules For IPv4

Routing Rules provide a way to route certain packets with exceptions, i.e., in accordance to a rule. 'Routing Rules For IPv4' displays user defined routing rules. It is empty by default. To create a new rule, click the 'Add' button and begin editing by clicking the 'Edit' button located to the right of the newly created rule.

Refer to table below for information on each configuration field.

Field	Value	Description
Priority	integer [0..65535]; default: none	Controls the order of IP rules. Rules with a lower priority value will be checked first.
Incoming interface	network interface \| Any; default: Any	Logical interface name for incoming traffic. Select 'Any' to make the rule apply to all network interfaces.
Outgoing interface	network interface \| None; default: None	Logical interface name for incoming traffic. Select 'None' to ignore outgoing interface.
Source subnet	netmask; default: none	Source subnet to match the rule.
Destination subnet	netmask; default: none	Destination subnet to match the rule.
TOS Value to Match	integer [0..255]; default: none	The type of service (ToS) value to match in IP headers.
Firewall Mark	integer [0..255] \| hex [0x00..0xFF]; default: none	Specifies the fwmark and optionally its mask to match. For example, 0xFF to match mark 255 or 0x0/0x1 to match any even mark value.
Invert matches	off \| on; default: off	If enabled, the meaning of the match options (Firewall Mark, TOS Value, Source and Destination subnets) is inverted.
Matched Traffic Action	Lookup Table \| Jump to rule \| Routing Action; default: Lookup Table	When network traffic matches this rule, the device will take an action specified in this field: Lookup Table - routes traffic in accordance with the specified routing table. Jump to rule - specifies another routing rule to follow. Routing Action - executes one of four predefined routing actions.
Lookup Table	routing table; default: none	Specifies a table for routing traffic that matches this rule. This field is visible only when 'Matched Traffic Action' is set to Lookup Table.
Jump to rule	rule priority number; default: none	Specifies a another rule to follow for traffic that matches this rule. This field is visible only when 'Matched Traffic Action' is set to Jump to rule.
Routing Action	Prohibit \| Unreachable \| Blackhole \| Throw; default: Prohibit	When traffic matches this rule, the action specified in this field will be executed. This field is visible only when 'Matched Traffic Action' is set to Routing Action.