Changes

no edit summary
Line 1: Line 1: −
{{Template: Networking_rutos_manual_fw_disclosure
+
{{Template: Networking_device_manual_fw_disclosure
| fw_version ={{Template: Networking_rutos_manual_latest_fw
+
| series = {{{series}}}
 +
| name  = {{{name}}}
 +
| fw_version ={{Template: Networking_device_manual_latest_fw
 
  | series = {{{series}}}
 
  | series = {{{series}}}
 
  | name  = {{{name}}}
 
  | name  = {{{name}}}
 
  }}
 
  }}
 
}}
 
}}
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} Routing (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}}
+
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} Routing (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}}
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} Routing (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
+
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} Routing (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
 
==Summary==
 
==Summary==
   Line 330: Line 332:  
<u><b>
 
<u><b>
   −
Note:</b> Dynamic Routing is additional software that can be installed from the <b>Services → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u>
+
Note:</b> Dynamic Routing is additional software that can be installed from the <b>System → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u>
 
}}
 
}}
 
===BGP===
 
===BGP===
Line 340: Line 342:  
The <b>General Settings</b> section is used to turn BGP protocol usage on or off or to upload an external BGP configuration. Below is an example of the BGP General Settings section.
 
The <b>General Settings</b> section is used to turn BGP protocol usage on or off or to upload an external BGP configuration. Below is an example of the BGP General Settings section.
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_general_settings.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_general_settings_v1.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 367: Line 369:  
====BGP Instance====
 
====BGP Instance====
 
----
 
----
The <b>BGP Instance</b> section is used to configure some of the main operating parameters of the BGP protocol. Below is an example of the BGP Instance section.
     −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance_v1.png|border|class=tlt-border]]
+
To create a new BGP instance, look to the Add New Instance section under BGP instances; type in a custom name for the BGP instance and click the 'Add' button or you can 'Edit' a general instance:
 +
 
 +
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance_edit.png|border|class=tlt-border]]
 +
 
 +
You will be redirected to general BGP instance settings:
 +
 
 +
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance_v2.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 384: Line 391:  
     <tr>
 
     <tr>
 
       <td>AS</td>
 
       <td>AS</td>
       <td>integer [1..65535]default: <b>none</b></td>
+
       <td>integer [1..4294967295]; default: <b>none</b></td>
         <td>BGP Autonomous System (AS) number. It is an identifier that represents a routing domain; BGP routers can exchange routes within the same Autonomous System.</td>
+
         <td>AS number is an identification of an autonomous system. BGP protocol uses the AS number for detecting whether the BGP connection is an internal one or external one.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 396: Line 403:  
         <td>ip/netmask; default: <b>none</b></td>
 
         <td>ip/netmask; default: <b>none</b></td>
 
         <td>Adds an announcement network(s). Routes to these networks will be shared over BGP.</td>
 
         <td>Adds an announcement network(s). Routes to these networks will be shared over BGP.</td>
 +
    </tr>
 +
    <tr>
 +
    <td>VRF interface</td>
 +
        <td>VRF interface; default: <b>Default</b></td>
 +
        <td>To create new VRF interface, please visit: [[{{{name}}} VRF|VRF]] </td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 414: Line 426:  
</table>
 
</table>
   −
====BGP Peers====
+
=====BGP Peers=====
 
----
 
----
 
<b>BGP Peers</b> are routers in the same BGP Peer Group that can redistribute routes among other BGP Peers. Below is an example of the BGP Peers section, which is empty by default.
 
<b>BGP Peers</b> are routers in the same BGP Peer Group that can redistribute routes among other BGP Peers. Below is an example of the BGP Peers section, which is empty by default.
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_v2.png|border|class=tlt-border]]
    
To create a new Peer, look to the Add New Instance section under BGP Peer; type in a custom name for the BGP Peer and click the 'Add' button:
 
To create a new Peer, look to the Add New Instance section under BGP Peer; type in a custom name for the BGP Peer and click the 'Add' button:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_add_button.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_add_button_v1.png|border|class=tlt-border]]
   −
The newly added BGP Peer configuration should look similar to this:
+
You will be redirected to general peer settings:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_added.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_bgp_peer_v4.png|border|class=tlt-border]]
 
  −
<table class="nd-mantable">
  −
    <tr>
  −
        <th>Field</th>
  −
      <th>Value</th>
  −
      <th>Description</th>
  −
    </tr>
  −
    <tr>
  −
      <td>Remote AS</td>
  −
      <td>integer [1..65535]; default: <b>none</b></td>
  −
      <td>Remote autonomous system number of this remote BGP Neighbor.</td>
  −
    </tr>
  −
    <tr>
  −
    <td>Remote address</td>
  −
        <td>ip4; default: <b>none</b></td>
  −
        <td>IPv4 address of this remote BGP Neighbor.</td>
  −
    </tr>
  −
    <tr>
  −
      <td>Enable</td>
  −
      <td>off {{!}} on; default: <b>off</b></td>
  −
      <td>Turns turns this BGP peer on or off.</td>
  −
    </tr>
  −
</table>
  −
 
  −
To see more settings for a BGP Peer, click the 'Edit' button next to it:
  −
 
  −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_edit_button.png|border|class=tlt-border]]
  −
 
  −
The full BGP Peer configuration page should look similar to this:
  −
 
  −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_bgp_peer_v3.png|border|class=tlt-border]]
      
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 472: Line 453:  
     <tr>
 
     <tr>
 
       <td>Remote AS</td>
 
       <td>Remote AS</td>
       <td>integer [1..65535]; default: <b>none</b></td>
+
       <td>integer [1..4294967295]; default: <b>none</b></td>
 
       <td>Remote autonomous system number of this remote BGP Neighbor.</td>
 
       <td>Remote autonomous system number of this remote BGP Neighbor.</td>
 
     </tr>
 
     </tr>
Line 478: Line 459:  
     <td>Remote address</td>
 
     <td>Remote address</td>
 
         <td>ip4; default: <b>none</b></td>
 
         <td>ip4; default: <b>none</b></td>
         <td>IPv4 address of this remote BGP Neighbor.</td>
+
         <td>IPv4 address of this remote BGP Neighbor. This option is required.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 527: Line 508:  
</table>
 
</table>
   −
====BGP Peer Groups====
+
=====BGP Peer Groups=====
 
----
 
----
 
A <b>BGP Peer Group</b> is a collection of routers that use the BGP protocol to dynamically redistribute routes among peers (other routers). The figure below is an example of the BGP Peer Groups section, which is empty by default.
 
A <b>BGP Peer Group</b> is a collection of routers that use the BGP protocol to dynamically redistribute routes among peers (other routers). The figure below is an example of the BGP Peer Groups section, which is empty by default.
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_v2.png|border|class=tlt-border]]
    
To create a new Peer Group, look to the Add New Instance section under BGP Peer Groups; type in a custom name for the BGP Peer Group and click the 'Add' button:
 
To create a new Peer Group, look to the Add New Instance section under BGP Peer Groups; type in a custom name for the BGP Peer Group and click the 'Add' button:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_add_button.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_groups_add_button_v1.png|border|class=tlt-border]]
   −
The newly added BGP Peer Group configuration should look similar to this:
+
You will be redirected to general peer groups settings:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_added.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_bgp_peer_group_v2.png|border|class=tlt-border]]
 
  −
<table class="nd-mantable">
  −
    <tr>
  −
        <th>Field</th>
  −
      <th>Value</th>
  −
      <th>Description</th>
  −
    </tr>
  −
    <tr>
  −
      <td>Remote AS</td>
  −
      <td>integer [1..65535]; default: <b>none</b></td>
  −
      <td>Remote autonomous system number.</td>
  −
    </tr>
  −
</table>
  −
 
  −
To see more settings for a BGP Peer Group, click the 'Edit' button next to it:
  −
 
  −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_edit_button.png|border|class=tlt-border]]
  −
 
  −
The full BGP Peer Group configuration page should look similar to this:
  −
 
  −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_bgp_peer_group_v1.png|border|class=tlt-border]]
      
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 576: Line 536:  
       <td>Remote AS</td>
 
       <td>Remote AS</td>
 
       <td>integer [1..65535]; default: <b>none</b></td>
 
       <td>integer [1..65535]; default: <b>none</b></td>
       <td>Remote autonomous system number.</td>
+
       <td>Neighbour's remote AS.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Neighbor address</td>
 
     <td>Neighbor address</td>
 
         <td>ip4; default: <b>none</b></td>
 
         <td>ip4; default: <b>none</b></td>
         <td>IPv4 address(es) of a remote BGP Neighbor.</td>
+
         <td>Neighbour's remote IPv4 address.</td>
 
     </tr>
 
     </tr>
 
         <tr>
 
         <tr>
Line 591: Line 551:  
         <td>Advertisement interval</td>
 
         <td>Advertisement interval</td>
 
         <td>integer; default: <b>none</b></td>
 
         <td>integer; default: <b>none</b></td>
         <td>BGP advertisement frequency (in seconds).</td>
+
         <td>Delay between updates for a neighbor session (in seconds).</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 625: Line 585:  
</table>
 
</table>
   −
====Access List Filters====
+
=====Route Map 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
+
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_access_list_filters_add_button.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_filters_add_button_v1.png|border|class=tlt-border]]
   −
An Access List Filter configuration for BGP should look similar to this:
+
An Route Map Filters configuration for BGP should look similar to this:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_access_list_filters_configuration.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_filters_configuration_v1.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 643: Line 603:  
     <tr>
 
     <tr>
 
       <td>Peer</td>
 
       <td>Peer</td>
       <td>bgp peer; default: <b>none</b></td>
+
       <td>bgp peer; default: <b>-</b></td>
 
       <td>Applies the filter rule for the specified peer.</td>
 
       <td>Applies the filter rule for the specified peer.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
    <td>Action</td>
+
      <td>Route map</td>
        <td>Permit {{!}} Deny; default: <b>Permit</b></td>
+
      <td>route map; default: <b>-</b></td>
        <td>When BGP traffic matches this rule, the device will take the action specified in this field, which is to either allow or block traffic.</td>
+
      <td>Route map filter to apply.</td>
    </tr>
  −
    <tr>
  −
    <td>Network</td>
  −
        <td>ip/netmask {{!}} Any; default: <b>Any</b></td>
  −
        <td>Matches traffic destined or originating from (depends on 'Direction' selection) to the network specified in this field.</td>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Direction</td>
 
     <td>Direction</td>
 
         <td>Inbound {{!}} Outbound; default: <b>Inbound</b></td>
 
         <td>Inbound {{!}} Outbound; default: <b>Inbound</b></td>
         <td>Matches network traffic direction, which can either be traffic destined to this device (Inbound) or traffic originating from this device (Outbound).</td>
+
         <td>If direction is Inbound, the access list is applied to input routes. If direction is Outbound the access list is applied to advertised routes.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Enable</td>
 
       <td>Enable</td>
 
       <td>off {{!}} on; default: <b>off</b></td>
 
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns an Access filter on or off.</td>
+
       <td>Turns an Route Map filter on or off.</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
   −
====Route Maps====
+
====Access List Filters====
 
----
 
----
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.
+
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_route_maps.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_access_list_filters_add_button_v1.png|border|class=tlt-border]]
   −
To create a new Route Maps, look to the Add New Instance section under Route Maps; type in a custom name for the Route Map and click the 'Add' button:
+
An Access List Filter configuration for BGP should look similar to this:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_add_button.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_access_list_filters_configuration_v2.png|border|class=tlt-border]]
 
  −
The newly added Route Map configuration should look similar to this:
  −
 
  −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_added.png|border|class=tlt-border]]
      
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 689: Line 640:  
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
       <td>Drag-cursor</td>
+
       <td>Peer</td>
       <td>- (interactive button)</td>
+
       <td>bgp peer; default: <b>-</b></td>
       <td>Changes the priority(metric) of the route maps.</td>
+
       <td>Applies the filter rule for the specified peer.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Action</td>
 
     <td>Action</td>
 
         <td>Permit {{!}} Deny; default: <b>Permit</b></td>
 
         <td>Permit {{!}} Deny; default: <b>Permit</b></td>
         <td>IPv4 address of this remote BGP Neighbor.</td>
+
         <td>When BGP traffic matches this rule, the device will take the action specified in this field, which is to either allow or block traffic.</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Filter network</td>
 +
        <td>Any {{!}} custom; default: <b>Any</b></td>
 +
        <td>Applies filter rule for this source network.</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: <b>off</b></td>
 
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns this Route Map on or off.</td>
+
       <td>Turns an Access filter on or off.</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
   −
To see more settings for a Route Maps, click the 'Edit' button next to it:
+
====Route Maps====
 +
----
 +
A <b>Route Maps</b>  allow you to configure a filtering criteria by defining a set of rules or match statements with a permit or deny condition. It includes a series of match statements to determine if a route matches the criteria defined in the statement and then apply the permit or deny rule accordingly.
 +
 
 +
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_v1.png|border|class=tlt-border]]
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_edit_button.png|border|class=tlt-border]]
+
To create a new Route Maps, look to the Add New Instance section under Route Maps; type in a custom name for the Route Map and click the 'Add' button:
   −
The full Route Maps configuration page should look similar to this:
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_add_button_v1.png|border|class=tlt-border]]
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_edit.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">
 
<table class="nd-mantable">
Line 738: Line 705:  
         <td>ip4 with mask; default: <b>none</b></td>
 
         <td>ip4 with mask; default: <b>none</b></td>
 
         <td>Sets a metric value for determining the preferred path into an AS.</td>
 
         <td>Sets a metric value for determining the preferred path into an AS.</td>
    </tr>
  −
</table>
  −
  −
====Route Map Filters====
  −
----
  −
The <b>Route Map Filters</b> section is used to configure special filters that changes direction for BGP Peers. Below is an example of the Route Map Filters section which is empty by default. You can add a new filter by clicking the 'Add' button
  −
  −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_filters_add_button.png|border|class=tlt-border]]
  −
  −
An Route Map Filters configuration for BGP should look similar to this:
  −
  −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_filters_configuration.png|border|class=tlt-border]]
  −
  −
<table class="nd-mantable">
  −
    <tr>
  −
        <th>Field</th>
  −
      <th>Value</th>
  −
      <th>Description</th>
  −
    </tr>
  −
    <tr>
  −
      <td>Peer</td>
  −
      <td>bgp peer; default: <b>none</b></td>
  −
      <td>Applies the filter rule for the specified peer.</td>
  −
    </tr>
  −
    <tr>
  −
      <td>Route map</td>
  −
      <td>route map; default: <b>none</b></td>
  −
      <td>Route map filter to apply.</td>
  −
    </tr>
  −
    <tr>
  −
    <td>Direction</td>
  −
        <td>Inbound {{!}} Outbound; default: <b>Inbound</b></td>
  −
        <td>If direction is Inbound, the access list is applied to input routes. If direction is Outbound the access list is applied to advertised routes.</td>
  −
    </tr>
  −
    <tr>
  −
      <td>Enable</td>
  −
      <td>off {{!}} on; default: <b>off</b></td>
  −
      <td>Turns an Route Map filter on or off.</td>
   
     </tr>
 
     </tr>
 
</table>
 
</table>
Line 787: Line 716:  
The <b>General Settings</b> section is used to configure some of the main operating parameters of the RIP protocol. Below is an example of the RIP General Settings section.
 
The <b>General Settings</b> section is used to configure some of the main operating parameters of the RIP protocol. Below is an example of the RIP General Settings section.
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_general_settings.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_general_settings_v1.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 834: Line 763:  
RIP Interface configuration should look similar to this:
 
RIP Interface configuration should look similar to this:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_rip_interfaces_configuration.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_rip_interfaces_configuration_v1.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 841: Line 770:  
       <th>Value</th>
 
       <th>Value</th>
 
       <th>Description</th>
 
       <th>Description</th>
    </tr>
  −
    <tr>
  −
      <td>Enable</td>
  −
      <td>off {{!}} on; default: <b>off</b></td>
  −
      <td>Turns a RIP Interface on or off.</td>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 856: Line 780:  
         <td>off {{!}} on; default: <b>off</b></td>
 
         <td>off {{!}} on; default: <b>off</b></td>
 
         <td>Sets the specified interface to passive mode. On passive mode interface, all receiving packets are processed as normal and <b>ripd</b> does not send either multicast or unicast RIP packets.</td>
 
         <td>Sets the specified interface to passive mode. On passive mode interface, all receiving packets are processed as normal and <b>ripd</b> does not send either multicast or unicast RIP packets.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Enable</td>
 +
      <td>off {{!}} on; default: <b>off</b></td>
 +
      <td>Turns a RIP Interface on or off.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Delete</td>
 +
      <td>- (interactive button)</td>
 +
      <td>Deletes RIP inerfaces instance.</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
Line 865: Line 799:  
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_access_list_filters.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_access_list_filters.png|border|class=tlt-border]]
   −
To add a new filter, look to the Add New Filter section; enter a custom name and click the 'Add' button:
+
To add a new filter, look to the Add New Instance section; enter a custom name and select RIP interface then click the 'Add' button:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_access_list_filters_add_button.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_access_list_filters_add_button_v1.png|border|class=tlt-border]]
    
An Access List Filter configuration for RIP should look similar to this:
 
An Access List Filter configuration for RIP should look similar to this:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_access_list_filters_configuration.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_rip_access_list_filters_configuration_v1.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 919: Line 853:  
The <b>General Settings</b> section is used to configure some of the main operating parameters of the OSPF protocol. Below is an example of the OSPF General Settings section.
 
The <b>General Settings</b> section is used to configure some of the main operating parameters of the OSPF protocol. Below is an example of the OSPF General Settings section.
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_general_settings_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_general_settings_v3.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 1,100: Line 1,034:  
The newly added new Area will appear in the OSPF Area list.
 
The newly added new Area will appear in the OSPF Area list.
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_area_configuration.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_ospf_protocol_ospf_area_configuration_v1.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 1,117: Line 1,051:  
       <td>32-bit integer; default: <b>none</b></td>
 
       <td>32-bit integer; default: <b>none</b></td>
 
       <td>OSPF Area ID. OSPF Networks that are meant to communicate with each other should belong to the same Area (have the Area ID).</td>
 
       <td>OSPF Area ID. OSPF Networks that are meant to communicate with each other should belong to the same Area (have the Area ID).</td>
 +
    </tr>
 +
    <tr>
 +
      <td>STUB</td>
 +
      <td>off {{!}} on; default: <b>off</b></td>
 +
      <td>A stub area is an area in which advertisements of external routes are not allowed, reducing the size of the database.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 1,177: Line 1,116:  
The <b>General Settings</b> section is used to configure some of the main operating parameters of the EIGRP protocol. Below is an example of the EIGRP General Settings section.
 
The <b>General Settings</b> section is used to configure some of the main operating parameters of the EIGRP protocol. Below is an example of the EIGRP General Settings section.
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_eigrp_general_settings.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_eigrp_general_settings_v1.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 1,230: Line 1,169:  
The <b>General Settings</b> section is used to turn NHRP protocol usage on or off. Below is an example of the NHRP General Settings section.
 
The <b>General Settings</b> section is used to turn NHRP protocol usage on or off. Below is an example of the NHRP General Settings section.
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_general_settings.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_general_settings_v2.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">