7,851
edits
Changes
Template:Networking rutos manual routing (view source)
Revision as of 10:40, 17 April 2024
, 17 Aprilno 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">
====BGP Instance====
====BGP Instance====
----
----
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance.png|border|class=tlt-border]]
To create a new BGP instance, look to the Add New Instance section under BGP instances; type in a custom name for the BGP instance and click the 'Add' button or you can 'Edit' a general instance:
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance_edit.png|border|class=tlt-border]]
You will be redirected to general BGP instance settings:
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<td>AS</td>
<td>AS</td>
<td>integer [1..65535]default: <b>none</b></td>
<td>integer [1..4294967295]; 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>
<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.</td>
</tr>
</tr>
<tr>
<tr>
<td>ip/netmask; default: <b>none</b></td>
<td>ip/netmask; default: <b>none</b></td>
<td>Adds an announcement network(s). Routes to these networks will be shared over BGP.</td>
<td>Adds an announcement network(s). Routes to these networks will be shared over BGP.</td>
</tr>
<tr>
<td>VRF interface</td>
<td>VRF interface; default: <b>Default</b></td>
<td>To create new VRF interface, please visit: [[{{{name}}} VRF|VRF]] </td>
</tr>
</tr>
<tr>
<tr>
<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>
====BGP Peers====
=====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.
<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]]
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_v2.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:
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]]
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_add_button_v1.png|border|class=tlt-border]]
You will be redirected to general peer settings:
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_added.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_bgp_peer_v4.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<td>Remote AS</td>
<td>Remote AS</td>
<td>integer [1..65535]; default: <b>none</b></td>
<td>integer [1..4294967295]; default: <b>none</b></td>
<td>Remote autonomous system number of this remote BGP Neighbor.</td>
<td>Remote autonomous system number of this remote BGP Neighbor.</td>
</tr>
</tr>
<td>Remote address</td>
<td>Remote address</td>
<td>ip4; default: <b>none</b></td>
<td>ip4; default: <b>none</b></td>
<td>IPv4 address of this remote BGP Neighbor.</td>
<td>IPv4 address of this remote BGP Neighbor. This option is required.</td>
</tr>
</tr>
<tr>
<tr>
<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>
</table>
</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.
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:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_v2.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:
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]]
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_groups_add_button_v1.png|border|class=tlt-border]]
You will be redirected to general peer groups settings:
[[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_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<td>Remote AS</td>
<td>Remote AS</td>
<td>integer [1..65535]; default: <b>none</b></td>
<td>integer [1..65535]; default: <b>none</b></td>
<td>Remote autonomous system number.</td>
<td>Neighbour's remote AS.</td>
</tr>
</tr>
<tr>
<tr>
<td>Neighbor address</td>
<td>Neighbor address</td>
<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>Neighbour's remote IPv4 address.</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>
<td>Advertisement interval</td>
<td>Advertisement interval</td>
<td>integer; default: <b>none</b></td>
<td>integer; default: <b>none</b></td>
<td>BGP advertisement frequency (in seconds).</td>
<td>Delay between updates for a neighbor session (in seconds).</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>
<td>off {{!}} on; default: <b>off</b></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>
<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>
=====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_v1.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_v1.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>-</b></td>
<td>Applies the filter rule for the specified peer.</td>
</tr>
<tr>
<td>Route map</td>
<td>route map; default: <b>-</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>
</tr>
</table>
</table>
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
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]]
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_access_list_filters_add_button_v1.png|border|class=tlt-border]]
An Access List Filter configuration for BGP should look similar to this:
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]]
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_access_list_filters_configuration_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<td>Peer</td>
<td>Peer</td>
<td>bgp peer; default: <b>none</b></td>
<td>bgp peer; default: <b>-</b></td>
<td>Applies the filter rule for the specified peer.</td>
<td>Applies the filter rule for the specified peer.</td>
</tr>
</tr>
</tr>
</tr>
<tr>
<tr>
<td>Network</td>
<td>Filter network</td>
<td>ip/netmask {{!}} Any; default: <b>Any</b></td>
<td>Any {{!}} custom; default: <b>Any</b></td>
<td>Matches traffic destined or originating from (depends on 'Direction' selection) to the network specified in this field.</td>
<td>Applies filter rule for this source network.</td>
</tr>
</tr>
<tr>
<tr>
<td>Direction</td>
<td>Direction</td>
<td>Inbound {{!}} Outbound; default: <b>Inbound</b></td>
<td>Inbound {{!}} Outbound; default: <b>Inbound</b></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>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>
<tr>
<tr>
<td>off {{!}} on; default: <b>off</b></td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Turns an Access filter on or off.</td>
<td>Turns an Access filter on or off.</td>
</tr>
</table>
====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_v1.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_v1.png|border|class=tlt-border]]
You will be redirected to general route maps settings:
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_edit_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 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>
</tr>
</table>
</table>
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">
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_v2.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">
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">