Difference between revisions of "Template:Networking rutos manual routing"
(27 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
− | {{Template: | + | {{Template: Networking_device_manual_fw_disclosure |
− | | | + | | series = {{{series}}} |
− | | series | + | | name = {{{name}}} |
+ | | fw_version ={{Template: Networking_device_manual_latest_fw | ||
+ | | series = {{{series}}} | ||
+ | | name = {{{name}}} | ||
+ | }} | ||
}} | }} | ||
− | {{#ifeq: {{{legacy}}} | | + | {{#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_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}} | ||
==Summary== | ==Summary== | ||
Line 189: | Line 194: | ||
</table> | </table> | ||
− | == | + | ==Policy Based Routing== |
− | The <b> | + | 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=== | ||
Line 207: | Line 212: | ||
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. | ||
− | [[File: | + | [[File:Networking_rutos_manual_routing_advanced_static_routes_routing_tables_routing_table_settings_v1.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 214: | Line 219: | ||
<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> | ||
Line 219: | Line 229: | ||
<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. A table can be invoked by the both its ID or name.</td> | <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 324: | Line 329: | ||
Each protocol is described in the sections below. | Each protocol is described in the sections below. | ||
+ | {{#switch: {{{series}}} | RUTX | RUTM= | #default= | ||
+ | <u><b> | ||
+ | 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=== | ||
---- | ---- | ||
Line 333: | Line 342: | ||
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: | + | [[File:Networking_rutos_manual_routing_dynamic_routes_bgp_general_settings_v1.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 343: | Line 352: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Turns BGP protocol usage on or off.</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>Turns vty access on or off.</td> | <td>Turns vty access on or off.</td> | ||
</tr> | </tr> | ||
Line 362: | Line 371: | ||
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: | + | [[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance_v1.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 372: | Line 381: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Turns the BGP instance on or off.</td> | <td>Turns the BGP instance on or off.</td> | ||
</tr> | </tr> | ||
Line 392: | Line 401: | ||
<tr> | <tr> | ||
<td>Redistribution options</td> | <td>Redistribution options</td> | ||
− | <td>Connected routes | + | <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> | <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> | ||
<tr> | <tr> | ||
<td>Deterministic MED</td> | <td>Deterministic MED</td> | ||
− | <td>off | + | <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> | ||
Line 434: | Line 448: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Turns turns this BGP peer on or off.</td> | <td>Turns turns this BGP peer on or off.</td> | ||
</tr> | </tr> | ||
Line 445: | Line 459: | ||
The full BGP Peer configuration page should look similar to this: | The full BGP Peer configuration page should look similar to this: | ||
− | [[File: | + | [[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"> | ||
Line 455: | Line 469: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Turns this BGP peer on or off.</td> | <td>Turns this BGP peer on or off.</td> | ||
</tr> | </tr> | ||
Line 477: | Line 491: | ||
<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> | ||
+ | <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> | ||
<tr> | <tr> | ||
<td>Default originate</td> | <td>Default originate</td> | ||
− | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Announces default routes to this peer.</td> | <td>Announces default routes to this peer.</td> | ||
</tr> | </tr> | ||
Line 487: | Line 521: | ||
<td>string; default: <b>none</b></td> | <td>string; default: <b>none</b></td> | ||
<td>A custom description for this BGP peer. Used for easier management purposes only.</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> | </tr> | ||
</table> | </table> | ||
Line 523: | Line 562: | ||
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: | + | [[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"> | ||
Line 533: | Line 572: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Turns the BGP Peer Group configuration on or off.</td> | <td>Turns the BGP Peer Group configuration on or off.</td> | ||
</tr> | </tr> | ||
Line 545: | Line 584: | ||
<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> | ||
Line 553: | Line 597: | ||
<tr> | <tr> | ||
<td>Neighbor configuration</td> | <td>Neighbor configuration</td> | ||
− | <td>None | + | <td>None {{!}} Route Reflector client {{!}} Route Server client; default: <b>None</b></td> |
<td>Defines the role of a BGP Neighbor. | <td>Defines the role of a BGP Neighbor. | ||
<ul> | <ul> | ||
Line 563: | Line 607: | ||
<tr> | <tr> | ||
<td>Disable next hop calculation</td> | <td>Disable next hop calculation</td> | ||
− | <td>off < | + | <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> | <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: <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> | ||
<tr> | <tr> | ||
<td>Inbound soft-reconfiguration</td> | <td>Inbound soft-reconfiguration</td> | ||
− | <td>off | + | <td>off {{!}} on; default: <b>off</b></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> | ||
<tr> | <tr> | ||
<td>Disable connected check</td> | <td>Disable connected check</td> | ||
− | <td>off | + | <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> | </tr> | ||
Line 601: | Line 650: | ||
<tr> | <tr> | ||
<td>Action</td> | <td>Action</td> | ||
− | <td>Permit | + | <td>Permit {{!}} Deny; default: <b>Permit</b></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>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> | ||
<tr> | <tr> | ||
<td>Network</td> | <td>Network</td> | ||
− | <td>ip/netmask | + | <td>ip/netmask {{!}} Any; 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>Matches traffic destined or originating from (depends on 'Direction' selection) to the network specified in this field.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Direction</td> | <td>Direction</td> | ||
− | <td>Inbound | + | <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>Matches network traffic direction, which can either be traffic destined to this device (Inbound) or traffic originating from this device (Outbound).</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <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> | </tr> | ||
</table> | </table> | ||
− | ===RIP | + | ====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. | ||
Line 629: | Line 789: | ||
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: | + | [[File:Networking_rutos_manual_routing_dynamic_routes_rip_general_settings_v1.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 639: | Line 799: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Turns RIP Protocol usage on or off.</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>Turns vty access on or off.</td> | <td>Turns vty access on or off.</td> | ||
</tr> | </tr> | ||
Line 654: | Line 814: | ||
<tr> | <tr> | ||
<td>Version</td> | <td>Version</td> | ||
− | <td>2 | + | <td>2 {{!}} 1; default: <b>2</b></td> |
<td>Specifies the used version of the RIP protocol.</td> | <td>Specifies the used version of the RIP protocol.</td> | ||
</tr> | </tr> | ||
Line 676: | Line 836: | ||
RIP Interface configuration should look similar to this: | RIP Interface configuration should look similar to this: | ||
− | [[File: | + | [[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"> | ||
Line 683: | Line 843: | ||
<th>Value</th> | <th>Value</th> | ||
<th>Description</th> | <th>Description</th> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 696: | Line 851: | ||
<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 <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> | ||
Line 707: | Line 872: | ||
[[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 | + | 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: | + | [[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: | + | [[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"> | ||
Line 728: | Line 893: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <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> | </tr> | ||
Line 738: | Line 903: | ||
<tr> | <tr> | ||
<td>Action</td> | <td>Action</td> | ||
− | <td>Permit | + | <td>Permit {{!}} Deny; default: <b>Permit</b></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>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> | ||
<tr> | <tr> | ||
<td>Network</td> | <td>Network</td> | ||
− | <td>ip/netmask | + | <td>ip/netmask {{!}} Any; 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>Matches traffic destined or originating from (depends on 'Direction' selection) to the network specified in this field.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Direction</td> | <td>Direction</td> | ||
− | <td>Inbound | + | <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>Matches network traffic direction, which can either be traffic destined to this device (Inbound) or traffic originating from this device (Outbound).</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. | <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. | ||
Line 761: | Line 926: | ||
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: | + | [[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"> | ||
Line 771: | Line 936: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Turns OSPF Protocol usage on or off.</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>Turns vty access on or off.</td> | <td>Turns vty access on or off.</td> | ||
</tr> | </tr> | ||
Line 804: | Line 969: | ||
</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> | ||
Line 830: | Line 1,000: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Turns an OSPF Interface on or off.</td> | <td>Turns an OSPF Interface on or off.</td> | ||
</tr> | </tr> | ||
Line 841: | Line 1,011: | ||
You should directed to a window such as this: | You should directed to a window such as this: | ||
− | [[File: | + | [[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"> | ||
Line 851: | Line 1,021: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Turns the OSPF area on or off.</td> | <td>Turns the OSPF area on or off.</td> | ||
</tr> | </tr> | ||
Line 881: | Line 1,051: | ||
<tr> | <tr> | ||
<td>Type</td> | <td>Type</td> | ||
− | <td>Broadcast | + | <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> | ||
<tr> | <tr> | ||
<td>Authentication</td> | <td>Authentication</td> | ||
− | <td>None | + | <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> | ||
Line 903: | Line 1,107: | ||
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: | + | [[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"> | ||
Line 920: | Line 1,124: | ||
<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> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Turns an OSPF Area on or off.</td> | <td>Turns an OSPF Area on or off.</td> | ||
</tr> | </tr> | ||
Line 967: | Line 1,176: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Turns the usage of this network (in OSPF) on or off.</td> | <td>Turns the usage of this network (in OSPF) on or off.</td> | ||
</tr> | </tr> | ||
Line 980: | Line 1,189: | ||
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: | + | [[File:Networking_rutos_manual_routing_dynamic_routes_eigrp_general_settings_v1.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 990: | Line 1,199: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Turns EIGRP protocol usage on or off.</td> | <td>Turns EIGRP 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>Turns logging of EIGRP traffic on or off.</td> | <td>Turns logging of EIGRP traffic on or off.</td> | ||
</tr> | </tr> | ||
Line 1,015: | Line 1,224: | ||
<tr> | <tr> | ||
<td>Redistribution options</td> | <td>Redistribution options</td> | ||
− | <td>Connected routes | + | <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> | <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> | ||
Line 1,033: | Line 1,242: | ||
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: | + | [[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_general_settings_v2.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 1,043: | Line 1,252: | ||
<tr> | <tr> | ||
<td>Enable service</td> | <td>Enable service</td> | ||
− | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Turns NHRP protocol usage on or off.</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>Turns NHRP traffic logging on or off.</td> | <td>Turns NHRP traffic logging on or off.</td> | ||
</tr></table> | </tr></table> | ||
Line 1,082: | Line 1,291: | ||
<tr> | <tr> | ||
<td>Enabled</td> | <td>Enabled</td> | ||
− | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Turns the NHRP Interface on or off.</td> | <td>Turns the NHRP Interface on or off.</td> | ||
</tr> | </tr> | ||
Line 1,102: | Line 1,311: | ||
<tr> | <tr> | ||
<td>NHS</td> | <td>NHS</td> | ||
− | <td>Dynamic | + | <td>Dynamic {{!}} custom(ip4); default: <b>none</b></td> |
<td>IP address of a Next-Hop server.</td> | <td>IP address of a Next-Hop server.</td> | ||
</tr> | </tr> | ||
Line 1,117: | Line 1,326: | ||
<tr> | <tr> | ||
<td>IPsec support</td> | <td>IPsec support</td> | ||
− | <td>off | + | <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> | <td>Turns usage of NHRP over IPsec for this Interface on or off.</td> | ||
</tr> | </tr> | ||
Line 1,145: | Line 1,354: | ||
<tr> | <tr> | ||
<td>Enabled</td> | <td>Enabled</td> | ||
− | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Turns this mapping configuration on or off.</td> | <td>Turns this mapping configuration on or off.</td> | ||
</tr> | </tr> |
Revision as of 12:00, 21 December 2023
The information in this page is updated in accordance with firmware version .
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:
|
Policy Based Routing
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
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]]