Changes

no edit summary
Line 369: Line 369:  
The <b>BGP Instance</b> section is used to configure some of the main operating parameters of the BGP protocol. Below is an example of the BGP Instance section.
 
The <b>BGP Instance</b> section is used to configure some of the main operating parameters of the BGP protocol. Below is an example of the BGP Instance section.
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance_v1.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 406: Line 406:  
         <td>off {{!}} on; default: <b>off</b></td>
 
         <td>off {{!}} on; default: <b>off</b></td>
 
         <td>Compares MEDs between same AS, while ignoring their age.</td>
 
         <td>Compares MEDs between same AS, while ignoring their age.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>eBGP Requires Policy</td>
 +
        <td>off {{!}} on; default: <b>on</b></td>
 +
        <td>Enable/Disable eBGP Import or Export policy requirement. Enabled by default as per RFC 8212.</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
Line 452: Line 457:  
The full BGP Peer configuration page should look similar to this:
 
The full BGP Peer configuration page should look similar to this:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peers_bgp_peer_v2.png|border|class=tlt-border]]
+
[[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 484: Line 489:  
         <td>integer; default: <b>none</b></td>
 
         <td>integer; default: <b>none</b></td>
 
         <td>Time to Live value for packets associated with this remote BGP Neighbor.</td>
 
         <td>Time to Live value for packets associated with this remote BGP Neighbor.</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Weight</td>
 +
        <td>integer [0..65535]; default: <b>none</b></td>
 +
        <td>Specifies a default weight value for the neighbor’s routes. Higher weight is preferred.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 550: Line 560:  
The full BGP Peer Group configuration page should look similar to this:
 
The full BGP Peer Group configuration page should look similar to this:
   −
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_bgp_peer_group.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_peer_groups_bgp_peer_group_v1.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 572: Line 582:  
         <td>ip4; default: <b>none</b></td>
 
         <td>ip4; default: <b>none</b></td>
 
         <td>IPv4 address(es) of a remote BGP Neighbor.</td>
 
         <td>IPv4 address(es) of a remote BGP Neighbor.</td>
 +
    </tr>
 +
        <tr>
 +
    <td>Listen Range</td>
 +
        <td>ip4 with mask; default: <b>none</b></td>
 +
        <td>Accept connections from any peers in the specified prefix.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 594: Line 609:  
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td><span style="color: blue;">Disable next hop calculation:</span> Apply also to ibgp-learned routes</td>
+
         <td>Apply also to ibgp-learned routes</td>
 
         <td>off {{!}} on; default: <b>off</b></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>
 
         <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>
Line 650: Line 665:  
       <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 Access filter on or off.</td>
 +
    </tr>
 +
</table>
 +
 +
====Route Maps====
 +
----
 +
A <b>Route Maps</b>  allow you to configure a filtering criteria by defining a set of rules or match statements with a permit or deny condition. It includes a series of match statements to determine if a route matches the criteria defined in the statement and then apply the permit or deny rule accordingly.
 +
 +
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps.png|border|class=tlt-border]]
 +
 +
To create a new Route Maps, look to the Add New Instance section under Route Maps; type in a custom name for the Route Map and click the 'Add' button:
 +
 +
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_add_button.png|border|class=tlt-border]]
 +
 +
The newly added Route Map configuration should look similar to this:
 +
 +
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_added.png|border|class=tlt-border]]
 +
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
      <th>Value</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td>Drag-cursor</td>
 +
      <td>- (interactive button)</td>
 +
      <td>Changes the priority(metric) of the route maps.</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Action</td>
 +
        <td>Permit {{!}} Deny; default: <b>Permit</b></td>
 +
        <td>IPv4 address of this remote BGP Neighbor.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Enable</td>
 +
      <td>off {{!}} on; default: <b>off</b></td>
 +
      <td>Turns this Route Map on or off.</td>
 +
    </tr>
 +
</table>
 +
 +
To see more settings for a Route Maps, click the 'Edit' button next to it:
 +
 +
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_edit_button.png|border|class=tlt-border]]
 +
 +
The full Route Maps configuration page should look similar to this:
 +
 +
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_edit.png|border|class=tlt-border]]
 +
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
      <th>Value</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td>Enable</td>
 +
      <td>off {{!}} on; default: <b>off</b></td>
 +
      <td>Turns the Route Maps configuration on or off.</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Action</td>
 +
        <td>Permit {{!}} Deny; default: <b>Permit</b></td>
 +
        <td>IPv4 address of this remote BGP Neighbor.</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Local preference</td>
 +
        <td>integer [0..4294967295]; default: <b>none</b></td>
 +
        <td>Used to determine best route towards a certain destination.</td>
 +
    </tr>
 +
        <tr>
 +
    <td>Metric</td>
 +
        <td>ip4 with mask; default: <b>none</b></td>
 +
        <td>Sets a metric value for determining the preferred path into an AS.</td>
 +
    </tr>
 +
</table>
 +
 +
====Route Map Filters====
 +
----
 +
The <b>Route Map Filters</b> section is used to configure special filters that changes direction for BGP Peers. Below is an example of the Route Map Filters section which is empty by default. You can add a new filter by clicking the 'Add' button
 +
 +
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_filters_add_button.png|border|class=tlt-border]]
 +
 +
An Route Map Filters configuration for BGP should look similar to this:
 +
 +
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_route_maps_filters_configuration.png|border|class=tlt-border]]
 +
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
      <th>Value</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td>Peer</td>
 +
      <td>bgp peer; default: <b>none</b></td>
 +
      <td>Applies the filter rule for the specified peer.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Route map</td>
 +
      <td>route map; default: <b>none</b></td>
 +
      <td>Route map filter to apply.</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Direction</td>
 +
        <td>Inbound {{!}} Outbound; default: <b>Inbound</b></td>
 +
        <td>If direction is Inbound, the access list is applied to input routes. If direction is Outbound the access list is applied to advertised routes.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Enable</td>
 +
      <td>off {{!}} on; default: <b>off</b></td>
 +
      <td>Turns an Route Map filter on or off.</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>

Navigation menu