Changes

Template:Networking rutos manual routing (view source)

Revision as of 12:00, 21 December 2023

7,557 bytes added , 12:00, 21 December 2023

no edit summary

Line 1: Line 1: −

{{Template: ~~Networking_rutos_manual_fw_disclosure~~

+

{{Template: Networking_device_manual_fw_disclosure

−

| ~~fw_version~~ = {{{series}}}~~_R_00.02.06.1~~

+

| series = {{{series}}}

−

| series = {{{series}}}

+

| name = {{{name}}}

+

| fw_version ={{Template: Networking_device_manual_latest_fw

+

| series = {{{series}}}

+

| name = {{{name}}}

+

}}

−

{{#ifeq: {{{legacy}}} | 1 | Note: [[{{{name}}} Routing (legacy WebUI)|click here]] for the old style WebUI (FW version ~~RUT9XX_R_00.06.08.1~~ and earlier) user manual page.|}}

+

{{#ifeq: {{{series}}} | RUT9 | Note: [[{{{name}}} Routing (legacy WebUI)|click here]] for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.|}}

+

{{#ifeq: {{{series}}} | RUT2 | Note: [[{{{name}}} Routing (legacy WebUI)|click here]] for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.|}}

==Summary==

Line 189: Line 194:

</table>

−

==~~Advanced Static Routes~~==

+

==Policy Based Routing==

−

The ~~Advanced Static Routes~~ section is used to configure policy-based routing infrastructures, which are usually used in more complex or specific networking scenarios.

+

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

===Routing Tables===

Line 207: Line 212:

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

−

[[File:~~Networking_rutos_manual_routing_advanced_static_routes_routing_tables_routing_table_settings~~.png|border|class=tlt-border]]

+

[[File:Networking_rutos_manual_routing_advanced_static_routes_routing_tables_routing_table_settings_v1.png|border|class=tlt-border]]

Line 214: Line 219:

<th>Value</th>

<th>Description</th>

+

</tr>

+

<tr>

+

<td>Name of Table</td>

+

<td>string; default: none</td>

+

<td>A custom name for the table. A table can be invoked by the both its ID or name.</td>

</tr>

<tr>

Line 219: Line 229:

<td>integer [1..252]; default: none</td>

<td>Unique numerical identifier for the table. A table can be invoked by the both its ID or name.</td>

−

~~</tr>~~

−

~~<tr>~~

−

~~<td>Name of Table</td>~~

−

~~<td>string; default: none</td>~~

−

~~<td>A custom name for the table. A table can be invoked by the both its ID or name.</td>~~

</tr>

</table>

Line 324: Line 329:

Each protocol is described in the sections below.

+

{{#switch: {{{series}}} | RUTX | RUTM= | #default=

+

+

Note: Dynamic Routing is additional software that can be installed from the System → [[{{{name}}} Package Manager|Package Manager]] page.

+

}}

===BGP===

----

Line 333: Line 342:

The General Settings 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]]

Line 343: Line 352:

<tr>

<td>Enable</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns BGP protocol usage on or off.</td>

</tr>

<tr>

<td>Enable vty</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns vty access on or off.</td>

</tr>

Line 362: Line 371:

The BGP Instance 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]]

Line 372: Line 381:

<tr>

<td>Enable</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns the BGP instance on or off.</td>

</tr>

Line 392: Line 401:

<tr>

<td>Redistribution options</td>

−

+

<td>Connected routes {{!}} Kernel added routes {{!}} NHRP routes {{!}} OSPF routes {{!}} Static routes {{!}} custom; default: none</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 ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Compares MEDs between same AS, while ignoring their age.</td>

+

</tr>

+

<tr>

+

<td>eBGP Requires Policy</td>

+

<td>off {{!}} on; default: on</td>

+

<td>Enable/Disable eBGP Import or Export policy requirement. Enabled by default as per RFC 8212.</td>

</tr>

</table>

Line 434: Line 448:

<tr>

<td>Enable</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns turns this BGP peer on or off.</td>

</tr>

Line 445: Line 459:

The full BGP Peer configuration page should look similar to this:

−

[[File:~~Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_bgp_peer~~.png|border|class=tlt-border]]

+

[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_bgp_peer_v3.png|border|class=tlt-border]]

Line 455: Line 469:

<tr>

<td>Enable</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns this BGP peer on or off.</td>

</tr>

Line 477: Line 491:

<td>integer; default: none</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: none</td>

+

<td>Specifies a default weight value for the neighbor’s routes. Higher weight is preferred.</td>

+

</tr>

+

<tr>

+

<td>Keepalive timer</td>

+

<td>integer [0..65535]; default: none</td>

+

<td>Frequency (in seconds) of keep alive messages.</td>

+

</tr>

+

<tr>

+

<td>Holdtime</td>

+

<td>integer [0..65535]; default: none</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: none</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 ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Announces default routes to this peer.</td>

</tr>

Line 487: Line 521:

<td>string; default: none</td>

<td>A custom description for this BGP peer. Used for easier management purposes only.</td>

+

</tr>

+

<tr>

+

<td>Password</td>

+

<td>string; default: none</td>

+

<td>Password for this BGP Neighbor.</td>

</tr>

</table>

Line 523: Line 562:

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]]

Line 533: Line 572:

<tr>

<td>Enable</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns the BGP Peer Group configuration on or off.</td>

</tr>

Line 545: Line 584:

<td>ip4; default: none</td>

<td>IPv4 address(es) of a remote BGP Neighbor.</td>

+

</tr>

+

<tr>

+

<td>Listen Range</td>

+

<td>ip4 with mask; default: none</td>

+

<td>Accept connections from any peers in the specified prefix.</td>

</tr>

<tr>

Line 553: Line 597:

<tr>

<td>Neighbor configuration</td>

−

<td>None ~~<nowiki>|</nowiki>~~ Route Reflector client ~~<nowiki>|</nowiki>~~ Route Server client; default: None</td>

+

<td>None {{!}} Route Reflector client {{!}} Route Server client; default: None</td>

<td>Defines the role of a BGP Neighbor.

<ul>

Line 563: Line 607:

<tr>

<td>Disable next hop calculation</td>

−

<td>off <~~nowiki~~>|</~~nowiki~~> on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns next hop calculation for this BGP Peer Group on or off.</td>

+

</tr>

+

<tr>

+

<td>Apply also to ibgp-learned routes</td>

+

<td>off {{!}} on; default: off</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 ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns inbound soft-reconfiguration for this Neighbor on or off.</td>

</tr>

<tr>

<td>Disable connected check</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</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>

Line 601: Line 650:

<tr>

<td>Action</td>

−

<td>Permit ~~<nowiki>|</nowiki>~~ Deny; default: Permit</td>

+

<td>Permit {{!}} Deny; default: Permit</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>

</tr>

<tr>

<td>Network</td>

−

<td>ip/netmask ~~<nowiki>|</nowiki>~~ Any; default: Any</td>

+

<td>ip/netmask {{!}} Any; default: Any</td>

<td>Matches traffic destined or originating from (depends on 'Direction' selection) to the network specified in this field.</td>

</tr>

<tr>

<td>Direction</td>

−

<td>Inbound ~~<nowiki>|</nowiki>~~ Outbound; default: Inbound</td>

+

<td>Inbound {{!}} Outbound; default: Inbound</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 ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns an Access filter on or off.</td>

</tr>

</table>

−

===RIP ~~Protocol~~===

+

====Route Maps====

+

----

+

A Route Maps 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]]

+

+

<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: Permit</td>

+

<td>IPv4 address of this remote BGP Neighbor.</td>

+

</tr>

+

<tr>

+

<td>Enable</td>

+

<td>off {{!}} on; default: off</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]]

+

+

<tr>

+

<th>Field</th>

+

<th>Value</th>

+

<th>Description</th>

+

</tr>

+

<tr>

+

<td>Enable</td>

+

<td>off {{!}} on; default: off</td>

+

<td>Turns the Route Maps configuration on or off.</td>

+

</tr>

+

<tr>

+

<td>Action</td>

+

<td>Permit {{!}} Deny; default: Permit</td>

+

<td>IPv4 address of this remote BGP Neighbor.</td>

+

</tr>

+

<tr>

+

<td>Local preference</td>

+

<td>integer [0..4294967295]; default: none</td>

+

<td>Used to determine best route towards a certain destination.</td>

+

</tr>

+

<tr>

+

<td>Metric</td>

+

<td>ip4 with mask; default: none</td>

+

<td>Sets a metric value for determining the preferred path into an AS.</td>

+

</tr>

+

</table>

+

====Route Map Filters====

+

----

+

The Route Map Filters 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]]

+

+

<tr>

+

<th>Field</th>

+

<th>Value</th>

+

<th>Description</th>

+

</tr>

+

<tr>

+

+

<td>bgp peer; default: none</td>

+

<td>Applies the filter rule for the specified peer.</td>

+

</tr>

+

<tr>

+

<td>Route map</td>

+

<td>route map; default: none</td>

+

<td>Route map filter to apply.</td>

+

</tr>

+

<tr>

+

<td>Direction</td>

+

<td>Inbound {{!}} Outbound; default: Inbound</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: off</td>

+

<td>Turns an Route Map filter on or off.</td>

+

</tr>

+

</table>

+

===RIP===

----

The Routing Information Protocol (RIP) 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.

Line 629: Line 789:

The General Settings 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]]

Line 639: Line 799:

<tr>

<td>Enable</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns RIP Protocol usage on or off.</td>

</tr>

<tr>

<td>Enable vty</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns vty access on or off.</td>

</tr>

Line 654: Line 814:

<tr>

<td>Version</td>

−

<td>2 ~~<nowiki>|</nowiki>~~ 1; default: 2</td>

+

<td>2 {{!}} 1; default: 2</td>

<td>Specifies the used version of the RIP protocol.</td>

</tr>

Line 676: Line 836:

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]]

Line 683: Line 843:

<th>Value</th>

<th>Description</th>

−

~~</tr>~~

−

~~<tr>~~

−

~~<td>Enable</td>~~

−

~~<td>off <nowiki>|</nowiki> on; default: off</td>~~

−

~~<td>Turns a RIP Interface on or off.</td>~~

</tr>

<tr>

Line 696: Line 851:

<tr>

<td>Passive interface</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</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>

+

</tr>

+

<tr>

+

<td>Enable</td>

+

<td>off {{!}} on; default: off</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>

</table>

Line 707: Line 872:

[[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:

−

[[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]]

Line 728: Line 893:

<tr>

<td>Enable</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns an Access filter on or off.</td>

</tr>

Line 738: Line 903:

<tr>

<td>Action</td>

−

<td>Permit ~~<nowiki>|</nowiki>~~ Deny; default: Permit</td>

+

<td>Permit {{!}} Deny; default: Permit</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>

</tr>

<tr>

<td>Network</td>

−

<td>ip/netmask ~~<nowiki>|</nowiki>~~ Any; default: Any</td>

+

<td>ip/netmask {{!}} Any; default: Any</td>

<td>Matches traffic destined or originating from (depends on 'Direction' selection) to the network specified in this field.</td>

</tr>

<tr>

<td>Direction</td>

−

<td>Inbound ~~<nowiki>|</nowiki>~~ Outbound; default: Inbound</td>

+

<td>Inbound {{!}} Outbound; default: Inbound</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>

</table>

−

===OSPF ~~Protocol~~===

+

===OSPF===

----

Open Shortest Path First (OSPF) 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.

Line 761: Line 926:

The General Settings 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]]

Line 771: Line 936:

<tr>

<td>Enable</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns OSPF Protocol usage on or off.</td>

</tr>

<tr>

<td>Enable vty</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns vty access on or off.</td>

</tr>

Line 804: Line 969:

</ul>

</td>

+

</tr>

+

<tr>

+

<td>Redistribution options</td>

+

<td>Connected routes {{!}} Kernel {{!}} NHRP {{!}} BGP {{!}} OSPF {{!}} RIP {{!}} EIGRP {{!}} Static; default: none</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>

</table>

Line 830: Line 1,000:

<tr>

<td>Enable</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns an OSPF Interface on or off.</td>

</tr>

Line 841: Line 1,011:

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]]

Line 851: Line 1,021:

<tr>

<td>Enable</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns the OSPF area on or off.</td>

</tr>

Line 881: Line 1,051:

<tr>

−

<td>Broadcast ~~<nowiki>|</nowiki> Nonbroadcast <nowiki>|</nowiki>~~ Point-to-point ~~<nowiki>|</nowiki>~~ Point-to-~~multipointl~~ default: ~~none~~</td>

+

<td>Broadcast {{!}} Non-Broadcast {{!}} Point-to-point {{!}} Point-to-Multipoint; default: Broadcast </td>

<td>OSPF interface configuration type.</td>

</tr>

<tr>

<td>Authentication</td>

−

<td>None ~~<nowiki>|</nowiki>~~ Password ~~<nowiki>|</nowiki>~~ MD5 HMAC; default: None</td>

+

<td>None {{!}} Password {{!}} MD5 HMAC; default: None</td>

<td>Specifies the Authentication method.</td>

+

</tr>

+

</table>

+

====OSPF Neighbors====

+

----

+

The OSPF Neighbors 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]]

+

+

<tr>

+

<th>Field</th>

+

<th>Value</th>

+

<th>Description</th>

+

</tr>

+

<tr>

+

<td>Enable</td>

+

<td>off {{!}} on; default: off</td>

+

<td>Turns this OSPF neighbor configuration on or off.</td>

+

</tr>

+

<tr>

+

<td>Neighbor</td>

+

<td>ip4; default: none</td>

+

<td>IP address of the OSPF neighbor.</td>

+

</tr>

+

<tr>

+

<td>Neighbor Priority</td>

+

<td>integer [1..255]; default: none</td>

+

<td>Priority of this neighbor</td>

+

</tr>

+

<tr>

+

<td>Polling interval</td>

+

<td>integer [1..65535]; default: none</td>

+

<td>Check for dead neighbor interval (in seconds).</td>

</tr>

</table>

Line 903: Line 1,107:

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]]

Line 920: Line 1,124:

<td>32-bit integer; default: none</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>off {{!}} on; default: off</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>

<td>Enable</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns an OSPF Area on or off.</td>

</tr>

Line 967: Line 1,176:

<tr>

<td>Enable</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns the usage of this network (in OSPF) on or off.</td>

</tr>

Line 980: Line 1,189:

The General Settings 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]]

Line 990: Line 1,199:

<tr>

<td>Enable</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns EIGRP protocol usage on or off.</td>

</tr>

<tr>

<td>Enable logging</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns logging of EIGRP traffic on or off.</td>

</tr>

Line 1,015: Line 1,224:

<tr>

<td>Redistribution options</td>

−

+

<td>Connected routes {{!}} Kernel added routes {{!}} NHRP routes {{!}} OSPF routes {{!}} Static routes {{!}} custom; default: none</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>

Line 1,033: Line 1,242:

The General Settings 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]]

Line 1,043: Line 1,252:

<tr>

<td>Enable service</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns NHRP protocol usage on or off.</td>

</tr>

<tr>

<td>Enable logging</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns NHRP traffic logging on or off.</td>

</tr></table>

Line 1,082: Line 1,291:

<tr>

<td>Enabled</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns the NHRP Interface on or off.</td>

</tr>

Line 1,102: Line 1,311:

<tr>

−

<td>Dynamic ~~<nowiki>|</nowiki>~~ custom(ip4); default: none</td>

+

<td>Dynamic {{!}} custom(ip4); default: none</td>

<td>IP address of a Next-Hop server.</td>

</tr>

Line 1,117: Line 1,326:

<tr>

<td>IPsec support</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns usage of NHRP over IPsec for this Interface on or off.</td>

</tr>

Line 1,145: Line 1,354:

<tr>

<td>Enabled</td>

−

<td>off ~~<nowiki>|</nowiki>~~ on; default: off</td>

+

<td>off {{!}} on; default: off</td>

<td>Turns this mapping configuration on or off.</td>

</tr>

TomasG

Administrators

1,223

edits

Namespaces

Variants

Views

More

Search

Changes

Template:Networking rutos manual routing (view source)

Revision as of 12:00, 21 December 2023

Navigation menu

Personal tools

NAVIGATION

Tools

Categories