Template:Networking rutos manual routing: Difference between revisions
No edit summary |
No edit summary |
||
(41 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
{{Template:Networking_rutos_manual_fw_disclosure | {{Template: Networking_rutos_manual_fw_disclosure | ||
| fw_version = {{{series}}} | | fw_version ={{Template: Networking_rutos_manual_latest_fw | ||
| | | series = {{{series}}} | ||
| name = {{{name}}} | |||
}} | |||
}} | }} | ||
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} Routing (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}} | |||
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} Routing (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}} | |||
==Summary== | ==Summary== | ||
The <b>Routing</b> page is used to set up static {{#ifeq:{{{ | The <b>Routing</b> page is used to set up static {{#ifeq:{{{dynamic}}}|1|and dynamic|}} routes, routing tables and rules. | ||
This manual page provides an overview of the Routing windows in {{{name}}} devices. | This manual page provides an overview of the Routing windows in {{{name}}} devices. | ||
Line 24: | Line 27: | ||
The <b>Static IPv4 Routes</b> 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. | The <b>Static IPv4 Routes</b> 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: | [[File:Networking_rutos_manual_routing_static_routes_static_ipv4_routes.png|border|class=tlt-border]] | ||
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. | 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: | [[File:Networking_rutos_manual_routing_static_routes_static_ipv4_routes_new_route.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 39: | Line 42: | ||
<td>Interface</td> | <td>Interface</td> | ||
<td>network interface; default: <b>lan</b></td> | <td>network interface; default: <b>lan</b></td> | ||
<td> | <td>Network interface of the target network.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Target<span class="asterisk">*</span></td> | <td>Target<span class="asterisk">*</span></td> | ||
<td>ip4; default: <b>none</b></td> | <td>ip4; default: <b>none</b></td> | ||
<td> | <td>Destination network address.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 78: | Line 81: | ||
<li><b>prohibit</b> - 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.</li> | <li><b>prohibit</b> - 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.</li> | ||
<li><b>blackhole</b> - packets that match this type of route are discarded without any response.</li> | <li><b>blackhole</b> - packets that match this type of route are discarded without any response.</li> | ||
<li><b>anycast</b> - provides a possibility to route incoming requests to | <li><b>anycast</b> - provides a possibility to route incoming requests to multiple different network locations.</li> | ||
<li><b>-- custom --</b> - does not use any of the predefined route types.</li> | <li><b>-- custom --</b> - does not use any of the predefined route types.</li> | ||
</ul> | </ul> | ||
Line 133: | Line 136: | ||
The <b>Static IPv6 Routes</b> 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. | The <b>Static IPv6 Routes</b> 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: | [[File:Networking_rutos_manual_routing_static_routes_static_ipv6_routes.png|border|class=tlt-border]] | ||
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. | 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: | [[File:Networking_rutos_manual_routing_static_routes_static_ipv6_routes_new_route.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 148: | Line 151: | ||
<td>Interface</td> | <td>Interface</td> | ||
<td>network interface; default: <b>lan</b></td> | <td>network interface; default: <b>lan</b></td> | ||
<td> | <td>Network interface of the target network.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Target</td> | <td>Target</td> | ||
<td>ip6; default: <b>none</b></td> | <td>ip6; default: <b>none</b></td> | ||
<td> | <td>Destination network address.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 182: | Line 185: | ||
<li><b>prohibit</b> - 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.</li> | <li><b>prohibit</b> - 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.</li> | ||
<li><b>blackhole</b> - packets that match this type of route are discarded without any response.</li> | <li><b>blackhole</b> - packets that match this type of route are discarded without any response.</li> | ||
<li><b>anycast</b> - provides a possibility to route incoming requests to | <li><b>anycast</b> - provides a possibility to route incoming requests to multiple different network locations.</li> | ||
<li><b>-- custom --</b> - does not use any of the predefined route types.</li> | <li><b>-- custom --</b> - does not use any of the predefined route types.</li> | ||
</ul> | </ul> | ||
Line 199: | Line 202: | ||
The 'Routing Tables' section displays user created routing tables. By default, the list is empty. | The 'Routing Tables' section displays user created routing tables. By default, the list is empty. | ||
[[File: | [[File:Networking_rutos_manual_routing_advanced_static_routes_routing_tables.png|border|class=tlt-border]] | ||
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. | 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: | [[File:Networking_rutos_manual_routing_advanced_static_routes_add_new_routing_table.gif]] | ||
Refer to the table below for information on configuration fields for routing tables. | Refer to the table below for information on configuration fields for routing tables. | ||
Line 214: | Line 217: | ||
<th>Value</th> | <th>Value</th> | ||
<th>Description</th> | <th>Description</th> | ||
</tr> | |||
<tr> | |||
<td>Name of Table</td> | |||
<td>string; default: <b>none</b></td> | |||
<td>A custom name for the table. A table can be invoked by the both its ID or name.</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>ID of Table</td> | <td>ID of Table</td> | ||
<td>integer [1..252]; default: <b>none</b></td> | <td>integer [1..252]; default: <b>none</b></td> | ||
<td>Unique numerical identifier for the table. | <td>Unique numerical identifier for the table. A table can be invoked by the both its ID or name.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
Line 231: | Line 234: | ||
<b>Routing Rules</b> 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. | <b>Routing Rules</b> 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. | ||
[[File: | [[File:Networking_rutos_manual_routing_advanced_static_routes_routing_rules_for_ipv4_v1_begin_to_edit.gif]] | ||
---- | ---- | ||
Refer to table below for information on each configuration field. | Refer to table below for information on each configuration field. | ||
[[File: | [[File:Networking_rutos_manual_routing_advanced_static_routes_routing_rules_for_ipv4_settings.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 305: | Line 308: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td | <td><span style="color: #0054A6;">Routing Action</span></td> | ||
<td>Prohibit | Unreachable | Blackhole | Throw; default: <b>Prohibit</b></td> | <td>Prohibit | Unreachable | Blackhole | Throw; default: <b>Prohibit</b></td> | ||
<td>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 <i>Routing Action</i>.</td> | <td>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 <i>Routing Action</i>.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
{{#ifeq: {{{dynamic}}} | 1 | | |||
==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. | |||
{{#ifeq: {{{series}}} | RUTX | | | |||
<u><b> | |||
Note:</b> Dynamic Routing is additional software that can be installed from the <b>Services → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u> | |||
}} | |||
===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==== | ||
= | |||
---- | ---- | ||
The <b>General Settings</b> section is used to turn BGP protocol usage on or off or to upload an external BGP configuration. Below is an example of the BGP General Settings section. | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_general_settings.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 | <td>off {{!}} on; default: <b>off</b></td> | ||
<td> | <td>Turns BGP protocol usage on or off.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable vty</td> | <td>Enable vty</td> | ||
<td>off | <td>off {{!}} on; default: <b>off</b></td> | ||
<td> | <td>Turns vty access on or off.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Import config</td> | <td>Import config</td> | ||
<td>-</td> | <td>- (interactive button)</td> | ||
<td>Uploads an external BGP configuration</td> | <td>Uploads an external BGP configuration.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
====BGP Instance==== | ====BGP Instance==== | ||
----Below is an example of | ---- | ||
The <b>BGP Instance</b> section is used to configure some of the main operating parameters of the BGP protocol. Below is an example of the BGP Instance section. | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance.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 | <td>off {{!}} on; default: <b>off</b></td> | ||
<td> | <td>Turns the BGP instance on or off.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>AS</td> | <td>AS</td> | ||
<td> | <td>integer [1..65535]default: <b>none</b></td> | ||
<td>BGP Autonomous System (AS) number. It is an identifier that represents a routing domain; BGP routers can exchange routes within the same Autonomous System.</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>BGP router ID</td> | <td>BGP router ID</td> | ||
<td> | <td>32-bit integer; default: <b>none</b></td> | ||
<td>The router | <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>ip/netmask; default: <b>none</b></td> | ||
<td> | <td>Adds an announcement network(s). Routes to these networks will be shared over BGP.</td> | ||
</tr><tr><td>Redistribution options</td><td> | </tr> | ||
<tr> | |||
<td>Redistribution options</td> | |||
<td>Connected routes {{!}} Kernel added routes {{!}} NHRP routes {{!}} OSPF routes {{!}} Static routes {{!}} custom; default: <b>none</b></td> | |||
<td>Distributes selected routes. Route redistribution is a process that allows a network to use a routing protocol to dynamically route traffic based on information learned from a separate routing protocol.</td> | |||
</tr> | |||
<tr> | |||
<td>Deterministic MED</td> | |||
<td>off {{!}} on; default: <b>off</b></td> | |||
<td>Compares MEDs between same AS, while ignoring their age.</td> | |||
</tr> | |||
</table> | |||
====BGP Peers==== | |||
---- | |||
<b>BGP Peers</b> are routers in the same BGP Peer Group that can redistribute routes among other BGP Peers. Below is an example of the BGP Peers section, which is empty by default. | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers.png|border|class=tlt-border]] | |||
To create a new Peer, look to the Add New Instance section under BGP Peer; type in a custom name for the BGP Peer and click the 'Add' button: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_add_button.png|border|class=tlt-border]] | |||
The newly added BGP Peer configuration should look similar to this: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_added.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> | <td>Remote AS</td> | ||
<td> | <td>integer [1..65535]; default: <b>none</b></td> | ||
<td> | <td>Remote autonomous system number of this remote BGP Neighbor.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Remote address</td> | |||
<td>ip4; default: <b>none</b></td> | |||
<td>IPv4 address of this remote BGP Neighbor.</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | |||
<td>off {{!}} on; default: <b>off</b></td> | |||
<td>Turns turns this BGP peer on or off.</td> | |||
</tr> | </tr> | ||
</table> | </table> | ||
To see more settings for a BGP Peer, click the 'Edit' button next to it: | |||
[[File: | [[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_edit_button.png|border|class=tlt-border]] | ||
The full BGP Peer configuration page should look similar to this: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_bgp_peer_v2.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 | <td>off {{!}} on; default: <b>off</b></td> | ||
<td> | <td>Turns this BGP peer on or off.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Remote AS</td> | <td>Remote AS</td> | ||
<td> | <td>integer [1..65535]; default: <b>none</b></td> | ||
<td> | <td>Remote autonomous system number of this remote BGP Neighbor.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Remote address</td> | <td>Remote address</td> | ||
<td> | <td>ip4; default: <b>none</b></td> | ||
<td> | <td>IPv4 address of this remote BGP Neighbor.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Remote port</td> | <td>Remote port</td> | ||
<td> | <td>integer [0..65535]; default: <b>none</b></td> | ||
<td> | <td>Listening port number of the BGP Neighbor.</td> | ||
</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>EBGP Multihop</td> | <td>EBGP Multihop</td> | ||
<td> | <td>integer; default: <b>none</b></td> | ||
<td>Time to Live value</td> | <td>Time to Live value for packets associated with this remote BGP Neighbor.</td> | ||
</tr><tr><td>Default originate</td><td>off | </tr> | ||
</td></tr></table> | <tr> | ||
<td>Keepalive timer</td> | |||
<td>integer [0..65535]; default: <b>none</b></td> | |||
<td>Frequency (in seconds) of keep alive messages.</td> | |||
</tr> | |||
<tr> | |||
<td>Holdtime</td> | |||
<td>integer [0..65535]; default: <b>none</b></td> | |||
<td>Max wait time (in seconds) for a response from this neighbor before considering the peer unreachable.</td> | |||
</tr> | |||
<tr> | |||
<td>Connect timer</td> | |||
<td>integer [1..65535]; default: <b>none</b></td> | |||
<td>Max time (in seconds) to make a connection to this peer. If a connection cannot be made in this time, connection to this peer is considered unsuccessful.</td> | |||
</tr> | |||
<tr> | |||
<td>Default originate</td> | |||
<td>off {{!}} on; default: <b>off</b></td> | |||
<td>Announces default routes to this peer.</td> | |||
</tr> | |||
<tr> | |||
<td>Description</td> | |||
<td>string; default: <b>none</b></td> | |||
<td>A custom description for this BGP peer. Used for easier management purposes only.</td> | |||
</tr> | |||
<tr> | |||
<td>Password</td> | |||
<td>string; default: <b>none</b></td> | |||
<td>Password for this BGP Neighbor.</td> | |||
</tr> | |||
</table> | |||
====BGP Peer Groups==== | ====BGP Peer Groups==== | ||
---- | ---- | ||
A <b>BGP Peer Group</b> is a collection of routers that use the BGP protocol to dynamically redistribute routes among peers (other routers). The figure below is an example of the BGP Peer Groups section, which is empty by default. | |||
[[File: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups.png|border|class=tlt-border]] | |||
To create a new Peer Group, look to the Add New Instance section under BGP Peer Groups; type in a custom name for the BGP Peer Group and click the 'Add' button: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_add_button.png|border|class=tlt-border]] | |||
The newly added BGP Peer Group configuration should look similar to this: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_added.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>integer [1..65535]; default: <b>none</b></td> | ||
<td> | <td>Remote autonomous system number.</td> | ||
</tr></table> | </tr> | ||
</table> | |||
To see more settings for a BGP Peer Group, click the 'Edit' button next to it: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_edit_button.png|border|class=tlt-border]] | |||
The full BGP Peer Group configuration page should look similar to this: | |||
[[File: | [[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_bgp_peer_group.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 | <td>off {{!}} on; default: <b>off</b></td> | ||
<td> | <td>Turns the BGP Peer Group configuration on or off.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Remote AS</td> | <td>Remote AS</td> | ||
<td> | <td>integer [1..65535]; default: <b>none</b></td> | ||
<td> | <td>Remote autonomous system number.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Neighbor address</td> | <td>Neighbor address</td> | ||
<td> | <td>ip4; default: <b>none</b></td> | ||
<td> | <td>IPv4 address(es) of a remote BGP Neighbor.</td> | ||
</tr><tr><td>Advertisement interval</td><td> | </tr> | ||
<tr> | |||
<td>Advertisement interval</td> | |||
<td>integer; default: <b>none</b></td> | |||
<td>BGP advertisement frequency (in seconds).</td> | |||
</tr> | |||
<tr> | |||
<td>Neighbor configuration</td> | |||
<td>None {{!}} Route Reflector client {{!}} Route Server client; default: <b>None</b></td> | |||
<td>Defines the role of a BGP Neighbor. | |||
<ul> | |||
<li><b>Route Reflector client</b> - redistributes received routes.</li> | |||
<li><b>Route Server client</b> - distributes routes.</li> | |||
</ul> | |||
</td> | |||
</tr> | |||
<tr> | |||
<td>Disable next hop calculation</td> | |||
<td>off {{!}} <span style="color: blue;"><b>on</b></span>; default: <b>off</b></td> | |||
<td>Turns next hop calculation for this BGP Peer Group on or off.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color: blue;">Disable next hop calculation:</span> Apply also to ibgp-learned routes</td> | |||
<td>off {{!}} on; default: <b>off</b></td> | |||
<td>When acting as a route reflector, applies to ibgp-learned routes as well. This field becomes visible when 'Disable next hop calculation' is turned on.</td> | |||
</tr> | |||
<tr> | |||
<td>Inbound soft-reconfiguration</td> | |||
<td>off {{!}} on; default: <b>off</b></td> | |||
<td>Turns inbound soft-reconfiguration for this Neighbor on or off.</td> | |||
</tr> | |||
<tr> | |||
<td>Disable connected check</td> | |||
<td>off {{!}} on; default: <b>off</b></td> | |||
<td>When turned on, Disable connected check enables a directly connected eBGP Neighbor to peer using a loopback address without adjusting the default TTL of 1.</td> | |||
</tr> | |||
</table> | |||
====Access List Filters==== | |||
---- | |||
The <b>Access List Filters</b> section is used to configure special filters that restrict or allow access to specified networks for BGP Peers. Below is an example of the Access List Filters section which is empty by default. You can add a new filter by clicking the 'Add' button | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_access_list_filters_add_button.png|border|class=tlt-border]] | |||
An Access List Filter configuration for BGP should look similar to this: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_access_list_filters_configuration.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>Peer</td> | <td>Peer</td> | ||
<td>bgp peer; | <td>bgp peer; default: <b>none</b></td> | ||
<td>Applies the rule for the specified peer</td> | <td>Applies the filter rule for the specified peer.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Action</td> | <td>Action</td> | ||
<td> | <td>Permit {{!}} Deny; default: <b>Permit</b></td> | ||
<td> | <td>When BGP traffic matches this rule, the device will take the action specified in this field, which is to either allow or block traffic.</td> | ||
</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Network</td> | <td>Network</td> | ||
<td> | <td>ip/netmask {{!}} Any; default: <b>Any</b></td> | ||
<td> | <td>Matches traffic destined or originating from (depends on 'Direction' selection) to the network specified in this field.</td> | ||
</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Direction</td> | <td>Direction</td> | ||
<td> | <td>Inbound {{!}} Outbound; default: <b>Inbound</b></td> | ||
<td> | <td>Matches network traffic direction, which can either be traffic destined to this device (Inbound) or traffic originating from this device (Outbound).</td> | ||
</tr> | |||
<tr> | |||
<td>Enable</td> | |||
<td>off {{!}} on; default: <b>off</b></td> | |||
<td>Turns an Access filter on or off.</td> | |||
</td> | |||
</tr> | </tr> | ||
</table> | </table> | ||
===RIP | ===RIP=== | ||
---- | ---- | ||
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==== | ====General Settings==== | ||
----Below is an example of RIP | ---- | ||
The <b>General Settings</b> section is used to configure some of the main operating parameters of the RIP protocol. Below is an example of the RIP General Settings section. | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_general_settings.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 | <td>off {{!}} on; default: <b>off</b></td> | ||
<td> | <td>Turns RIP Protocol usage on or off.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable vty</td> | <td>Enable vty</td> | ||
<td>off | <td>off {{!}} on; default: <b>off</b></td> | ||
<td> | <td>Turns vty access on or off.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Import config</td> | <td>Import config</td> | ||
<td>-</td> | <td>- (interactive button)</td> | ||
<td> | <td>Upload a external RIP configuration.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Version</td> | <td>Version</td> | ||
<td> | <td>2 {{!}} 1; default: <b>2</b></td> | ||
<td>Specifies the version of RIP. | <td>Specifies the used version of the RIP protocol.</td> | ||
</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Neighbor</td> | <td>Neighbor</td> | ||
<td> | <td>rip neighbor; default: <b>none</b></td> | ||
<td> | <td>Defines a RIP Neighbor(s).</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
====RIP Interfaces==== | ====RIP Interfaces==== | ||
----Below is an example of | ---- | ||
The <b>RIP Interfaces</b> section is used to define which existing network interfaces can participate in RIP communication. Below is an example of the RIP Interfaces section which is empty by default. | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_rip_interfaces.png|border|class=tlt-border]] | |||
To create a new RIP Interface, look to the Add New Interface section; enter a custom name and click the 'Add' button: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_rip_interfaces_add_button.png|border|class=tlt-border]] | |||
RIP Interface configuration should look similar to this: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_rip_interfaces_configuration.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 | <td>off {{!}} on; default: <b>off</b></td> | ||
<td> | <td>Turns a RIP Interface on or off.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Interface</td> | <td>Interface</td> | ||
<td>network | <td>network interface; default: <b>loopback</b></td> | ||
<td>Network interface | <td>Network interface that will be used with the RIP protocol.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Passive interface</td> | <td>Passive interface</td> | ||
<td>off | <td>off {{!}} 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 <b>ripd</b> does not send either multicast or unicast RIP packets.</td> | ||
</td> | |||
</tr> | </tr> | ||
</table> | </table> | ||
====Access list filters==== | ====Access list filters==== | ||
----Below is an example of | ---- | ||
The <b>Access List Filters</b> section is used to configure special filters that restrict or allow access to specified networks for RIP Neighbors. Below is an example of the Access List Filters section which is empty by default. | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_access_list_filters.png|border|class=tlt-border]] | |||
To add a new filter, look to the Add New Filter section; enter a custom name and click the 'Add' button: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_access_list_filters_add_button.png|border|class=tlt-border]] | |||
An Access List Filter configuration for RIP should look similar to this: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_access_list_filters_configuration.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> | |||
<td>Name</td> | |||
<td>string on; default: <b>none</b></td> | |||
<td>A custom name for a filter. Used for easier management purposes only.</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
<td>off | <td>off {{!}} on; default: <b>off</b></td> | ||
<td> | <td>Turns an Access filter on or off.</td> | ||
</tr><tr><td>RIP interface</td><td> | </tr> | ||
</td><td> | <tr> | ||
</td></tr><tr> | <td>RIP interface</td> | ||
<td>rip interface; default: <b>none</b></td> | |||
<td>Specifies the RIP interface to which the filter will apply to.</td> | |||
</tr> | |||
<tr> | |||
<td>Action</td> | <td>Action</td> | ||
<td> | <td>Permit {{!}} Deny; default: <b>Permit</b></td> | ||
<td> | <td>When RIP traffic matches this rule, the device will take the action specified in this field, which is to either allow or block traffic.</td> | ||
</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Network</td> | <td>Network</td> | ||
<td> | <td>ip/netmask {{!}} Any; default: <b>Any</b></td> | ||
<td> | <td>Matches traffic destined or originating from (depends on 'Direction' selection) to the network specified in this field.</td> | ||
</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Direction</td> | <td>Direction</td> | ||
<td> | <td>Inbound {{!}} Outbound; default: <b>Inbound</b></td> | ||
<td> | <td>Matches network traffic direction, which can either be traffic destined to this device (Inbound) or traffic originating from this device (Outbound).</td> | ||
</td> | |||
</tr> | </tr> | ||
</table> | </table> | ||
===OSPF | ===OSPF=== | ||
---- | ---- | ||
<b>Open Shortest Path First</b> (<b>OSPF</b>) is a routing protocol for Internet Protocol (IP) networks. It uses a link state routing (LSR) algorithm and falls into the group of interior gateway protocols (IGPs), operating within a single autonomous system (AS). It is defined as OSPF Version 2 in RFC 2328 for IPv4. | |||
====General Settings==== | ====General Settings==== | ||
----Below is an example of OSPF | ---- | ||
The <b>General Settings</b> section is used to configure some of the main operating parameters of the OSPF protocol. Below is an example of the OSPF General Settings section. | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_general_settings_v2.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 | <td>off {{!}} on; default: <b>off</b></td> | ||
<td> | <td>Turns OSPF Protocol usage on or off.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable vty</td> | <td>Enable vty</td> | ||
<td>off | <td>off {{!}} on; default: <b>off</b></td> | ||
<td> | <td>Turns vty access on or off.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Import</td> | <td>Import</td> | ||
<td>-</td> | <td>- (interactive)</td> | ||
<td> | <td>Uploads a external OSPF configuration.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Router ID</td> | <td>Router ID</td> | ||
<td> | <td>32-bit integer; default: <b>none</b></td> | ||
<td>Sets the router-ID | <td>Sets the router-ID in the OSPF network.</td> | ||
</tr> | |||
<tr> | |||
<td>Passive interfaces</td> | |||
<td>network interface(s); default: <b>none</b></td> | |||
<td>Network interfaces that should be considered as passive. OSPF hello packets are not sent on these interfaces.</td> | |||
</tr> | |||
<tr> | |||
<td>Generate a default external route</td> | |||
<td>off {{!}} default {{!}} always; default: <b>off</b></td> | |||
<td>Defines the behavior for advertising a default route over OSPF. Possible values are: | |||
<ul> | |||
<li><b>off</b> - does not advertise a default route.</li> | |||
<li><b>default</b> - advertises the default route if the route is in the routing table.</li> | |||
<li><b>always</b> - specifies to always advertise the default route regardless of whether the routing table has a default route.</li> | |||
</ul> | |||
</td> | |||
</tr> | |||
<tr> | |||
<td>Redistribution options</td> | |||
<td>Connected routes {{!}} Kernel {{!}} NHRP {{!}} BGP {{!}} OSPF {{!}} RIP {{!}} EIGRP {{!}} Static; default: <b>none</b></td> | |||
<td>Distributes selected routes. Route redistribution is a process that allows a network to use a routing protocol to dynamically route traffic based on information learned from a separate routing protocol.</td> | |||
</tr> | </tr> | ||
</table> | </table> | ||
====OSPF Interface==== | ====OSPF Interface==== | ||
----Below is an example of | ---- | ||
< | The <b>OSPF Interfaces</b> section is used to define which existing network interfaces can participate in OSPF communication. Below is an example of the OSPF Interfaces section which is empty by default. To create a new OSPF Interface, simply click the 'Add' button: | ||
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_interface_add_button.png|border|class=tlt-border]] | |||
OSPF Interface configuration should look similar to this: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_interface_begin_to_edit.png|border|class=tlt-border]] | |||
<table class="nd-mantable"> | |||
<tr> | |||
<th>Field</th> | |||
<th>Value</th> | |||
<th>Description</th> | |||
</tr> | |||
<tr> | |||
<td>Interface</td> | |||
<td>network interface; default: <b>loopback</b></td> | |||
<td>Network interface that will be used with the OSPF protocol.</td> | |||
</tr> | |||
<tr> | |||
<td>Enable</td> | |||
<td>off {{!}} on; default: <b>off</b></td> | |||
<td>Turns an OSPF Interface on or off.</td> | |||
</tr> | |||
</table> | |||
To see more settings for an OSPF interface, click the 'Edit' button next to it: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_interface_edit_button.png|border|class=tlt-border]] | |||
You should directed to a window such as this: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_interface_configuration_v2.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 | <td>off {{!}} on; default: <b>off</b></td> | ||
<td> | <td>Turns the OSPF area on or off.</td> | ||
</tr> | |||
<tr> | |||
<td>Cost</td> | |||
<td>integer [1..65535]; 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>integer [1..65535]; default: <b>10</b></td> | |||
<td>Frequency (in seconds) at which a "Hello" packet is sent out on the specified interface.</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Router Dead Interval</td> | |||
<td>integer [1..65535]; default: <b>40</b></td> | |||
<td>This value must be the same for all routers attached to a common OSPF network.</td> | |||
</tr> | |||
<tr> | |||
<td>Retransmit</td> | |||
<td>integer [0..65535]; default: <b>5</b></td> | |||
<td>Used in Database Description and Link State Request packet re-transmission.</td> | |||
</tr> | |||
<tr> | |||
<td>Priority</td> | |||
<td>integer [0..255]; default: <b>1</b></td> | |||
<td>OSPF router priority. The router with the highest priority will be more eligible to become the "Designated Router". Setting the value to 0, makes the router ineligible to become a "Designated Router."</td> | |||
</tr> | |||
<tr> | |||
<td>Type</td> | |||
<td>Broadcast {{!}} Non-Broadcast {{!}} Point-to-point {{!}} Point-to-Multipoint; default: <b>Broadcast </b></td> | |||
<td>OSPF interface configuration type.</td> | |||
</tr> | |||
<tr> | |||
<td>Authentication</td> | |||
<td>None {{!}} Password {{!}} MD5 HMAC; default: <b>None</b></td> | |||
<td>Specifies the Authentication method.</td> | |||
</tr> | </tr> | ||
</table> | </table> | ||
====OSPF Neighbors==== | |||
---- | |||
The <b>OSPF Neighbors</b> section can be used to configure other users ("neighbors") of the same OSPF network statically. | |||
[[File: | [[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_neighbor_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 | <td>off {{!}} on; default: <b>off</b></td> | ||
<td> | <td>Turns this OSPF neighbor configuration on or off.</td> | ||
</tr><tr><td> | </tr> | ||
</ | <tr> | ||
<td>Neighbor</td> | |||
< | <td>ip4; default: <b>none</b></td> | ||
<td>IP address of the OSPF neighbor.</td> | |||
</tr> | |||
<tr> | |||
<td>Neighbor Priority</td> | |||
<td>integer [1..255]; default: <b>none</b></td> | |||
<td>Priority of this neighbor</td> | |||
</tr> | |||
<tr> | |||
<td>Polling interval</td> | |||
<td>integer [1..65535]; default: <b>none</b></td> | |||
<td>Check for dead neighbor interval (in seconds).</td> | |||
</tr> | |||
</table> | |||
====OSPF Area==== | |||
---- | |||
An <b>OSPF Area</b> is a collection of OSPF Networks that can serve each other. Below is an example of the OSPF Area section which is empty by default. | |||
< | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_area.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. | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_area_add_button.png|border|class=tlt-border]] | |||
The newly added new Area will appear in the OSPF Area list. | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_area_configuration.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> | |||
<td>Name</td> | |||
<td>string on; default: <b>none</b></td> | |||
<td>A custom name for an OSPF Area. Used for easier management purposes only.</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Area</td> | ||
<td> | <td>32-bit integer; default: <b>none</b></td> | ||
<td> | <td>OSPF Area ID. OSPF Networks that are meant to communicate with each other should belong to the same Area (have the Area ID).</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Enable</td> | ||
<td> | <td>off {{!}} on; default: <b>off</b></td> | ||
<td> | <td>Turns an OSPF Area on or off.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
====OSPF Networks==== | ====OSPF Networks==== | ||
----Below is an example of | ---- | ||
The <b>OSPF Network</b> section is used to add networks to OSPF areas that can later be shared (provide access to) with other OSPF routers. | |||
Below is an example of the OSPF Area section which is empty by default. | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_networks.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. | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_network_add_button.png|border|class=tlt-border]] | |||
Your new network will appear in the OSPF Networks list | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_networks_configuration.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> | <td>Name</td> | ||
<td> | <td>string on; default: <b>none</b></td> | ||
<td> | <td>A custom name for an OSPF Area. Used for easier management purposes only.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Network</td> | <td>Network</td> | ||
<td> | <td>ip/netmask; default: <b>none</b></td> | ||
<td> | <td>IP address/netmask of a network. OSPF Network locations are shared with other OSPF routers.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Area</td> | <td>Area</td> | ||
<td>OSPF area; | <td>OSPF area; default: <b>none</b></td> | ||
<td> | <td>ID of an OSPF Area (to which this network should belong to).</td> | ||
</tr> | |||
<tr> | |||
<td>Enable</td> | |||
<td>off {{!}} on; default: <b>off</b></td> | |||
<td>Turns the usage of this network (in OSPF) on or off.</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 1,049: | ||
====General==== | ====General==== | ||
---- | ---- | ||
Below is an example of EIGRP | The <b>General Settings</b> section is used to configure some of the main operating parameters of the EIGRP protocol. Below is an example of the EIGRP General Settings section. | ||
[[File: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_eigrp_general_settings.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 | <td>off {{!}} on; default: <b>off</b></td> | ||
<td> | <td>Turns EIGRP protocol usage on or off.</td> | ||
</tr><tr><td>Enable logging</td><td>off | </tr> | ||
</td></tr><tr><td>Router ID</td><td> | <tr> | ||
<td>Enable logging</td> | |||
<td>off {{!}} on; default: <b>off</b></td> | |||
<td>Turns logging of EIGRP traffic on or off.</td> | |||
</tr> | |||
<tr> | |||
<td>AS</td> | |||
<td>integer [1..65535]; default: <b>none</b></td> | |||
<td>EIGRP Autonomous System (AS) number. It is an identifier that represents a routing domain; EIGRP routers can exchange routes within the same Autonomous System.</td> | |||
</tr> | |||
<tr> | |||
<td>Router ID</td> | |||
<td>ip4; default: <b>none</b></td> | |||
<td>The router ID is used by EIGRP 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> | |||
<td>Network</td> | <td>Network</td> | ||
<td>ip/netmask; default: <b>none</b></td> | |||
<td>Adds an announcement network(s). Routes to these networks will be shared over EIGRP.</td> | |||
</tr><tr><td>Redistribution options</td><td> | </tr> | ||
</td><td> | <tr> | ||
<td>Redistribution options</td> | |||
<td>Connected routes {{!}} Kernel added routes {{!}} NHRP routes {{!}} OSPF routes {{!}} Static routes {{!}} custom; default: <b>none</b></td> | |||
<td>Distributes selected routes. Route redistribution is a process that allows a network to use a routing protocol to dynamically route traffic based on information learned from a separate routing protocol.</td> | |||
</tr> | |||
<tr> | |||
<td>Neighbors</td> | <td>Neighbors</td> | ||
<td> | <td>ip4; default: <b>none</b></td> | ||
<td> | <td>Defines the EIGRP Neighbors (based on their IP addresses) that this device is meant to associate with.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
===NHRP | ===NHRP=== | ||
----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. | ---- | ||
<b>Next Hop Resolution Protocol</b> (<b>NHRP</b>) 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 | ---- | ||
The <b>General Settings</b> section is used to turn NHRP protocol usage on or off. Below is an example of the NHRP General Settings section. | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_general_settings.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 | <td>off {{!}} on; default: <b>off</b></td> | ||
<td> | <td>Turns NHRP protocol usage on or off.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable logging</td> | <td>Enable logging</td> | ||
<td>off | <td>off {{!}} on; default: <b>off</b></td> | ||
<td> | <td>Turns NHRP traffic logging on or off.</td> | ||
</tr></table> | </tr></table> | ||
====Interfaces==== | ====Interfaces==== | ||
----Below is an example of NHRP '' | ---- | ||
[[File: | The <b>Interfaces</b> section is used to define which existing network interfaces can participate in NHRP communication. Below is an example of the NHRP Interfaces section which is empty by default. | ||
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces.png|border|class=tlt-border]] | |||
To create a new NHRP Interface, look to the Add New Interface section; enter a custom name and click the 'Add' button. | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_add_button.png|border|class=tlt-border]] | |||
The newly added NHRP interface will appear in the Interfaces list and should look similar to this: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_begin_to_edit.png|border|class=tlt-border]] | |||
To see more settings for an NHRP Interface, click the 'Edit' button next to it: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_edit_button.png|border|class=tlt-border]] | |||
You should redirected to a windows that looks similar to this: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_interface_configuration.png|border|class=tlt-border]] | |||
<table class="nd-mantable"> | |||
<tr> | |||
<th>Field</th> | |||
<th>Value</th> | |||
<th>Description</th> | |||
</tr> | |||
<tr> | <tr> | ||
< | <td>Enabled</td> | ||
<td>off {{!}} on; default: <b>off</b></td> | |||
<td>Turns the NHRP Interface on or off.</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Interface</td> | |||
<td>network interface; default: <b>br-lan</b></td> | |||
<td>Network interface associated with this NHRP Interface.</td> | |||
</tr></table> | </tr> | ||
<tr> | |||
<td>Network ID</td> | |||
<td>32-bit integer; default: <b>none</b></td> | |||
<td>A numerical identifier for this NHRP Interface.</td> | |||
</tr> | |||
<tr> | |||
<td>NHRP authentication key</td> | |||
<td>string; default: <b>none</b></td> | |||
<td>A password used in NHRP authentication.</td> | |||
</tr> | |||
<tr> | |||
<td>NHS</td> | |||
<td>Dynamic {{!}} custom(ip4); default: <b>none</b></td> | |||
<td>IP address of a Next-Hop server.</td> | |||
</tr> | |||
<tr> | |||
<td>NBMA</td> | |||
<td>ip4; default: <b>none</b></td> | |||
<td>Non-Broadcast Multi-Access (NBMA) network IP address.</td> | |||
</tr> | |||
<tr> | |||
<td>Hold-time</td> | |||
<td>integer; default: <b>7200</b></td> | |||
<td>Specifies the holding time (in seconds) for NHRP Registration Requests and Resolution Replies sent from this interface or shortcut-target.</td> | |||
</tr> | |||
<tr> | |||
<td>IPsec support</td> | |||
<td>off {{!}} <span style="color: red;">on</span>; default: <b>off</b></td> | |||
<td>Turns usage of NHRP over IPsec for this Interface on or off.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color: red;">IPsec instance</span></td> | |||
<td>string; default: <b>none</b></td> | |||
<td>Specifies which existing IPsec instance should be associated with this NHRP Interface. This field becomes visible only when IPsec support is set to 'on'.</td> | |||
</tr> | |||
</table> | |||
=====NHRP Mappings Configuration===== | |||
---- | |||
The <b>NHRP Mappings Configuration</b> section is used to configure (map) associations between NHRP router IP address and NBMAs. Below is an example of the NHRP Mappings Configuration section which is empty by default. To add a new configuration, simply click the 'Add' button: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_nhrp_mappings_configuration_add_button.png|border|class=tlt-border]] | |||
The newly added configuration should appear in the NHRP Mappings Configuration list and look similar to this: | |||
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_nhrp_mappings_configuration_edit.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 {{!}} on; default: <b>off</b></td> | |||
<td>Turns this mapping configuration on or off.</td> | |||
</tr> | |||
<tr> | |||
<td>IP Address</td> | |||
<td>ip4; default: <b>none</b></td> | |||
<td>Network ID of another NHRP router.</td> | |||
</tr> | |||
<tr> | |||
<td>NBMA</td> | |||
<td>ip4; default: <b>none</b></td> | |||
<td>IP address of a Next-Hop server.</td> | |||
</tr> | |||
</table>|}} | |||
[[Category:{{{name}}} Network section]] |
Revision as of 10:43, 24 November 2022
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.
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:
|
*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:
|
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.
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 | 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]]