Difference between revisions of "Template:Networking rutos manual routing"
From Teltonika Networks Wiki
| Line 310: | Line 310: | ||
</tr> | </tr> | ||
</table> | </table> | ||
| + | {{#ifeq: {{{series}}} | RUTX | | ||
| + | ==Dynamic Routes== | ||
| − | + | <b>Dynamic Routing</b> provides the possibility to route data based on current network or device state instead of relying on static entries in the routing table. The {{{name}}} device supports these dynamic routing protocols: | |
| − | |||
| + | <ul> | ||
| + | <li>[[#BGP|BGP]] (Border Gateway Protocol)</li> | ||
| + | <li>[[#RIP|RIP]] (Routing Information Protocol)</li> | ||
| + | <li>[[#OSPF_Protocol|OSPF]] (Open Shortest Path First)</li> | ||
| + | <li>[[#EIGRP|EIGRP]] (Enhanced Interior Gateway Routing Protocol)</li> | ||
| + | <li>[[#NHRP|NHRP]] (Next Hop Resolution Protocol)</li> | ||
| + | </ul> | ||
| + | Each protocol is described in the sections below. | ||
| + | ===BGP=== | ||
| + | ---- | ||
| + | The <b>Border Gateway Protocol (BGP)</b> is a standardized exterior gateway protocol designed to exchange routing and reachability information among autonomous systems (AS) on the Internet. The protocol is often classified as a path vector protocol but is sometimes also classed as a distance-vector routing protocol. The Border Gateway Protocol makes routing decisions based on paths, network policies, or rule-sets configured by a network administrator and is involved in making core routing decisions. | ||
| − | == | + | ====General Settings==== |
| − | |||
| − | = | ||
---- | ---- | ||
| − | ''' | + | Below is an example of BGP '''General''' settings section. |
| − | + | [[File:Networking_rutos_manual_routing_dynamic_routes_bgp_general_settings_v1.png|border|class=tlt-border]] | |
| − | |||
| − | |||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
| − | <th> | + | <th>Field</th> |
| − | <th> | + | <th>Value</th> |
| − | <th> | + | <th>Description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles the BGP protocol | + | <td>Toggles the BGP protocol on or off</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable vty</td> | <td>Enable vty</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles vty access | + | <td>Toggles vty access on or off</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 351: | Line 359: | ||
====BGP Instance==== | ====BGP Instance==== | ||
| − | ----Below is an example of '''BGP Instance''' settings section.[[File: | + | ---- |
| − | + | Below is an example of '''BGP Instance''' settings section. | |
| + | |||
| + | [[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance_v1.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
| − | <th> | + | <th>Field</th> |
| − | <th> | + | <th>Value</th> |
| − | <th> | + | <th>Description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles the BGP instance | + | <td>Toggles the BGP instance on or off</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>AS</td> | <td>AS</td> | ||
| − | <td> | + | <td>default: <b>none</b></td> |
<td>AS number is an identification of an autonomous system. BGP protocol uses the AS number for detecting whether the BGP connection is an internal one or external one. '''[Required]'''</td> | <td>AS number is an identification of an autonomous system. BGP protocol uses the AS number for detecting whether the BGP connection is an internal one or external one. '''[Required]'''</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>BGP router ID</td> | <td>BGP router ID</td> | ||
| − | <td> | + | <td>default: <b>none</b></td> |
| − | <td>The router id is used by BGP to identify the routing device from which a packet originated. | + | <td>The router id is used by BGP to identify the routing device from which a packet originated. default router ID value is selected as the largest IP Address of the interface.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Network</td> | <td>Network</td> | ||
| − | <td> | + | <td>default: <b>none</b></td> |
<td>Add an announcement network(s)</td> | <td>Add an announcement network(s)</td> | ||
| − | </tr><tr><td>Redistribution options</td><td> | + | </tr> |
| + | <tr> | ||
| + | <td>Redistribution options</td> | ||
| + | <td>default: <b>none</b></td> | ||
| + | <td>'''Route redistribution''' is a process that allows a network to use a '''routing''' protocol to dynamically '''route''' traffic based on information learned from a different '''routing''' protocol.</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>Deterministic</td> | ||
| + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> | ||
| + | <td>Compare MED between same AS ignoring their age</td> | ||
| + | </tr> | ||
| + | </table> | ||
| − | + | ====BGP Peers==== | |
| − | + | ---- | |
| − | + | Below is an example of <b>BGP Peers</b> section. You can create a new peer by clicking the 'Add' button. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | [[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_v1.png|border|class=tlt-border]] | |
| − | |||
| − | |||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
| − | <th> | + | <th>Field</th> |
| − | <th> | + | <th>Value</th> |
| − | <th> | + | <th>Description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles the BGP peer | + | <td>Toggles the BGP peer on or off</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Remote AS</td> | <td>Remote AS</td> | ||
| − | <td> | + | <td>default: <b>none</b></td> |
<td>Neighbour's remote AS</td> | <td>Neighbour's remote AS</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Remote address</td> | <td>Remote address</td> | ||
| − | <td>IP; | + | <td>IP; default: <b>none</b></td> |
<td>Neighbour's remote IPv4 address</td> | <td>Neighbour's remote IPv4 address</td> | ||
</tr> | </tr> | ||
| Line 419: | Line 433: | ||
By pressing '''Edit''' button you can find more settings related to '''BGP Peer.''' | By pressing '''Edit''' button you can find more settings related to '''BGP Peer.''' | ||
| − | [[File: | + | [[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_bgp_peer_v1.png|border|class=tlt-border]] |
| − | + | <table class="nd-mantable"> | |
<tr> | <tr> | ||
| − | <th> | + | <th>Field</th> |
| − | <th> | + | <th>Value</th> |
| − | <th> | + | <th>Description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles BGP Peer | + | <td>Toggles BGP Peer on or off</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Remote AS</td> | <td>Remote AS</td> | ||
| − | <td> | + | <td>default: <b>none</b></td> |
<td>Neighbour's remote AS</td> | <td>Neighbour's remote AS</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Remote address</td> | <td>Remote address</td> | ||
| − | <td>IP; | + | <td>IP; default: <b>none</b></td> |
<td>Neighbour's remote IPv4 address</td> | <td>Neighbour's remote IPv4 address</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Remote port</td> | <td>Remote port</td> | ||
| − | <td> | + | <td>default: <b>none</b></td> |
| − | <td>Neighbour's remote port | + | <td>Neighbour's remote port</td> |
| − | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>EBGP Multihop</td> | <td>EBGP Multihop</td> | ||
| − | <td> | + | <td>default: <b>none</b></td> |
<td>Time to Live value</td> | <td>Time to Live value</td> | ||
| − | </tr><tr><td> | + | </tr> |
| − | </td></tr></table> | + | <tr> |
| + | <td>default originate</td> | ||
| + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> | ||
| + | <td>Announce default routes to the peer</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>Description</td> | ||
| + | <td>default: <b>none</b></td> | ||
| + | <td>You can leave notes here</td> | ||
| + | </tr> | ||
| + | </table> | ||
====BGP Peer Groups==== | ====BGP Peer Groups==== | ||
---- | ---- | ||
Below is an example of '''BGP Peer Groups''' section. You can create a new group by writing a name and pressing '''Add''' button. | Below is an example of '''BGP Peer Groups''' section. You can create a new group by writing a name and pressing '''Add''' button. | ||
| − | [[File: | + | |
| + | [[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_v1.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
| − | <th> | + | <th>Field</th> |
| − | <th> | + | <th>Value</th> |
| − | <th> | + | <th>Description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Remote AS</td> | <td>Remote AS</td> | ||
| − | <td> | + | <td>default: <b>none</b></td> |
<td>Neighbour's remote AS</td> | <td>Neighbour's remote AS</td> | ||
</tr></table> | </tr></table> | ||
| − | By pressing | + | By pressing 'Edit' button you can find more settings related to '''BGP Peer Groups.''' |
| − | [[File: | + | [[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_bgp_peer_group_v1.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
| − | <th> | + | <th>Field</th> |
| − | <th> | + | <th>Value</th> |
| − | <th> | + | <th>Description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles the BGP Peer-Group | + | <td>Toggles the BGP Peer-Group on or off</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Remote AS</td> | <td>Remote AS</td> | ||
| − | <td> | + | <td>default: <b>none</b></td> |
<td>Neighbour's remote AS</td> | <td>Neighbour's remote AS</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Neighbor address</td> | <td>Neighbor address</td> | ||
| − | <td>IP; | + | <td>IP; default: <b>none</b></td> |
<td>Neighbour's remote IPv4 address</td> | <td>Neighbour's remote IPv4 address</td> | ||
| − | </tr><tr><td>Advertisement interval</td><td> | + | </tr> |
| + | <tr> | ||
| + | <td>Advertisement interval</td> | ||
| + | <td>default: <b>none</b></td> | ||
| + | <td>Delay between updates for a neighbor session</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>Neighbor configuration</td> | ||
| + | <td>default: '''None'''</td> | ||
| + | <td>Configure a neighbor as Route Reflector or Route Server client.</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>Disable next hop calculation</td> | ||
| + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> | ||
| + | <td>Disable the next hop calculation for this group</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>Inbound soft-reconfiguration</td> | ||
| + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> | ||
| + | <td>Allow inbound soft reconfiguration for this neighbor</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>Disable connected check</td> | ||
| + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> | ||
| + | <td>One-hop away EBGP peer using loopback address</td> | ||
| + | </tr> | ||
| + | </table> | ||
| + | |||
| + | ====Access List Filters==== | ||
| + | ---- | ||
| + | Below is an example of '''Access List Filters''' section. | ||
| + | |||
| + | [[File:Networking_rutos_manual_routing_dynamic_routes_bgp_access_list_filters_v1.png|border|class=tlt-border]] | ||
| − | + | You can add a new list by simply pressing '''Add''' button. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | [[File:Networking_rutos_manual_routing_dynamic_routes_bgp_access_list_filters_configuration_v1.png|border|class=tlt-border]] | |
| − | |||
| − | |||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
| − | <th> | + | <th>Field</th> |
| − | <th> | + | <th>Value</th> |
| − | <th> | + | <th>Description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles the Access filter | + | <td>Toggles the Access filter on or off</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Peer</td> | <td>Peer</td> | ||
| − | <td>bgp peer; | + | <td>bgp peer; default: '''first peer on list'''</td> |
| − | <td>Applies the rule for the specified peer</td> | + | <td>Applies the rule for the specified peer.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Action</td> | <td>Action</td> | ||
| − | <td> | + | <td>default: '''Permit'''</td> |
| − | <td>Denies or permits matched entry. | + | <td>Denies or permits matched entry.</td> |
| − | |||
| − | |||
| − | |||
| − | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Network</td> | <td>Network</td> | ||
| − | <td> | + | <td>default: '''Any'''</td> |
| − | <td>Applies filter rule for this source network. | + | <td>Applies filter rule for this source network.</td> |
| − | |||
| − | |||
| − | |||
| − | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Direction</td> | <td>Direction</td> | ||
| − | <td> | + | <td>default: '''Inbound'''</td> |
| − | <td> | + | <td>If direction is '''Inbound''', the access list is applied to input routes. If direction is '''Outbound''' the access list is applied to advertised routes.</td> |
| − | |||
| − | |||
| − | |||
| − | |||
| − | If direction is '''Inbound''', the access list is applied to input routes. If direction is '''Outbound''' the access list is applied to advertised routes | ||
| − | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
| Line 560: | Line 593: | ||
===RIP Protocol=== | ===RIP Protocol=== | ||
---- | ---- | ||
| − | The | + | The <b>Routing Information Protocol (RIP)</b> is one of the oldest distance-vector routing protocols which employ the hop count as a routing metric. RIP prevents routing loops by implementing a limit on the number of hops allowed in a path from source to destination. The maximum number of hops allowed for RIP is 15, which limits the size of networks that RIP can support. A hop count of 16 is considered an infinite distance and the route is considered unreachable. RIP implements the split horizon, route poisoning and holddown mechanisms to prevent incorrect routing information from being propagated. |
| + | |||
| + | ====General Settings==== | ||
| + | ---- | ||
| + | Below is an example of RIP '''General''' settings section. | ||
| − | + | [[File:Networking_rutos_manual_routing_dynamic_routes_rip_general_settings_v1.png|border|class=tlt-border]] | |
| − | |||
| − | |||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
| − | <th> | + | <th>Field</th> |
| − | <th> | + | <th>Value</th> |
| − | <th> | + | <th>Description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles RIP Protocol | + | <td>Toggles RIP Protocol on or off</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable vty</td> | <td>Enable vty</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles vty access | + | <td>Toggles vty access on or off</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Import config</td> | <td>Import config</td> | ||
<td>-</td> | <td>-</td> | ||
| − | <td>Uses imported RIP configurations</td> | + | <td>Uses imported RIP configurations.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Version</td> | <td>Version</td> | ||
| − | <td> | + | <td>default: '''2'''</td> |
| − | <td>Specifies the version of RIP. | + | <td>Specifies the version of RIP.</td> |
| − | |||
| − | |||
| − | |||
| − | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Neighbor</td> | <td>Neighbor</td> | ||
| − | <td> | + | <td>default: <b>none</b></td> |
<td>Neighbour IP addres</td> | <td>Neighbour IP addres</td> | ||
</tr> | </tr> | ||
| Line 604: | Line 635: | ||
====RIP Interfaces==== | ====RIP Interfaces==== | ||
| − | ----Below is an example of '''RIP Interfaces''' settings section.[[File: | + | ---- |
| − | + | Below is an example of '''RIP Interfaces''' settings section. | |
| + | |||
| + | [[File:Networking_rutos_manual_routing_dynamic_routes_rip_rip_interfaces_v1.png|border|class=tlt-border]] | ||
| + | |||
| + | [[File:Networking_rutos_manual_routing_dynamic_routes_rip_rip_interfaces_configuration_v1.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
| − | <th> | + | <th>Field</th> |
| − | <th> | + | <th>Value</th> |
| − | <th> | + | <th>Description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles RIP Interface | + | <td>Toggles RIP Interface on or off</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Interface</td> | <td>Interface</td> | ||
| − | <td>network interfaces; | + | <td>network interfaces; default: '''loopback'''</td> |
<td>Network interface to be used with the RIP interface</td> | <td>Network interface to be used with the RIP interface</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Passive interface</td> | <td>Passive interface</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
<td>Sets the specified interface to passive mode. On passive mode interface, all receiving packets are processed as normal and ripd does not send either multicast or unicast RIP packets | <td>Sets the specified interface to passive mode. On passive mode interface, all receiving packets are processed as normal and ripd does not send either multicast or unicast RIP packets | ||
</td> | </td> | ||
| Line 632: | Line 667: | ||
====Access list filters==== | ====Access list filters==== | ||
| − | ----Below is an example of '''Access list filters''' settings section.[[File: | + | ---- |
| − | + | Below is an example of '''Access list filters''' settings section. | |
| + | |||
| + | [[File:Networking_rutos_manual_routing_dynamic_routes_rip_access_list_filters_v1.png|border|class=tlt-border]] | ||
| + | |||
| + | [[File:Networking_rutos_manual_routing_dynamic_routes_rip_access_list_filters_configuration_v1.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
| − | <th> | + | <th>Field</th> |
| − | <th> | + | <th>Value</th> |
| − | <th> | + | <th>Description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles the Access filter | + | <td>Toggles the Access filter on or off</td> |
| − | </tr><tr><td>RIP interface</td><td>RIP interface; | + | </tr> |
| − | </td><td>Applies the rule for the specified interface | + | <tr> |
| − | </td></tr><tr> | + | <td>RIP interface</td> |
| + | <td>RIP interface; default: '''first interface on list'''</td> | ||
| + | <td>Applies the rule for the specified interface</td> | ||
| + | </tr> | ||
| + | <tr> | ||
<td>Action</td> | <td>Action</td> | ||
| − | <td> | + | <td>default: '''Permit'''</td> |
| − | <td> | + | <td>Denies or permits matched entry</td> |
| − | |||
| − | |||
| − | |||
| − | |||
| − | Denies or permits matched entry | ||
| − | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Network</td> | <td>Network</td> | ||
| − | <td> | + | <td>default: '''Any'''</td> |
| − | <td>Applies filter rule for this source network. | + | <td>Applies filter rule for this source network.</td> |
| − | |||
| − | |||
| − | |||
| − | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Direction</td> | <td>Direction</td> | ||
| − | <td> | + | <td>default: '''Inbound'''</td> |
| − | <td> | + | <td>If direction is '''Inbound''', the access list is applied to input routes. If direction is '''Outbound''' the access list is applied to advertised routes.</td> |
| − | |||
| − | |||
| − | |||
| − | |||
| − | If direction is '''Inbound''', the access list is applied to input routes. If direction is '''Outbound''' the access list is applied to advertised routes | ||
| − | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
| Line 685: | Line 712: | ||
====General Settings==== | ====General Settings==== | ||
| − | ----Below is an example of OSPF '''General''' settings section.[[File: | + | ---- |
| − | + | Below is an example of OSPF '''General''' settings section. | |
| + | |||
| + | [[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_general_settings_v1.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
| − | <th> | + | <th>Field</th> |
| − | <th> | + | <th>Value</th> |
| − | <th> | + | <th>Description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles OSPF Protocol | + | <td>Toggles OSPF Protocol on or off</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable vty</td> | <td>Enable vty</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles vty access | + | <td>Toggles vty access on or off</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 711: | Line 740: | ||
<tr> | <tr> | ||
<td>Router ID</td> | <td>Router ID</td> | ||
| − | <td> | + | <td>default: <b>none</b></td> |
<td>Sets the router-ID of the OSPF process. The router-ID may be an IP address of the router, but need not be - it can be any arbitrary 32bit number</td> | <td>Sets the router-ID of the OSPF process. The router-ID may be an IP address of the router, but need not be - it can be any arbitrary 32bit number</td> | ||
</tr> | </tr> | ||
| Line 717: | Line 746: | ||
====OSPF Interface==== | ====OSPF Interface==== | ||
| − | ----Below is an example of '''OSPF Interface''' settings section.[[File: | + | ---- |
| − | + | Below is an example of '''OSPF Interface''' settings section. | |
| + | |||
| + | [[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_interface_v1.png|border|class=tlt-border]] | ||
| + | |||
| + | By pressing the '''Edit''' button you can find more settings related to '''OSPF Interface'''. | ||
| + | |||
| + | [[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_oqspf_interface_begin_to_edit_v1.png|border|class=tlt-border]] | ||
| + | |||
| + | You should directed to a window such as this: | ||
| + | |||
| + | [[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_oqspf_interface_configuration_v1.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
| − | <th> | + | <th>Field</th> |
| − | <th> | + | <th>Value</th> |
| − | <th> | + | <th>Description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles OSPF area | + | <td>Toggles OSPF area on or off</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
| − | + | <td>Cost</td> | |
| − | + | <td>default: <b>none</b></td> | |
| − | + | <td>The cost value is set to router-LSA’s metric field and used for SPF calculation</td> | |
| + | </tr> | ||
| + | <tr> | ||
| + | <td>Hello Interval</td> | ||
| + | <td>default: '''10'''</td> | ||
| + | <td>This value controls how frequently (every n seconds) a 'Hello' packet is sent out on the specified interface</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>Router Dead Interval</td> | ||
| + | <td>default: '''40'''</td> | ||
| + | <td>This value must be the same for all routers attached to a common network</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>Retransmit</td> | ||
| + | <td>default: '''5'''</td> | ||
| + | <td>This value is used when re-transmitting Database Description and Link State Request packets</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>Priority</td> | ||
| + | <td>default: '''1'''</td> | ||
| + | <td>The router with the highest priority will be more eligible to become Designated Router. Setting the value to 0, makes the router ineligible to become Designated Router</td> | ||
</tr> | </tr> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
<tr> | <tr> | ||
| − | < | + | <td>Type</td> |
| − | + | <td>default: <b>none</b></td> | |
| − | + | <td>OSPF interface configuration type.</td> | |
</tr> | </tr> | ||
<tr> | <tr> | ||
| − | + | <td>Authentication</td> | |
| − | + | <td>default: '''None'''</td> | |
| − | + | <td>Authentication method.</td> | |
| − | </tr> | + | </tr> |
| − | + | </table> | |
| − | + | ||
| − | + | ====OSPF Area==== | |
| + | ---- | ||
| + | Below is an example of '''OSPF Area''' settings section. | ||
| − | + | [[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_area_v1.png|border|class=tlt-border]] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | To add a new OSPF area, look to the 'Add New Area' section. Enter a custom name and click the 'Add' button. Your new area will appear in the 'OSPF Area' list. | |
| − | |||
| − | |||
| − | |||
| − | + | [[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_area_configuration_v1.png|border|class=tlt-border]] | |
| − | |||
| − | |||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
| − | <th> | + | <th>Field</th> |
| − | <th> | + | <th>Value</th> |
| − | <th> | + | <th>Description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles OSPF area | + | <td>Toggles OSPF area on or off</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Cost</td> | <td>Cost</td> | ||
| − | <td>IP; | + | <td>IP;default: <b>none</b></td> |
<td>Specifies OSPF area</td> | <td>Specifies OSPF area</td> | ||
</tr> | </tr> | ||
| Line 791: | Line 836: | ||
====OSPF Networks==== | ====OSPF Networks==== | ||
| − | ----Below is an example of '''OSPF Networks''' settings section.[[File: | + | ---- |
| − | + | Below is an example of '''OSPF Networks''' settings section. | |
| + | |||
| + | [[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_networks_v1.png|border|class=tlt-border]] | ||
| + | |||
| + | To add a new OSPF network, look to the 'Add New Network' section. Enter a custom name and click the 'Add' button. Your new network will appear in the 'OSPF Networks' list. | ||
| + | |||
| + | [[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_networks_configuration_v1.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
| − | <th> | + | <th>Field</th> |
| − | <th> | + | <th>Value</th> |
| − | <th> | + | <th>Description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles OSPF network | + | <td>Toggles OSPF network on or off</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Network</td> | <td>Network</td> | ||
| − | <td>[a.b.c.d/m]; | + | <td>[a.b.c.d/m]; default: <b>none</b></td> |
<td>This command specifies the OSPF enabled interface. If the interface has an address from the range '''a.b.c.d/m''' then enables OSPF on this interface so the router can provide network information to the other OSPF routers via this interface</td> | <td>This command specifies the OSPF enabled interface. If the interface has an address from the range '''a.b.c.d/m''' then enables OSPF on this interface so the router can provide network information to the other OSPF routers via this interface</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Area</td> | <td>Area</td> | ||
| − | <td>OSPF area; | + | <td>OSPF area; default: <b>none</b></td> |
<td>Specifies OSPF area</td> | <td>Specifies OSPF area</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
| − | ===EIGRP | + | ===EIGRP=== |
---- | ---- | ||
Enhanced Interior Gateway Routing Protocol (EIGRP) is an advanced distance-vector routing protocol that is used on a computer network for automating routing decisions and configuration. | Enhanced Interior Gateway Routing Protocol (EIGRP) is an advanced distance-vector routing protocol that is used on a computer network for automating routing decisions and configuration. | ||
| Line 823: | Line 874: | ||
====General==== | ====General==== | ||
---- | ---- | ||
| − | Below is an example of EIGRP '''General''' settings section. | + | Below is an example of EIGRP '''General''' settings section. |
| − | [[File: | + | |
| + | [[File:Networking_rutos_manual_routing_dynamic_routes_eigrp_general_settings_v1.png|border|class=tlt-border]] | ||
| + | |||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
| − | <th> | + | <th>Field</th> |
| − | <th> | + | <th>Value</th> |
| − | <th> | + | <th>Description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles EIGRP network | + | <td>Toggles EIGRP network on or off</td> |
| − | </tr><tr><td>Enable logging</td><td>off | on; | + | </tr> |
| − | </td></tr><tr><td>Router ID</td><td>IP; | + | <tr> |
| + | <td>Enable logging</td> | ||
| + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> | ||
| + | <td>Enable logging of EIGRP</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>AS</td> | ||
| + | <td>default: <b>none</b></td> | ||
| + | <td>'''EIGRP''' uses this number so that it makes sure it only talks to other EIGRP speakers that are in the same AS. For instance, if you have two routers, one with "router eigrp 1" and one with "router eigrp 2," then they would not form an adjacency</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>Router ID</td> | ||
| + | <td>IP; default: <b>none</b></td> | ||
| + | <td>'''EIGRP''' router-ID in IP address format</td> | ||
| + | </tr> | ||
| + | <tr> | ||
<td>Network</td> | <td>Network</td> | ||
| − | <td>IP; | + | <td>IP; default: <b>none</b></td> |
<td>The announcement network</td> | <td>The announcement network</td> | ||
| − | </tr><tr><td>Redistribution options</td><td> | + | </tr> |
| − | </td><td>'''Route redistribution''' is a process that allows a network to use a '''routing''' protocol to dynamically '''route''' traffic based on information learned from a different '''routing''' protocol. | + | <tr> |
| − | + | <td>Redistribution options</td> | |
| − | + | <td>default: <b>none</b></td> | |
| − | + | <td>'''Route redistribution''' is a process that allows a network to use a '''routing''' protocol to dynamically '''route''' traffic based on information learned from a different '''routing''' protocol.</td> | |
| − | + | </tr> | |
| − | + | <tr> | |
| − | |||
| − | |||
| − | |||
<td>Neighbors</td> | <td>Neighbors</td> | ||
| − | <td>IP; | + | <td>IP; default: <b>none</b></td> |
<td>Neighbour IP addres</td> | <td>Neighbour IP addres</td> | ||
</tr> | </tr> | ||
| Line 857: | Line 922: | ||
===NHRP Protocol=== | ===NHRP Protocol=== | ||
| − | ----Next Hop Resolution Protocol (NHRP) is a protocol or method that can be used so that a computer sending data to another computer can learn the most direct route (the fewest number of hops) to the receiving computer. | + | ---- |
| + | Next Hop Resolution Protocol (NHRP) is a protocol or method that can be used so that a computer sending data to another computer can learn the most direct route (the fewest number of hops) to the receiving computer. | ||
====General Settings==== | ====General Settings==== | ||
| − | ----Below is an example of NHRP '''General''' settings section.[[File: | + | ---- |
| + | Below is an example of NHRP '''General''' settings section. | ||
| + | |||
| + | [[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_general_settings_v1.png|border|class=tlt-border]] | ||
| + | |||
| + | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
| − | <th> | + | <th>Field</th> |
| − | <th> | + | <th>Value</th> |
| − | <th> | + | <th>Description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable service</td> | <td>Enable service</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles NHRP network | + | <td>Toggles NHRP network on or off</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable logging</td> | <td>Enable logging</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles NHRP logging | + | <td>Toggles NHRP logging on or off</td> |
</tr></table> | </tr></table> | ||
====Interfaces==== | ====Interfaces==== | ||
| − | ----Below is an example of NHRP | + | ---- |
| − | [[File: | + | Below is an example of NHRP <b>Interfaces</b> settings section. |
| + | |||
| + | [[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_v1.png|border|class=tlt-border]] | ||
| + | |||
| + | [[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_begin_to_edit_v1.png|border|class=tlt-border]] | ||
| + | |||
| + | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
| − | <th> | + | <th>Field</th> |
| − | <th> | + | <th>Value</th> |
| − | <th> | + | <th>Description</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
| − | <td>off | on; | + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> |
| − | <td>Toggles interface | + | <td>Toggles interface on or off</td> |
</tr></table> | </tr></table> | ||
| + | |||
| + | =====NHRP Interface Configuration===== | ||
| + | ---- | ||
By pressing '''Edit''' button you can find more settings related to '''NHRP Interface.''' | By pressing '''Edit''' button you can find more settings related to '''NHRP Interface.''' | ||
| − | [[File: | + | [[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_interface_configuration_v1.png|border|class=tlt-border]] |
| − | <table class="nd-mantable"><tr><th> | + | |
| − | </td><td>Interface which will be using NHRP</td></tr><tr><td>Network ID</td><td> | + | <table class="nd-mantable"> |
| − | </td><td>Network ID of NHRP</td></tr><tr><td>NHS</td><td> | + | <tr> |
| − | </td><td>IP address of Next-Hop Server. | + | <th>Field</th> |
| + | <th>Value</th> | ||
| + | <th>Description</th> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>Enabled</td> | ||
| + | <td>off <nowiki>|</nowiki> on; default: <b>off</b> | ||
| + | </td><td>Enables DMVPN client</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>Interface</td> | ||
| + | <td>default: <b>br-lan</b></td> | ||
| + | <td>Interface which will be using NHRP</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>Network ID</td> | ||
| + | <td>default: <b>none</b></td> | ||
| + | <td>Network ID of NHRP</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>NHS</td> | ||
| + | <td>Dynamic <nowiki>|</nowiki> custom; default: <b>none</b></td> | ||
| + | <td>IP address of Next-Hop Server.</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>NBMA</td> | ||
| + | <td>default: <b>none</b></td> | ||
| + | <td>Non-Broadcast Multi-Access(NBMA) network IP address</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>Hold-time</td> | ||
| + | <td>default: '''7200'''</td> | ||
| + | <td>Specifies the holding time for NHRP Registration Requests and Resolution Replies sent from this interface or shortcut-target. The holdtime is specified in seconds and defaults to two hours.</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>IPsec support</td> | ||
| + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> | ||
| + | <td>Use NHRP over IPsec</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>IP address</td> | ||
| + | <td>IP; default: <b>none</b></td> | ||
| + | <td>Network ID of NHRP</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>NBMA</td> | ||
| + | <td>IP; default: <b>none</b></td> | ||
| + | <td>IP address of Next-Hop Server</td> | ||
| + | </tr> | ||
| + | </table> | ||
| + | |||
| + | =====NHRP Mappings Configuration===== | ||
| + | ---- | ||
| − | + | [[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_nhrp_mappings_configuration_v1.png|border|class=tlt-border]] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | --> | + | [[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_nhrp_mappings_configuration_edit_v1.png|border|class=tlt-border]] |
| + | |||
| + | <table class="nd-mantable"> | ||
| + | <tr> | ||
| + | <th>Field</th> | ||
| + | <th>Value</th> | ||
| + | <th>Description</th> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>Enabled</td> | ||
| + | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> | ||
| + | <td>Turns this mapping configuration on or off.</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>IP Address</td> | ||
| + | <td>ip; default: <b>none</b></td> | ||
| + | <td>Network ID of another NHRP.</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>NBMA</td> | ||
| + | <td>ip; default: <b>none</b></td> | ||
| + | <td>IP address of next-hop server.</td> | ||
| + | </tr> | ||
| + | </table>|}} | ||
| + | [[Category:{{{name}}} Network section]] | ||
Revision as of 16:54, 14 May 2020
Template:Networking rutos manual fw disclosure
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 {{{name}}} 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.
File:Networking rutos manual routing static routes static ipv4 routes v1.png
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.
File:Networking rutos manual routing static routes static ipv4 routes new route v1.png
| Field | Value | Description |
|---|---|---|
| Interface | network interface; default: lan | The zone where the target network resides |
| Target* | ip4; default: none | The address of a destination network. |
| 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:
|
*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.
File:Networking rutos manual routing static routes static ipv6 routes v1.png
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.
File:Networking rutos manual routing static routes static ipv4 routes new route v1.png
| Field | Value | Description |
|---|---|---|
| Interface | network interface; default: lan | The zone where the target network resides |
| Target | ip6; default: none | The address of a destination network. |
| 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:
|
Advanced Static Routes
The Advanced Static Routes 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.
File:Networking rutos manual routing advanced static routes routing tables v1.png
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.
File:Networking rutos manual routing advanced static routes add new routing table v1.gif
Refer to the table below for information on configuration fields for routing tables.
| Field | Value | Description |
|---|---|---|
| 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. |
| Name of Table | string; default: none | A custom name 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.
File:Networking rutos manual routing advanced static routes routing rules for ipv4 settings v1.png
| 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 | 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. |
[[Category:{{{name}}} Network section]]
