Template:Networking rutos manual routing: Difference between revisions

From Teltonika Networks Wiki
VisualWikitext
No edit summary
No edit summary
 
(65 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{{Template: Networking_device_manual_fw_disclosure
| series = {{{series}}}
| name  = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| series = {{{series}}}
| name  = {{{name}}}
}}
}}
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} Routing (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_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==


This chapter is an overview of the <b>Routing</b> section in {{{name}}} devices.
The <b>Routing</b> page is used to set up static {{#ifeq:{{{dynamic}}}|1|and dynamic|}} routes, routing tables and rules.
 
This manual page provides an overview of the Routing windows in {{{name}}} devices.
 
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
| series = {{{series}}}
}}


==Static Routes==
==Static Routes==


Static routes specify over which interface and gateway a certain host or network can be reached. In this page you can configure your own custom routes.
<b>Routes</b> 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===
===Static IPv4 Routes===
----
----
Below is an example and information about Static IPv4 Routes.
The <b>Static IPv4 Routes</b> 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.
[[File:Networking_RUTX_manual_static_routes_ipv4_v1.png|alt=|border|center|1150x1150px]]


<table class="nd-mantable"><tr><th>Field</th><th>Value</th><th>Description</th></tr><tr><td>Interface</td><td>Default: '''lan'''</td><td>The zone where the target network resides</td></tr><tr><td>Target<span class="asterisk">*</span></td><td>IPv4; Default: <b>0.0.0.0</b></td><td>The address of the destination network</td></tr><tr><td>Netmask<span class="asterisk">*</span></td><td>Default: <b>255.255.255.255</b></td><td>A Mask that is applied to the Target to determine to what actual IP addresses the routing rule applies</td></tr><tr><td>Gateway</td><td>IP; Default: '''0.0.0.0'''</td><td>Defines where the router should send all the traffic that applies to the rule</td></tr><tr><td>Metric</td><td>Default: <b>0</b></td><td>The <b>metric</b> value is used as a sorting measure. If a packet about to be routed fits two rules, the one with the lower metric is applied.</td></tr><tr><td>MTU</td><td>[64..9000]; Default: <b>1500</b></td><td>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.</td></tr><tr><td>Route Type</td><td>Default: <b>unicast</b></td><td>Selects route type. Each type specifies a different behavior for the route, available options:<ul><li><b>unicast</b> </li><li><b>local</b> - routes of this type are added to the 'local' routing table and used only for locally hosted IPs.</li><li><b>broadcast</b> - routes of this type are added to the 'local' routing table and used by link layer devices that support the broadcast address principle.</li><li><b>multicast</b> </li><li><b>unreachable</b> </li><li><b>prohibit</b> - used to prohibit traffic to specified host or network. When a destination is prohibited, the kernel sends a 'Network is unreachable' response the source address.</li><li><b>blackhole</b> - packets that match this type of route are discarded without any response.</li><li><b>anycast</b> -</li><li><b>-- custom --</b> -</li></ul></td></tr></table>
[[File:Networking_rutos_manual_routing_static_routes_static_ipv4_routes.png|border|class=tlt-border]]
 
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.
 
[[File:Networking_rutos_manual_routing_static_routes_static_ipv4_routes_new_route.png|border|class=tlt-border]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
      <td>Interface</td>
      <td>network interface; default: <b>lan</b></td>
      <td>Network interface of the target network.</td>
    </tr>
    <tr>
    <td>Target<span class="asterisk">*</span></td>
        <td>ip4; default: <b>none</b></td>
        <td>Destination network address.</td>
    </tr>
    <tr>
    <td>IPv4-Netmask<span class="asterisk">*</span></td>
        <td>netmask; default: <b>none</b></td>
        <td>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.</td>
    </tr>
    <tr>
    <td>IPv4-Gateway</td>
        <td>ip4; default: <b>none</b></td>
        <td>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.</td>
    </tr>
    <tr>
    <td>Metric</td>
        <td>integer [0..255]; default: <b>none</b></td>
        <td>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.</td>
    </tr>
    <tr>
    <td>MTU</td>
        <td>integer [64..9000]; default: <b>1500</b></td>
      <td>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.</td>
    </tr>
    <tr>
    <td>Route Type</td>
        <td>unicast | local | broadcast | multicast | unreachable | prohibit | backhole | anycast | -- custom -- ; default: <b>unicast</b></td>
        <td>Selects route type. Each type specifies a different behavior for the route:
            <ul>
                <li><b>unicast</b> - most common type of route, simply describes a path to a destination.</li>
                <li><b>local</b> - routes of this type are added to the 'local' routing table and used only for locally hosted IPs.</li>
                <li><b>broadcast</b> - routes of this type are added to the 'local' routing table and used by link layer devices that support the broadcast address principle.</li>
                <li><b>multicast</b> - used for distribution of multicast traffic.</li>
                <li><b>unreachable</b> - sends an ICMP "unreachable" response to the source address when a request for a routing decision returns a "destination with an unreachable route type" message.</li>
                <li><b>prohibit</b> - used to prohibit traffic to specified host or network. When a destination is prohibited, the kernel sends a 'Network is unreachable' response the source address.</li>
                <li><b>blackhole</b> - packets that match this type of route are discarded without any response.</li>
                <li><b>anycast</b> - provides a possibility to route incoming requests to multiple different network locations.</li>
                <li><b>-- custom --</b> - does not use any of the predefined route types.</li>
            </ul>
        </td>
    </tr>
</table>


<span class="asterisk">*</span><b>Additional notes on Target & Netmask:</b>
<span class="asterisk">*</span><b>Additional notes on 'Target' & 'Netmask' fields:</b>
----
You can define a rule that applies to a single IP like this:
 
<ul>
    <li><b>Target</b>: some IP</li>
    <li><b>Netmask</b>: 255.255.255.255</li>
</ul>
 
Furthermore, you can create target/netmask combinations that apply to a range of IPs. Refer to the table below for examples.
 
<table class="nd-mantable">
    <tr>
        <th>Target</th>
        <th>Netmask</th>
        <th>Network range</th>
    </tr>
    <tr>
        <td>192.168.2.0</td>
        <td>255.255.255.240</td>
        <td>192.168.2.0 - 192.168.2.15</td>
    </tr>
    <tr>
        <td>192.168.2.240</td>
        <td>255.255.255.240</td>
        <td>192.168.2.240 - 192.168.2.255</td>
    </tr>
    <tr>
        <td>192.168.2.161</td>
        <td>255.255.255.0</td>
        <td>192.168.2.0 - 192.168.55.255</td>
    </tr>
    <tr>
        <td>192.168.0.0</td>
        <td>255.255.0.0</td>
        <td>192.168.0.0 - 192.168.255.255</td>
    </tr>
    <tr>
        <td>192.168.2.161</td>
        <td>255.255.255.255</td>
        <td>192.168.2.161</td>
    </tr>
</table>


You can define a rule that applies to a single IP like this:<ul><li><b>Target</b>: some IP</li><li><b>Netmask</b>: 255.255.255.255</li></ul>Furthermore, you can define a rules that apply to a range of IPs. Refer to the table below for examples.<table class="nd-mantable"><tr><th>Target</th><th>Netmask</th><th>Description</th></tr><tr><td>192.168.2.0</td><td>255.255.255.240</td><td>Applies to IPs in the 192.168.2.0 - 192.168.2.15 range.</td></tr><tr><td>192.168.2.240</td><td>255.255.255.240</td><td>Applies to IPs in the 192.168.2.240 - 192.168.2.255 range.</td></tr><tr><td>192.168.2.161</td><td>255.255.255.0</td><td>Applies to IPs in the 192.168.2.0 - 192.168.55.255 range.</td></tr><tr><td>192.168.0.0</td><td>255.255.0.0</td><td>Applies to IPs in the 192.168.0.0 - 192.168.255.255 range.</td></tr><tr><td>192.168.2.161</td><td>255.255.255.255</td><td>Only applies to 192.168.2.161.</td></tr></table><br />
===Static IPv6 Routes===
===Static IPv6 Routes===
----
----
Settings for Static IPv6 routes are the same as for IPv4 only that the target IP and and gateway are different.
The <b>Static IPv6 Routes</b> 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.
[[File:Networking_RUTX_manual_static_routes_ipv6_v1.png|alt=|border|center]]
 
<br />
[[File:Networking_rutos_manual_routing_static_routes_static_ipv6_routes.png|border|class=tlt-border]]
 
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.
 
[[File:Networking_rutos_manual_routing_static_routes_static_ipv6_routes_new_route.png|border|class=tlt-border]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
      <td>Interface</td>
      <td>network interface; default: <b>lan</b></td>
      <td>Network interface of the target network.</td>
    </tr>
    <tr>
    <td>Target</td>
        <td>ip6; default: <b>none</b></td>
        <td>Destination network address.</td>
    </tr>
    <tr>
    <td>IPv6-Gateway</td>
        <td>ip6; default: <b>none</b></td>
        <td>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.</td>
    </tr>
    <tr>
    <td>Metric</td>
        <td>integer [0..255]; default: <b>none</b></td>
        <td>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.</td>
    </tr>
    <tr>
    <td>MTU</td>
        <td>integer [64..9000]; default: <b>1500</b></td>
      <td>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.</td>
    </tr>
    <tr>
    <td>Route Type</td>
        <td>unicast | local | broadcast | multicast | unreachable | prohibit | backhole | anycast | -- custom -- ; default: <b>unicast</b></td>
        <td>Selects route type. Each type specifies a different behavior for the route:
            <ul>
                <li><b>unicast</b> - most common type of route, simply describes a path to a destination.</li>
                <li><b>local</b> - routes of this type are added to the 'local' routing table and used only for locally hosted IPs.</li>
                <li><b>broadcast</b> - routes of this type are added to the 'local' routing table and used by link layer devices that support the broadcast address principle.</li>
                <li><b>multicast</b> - used for distribution of multicast traffic.</li>
                <li><b>unreachable</b> - sends an ICMP "unreachable" response to the source address when a request for a routing decision returns a "destination with an unreachable route type" message.</li>
                <li><b>prohibit</b> - used to prohibit traffic to specified host or network. When a destination is prohibited, the kernel sends a 'Network is unreachable' response the source address.</li>
                <li><b>blackhole</b> - packets that match this type of route are discarded without any response.</li>
                <li><b>anycast</b> - provides a possibility to route incoming requests to multiple different network locations.</li>
                <li><b>-- custom --</b> - does not use any of the predefined route types.</li>
            </ul>
        </td>
    </tr>
</table>


==Advanced Static Routes==
==Policy Based Routing==


Advanced static routing includes features and concepts that are used in more complex networks.
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===
----
----
Below is an example of routing tables. You can create a new one by writing '''ID''' (anything you want, but only numbers are allowed), '''Name''' and pressing '''Add''' button. You can edit them by pressing '''Edit''' button
<b>Routing Tables</b> 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.
[[File:Networking RUTX manual advaced static routes tables v1.png|alt=|border|center|1128x1128px]]
 
The 'Routing Tables' section displays user created routing tables. By default, the list is empty.
 
[[File:Networking_rutos_manual_routing_advanced_static_routes_routing_tables.png|border|class=tlt-border]]
 
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.
 
[[File:Networking_rutos_manual_routing_advanced_static_routes_add_new_routing_table.gif]]
 
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_v1.png|border|class=tlt-border]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</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>
      <td>ID of Table</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>
    </tr>
</table>


===Routing Rules For IPv4===
===Routing Rules For IPv4===
----
----
Below is an example of routing rules for IPv4. You can create a new rule by pressing '''Add''' button, also you can edit them by pressing '''Edit''' button.
<b>Routing Rules</b> 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.
[[File:Networking RUTX manual advaced static routes rules v1.png|alt=|border|center|1127x1127px]]
 
An example of rule editing window and meanings of all the configurations are presented below.
[[File:Networking_rutos_manual_routing_advanced_static_routes_routing_rules_for_ipv4_v1_begin_to_edit.gif]]
[[File:Networking RUTX manual advaced static routes rules settings v1.png|alt=|border|center|1145x1145px]]<table class="nd-mantable">
----
Refer to table below for information on each configuration field.
 
[[File:Networking_rutos_manual_routing_advanced_static_routes_routing_rules_for_ipv4_settings.png|border|class=tlt-border]]
 
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Priority</td>
       <td>Priority</td>
       <td>Default: '''auto-assigned'''</td>
       <td>integer [0..65535]; default: <b>none</b></td>
       <td>Controls the order of the IP rules, by default the priority is auto-assigned so that they are processed in the same order.
       <td>Controls the order of IP rules. Rules with a lower priority value will be checked first.</td>
</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Incoming interface</td>
       <td>Incoming interface</td>
       <td>Default: '''Any'''</td>
       <td>network interface | Any; default: <b>Any</b></td>
       <td>Specifies the incoming logical interface name</td>
       <td>Logical interface name for incoming traffic. Select 'Any' to make the rule apply to all network interfaces.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Outgoing interface</td>
     <td>Outgoing interface</td>
         <td>Default: '''None'''</td>
         <td>network interface | None; default: <b>None</b></td>
         <td>Specifies the outgoing logical interface name
         <td>Logical interface name for incoming traffic. Select 'None' to ignore outgoing interface.</td>
</td>
     </tr>
     </tr><tr><td>Source subnet</td><td>IPv4; Default: <b>0.0.0.0</b></td><td>Specifies the source subnet to match (CIDR notation)
    <tr>
</td></tr><tr><td>Destination subnet</td><td>IPv4; Default: '''0.0.0.0'''</td><td>Specifies the destination subnet to match (CIDR notation)
        <td>Source subnet</td>
</td></tr><tr><td>TOS Value to Match</td><td>Default: <b>0</b>
        <td>netmask; default: <b>none</b></td>
</td><td>Specifies the TOS value to match in IP headers
        <td>Source subnet to match the rule.</td>
</td></tr><tr><td>Firewall Mark</td><td>Default: '''0xFF'''
    </tr>
</td><td>Specifies the fwmark and optionally its mask to match, e.g. 0xFF to match mark 255 or 0x0/0x1 to match any even mark value
    <tr>
</td></tr><tr><td>Invert matches</td><td>off | on; Default: '''off'''
        <td>Destination subnet</td>
</td><td>If enabled, the meaning of the match options (Firewall Mark, TOS Value, Source and Destination subnets) is inverted
        <td>netmask; default: <b>none</b></td>
</td></tr><tr><td>Matched Traffic Action</td><td>Default: '''Lookup Table'''
        <td>Destination subnet to match the rule.</td>
</td><td>Available options:
    </tr>
    <tr>
        <td>TOS Value to Match</td>
        <td>integer [0..255]; default: <b>none</b></td>
        <td>The type of service (ToS) value to match in IP headers.</td>
    </tr>
    <tr>
        <td>Firewall Mark</td>
        <td>integer [0..255] | hex [0x00..0xFF]; default: <b>none</b></td>
        <td>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.</td>
    </tr>
    <tr>
        <td>Invert matches</td>
        <td>off | on; default: <b>off</b></td>
        <td>If enabled, the meaning of the match options (Firewall Mark, TOS Value, Source and Destination subnets) is inverted.</td>
    </tr>
    <tr>
        <td>Matched Traffic Action</td>
        <td><span style="color: red;">Lookup Table</span> | <span style="color: green;">Jump to rule</span> | <span style="color: #0054A6;">Routing Action</span>; default: <b>Lookup Table</b></td>
        <td>When network traffic matches this rule, the device will take an action specified in this field:
            <ul>
                <li><b><span style="color: red;">Lookup Table</span></b> - routes traffic in accordance with the specified routing table.</li>
                <li><b><span style="color: green;">Jump to rule</span></b> - specifies another routing rule to follow.</li>
                <li><b><span style="color: #0054A6;">Routing Action</span></b> - executes one of four predefined routing actions.</li>
            </ul>
        </td>
    </tr>
    <tr>
        <td><span style="color: red;">Lookup Table</span></td>
        <td>routing table; default: <b>none</b></td>
        <td>Specifies a table for routing traffic that matches this rule. This field is visible only when 'Matched Traffic Action' is set to <i>Lookup Table</i>.</td>
    </tr>
    <tr>
        <td><span style="color: green;">Jump to rule</span></td>
        <td>rule priority number; default: <b>none</b></td>
        <td>Specifies a another rule to follow for traffic that matches this rule. This field is visible only when 'Matched Traffic Action' is set to <i>Jump to rule</i>.</td>
    </tr>
    <tr>
        <td><span style="color: #0054A6;">Routing Action</span></td>
        <td>Prohibit | Unreachable | Blackhole | Throw; default: <b>Prohibit</b></td>
        <td>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 <i>Routing Action</i>.</td>
    </tr>
</table>
{{#ifeq: {{{dynamic}}} | 1 |
==Dynamic Routes==


*'''Lookup table'''
<b>Dynamic Routing</b> provides the possibility to route data based on current network or device state instead of relying on static entries in the routing table. The {{{name}}} device supports these dynamic routing protocols:
*'''Jump to rule'''
*'''Routing action'''
</td></tr><tr><td>Lookup Table</td><td>Default: " "
</td><td>The rule target is a table lookup
</td></tr></table>


[[Category:{{{name}}} Network section]]
<ul>
<!--
    <li>[[#BGP|BGP]] (Border Gateway Protocol)</li>
    <li>[[#RIP|RIP]] (Routing Information Protocol)</li>
    <li>[[#OSPF_Protocol|OSPF]] (Open Shortest Path First)</li>
    <li>[[#EIGRP|EIGRP]] (Enhanced Interior Gateway Routing Protocol)</li>
    <li>[[#NHRP|NHRP]] (Next Hop Resolution Protocol)</li>
</ul>


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===
----
The <b>Border Gateway Protocol (BGP)</b> is a standardized exterior gateway protocol designed to exchange routing and reachability information among autonomous systems (AS) on the Internet. The protocol is often classified as a path vector protocol but is sometimes also classed as a distance-vector routing protocol. The Border Gateway Protocol makes routing decisions based on paths, network policies, or rule-sets configured by a network administrator and is involved in making core routing decisions.


 
====General Settings====
==Dynamic Routes==
 
===BGP Protocol===
----
----
'''Border Gateway Protocol (BGP)''' is a standardized exterior gateway protocol designed to exchange routing and reachability information among autonomous systems (AS) on the Internet. The protocol is often classified as a path vector protocol but is sometimes also classed as a distance-vector routing protocol. The Border Gateway Protocol makes routing decisions based on paths, network policies, or rule-sets configured by a network administrator and is involved in making core routing decisions.
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.


====General Settings====
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_general_settings_v1.png|border|class=tlt-border]]
----Below is an example of BGP '''General''' settings section.[[File:Networking_RUTX_manual_dynamic_routes_bgp_general_v1.png|alt=|border|center]]
<br />


<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off | on; Default: '''off'''</td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Toggles the BGP protocol 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 | on; Default: '''off'''</td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Toggles vty access ON or OFF</td>
       <td>Turns vty access on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Import config</td>
     <td>Import config</td>
         <td>-</td>
         <td>- (interactive button)</td>
         <td>Uploads an external BGP configuration</td>
         <td>Uploads an external BGP configuration.</td>
     </tr>
     </tr>
</table>
</table>


====BGP Instance====
====BGP Instance====
----Below is an example of '''BGP Instance''' settings section.[[File:Networking_RUTX_manual_dynamic_routes_bgp_instance_v1.png|alt=|border|center]]
----
<br />
 
To create a new BGP instance, look to the Add New Instance section under BGP instances; type in a custom name for the BGP instance and click the 'Add' button or you can 'Edit' a general instance:
 
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance_edit.png|border|class=tlt-border]]
 
You will be redirected to general BGP instance settings:
 
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance_v2.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off | on; Default: '''off'''</td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Toggles the BGP instance ON or OFF</td>
       <td>Turns the BGP instance on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>AS</td>
       <td>AS</td>
       <td>Default: " "</td>
       <td>integer [1..4294967295]; default: <b>none</b></td>
      <td>AS number is an identification of an autonomous system. BGP protocol uses the AS number for detecting whether the BGP connection is an internal one or external one. '''[Required]'''</td>
        <td>AS number is an identification of an autonomous system. BGP protocol uses the AS number for detecting whether the BGP connection is an internal one or external one.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>BGP router ID</td>
     <td>BGP router ID</td>
         <td>Default: " "</td>
         <td>32-bit integer; default: <b>none</b></td>
         <td>The router id is used by BGP to identify the routing device from which a packet originated. Default router ID value is selected as the largest IP Address of the interface.</td>
         <td>The router ID is used by BGP to identify the routing device from which a packet originated. Default router ID value is selected as the largest IP Address of the interface.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Network</td>
     <td>Network</td>
         <td>Default: " "</td>
         <td>ip/netmask; default: <b>none</b></td>
         <td>Add an announcement network(s)</td>
         <td>Adds an announcement network(s). Routes to these networks will be shared over BGP.</td>
    </tr><tr><td>Redistribution options</td><td>Default: " "</td><td>'''Route redistribution''' is a process that allows a network to use a '''routing''' protocol to dynamically '''route''' traffic based on information learned from a different '''routing''' protocol. Available options:
    </tr>
 
*'''Connected routes'''
*<b>Kernel added routes</b>
*<b>NHRP routes</b>
*<b>OSPF routes</b>
*<b>Static routes</b>
*<b>Custom</b>
</td></tr><tr><td>Deterministic</td><td>off | on; Default: '''off'''
</td><td>Compare MED between same AS ignoring their age</td></tr></table>
 
====BGP Peers====
----Below is an example of '''BGP Peers''' section. You can create a new peer by pressing '''Add''' button.[[File:Networking_RUTX_manual_dynamic_routes_bgp_peers_v1.png|alt=|border|center]]
<br />
 
<table class="nd-mantable">
     <tr>
     <tr>
        <th>field name</th>
    <td>VRF interface</td>
      <th>value</th>
        <td>VRF interface; default: <b>Default</b></td>
      <th>description</th>
        <td>To create new VRF interface, please visit: [[{{{name}}} VRF|VRF]] </td>
     </tr>
     </tr>
     <tr>
     <tr>
      <td>Enable</td>
        <td>Redistribution options</td>
      <td>off | on; Default: '''off'''</td>
        <td>Connected routes {{!}} Kernel added routes {{!}} NHRP routes {{!}} OSPF routes {{!}} Static routes {{!}} custom; default: <b>none</b></td>
      <td>Toggles the BGP peer ON or OFF</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>Remote AS</td>
        <td>Deterministic MED</td>
      <td>Default: " "</td>
        <td>off {{!}} on; default: <b>off</b></td>
      <td>Neighbour's remote AS</td>
        <td>Compares MEDs between same AS, while ignoring their age.</td>
     </tr>
     </tr>
     <tr>
     <tr>
    <td>Remote address</td>
        <td>eBGP Requires Policy</td>
         <td>IP; Default: " "</td>
         <td>off {{!}} on; default: <b>on</b></td>
         <td>Neighbour's remote IPv4 address</td>
         <td>Enable/Disable eBGP Import or Export policy requirement. Enabled by default as per RFC 8212.</td>
     </tr>
     </tr>
</table>
</table>


By pressing '''Edit''' button you can find more settings related to '''BGP Peer.'''
=====BGP Peers=====
----
<b>BGP Peers</b> are routers in the same BGP Peer Group that can redistribute routes among other BGP Peers. Below is an example of the BGP Peers section, which is empty by default.
 
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_v2.png|border|class=tlt-border]]


[[File:Networking_RUTX_manual_dynamic_routes_bgp_peers_advanced_v1.png|alt=|border|1145x1145px|center]]
To create a new Peer, look to the Add New Instance section under BGP Peer; type in a custom name for the BGP Peer and click the 'Add' button:


<br /><table class="nd-mantable">
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_add_button_v1.png|border|class=tlt-border]]
 
You will be redirected to general peer settings:
 
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_bgp_peer_v4.png|border|class=tlt-border]]
 
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off | on; Default: '''off'''</td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Toggles BGP Peer ON or OFF</td>
       <td>Turns this BGP peer on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Remote AS</td>
       <td>Remote AS</td>
       <td>Default: " "</td>
       <td>integer [1..4294967295]; default: <b>none</b></td>
       <td>Neighbour's remote AS</td>
       <td>Remote autonomous system number of this remote BGP Neighbor.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Remote address</td>
     <td>Remote address</td>
         <td>IP; Default: " "</td>
         <td>ip4; default: <b>none</b></td>
         <td>Neighbour's remote IPv4 address</td>
         <td>IPv4 address of this remote BGP Neighbor. This option is required.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Remote port</td>
     <td>Remote port</td>
         <td>Default: " "</td>
         <td>integer [0..65535]; default: <b>none</b></td>
         <td>Neighbour's remote port
         <td>Listening port number of the BGP Neighbor.</td>
</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>EBGP Multihop</td>
     <td>EBGP Multihop</td>
         <td>Default: " "</td>
         <td>integer; default: <b>none</b></td>
         <td>Time to Live value</td>
         <td>Time to Live value for packets associated with this remote BGP Neighbor.</td>
     </tr><tr><td>Default originate</td><td>off | on; Default: '''off'''</td><td>Announce default routes to the peer</td></tr><tr><td>Description</td><td>Default: " "</td><td>You can leave notes here
    </tr>
</td></tr></table>
    <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>
        <td>Default originate</td>
        <td>off {{!}} on; default: <b>off</b></td>
        <td>Announces default routes to this peer.</td>
    </tr>
    <tr>
        <td>Description</td>
        <td>string; default: <b>none</b></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>
</table>


====BGP Peer Groups====
=====BGP Peer Groups=====
----
----
Below is an example of '''BGP Peer Groups''' section. You can create a new group by writing a name and pressing '''Add''' button.
A <b>BGP Peer Group</b> is a collection of routers that use the BGP protocol to dynamically redistribute routes among peers (other routers). The figure below is an example of the BGP Peer Groups section, which is empty by default.
[[File:Networking RUTX manual dynamic routes bgp peer groups v1.png|alt=|border|center|]]
 
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_v2.png|border|class=tlt-border]]


<table class="nd-mantable">
To create a new Peer Group, look to the Add New Instance section under BGP Peer Groups; type in a custom name for the BGP Peer Group and click the 'Add' button:
    <tr>
 
        <th>field name</th>
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_groups_add_button_v1.png|border|class=tlt-border]]
      <th>value</th>
      <th>description</th>
    </tr>
    <tr>
      <td>Remote AS</td>
      <td>Default: " "</td>
      <td>Neighbour's remote AS</td>
    </tr></table>


By pressing '''Edit''' button you can find more settings related to '''BGP Peer Groups.'''
You will be redirected to general peer groups settings:


[[File:Networking RUTX manual dynamic routes bgp peer groups config v1.png|alt=|border|center]]
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_bgp_peer_group_v2.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off | on; Default: '''off'''</td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Toggles the BGP Peer-Group ON or OFF</td>
       <td>Turns the BGP Peer Group configuration on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Remote AS</td>
       <td>Remote AS</td>
       <td>Default: " "</td>
       <td>integer [1..65535]; default: <b>none</b></td>
       <td>Neighbour's remote AS</td>
       <td>Neighbour's remote AS.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Neighbor address</td>
     <td>Neighbor address</td>
         <td>IP; Default: " "</td>
         <td>ip4; default: <b>none</b></td>
         <td>Neighbour's remote IPv4 address</td>
         <td>Neighbour's remote IPv4 address.</td>
     </tr><tr><td>Advertisement interval</td><td>Default: " "</td><td>Delay between updates for a neighbor session</td></tr><tr><td>Neighbor configuration</td><td>Default: '''None'''</td><td>Configure a neighbor as Route Reflector or Route Server client. Available options:
     </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>
        <td>Advertisement interval</td>
        <td>integer; default: <b>none</b></td>
        <td>Delay between updates for a neighbor session (in seconds).</td>
    </tr>
    <tr>
        <td>Neighbor configuration</td>
        <td>None {{!}} Route Reflector client {{!}} Route Server client; default: <b>None</b></td>
        <td>Defines the role of a BGP Neighbor.
            <ul>
                <li><b>Route Reflector client</b> - redistributes received routes.</li>
                <li><b>Route Server client</b> - distributes routes.</li>
            </ul>
        </td>
    </tr>
    <tr>
        <td>Disable next hop calculation</td>
        <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>
    </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>
        <td>Inbound soft-reconfiguration</td>
        <td>off {{!}} on; default: <b>off</b></td>
        <td>Turns inbound soft-reconfiguration for this Neighbor on or off.</td>
    </tr>
    <tr>
        <td>Disable connected check</td>
        <td>off {{!}} on; default: <b>off</b></td>
        <td>When turned on, Disable connected check enables a directly connected eBGP Neighbor to peer using a loopback address without adjusting the default TTL of 1.</td>
    </tr>
</table>
 
=====Route Map Filters=====
----
The <b>Route Map Filters</b> section is used to configure special filters that changes direction for BGP Peers. Below is an example of the Route Map Filters section which is empty by default. You can add a new filter by clicking the 'Add' button
 
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_filters_add_button_v1.png|border|class=tlt-border]]


*'''None'''
An Route Map Filters configuration for BGP should look similar to this:
*'''Route Reflector client'''
*'''Route Server client'''
</td></tr><tr><td>Disable next hop calculation</td><td>off | on; Default: '''off'''
</td><td>Disable the next hop calculation for this group
</td></tr><tr><td>Inbound soft-reconfiguration</td><td>off | on; Default: '''off'''
</td><td>Allow inbound soft reconfiguration for this neighbor</td></tr><tr><td>Disable connected check</td><td>off | on; Default: '''off'''
</td><td>One-hop away EBGP peer using loopback address</td></tr></table>


====Access List Filters====
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_filters_configuration_v1.png|border|class=tlt-border]]
----Below is an example of '''Access List Filters''' section. You can add a new list by simply pressing '''Add''' button. [[File:Networking_RUTX_manual_dynamic_routes_bgp_access_list_v2.png|alt=|border|center|1138x1138px]]
<br />


<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
    </tr>
    <tr>
      <td>Peer</td>
      <td>bgp peer; default: <b>-</b></td>
      <td>Applies the filter rule for the specified peer.</td>
    </tr>
    <tr>
      <td>Route map</td>
      <td>route map; default: <b>-</b></td>
      <td>Route map filter to apply.</td>
    </tr>
    <tr>
    <td>Direction</td>
        <td>Inbound {{!}} Outbound; default: <b>Inbound</b></td>
        <td>If direction is Inbound, the access list is applied to input routes. If direction is Outbound the access list is applied to advertised routes.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off | on; Default: '''off'''</td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Toggles the Access filter ON or OFF</td>
       <td>Turns an Route Map filter on or off.</td>
    </tr>
</table>
 
====Access List Filters====
----
The <b>Access List Filters</b> section is used to configure special filters that restrict or allow access to specified networks for BGP Peers. Below is an example of the Access List Filters section which is empty by default. You can add a new filter by clicking the 'Add' button
 
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_access_list_filters_add_button_v1.png|border|class=tlt-border]]
 
An Access List Filter configuration for BGP should look similar to this:
 
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_access_list_filters_configuration_v2.png|border|class=tlt-border]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Peer</td>
       <td>Peer</td>
       <td>bgp peer; Default: '''first peer on list'''</td>
       <td>bgp peer; default: <b>-</b></td>
       <td>Applies the rule for the specified peer</td>
       <td>Applies the filter rule for the specified peer.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Action</td>
     <td>Action</td>
         <td>Default: '''Permit'''</td>
         <td>Permit {{!}} Deny; default: <b>Permit</b></td>
         <td>Denies or permits matched entry. Available options:
         <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>
 
*'''Permit'''
*'''Deny'''
</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Network</td>
     <td>Filter network</td>
         <td>Default: '''Any'''</td>
         <td>Any {{!}} custom; default: <b>Any</b></td>
         <td>Applies filter rule for this source network. Available options:
         <td>Applies filter rule for this source network.</td>
 
*'''Any'''
*'''Custom (IP)'''
</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Direction</td>
     <td>Direction</td>
         <td>Default: '''Inbound'''</td>
         <td>Inbound {{!}} Outbound; default: <b>Inbound</b></td>
         <td>Available options:
         <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 Access filter on or off.</td>
    </tr>
</table>


*'''Inbound'''
====Route Maps====
*'''Outbund'''
----
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.


If direction is '''Inbound''', the access list is applied to input routes. If direction is '''Outbound''' the access list is applied to advertised routes
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_v1.png|border|class=tlt-border]]
</td>
 
To create a new Route Maps, look to the Add New Instance section under Route Maps; type in a custom name for the Route Map and click the 'Add' button:
 
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_add_button_v1.png|border|class=tlt-border]]
 
You will be redirected to general route maps settings:
 
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_edit_v1.png|border|class=tlt-border]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
      <td>Enable</td>
      <td>off {{!}} on; default: <b>off</b></td>
      <td>Turns the Route Maps configuration on or off.</td>
    </tr>
    <tr>
    <td>Action</td>
        <td>Permit {{!}} Deny; default: <b>Permit</b></td>
        <td>IPv4 address of this remote BGP Neighbor.</td>
    </tr>
    <tr>
    <td>Local preference</td>
        <td>integer [0..4294967295]; default: <b>none</b></td>
        <td>Used to determine best route towards a certain destination.</td>
    </tr>
        <tr>
    <td>Metric</td>
        <td>ip4 with mask; default: <b>none</b></td>
        <td>Sets a metric value for determining the preferred path into an AS.</td>
     </tr>
     </tr>
</table>
</table>


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


====General====
====General Settings====
----Below is an example of RIP '''General''' settings section.[[File:Networking_RUTX_manual_dynamic_routes_rip_general_v1.png|alt=|border|center]]
----
<br />
The <b>General Settings</b> section is used to configure some of the main operating parameters of the RIP protocol. Below is an example of the RIP General Settings section.
 
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_general_settings_v1.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off | on; Default: '''off'''</td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Toggles RIP Protocol 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 | on; Default: '''off'''</td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Toggles vty access ON or OFF</td>
       <td>Turns vty access on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Import config</td>
     <td>Import config</td>
         <td>-</td>
         <td>- (interactive button)</td>
         <td>Uses imported RIP configurations</td>
         <td>Upload a external RIP configuration.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Version</td>
     <td>Version</td>
         <td>Default: '''2'''</td>
         <td>2 {{!}} 1; default: <b>2</b></td>
         <td>Specifies the version of RIP. Available options:
         <td>Specifies the used version of the RIP protocol.</td>
 
*'''1'''
*'''2'''
</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Neighbor</td>
     <td>Neighbor</td>
         <td>Default: " "</td>
         <td>rip neighbor; default: <b>none</b></td>
         <td>Neighbour IP addres</td>
         <td>Defines a RIP Neighbor(s).</td>
     </tr>
     </tr>
</table>
</table>


====RIP Interfaces====
====RIP Interfaces====
----Below is an example of '''RIP Interfaces''' settings section.[[File:Networking_RUTX_manual_dynamic_routes_rip_interfaces_v1.png|alt=|border|center|1135x1135px]]
----
<br />
The <b>RIP Interfaces</b> section is used to define which existing network interfaces can participate in RIP communication. Below is an example of the RIP Interfaces section which is empty by default.
 
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_rip_interfaces.png|border|class=tlt-border]]
 
To create a new RIP Interface, look to the Add New Interface section; enter a custom name and click the 'Add' button:
 
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_rip_interfaces_add_button.png|border|class=tlt-border]]
 
RIP Interface configuration should look similar to this:
 
[[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">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable</td>
       <td>Interface</td>
       <td>off | on; Default: '''off'''</td>
      <td>network interface; default: <b>loopback</b></td>
      <td>Toggles RIP Interface ON or OFF</td>
       <td>Network interface that will be used with the RIP protocol.</td>
    </tr>
    <tr>
    <td>Passive interface</td>
        <td>off {{!}} on; default: <b>off</b></td>
        <td>Sets the specified interface to passive mode. On passive mode interface, all receiving packets are processed as normal and <b>ripd</b> does not send either multicast or unicast RIP packets.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Interface</td>
       <td>Enable</td>
       <td>network interfaces; Default: '''loopback'''</td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Network interface to be used with the RIP interface</td>
       <td>Turns a RIP Interface on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
    <td>Passive interface</td>
      <td>Delete</td>
        <td>off | on; Default: '''off'''</td>
      <td>- (interactive button)</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>Deletes RIP inerfaces instance.</td>
</td>
     </tr>
     </tr>
</table>
</table>


====Access list filters====
====Access list filters====
----Below is an example of '''Access list filters''' settings section.[[File:Networking_RUTX_manual_dynamic_routes_rip_access_list_v1.png|alt=|border|center]]
----
<br />
The <b>Access List Filters</b> 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]]
 
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_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_v1.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
    </tr>
    <tr>
      <td>Name</td>
      <td>string on; default: <b>none</b></td>
      <td>A custom name for a filter. Used for easier management purposes only.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off | on; Default: '''off'''</td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Toggles the Access filter ON or OFF</td>
       <td>Turns an Access filter on or off.</td>
     </tr><tr><td>RIP interface</td><td>RIP interface; Default: '''first interface on list'''
     </tr>
</td><td>Applies the rule for the specified interface
    <tr>
</td></tr><tr>
        <td>RIP interface</td>
        <td>rip interface; default: <b>none</b></td>
        <td>Specifies the RIP interface to which the filter will apply to.</td>
    </tr>
    <tr>
     <td>Action</td>
     <td>Action</td>
         <td>Default: '''Permit'''</td>
         <td>Permit {{!}} Deny; default: <b>Permit</b></td>
         <td>Available options:
         <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>
 
*'''Permit'''
*'''Deny'''
 
Denies or permits matched entry
</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Network</td>
     <td>Network</td>
         <td>Default: '''Any'''</td>
         <td>ip/netmask {{!}} Any; default: <b>Any</b></td>
         <td>Applies filter rule for this source network. Available options:
         <td>Matches traffic destined or originating from (depends on 'Direction' selection) to the network specified in this field.</td>
 
*'''Any'''
*'''Custom'''
</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Direction</td>
     <td>Direction</td>
         <td>Default: '''Inbound'''</td>
         <td>Inbound {{!}} Outbound; default: <b>Inbound</b></td>
         <td>Available options:
         <td>Matches network traffic direction, which can either be traffic destined to this device (Inbound) or traffic originating from this device (Outbound).</td>
 
*'''Inbound'''
*'''Outbund'''
 
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>
</table>
</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.
<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.


====General Settings====
====General Settings====
----Below is an example of OSPF '''General''' settings section.[[File:Networking_RUTX_manual_dynamic_routes_ospf_general_v1.png|alt=|center|border|1139x1139px]]
----
<br />
The <b>General Settings</b> section is used to configure some of the main operating parameters of the OSPF protocol. Below is an example of the OSPF General Settings section.
 
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_general_settings_v3.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off | on; Default: '''off'''</td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Toggles OSPF Protocol 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 | on; Default: '''off'''</td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Toggles vty access ON or OFF</td>
       <td>Turns vty access on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Import</td>
     <td>Import</td>
         <td>-</td>
         <td>- (interactive)</td>
         <td>Uses imported OSPF configurations</td>
         <td>Uploads a external OSPF configuration.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Router ID</td>
     <td>Router ID</td>
         <td>Default: " "</td>
         <td>32-bit integer; default: <b>none</b></td>
         <td>Sets the router-ID of the OSPF process. The router-ID may be an IP address of the router, but need not be - it can be any arbitrary 32bit number</td>
         <td>Sets the router-ID in the OSPF network.</td>
    </tr>
    <tr>
    <td>Passive interfaces</td>
        <td>network interface(s); default: <b>none</b></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: <b>off</b></td>
        <td>Defines the behavior for advertising a default route over OSPF. Possible values are:
            <ul>
                <li><b>off</b> - does not advertise a default route.</li>
                <li><b>default</b> - advertises the default route if the route is in the routing table.</li>
                <li><b>always</b> - 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: <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>


====OSPF Interface====
====OSPF Interface====
----Below is an example of '''OSPF Interface''' settings section.[[File:Networking_RUTX_manual_dynamic_routes_ospf_interface_v1.png|alt=|border|center]]
----
<br />
The <b>OSPF Interfaces</b> section is used to define which existing network interfaces can participate in OSPF communication. Below is an example of the OSPF Interfaces section which is empty by default. To create a new OSPF Interface, simply click the 'Add' button:
 
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_interface_add_button.png|border|class=tlt-border]]
 
OSPF Interface configuration should look similar to this:
 
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_interface_begin_to_edit.png|border|class=tlt-border]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
      <td>Interface</td>
      <td>network interface; default: <b>loopback</b></td>
      <td>Network interface that will be used with the OSPF protocol.</td>
    </tr>
    <tr>
      <td>Enable</td>
      <td>off {{!}} on; default: <b>off</b></td>
      <td>Turns an OSPF Interface on or off.</td>
    </tr>
</table>
 
To see more settings for an OSPF interface, click the 'Edit' button next to it:
 
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_interface_edit_button.png|border|class=tlt-border]]
 
You should directed to a window such as this:
 
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_interface_configuration_v2.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off | on; Default: off</td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Toggles OSPF area ON or OFF</td>
       <td>Turns the OSPF area on or off.</td>
    </tr>
    <tr>
        <td>Cost</td>
        <td>integer [1..65535]; default: <b>none</b></td>
        <td>The cost value is set to router-LSA’s metric field and used for SPF calculation.</td>
     </tr>
     </tr>
     <tr>
     <tr>
      <td>Interface</td>
        <td>Hello Interval</td>
      <td>network interfaces; Default: '''loopback'''</td>
        <td>integer [1..65535]; default: <b>10</b></td>
      <td>Network interface to be used with the RIP interface. Available options:</td>
        <td>Frequency (in seconds) at which a "Hello" packet is sent out on the specified interface.</td>
    </tr>
    <tr>
        <td>Router Dead Interval</td>
        <td>integer [1..65535]; default: <b>40</b></td>
        <td>This value must be the same for all routers attached to a common OSPF network.</td>
    </tr>
    <tr>
        <td>Retransmit</td>
        <td>integer [0..65535]; default: <b>5</b></td>
        <td>Used in Database Description and Link State Request packet re-transmission.</td>
    </tr>
    <tr>
        <td>Priority</td>
        <td>integer [0..255]; default: <b>1</b></td>
        <td>OSPF router priority. The router with the highest priority will be more eligible to become the "Designated Router". Setting the value to 0, makes the router ineligible to become a "Designated Router."</td>
    </tr>
    <tr>
        <td>Type</td>
        <td>Broadcast {{!}} Non-Broadcast {{!}} Point-to-point {{!}} Point-to-Multipoint; default: <b>Broadcast </b></td>
        <td>OSPF interface configuration type.</td>
    </tr>
    <tr>
        <td>Authentication</td>
        <td>None {{!}} Password {{!}} MD5 HMAC; default: <b>None</b></td>
        <td>Specifies the Authentication method.</td>
     </tr>
     </tr>
</table>
</table>


By pressing '''Edit''' button you can find more settings related to '''OSPF Interface'''.
====OSPF Neighbors====
----
The <b>OSPF Neighbors</b> section can be used to configure other users ("neighbors") of the same OSPF network statically.


[[File:Networking_RUTX_manual_dynamic_routes_ospf_interface_advanced_v1.png|alt=|border|center]]
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_neighbor_configuration_v1.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off | on; Default: '''off'''</td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Toggles OSPF area ON or OFF</td>
       <td>Turns this OSPF neighbor configuration on or off.</td>
     </tr><tr><td>Cost</td><td>Default: " "</td><td>The cost value is set to router-LSA’s metric field and used for SPF calculation</td></tr><tr><td>Hello Interval</td><td>Default: '''10'''</td><td>This value controls how frequently (every n seconds) a 'Hello' packet is sent out on the specified interface</td></tr><tr><td>Router Dead Interval</td><td>Default: '''40'''</td><td>This value must be the same for all routers attached to a common network
     </tr>
</td></tr><tr><td>Retransmit</td><td>Default: '''5'''</td><td>This value is used when re-transmitting Database Description and Link State Request packets
    <tr>
</td></tr><tr><td>Priority</td><td>Default: '''1'''</td><td>The router with the highest priority will be more eligible to become Designated Router. Setting the value to 0, makes the router ineligible to become Designated Router
        <td>Neighbor</td>
</td></tr><tr><td>Type</td><td>Default: " "</td><td>You can choose different Type. Available options:
        <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>
</table>
 
====OSPF Area====
----
An <b>OSPF Area</b> is a collection of OSPF Networks that can serve each other. Below is an example of the OSPF Area section which is empty by default.
 
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_area.png|border|class=tlt-border]]


*'''Broadcast'''
To add a new OSPF Area, look to the Add New Area section; enter a custom name and click the 'Add' button.
*'''Nonbroadcast'''
*'''Point-to-point'''
*'''Point-to-multipoint'''
</td></tr><tr><td>Authentication</td><td>Default: '''None'''</td><td>You can use different authentication methods. Available options:


*'''None'''
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_area_add_button.png|border|class=tlt-border]]
*'''Password'''
*'''MD5 HMAC'''
</td></tr></table>


====OSPF Area====
The newly added new Area will appear in the OSPF Area list.
----Below is an example of '''OSPF Area''' settings section.[[File:Networking_RUTX_manual_dynamic_routes_ospf_area_v1.png|alt=|border|center]]
 
<br />
[[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">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable</td>
       <td>Name</td>
       <td>off | on; Default: '''off'''</td>
      <td>string on; default: <b>none</b></td>
       <td>Toggles OSPF area ON or OFF</td>
      <td>A custom name for an OSPF Area. Used for easier management purposes only.</td>
    </tr>
    <tr>
      <td>Area</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>
    </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>Cost</td>
       <td>Enable</td>
       <td>IP;Default: " "</td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Specifies OSPF area</td>
       <td>Turns an OSPF Area on or off.</td>
     </tr>
     </tr>
</table>
</table>


====OSPF Networks====
====OSPF Networks====
----Below is an example of '''OSPF Networks''' settings section.[[File:Networking_RUTX_manual_dynamic_routes_ospf_networks_v1.png|alt=|border|center]]
----
<br />
The <b>OSPF Network</b> section is used to add networks to OSPF areas that can later be shared (provide access to) with other OSPF routers.
 
Below is an example of the OSPF Area section which is empty by default.
 
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_networks.png|border|class=tlt-border]]
 
To add a new OSPF Network, look to the Add New Network section; enter a custom name and click the 'Add' button.
 
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_network_add_button.png|border|class=tlt-border]]
 
Your new network will appear in the OSPF Networks list
 
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_networks_configuration.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable</td>
       <td>Name</td>
       <td>off | on; Default: '''off'''</td>
       <td>string on; default: <b>none</b></td>
       <td>Toggles OSPF network ON or OFF</td>
       <td>A custom name for an OSPF Area. Used for easier management purposes only.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Network</td>
       <td>Network</td>
       <td>[a.b.c.d/m]; Default: " "</td>
       <td>ip/netmask; default: <b>none</b></td>
       <td>This command specifies the OSPF enabled interface. If the interface has an address from the range '''a.b.c.d/m''' then enables OSPF on this interface so the router can provide network information to the other OSPF routers via this interface</td>
       <td>IP address/netmask of a network. OSPF Network locations are shared with other OSPF routers.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Area</td>
     <td>Area</td>
         <td>OSPF area; Default: " "</td>
         <td>OSPF area; default: <b>none</b></td>
         <td>Specifies OSPF area</td>
         <td>ID of an OSPF Area (to which this network should belong to).</td>
    </tr>
    <tr>
      <td>Enable</td>
      <td>off {{!}} on; default: <b>off</b></td>
      <td>Turns the usage of this network (in OSPF) on or off.</td>
     </tr>
     </tr>
</table>
</table>


===EIGRP Protocol===
===EIGRP===
----
----
Enhanced Interior Gateway Routing Protocol (EIGRP) is an advanced distance-vector routing protocol that is used on a computer network for automating routing decisions and configuration.
Enhanced Interior Gateway Routing Protocol (EIGRP) is an advanced distance-vector routing protocol that is used on a computer network for automating routing decisions and configuration.
Line 589: Line 1,114:
====General====
====General====
----
----
Below is an example of EIGRP '''General''' settings section.<br />
The <b>General Settings</b> section is used to configure some of the main operating parameters of the EIGRP protocol. Below is an example of the EIGRP General Settings section.
[[File:Networking_RUTX_manual_dynamic_routes_eigrp_general_v1.png|alt=|border|center]]
 
[[File:Networking_rutos_manual_routing_dynamic_routes_eigrp_general_settings_v1.png|border|class=tlt-border]]
 
<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off | on; Default: '''off'''</td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Toggles EIGRP network ON or OFF</td>
       <td>Turns EIGRP protocol usage on or off.</td>
     </tr><tr><td>Enable logging</td><td>off | on; Default: '''off'''</td><td>Enable logging of EIGRP</td></tr><tr><td>AS</td><td>Default: " "</td><td>'''EIGRP''' uses this number so that it makes sure it only talks to other EIGRP speakers that are in the same AS. For instance, if you have two routers, one with "router eigrp 1" and one with "router eigrp 2," then they would not form an adjacency
     </tr>
</td></tr><tr><td>Router ID</td><td>IP; Default: " "</td><td>'''EIGRP''' router-ID in IP address format</td></tr><tr>
    <tr>
        <td>Enable logging</td>
        <td>off {{!}} on; default: <b>off</b></td>
        <td>Turns logging of EIGRP traffic on or off.</td>
    </tr>
    <tr>
        <td>AS</td>
        <td>integer [1..65535]; default: <b>none</b></td>
        <td>EIGRP Autonomous System (AS) number. It is an identifier that represents a routing domain; EIGRP routers can exchange routes within the same Autonomous System.</td>
    </tr>
    <tr>
        <td>Router ID</td>
        <td>ip4; default: <b>none</b></td>
        <td>The router ID is used by EIGRP to identify the routing device from which a packet originated. Default router ID value is selected as the largest IP Address of the interface.</td>
    </tr>
    <tr>
       <td>Network</td>
       <td>Network</td>
      <td>IP; Default: " "</td>
        <td>ip/netmask; default: <b>none</b></td>
      <td>The announcement network</td>
        <td>Adds an announcement network(s). Routes to these networks will be shared over EIGRP.</td>
     </tr><tr><td>Redistribution options</td><td>Default: " "
     </tr>
</td><td>'''Route redistribution''' is a process that allows a network to use a '''routing''' protocol to dynamically '''route''' traffic based on information learned from a different '''routing''' protocol. Available options:
    <tr>
 
        <td>Redistribution options</td>
*'''Connected routes'''
        <td>Connected routes {{!}} Kernel added routes {{!}} NHRP routes {{!}} OSPF routes {{!}} Static routes {{!}} custom; default: <b>none</b></td>
*<b>Kernel added routes</b>
        <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>
*<b>NHRP routes</b>
    </tr>
*<b>OSPF routes</b>
    <tr>
*<b>Static routes</b>
*<b>Custom</b>
</td></tr><tr>
     <td>Neighbors</td>
     <td>Neighbors</td>
         <td>IP; Default: " "</td>
         <td>ip4; default: <b>none</b></td>
         <td>Neighbour IP addres</td>
         <td>Defines the EIGRP Neighbors (based on their IP addresses) that this device is meant to associate with.</td>
     </tr>
     </tr>
</table>
</table>


===NHRP Protocol===
===NHRP===
----Next Hop Resolution Protocol (NHRP) is a protocol or method that can be used so that a computer sending data to another computer can learn the most direct route (the fewest number of hops) to the receiving computer.
----
<b>Next Hop Resolution Protocol</b> (<b>NHRP</b>) is a protocol or method that can be used so that a computer sending data to another computer can learn the most direct route (the fewest number of hops) to the receiving computer.


====General Settings====
====General Settings====
----Below is an example of NHRP '''General''' settings section.[[File:Networking_RUTX_manual_dynamic_routes_nhrp_general_v1.png|alt=|border|center]]<br /><table class="nd-mantable">
----
The <b>General Settings</b> section is used to turn NHRP protocol usage on or off. Below is an example of the NHRP General Settings section.
 
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_general_settings_v2.png|border|class=tlt-border]]
 
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable service</td>
       <td>Enable service</td>
       <td>off | on; Default: '''off'''</td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Toggles NHRP network 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 | on; Default: '''off'''</td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Toggles NHRP logging ON or OFF</td>
       <td>Turns NHRP traffic logging on or off.</td>
     </tr></table>
     </tr></table>


====Interfaces====
====Interfaces====
----Below is an example of NHRP '''Interface''' settings section.
----
[[File:Networking RUTX manual dynamic routes eigrp interfaces v1.png|alt=|border|center]]<br /><table class="nd-mantable">
The <b>Interfaces</b> section is used to define which existing network interfaces can participate in NHRP communication. Below is an example of the NHRP Interfaces section which is empty by default.
 
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_v2.png|border|class=tlt-border]]
 
To create a new NHRP Interface, look to the Add New Interface section; enter a custom name and click the 'Add' button.
 
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_add_button_v2.png|border|class=tlt-border]]
 
The newly added NHRP interface will appear in the Interfaces list and should look similar to this:
 
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_begin_to_edit_v2.png|border|class=tlt-border]]
 
To see more settings for an NHRP Interface, click the 'Edit' button next to it. You will be redirected to a window that looks similar to this:
 
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_interface_configuration_v2.png|border|class=tlt-border]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
        <th>Value</th>
        <th>Description</th>
    </tr>
    <tr>
        <td>Enabled</td>
        <td>off {{!}} on; default: <b>off</b></td>
        <td>Turns the NHRP Interface on or off.</td>
    </tr>
    <tr>
        <td>Interface</td>
        <td>network interface; default: <b>br-lan</b></td>
        <td>Network interface associated with this NHRP Interface.</td>
    </tr>
    <tr>
        <td>Network ID</td>
        <td>32-bit integer; default: <b>none</b></td>
        <td>A numerical identifier for this NHRP Interface.</td>
    </tr>
    <tr>
        <td>NHRP authentication key</td>
        <td>string; default: <b>none</b></td>
        <td>A password used in NHRP authentication.</td>
    </tr>
    <tr>
        <td>NHS</td>
        <td>dynamic {{!}} custom(ip4); default: <b>dynamic</b></td>
        <td>IP address of a Next-Hop server.</td>
    </tr>
    <tr>
        <td>NBMA</td>
        <td>ip4; default: <b>none</b></td>
        <td>Non-Broadcast Multi-Access (NBMA) network IP address.</td>
    </tr>
    <tr>
        <td>Hold-time</td>
        <td>integer; default: <b>7200</b></td>
        <td>Specifies the holding time (in seconds) for NHRP Registration Requests and Resolution Replies sent from this interface or shortcut-target.</td>
    </tr>
    <tr>
        <td>IPsec support</td>
        <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>
    </tr>
    <tr>
        <td><span style="color: red;">IPsec instance</span></td>
        <td>string; default: <b>none</b></td>
        <td>Specifies which existing IPsec instance should be associated with this NHRP Interface. This field becomes visible only when IPsec support is set to 'on'.</td>
    </tr>
</table>
 
=====NHRP Mappings Configuration=====
----
The <b>NHRP Mappings Configuration</b> section is used to configure (map) associations between NHRP router IP address and NBMAs. Below is an example of the NHRP Mappings Configuration section which is empty by default. To add a new configuration, simply click the 'Add' button:
 
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_nhrp_mappings_configuration_add_button_v2.png|border|class=tlt-border]]
 
The newly added configuration should appear in the NHRP Mappings Configuration list and look similar to this:
 
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_nhrp_mappings_configuration_edit_v2.png|border|class=tlt-border]]
 
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
      <th>value</th>
        <th>Value</th>
      <th>description</th>
        <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
      <td>Enable</td>
        <td>IP Address</td>
      <td>off | on; Default: '''off'''</td>
        <td>ip4; default: <b>none</b></td>
      <td>Toggles interface ON or OFF</td>
        <td>Network ID of another NHRP router.</td>
     </tr></table>
    </tr>
    <tr>
        <td>NBMA</td>
        <td>ip4; default: <b>none</b></td>
        <td>IP address of a Next-Hop server.</td>
    </tr>
    <tr>
        <td>Enabled</td>
        <td>off {{!}} on; default: <b>off</b></td>
        <td>Turns this mapping configuration on or off.</td>
     </tr>
</table>
 
=====NHRP NHS Configuration=====
----
The NHRP uses next hop servers (NHS) to register. Below is an example of the NHRP NHS Configuration section which is empty by default. To add a new configuration, simply click the 'Add' button:
 
[[File:Networking rutos manual routing dynamic routes nhrp interfaces nhrp nhs configuration v1.png|border|class=tlt-border]]


By pressing '''Edit''' button you can find more settings related to '''NHRP Interface.'''
The newly added configuration should appear in the NHRP NHS Configuration list and look similar to this:


[[File:Networking_RUTX_manual_dynamic_routes_nhrp_advanced_v1.png|alt=|border|center]]
[[File:Networking rutos manual routing dynamic routes nhrp interfaces nhrp nhs configuration add v1.png|border|class=tlt-border]]
<table class="nd-mantable"><tr><th>field name</th><th>value</th><th>description</th></tr><tr><td>Enable</td><td>off | on; Default: '''off'''</td><td>Enables DMVPN client</td></tr><tr><td>Interface</td><td>Default: '''br-lan'''
</td><td>Interface which will be using NHRP</td></tr><tr><td>Network ID</td><td>Default: " "
</td><td>Network ID of NHRP</td></tr><tr><td>NHS</td><td>Default: " "
</td><td>IP address of Next-Hop Server. Available options:


*'''Dynamic'''
<table class="nd-mantable">
*'''Custom'''
    <tr>
</td></tr><tr><td>NBMA</td><td>Default: " "
        <th>Field</th>
</td><td>Non-Broadcast Multi-Access(NBMA) network IP address</td></tr><tr><td>Hold-time</td><td>Default: '''7200'''
        <th>Value</th>
</td><td>Specifies the holding time for NHRP Registration Requests and Resolution Replies sent from this interface or shortcut-target. The holdtime is specified in seconds and defaults to two hours.</td></tr><tr><td>IPsec support</td><td>off | on; Default: '''off'''
        <th>Description</th>
</td><td>Use NHRP over IPsec</td></tr><tr><td>IP address</td><td>IP; Default: " "
    </tr>
</td><td>Network ID of NHRP</td></tr><tr><td>NBMA</td><td>IP; Default: " "
    <tr>
</td><td>IP address of Next-Hop Server</td></tr></table>
        <td>NHS IP Address</td>
        <td>ip4; default: <b>none</b></td>
        <td>Static Next Hop Server IP address.</td>
    </tr>
    <tr>
        <td>NBMA</td>
        <td>ip4; default: <b>none</b></td>
        <td>Non-Broadcast Multi-Access(NBMA) network IP address of this NHS.</td>
    </tr>
    <tr>
        <td>Enabled</td>
        <td>off {{!}} on; default: <b>off</b></td>
        <td>Turns NHFRP NHS configuration on or off.</td>
    </tr>
</table>|}}


-->
[[Category:{{{name}}} Network section]]

Latest revision as of 08:15, 8 October 2024

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:
  • unicast - most common type of route, simply describes a path to a destination.
  • local - routes of this type are added to the 'local' routing table and used only for locally hosted IPs.
  • broadcast - routes of this type are added to the 'local' routing table and used by link layer devices that support the broadcast address principle.
  • multicast - used for distribution of multicast traffic.
  • unreachable - sends an ICMP "unreachable" response to the source address when a request for a routing decision returns a "destination with an unreachable route type" message.
  • prohibit - used to prohibit traffic to specified host or network. When a destination is prohibited, the kernel sends a 'Network is unreachable' response the source address.
  • blackhole - packets that match this type of route are discarded without any response.
  • anycast - provides a possibility to route incoming requests to multiple different network locations.
  • -- custom -- - does not use any of the predefined route types.

*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:
  • unicast - most common type of route, simply describes a path to a destination.
  • local - routes of this type are added to the 'local' routing table and used only for locally hosted IPs.
  • broadcast - routes of this type are added to the 'local' routing table and used by link layer devices that support the broadcast address principle.
  • multicast - used for distribution of multicast traffic.
  • unreachable - sends an ICMP "unreachable" response to the source address when a request for a routing decision returns a "destination with an unreachable route type" message.
  • prohibit - used to prohibit traffic to specified host or network. When a destination is prohibited, the kernel sends a 'Network is unreachable' response the source address.
  • blackhole - packets that match this type of route are discarded without any response.
  • anycast - provides a possibility to route incoming requests to multiple different network locations.
  • -- custom -- - does not use any of the predefined route types.

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 - routes traffic in accordance with the specified routing table.
  • Jump to rule - specifies another routing rule to follow.
  • Routing Action - executes one of four predefined routing actions.
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]]

Retrieved from "https://wiki.teltonika-networks.com/index.php?title=Template:Networking_rutos_manual_routing&oldid=133814"