1,223
edits
Changes
Template:Networking rutos manual routing (view source)
Revision as of 12:00, 21 December 2023
, 12:00, 21 December 2023no edit summary
{{Template: Networking_rutos_manual_fw_disclosure
{{Template: Networking_device_manual_fw_disclosure
| fw_version ={{Template: Networking_rutos_manual_latest_fw
| series = {{{series}}}
| name = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| series = {{{series}}}
| series = {{{series}}}
| name = {{{name}}}
| 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}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} Routing (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_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>|}}
{{#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_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
==Summary==
==Summary==
</table>
</table>
==Advanced Static Routes==
==Policy Based Routing==
The <b>Advanced Static Routes</b> section is used to configure policy-based routing infrastructures, which are usually used in more complex or specific networking scenarios.
The <b>Policy Based Routing</b> section is used to configure policy-based routing infrastructures, which are usually used in more complex or specific networking scenarios.
===Routing Tables===
===Routing Tables===
Each protocol is described in the sections below.
Each protocol is described in the sections below.
{{#ifeq: {{{series}}} | RUTX | |
{{#switch: {{{series}}} | RUTX | RUTM= | #default=
<u><b>
<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>
Note:</b> Dynamic Routing is additional software that can be installed from the <b>System → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u>
}}
}}
===BGP===
===BGP===
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.
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]]
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_general_settings_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
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.
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]]
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<td>off {{!}} on; default: <b>off</b></td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Compares MEDs between same AS, while ignoring their age.</td>
<td>Compares MEDs between same AS, while ignoring their age.</td>
</tr>
<tr>
<td>eBGP Requires Policy</td>
<td>off {{!}} on; default: <b>on</b></td>
<td>Enable/Disable eBGP Import or Export policy requirement. Enabled by default as per RFC 8212.</td>
</tr>
</tr>
</table>
</table>
The full BGP Peer configuration page should look similar to this:
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]]
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_bgp_peer_v3.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<td>integer; default: <b>none</b></td>
<td>integer; default: <b>none</b></td>
<td>Time to Live value for packets associated with this remote BGP Neighbor.</td>
<td>Time to Live value for packets associated with this remote BGP Neighbor.</td>
</tr>
<tr>
<td>Weight</td>
<td>integer [0..65535]; default: <b>none</b></td>
<td>Specifies a default weight value for the neighbor’s routes. Higher weight is preferred.</td>
</tr>
</tr>
<tr>
<tr>
The full BGP Peer Group configuration page should look similar to this:
The full BGP Peer Group configuration page should look similar to this:
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_bgp_peer_group.png|border|class=tlt-border]]
[[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">
<td>ip4; default: <b>none</b></td>
<td>ip4; default: <b>none</b></td>
<td>IPv4 address(es) of a remote BGP Neighbor.</td>
<td>IPv4 address(es) of a remote BGP Neighbor.</td>
</tr>
<tr>
<td>Listen Range</td>
<td>ip4 with mask; default: <b>none</b></td>
<td>Accept connections from any peers in the specified prefix.</td>
</tr>
</tr>
<tr>
<tr>
</tr>
</tr>
<tr>
<tr>
<td><span style="color: blue;">Disable next hop calculation:</span> Apply also to ibgp-learned routes</td>
<td>Apply also to ibgp-learned routes</td>
<td>off {{!}} on; default: <b>off</b></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>
<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>
</table>
</table>
===RIP Protocol===
====Route Maps====
----
A <b>Route Maps</b> allow you to configure a filtering criteria by defining a set of rules or match statements with a permit or deny condition. It includes a series of match statements to determine if a route matches the criteria defined in the statement and then apply the permit or deny rule accordingly.
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps.png|border|class=tlt-border]]
To create a new Route Maps, look to the Add New Instance section under Route Maps; type in a custom name for the Route Map and click the 'Add' button:
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_add_button.png|border|class=tlt-border]]
The newly added Route Map configuration should look similar to this:
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_added.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Drag-cursor</td>
<td>- (interactive button)</td>
<td>Changes the priority(metric) of the route maps.</td>
</tr>
<tr>
<td>Action</td>
<td>Permit {{!}} Deny; default: <b>Permit</b></td>
<td>IPv4 address of this remote BGP Neighbor.</td>
</tr>
<tr>
<td>Enable</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Turns this Route Map on or off.</td>
</tr>
</table>
To see more settings for a Route Maps, click the 'Edit' button next to it:
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_edit_button.png|border|class=tlt-border]]
The full Route Maps configuration page should look similar to this:
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_edit.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Turns the Route Maps configuration on or off.</td>
</tr>
<tr>
<td>Action</td>
<td>Permit {{!}} Deny; default: <b>Permit</b></td>
<td>IPv4 address of this remote BGP Neighbor.</td>
</tr>
<tr>
<td>Local preference</td>
<td>integer [0..4294967295]; default: <b>none</b></td>
<td>Used to determine best route towards a certain destination.</td>
</tr>
<tr>
<td>Metric</td>
<td>ip4 with mask; default: <b>none</b></td>
<td>Sets a metric value for determining the preferred path into an AS.</td>
</tr>
</table>
====Route Map Filters====
----
The <b>Route Map Filters</b> section is used to configure special filters that changes direction for BGP Peers. Below is an example of the Route Map 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_route_maps_filters_add_button.png|border|class=tlt-border]]
An Route Map Filters configuration for BGP should look similar to this:
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_filters_configuration.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Peer</td>
<td>bgp peer; default: <b>none</b></td>
<td>Applies the filter rule for the specified peer.</td>
</tr>
<tr>
<td>Route map</td>
<td>route map; default: <b>none</b></td>
<td>Route map filter to apply.</td>
</tr>
<tr>
<td>Direction</td>
<td>Inbound {{!}} Outbound; default: <b>Inbound</b></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>
</tr>
<tr>
<td>Enable</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Turns an Route Map filter on or off.</td>
</tr>
</table>
===RIP===
----
----
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.
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.
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.
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]]
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_general_settings_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
RIP Interface configuration should look similar to this:
RIP Interface configuration should look similar to this:
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_rip_interfaces_configuration.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">
<th>Value</th>
<th>Value</th>
<th>Description</th>
<th>Description</th>
</tr>
</tr>
<tr>
<tr>
<td>off {{!}} on; default: <b>off</b></td>
<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 <b>ripd</b> does not send either multicast or unicast RIP packets.</td>
<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>
</tr>
<tr>
<td>Enable</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Turns a RIP Interface on or off.</td>
</tr>
<tr>
<td>Delete</td>
<td>- (interactive button)</td>
<td>Deletes RIP inerfaces instance.</td>
</tr>
</tr>
</table>
</table>
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_access_list_filters.png|border|class=tlt-border]]
[[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:
To add a new filter, look to the Add New Instance section; enter a custom name and select RIP interface then click the 'Add' button:
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_access_list_filters_add_button.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_access_list_filters_add_button_v1.png|border|class=tlt-border]]
An Access List Filter configuration for RIP should look similar to this:
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]]
[[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">
</table>
</table>
===OSPF Protocol===
===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.
<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.
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.
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.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_general_settings_v3.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
</ul>
</ul>
</td>
</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>
You should directed to a window such as this:
You should directed to a window such as this:
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_interface_configuration.png|border|class=tlt-border]]
[[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>
<td>Type</td>
<td>Type</td>
<td>Broadcast {{!}} Nonbroadcast {{!}} Point-to-point {{!}} Point-to-multipointl default: <b>none</b></td>
<td>Broadcast {{!}} Non-Broadcast {{!}} Point-to-point {{!}} Point-to-Multipoint; default: <b>Broadcast </b></td>
<td>OSPF interface configuration type.</td>
<td>OSPF interface configuration type.</td>
</tr>
</tr>
<td>None {{!}} Password {{!}} MD5 HMAC; default: <b>None</b></td>
<td>None {{!}} Password {{!}} MD5 HMAC; default: <b>None</b></td>
<td>Specifies the Authentication method.</td>
<td>Specifies the Authentication method.</td>
</tr>
</table>
====OSPF Neighbors====
----
The <b>OSPF Neighbors</b> section can be used to configure other users ("neighbors") of the same OSPF network statically.
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_neighbor_configuration_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Turns this OSPF neighbor configuration on or off.</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>
</tr>
</table>
</table>
The newly added new Area will appear in the OSPF Area list.
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]]
[[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">
<td>32-bit integer; default: <b>none</b></td>
<td>32-bit integer; default: <b>none</b></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>
<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>
<td>STUB</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>A stub area is an area in which advertisements of external routes are not allowed, reducing the size of the database.</td>
</tr>
</tr>
<tr>
<tr>
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.
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:Networking_rutos_manual_routing_dynamic_routes_eigrp_general_settings.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_routing_dynamic_routes_eigrp_general_settings_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
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.
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]]
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_general_settings_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
