Changes

Template:Networking rutos manual routing (view source)

Revision as of 11:43, 24 November 2022

3,518 bytes added , 11:43, 24 November 2022

no edit summary

Line 1: Line 1: −

{{Template:Networking_rutos_manual_fw_disclosure

+

{{Template: Networking_rutos_manual_fw_disclosure

−

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

+

| fw_version ={{Template: Networking_rutos_manual_latest_fw

−

| ~~series~~ = {{{~~series~~}}}

+

| series = {{{series}}}

+

| name = {{{name}}}

+

}}

−

+

{{#ifeq: {{{series}}} | RUT9 | Note: [[{{{name}}} Routing (legacy WebUI)|click here]] for the old style WebUI (FW version {{Template: Networking_rutos_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_rutos_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.|}}

==Summary==

Line 207: Line 210:

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

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

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

Each protocol is described in the sections below.

+

{{#ifeq: {{{series}}} | RUTX | |

+

+

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

+

}}

===BGP===

----

Line 343: Line 350:

<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 372: Line 379:

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

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

Line 425: Line 432:

<td>Remote AS</td>

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

−

<td>Remote autonomous system number of this remote BGP ~~Neighbour~~.</td>

+

<td>Remote autonomous system number of this remote BGP Neighbor.</td>

</tr>

<tr>

<td>Remote address</td>

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

−

<td>IPv4 address of this remote BGP ~~Neighbour~~.</td>

+

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

</tr>

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

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_v2.png|border|class=tlt-border]]

Line 455: Line 462:

<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 461: Line 468:

<td>Remote AS</td>

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

−

<td>Remote autonomous system number of this remote BGP ~~Neighbour~~.</td>

+

<td>Remote autonomous system number of this remote BGP Neighbor.</td>

</tr>

<tr>

<td>Remote address</td>

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

−

<td>IPv4 address of this remote BGP ~~Neighbour~~.</td>

+

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

</tr>

<tr>

<td>Remote port</td>

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

−

<td>Listening port number of the BGP ~~Neighbour~~.</td>

+

<td>Listening port number of the BGP Neighbor.</td>

</tr>

<tr>

<td>EBGP Multihop</td>

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

−

<td>Time to Live value for packets associated with this remote BGP ~~Neighbour~~.</td>

+

<td>Time to Live value for packets associated with this remote BGP Neighbor.</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 509:

<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 533: Line 560:

<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 544: Line 571:

<td>Neighbor address</td>

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

−

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

+

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

</tr>

<tr>

Line 553: Line 580:

<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 ~~Neighbour~~.

+

<td>Defines the role of a BGP Neighbor.

<ul>

<li>Route Reflector client - redistributes received routes.</li>

Line 563: Line 590:

<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>Disable next hop calculation: 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>

+

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

+

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

Line 601: Line 633:

<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~~===

+

===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 639: Line 671:

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

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

<tr>

<td>Neighbor</td>

−

<td>rip ~~neighbour~~; default: none</td>

+

<td>rip neighbor; default: none</td>

−

<td>Defines a RIP ~~Neighbour~~(s).</td>

+

<td>Defines a RIP Neighbor(s).</td>

</tr>

</table>

Line 686: Line 718:

<tr>

<td>Enable</td>

−

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

+

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

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

</tr>

Line 696: Line 728:

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

Line 703: Line 735:

====Access list filters====

----

−

The Access List Filters section is used to configure special filters that restrict or allow access to specified networks for RIP ~~Neighbours~~. Below is an example of the Access List Filters section which is empty by default.

+

The Access List Filters 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]]

Line 728: Line 760:

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

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

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_v2.png|border|class=tlt-border]]

Line 771: Line 803:

<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 788: Line 820:

<td>32-bit integer; default: none</td>

<td>Sets the router-ID in the OSPF network.</td>

+

</tr>

+

<tr>

+

<td>Passive interfaces</td>

+

<td>network interface(s); default: none</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: off</td>

+

<td>Defines the behavior for advertising a default route over OSPF. Possible values are:

+

<ul>

+

<li>off - does not advertise a default route.</li>

+

<li>default - advertises the default route if the route is in the routing table.</li>

+

<li>always - 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: 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 814: Line 867:

<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 825: Line 878:

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 835: Line 888:

<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 865: Line 918:

<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 907: Line 994:

<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 951: Line 1,038:

<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 974: Line 1,061:

<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 999: Line 1,086:

<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,005: Line 1,092:

<td>Neighbors</td>

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

−

<td>Defines the EIGRP ~~Neighbours~~ (based on their IP addresses) that this device is meant to associate with.</td>

+

<td>Defines the EIGRP Neighbors (based on their IP addresses) that this device is meant to associate with.</td>

</tr>

</table>

Line 1,027: Line 1,114:

<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,066: Line 1,153:

<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,086: Line 1,173:

<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,101: Line 1,188:

<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,129: Line 1,216:

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

Dziugas

Bureaucrats, Interface administrators, Administrators

31,703

edits

Namespaces

Variants

Views

More

Search

Changes

Template:Networking rutos manual routing (view source)

Revision as of 11:43, 24 November 2022

Navigation menu

Personal tools

NAVIGATION

Tools

Categories