Difference between revisions of "Template:Networking rutx manual routing"

From Wiki Knowledge Base | Teltonika
 
(108 intermediate revisions by 2 users not shown)
Line 7: Line 7:
 
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.
 
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.
  
[[Image:Network routing static routes.PNG]]
+
===Static IPv4 Routes===
 +
----
 +
Below is an example and information about Static IPv4 Routes.
 +
[[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>
 +
 
 +
<span class="asterisk">*</span><b>Additional notes on Target & Netmask:</b>
  
<table class="nd-mantable">
+
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 />
    <tr>
+
===Static IPv6 Routes===
        <th>field name</th>
+
----
      <th>value</th>
+
Settings for Static IPv6 routes are the same as for IPv4 only that the target IP and and gateway are different.
      <th>description</th>
+
[[File:Networking_RUTX_manual_static_routes_ipv6_v1.png|alt=|border|center]]
    </tr>
+
<br />
    <tr>
 
      <td>Routing table</td>
 
      <td>MAIN | WAN | WAN2 | WAN3; Default: '''MAIN'''</td>
 
      <td>Defines which table will be used for the route in question</td>
 
    </tr>
 
    <tr>
 
      <td>Interface</td>
 
      <td>LAN | WAN(Wired) | WAN2(Mobile) | WAN3(WiFi) | VPN instances; Default: '''WAN(Wired)'''</td>
 
      <td>The zone where the target network resides</td>
 
    </tr>
 
    <tr>
 
    <td>Destination address'''*'''</td>
 
        <td>ip; Default: '''0.0.0.0'''</td>
 
        <td>The address of the destination network</td>
 
    </tr>
 
    <tr>
 
    <td>Netmask'''*'''</td>
 
        <td>ip; Default: '''0.0.0.0'''</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: " "</td>
 
        <td>Defines where the router should send all the traffic that applies to the rule</td>
 
    </tr>
 
    <tr>
 
    <td>Metric</td>
 
        <td>integer; Default: '''0'''</td>
 
        <td>The '''Metric''' value is used as a sorting measure. If a packet about to be routed fits two rules, the one with the higher metric is applied</td>
 
    </tr>
 
</table>
 
  
 +
==Advanced Static Routes==
  
'''*Additional notes on Destination & Netmask:'''
+
Advanced static routing includes features and concepts that are used in more complex networks.
  
You can define a rule that applies to a single IP like this: Destination - some IP; Netmask - 255.255.255.255. Furthermore, you can define a rule that applies to a segment of IPs like this: Destination – some IP that STARTS some segment; Netmask – Netmask that defines how large the segment is. e.g.:
+
===Routing Tables===
<table class="nd-mantable">
+
----
 +
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
 +
[[File:Networking RUTX manual advaced static routes tables v1.png|alt=|border|center|1128x1128px]]
 +
 
 +
===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.
 +
[[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 RUTX manual advaced static routes rules settings v1.png|alt=|border|center|1145x1145px]]<table class="nd-mantable">
 
     <tr>
 
     <tr>
 
         <th>field name</th>
 
         <th>field name</th>
Line 58: Line 44:
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
       <td>192.168.55.161</td>
+
       <td>Priority</td>
       <td>255.255.255.255</td>
+
       <td>Default: '''auto-assigned'''</td>
       <td>Only applies to 192.168.55.161</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.
    </tr>
+
</td>
    <tr>
 
      <td>192.168.55.0</td>
 
      <td>255.255.255.240</td>
 
      <td>Applies to IPs in the 192.168.55.0 - 192.168.55.255</td>
 
    </tr>
 
    <tr>
 
    <td>192.168.55.240</td>
 
        <td>255.255.255.240</td>
 
        <td>192.168.55.240 - 192.168.55.255</td>
 
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
    <td>192.168.55.161</td>
+
      <td>Incoming interface</td>
        <td>255.255.255.0</td>
+
      <td>Default: '''Any'''</td>
        <td>192.168.55.0 - 192.168.55.255</td>
+
      <td>Specifies the incoming logical interface name</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
     <td>192.168.0.0</td>
+
     <td>Outgoing interface</td>
         <td>255.255.0.0</td>
+
        <td>Default: '''None'''</td>
        <td>192.168.0.0 - 192.168.255.255</td>
+
         <td>Specifies the outgoing logical interface name
    </tr>
+
</td>
</table>
+
    </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)
 
+
</td></tr><tr><td>Destination subnet</td><td>IPv4; Default: '''0.0.0.0'''</td><td>Specifies the destination subnet to match (CIDR notation)
===Static ARP entries===
+
</td></tr><tr><td>TOS Value to Match</td><td>Default: <b>0</b>
----
+
</td><td>Specifies the TOS value to match in IP headers
Static ARP entries are used to bind a MAC address to a specific IP address. For example, if you want a device to get the same IP every time it connects to the router, you can create a Static ARP entry by binding that device’s MAC address to the desired IP address. The router will then create an entry in the ARP table, which in turn will make sure that that device will get the specified IP address every time.
+
</td></tr><tr><td>Firewall Mark</td><td>Default: '''0xFF'''
 +
</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
 +
</td></tr><tr><td>Invert matches</td><td>off | on; Default: '''off'''
 +
</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>Default: '''Lookup Table'''
 +
</td><td>Available options:
  
[[Image:Network routing static routes static arp entries.PNG]]
+
*'''Lookup table'''
 +
*'''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>
  
 
==Dynamic Routes==
 
==Dynamic Routes==
 
  
 
===BGP Protocol===
 
===BGP Protocol===
Line 98: Line 84:
  
 
====General Settings====
 
====General Settings====
----
+
----Below is an example of BGP '''General''' settings section.[[File:Networking_RUTX_manual_dynamic_routes_bgp_general_v1.png|alt=|border|center]]
 
+
<br />
[[Image:Network routing dynamic routes bgp general.PNG]]
 
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 110: Line 95:
 
     <tr>
 
     <tr>
 
       <td>Enable</td>
 
       <td>Enable</td>
       <td>yes | no; Default: '''no'''</td>
+
       <td>off | on; Default: '''off'''</td>
 
       <td>Toggles the BGP protocol ON or OFF</td>
 
       <td>Toggles the BGP protocol ON or OFF</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Enable vty</td>
 
       <td>Enable vty</td>
       <td>yes | no; Default: '''no'''</td>
+
       <td>off | on; Default: '''off'''</td>
       <td>Toggles vty access from LAN ON or OFF</td>
+
       <td>Toggles vty access ON or OFF</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 126: Line 111:
  
 
====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 />
[[Image:Network routing dynamic routes bgp instance.PNG]]
 
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 138: Line 122:
 
     <tr>
 
     <tr>
 
       <td>Enable</td>
 
       <td>Enable</td>
       <td>yes | no; Default: '''no'''</td>
+
       <td>off | on; Default: '''off'''</td>
 
       <td>Toggles the BGP instance ON or OFF</td>
 
       <td>Toggles the BGP instance ON or OFF</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>AS</td>
 
       <td>AS</td>
       <td>integer: " "</td>
+
       <td>Default: " "</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. '''[Required]'''</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>BGP router ID</td>
 
     <td>BGP router ID</td>
         <td>string; Default: " "</td>
+
         <td>Default: " "</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>string; Default: " "</td>
+
         <td>Default: " "</td>
 
         <td>Add an announcement network(s)</td>
 
         <td>Add an announcement network(s)</td>
     </tr>
+
     </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:
</table>
+
 
 +
*'''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====
 
====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 />
[[Image:Network routing dynamic routes bgp peers.PNG]]
 
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 171: Line 162:
 
     <tr>
 
     <tr>
 
       <td>Enable</td>
 
       <td>Enable</td>
       <td>yes | no; Default: '''no'''</td>
+
       <td>off | on; Default: '''off'''</td>
 
       <td>Toggles the BGP peer ON or OFF</td>
 
       <td>Toggles the BGP peer ON or OFF</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Remote AS</td>
 
       <td>Remote AS</td>
       <td>integer: " "</td>
+
       <td>Default: " "</td>
 
       <td>Neighbour's remote AS</td>
 
       <td>Neighbour's remote AS</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Remote address</td>
 
     <td>Remote address</td>
         <td>ip; Default: " "</td>
+
         <td>IP; Default: " "</td>
 
         <td>Neighbour's remote IPv4 address</td>
 
         <td>Neighbour's remote IPv4 address</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
  
====Access List Filters====
+
By pressing '''Edit''' button you can find more settings related to '''BGP Peer.'''
 +
 
 +
[[File:Networking_RUTX_manual_dynamic_routes_bgp_peers_advanced_v1.png|alt=|border|1145x1145px|center]]
 +
 
 +
<br /><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>Toggles BGP Peer ON or OFF</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Remote AS</td>
 +
      <td>Default: " "</td>
 +
      <td>Neighbour's remote AS</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Remote address</td>
 +
        <td>IP; Default: " "</td>
 +
        <td>Neighbour's remote IPv4 address</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Remote port</td>
 +
        <td>Default: " "</td>
 +
        <td>Neighbour's remote port
 +
</td>
 +
    </tr>
 +
    <tr>
 +
    <td>EBGP Multihop</td>
 +
        <td>Default: " "</td>
 +
        <td>Time to Live value</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
 +
</td></tr></table>
 +
 
 +
====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.
 +
[[File:Networking RUTX manual dynamic routes bgp peer groups v1.png|alt=|border|center|]]
 +
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>field name</th>
 +
      <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.'''
 +
 +
[[File:Networking RUTX manual dynamic routes bgp peer groups config v1.png|alt=|border|center]]
 +
 +
<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>Toggles the BGP Peer-Group ON or OFF</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Remote AS</td>
 +
      <td>Default: " "</td>
 +
      <td>Neighbour's remote AS</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Neighbor address</td>
 +
        <td>IP; Default: " "</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:
 +
 +
*'''None'''
 +
*'''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>
  
[[Image:Network routing dynamic routes bgp access list filters.PNG]]
+
====Access List Filters====
 +
----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">
Line 199: Line 279:
 
     <tr>
 
     <tr>
 
       <td>Enable</td>
 
       <td>Enable</td>
       <td>yes | no; Default: '''no'''</td>
+
       <td>off | on; Default: '''off'''</td>
 
       <td>Toggles the Access filter ON or OFF</td>
 
       <td>Toggles the Access filter ON or OFF</td>
 
     </tr>
 
     </tr>
Line 209: Line 289:
 
     <tr>
 
     <tr>
 
     <td>Action</td>
 
     <td>Action</td>
         <td>Permit | Deny; Default: '''Permit'''</td>
+
         <td>Default: '''Permit'''</td>
         <td>Denies or permits matched entry</td>
+
         <td>Denies or permits matched entry. Available options:
 +
 
 +
*'''Permit'''
 +
*'''Deny'''
 +
</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Network</td>
 
     <td>Network</td>
         <td>Any | ip; Default: '''Any'''</td>
+
         <td>Default: '''Any'''</td>
         <td>Applies filter rule for this source network</td>
+
         <td>Applies filter rule for this source network. Available options:
 +
 
 +
*'''Any'''
 +
*'''Custom (IP)'''
 +
</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Direction</td>
 
     <td>Direction</td>
         <td>Inbound | Outbound; Default: '''Inbound'''</td>
+
         <td>Default: '''Inbound'''</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>
+
         <td>Available options:
 +
 
 +
*'''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>
Line 229: Line 323:
  
 
====General====
 
====General====
----
+
----Below is an example of RIP '''General''' settings section.[[File:Networking_RUTX_manual_dynamic_routes_rip_general_v1.png|alt=|border|center]]
 
+
<br />
[[Image:Network routing dynamic routes rip general.PNG]]
 
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 241: Line 334:
 
     <tr>
 
     <tr>
 
       <td>Enable</td>
 
       <td>Enable</td>
       <td>yes | no; Default: '''no'''</td>
+
       <td>off | on; Default: '''off'''</td>
 
       <td>Toggles RIP Protocol ON or OFF</td>
 
       <td>Toggles RIP Protocol ON or OFF</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Enable vty</td>
 
       <td>Enable vty</td>
       <td>yes | no; Default: '''no'''</td>
+
       <td>off | on; Default: '''off'''</td>
       <td>Toggles vty access from LAN ON or OFF</td>
+
       <td>Toggles vty access ON or OFF</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 256: Line 349:
 
     <tr>
 
     <tr>
 
     <td>Version</td>
 
     <td>Version</td>
         <td>2 | 1; Default: '''2'''</td>
+
         <td>Default: '''2'''</td>
         <td>Specifies the version of RIP</td>
+
         <td>Specifies the version of RIP. Available options:
 +
 
 +
*'''1'''
 +
*'''2'''
 +
</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Neighbor</td>
 
     <td>Neighbor</td>
         <td>ip; Default: " "</td>
+
         <td>Default: " "</td>
 
         <td>Neighbour IP addres</td>
 
         <td>Neighbour IP addres</td>
 
     </tr>
 
     </tr>
Line 267: Line 364:
  
 
====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 />
[[Image:Network routing dynamic routes rip rip interfaces.PNG]]
 
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 279: Line 375:
 
     <tr>
 
     <tr>
 
       <td>Enable</td>
 
       <td>Enable</td>
       <td>yes | no; Default: '''no'''</td>
+
       <td>off | on; Default: '''off'''</td>
 
       <td>Toggles RIP Interface ON or OFF</td>
 
       <td>Toggles RIP Interface ON or OFF</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Interface</td>
 
       <td>Interface</td>
       <td>network interface; Default: '''no'''</td>
+
       <td>network interfaces; Default: '''loopback'''</td>
 
       <td>Network interface to be used with the RIP interface</td>
 
       <td>Network interface to be used with the RIP interface</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Passive interface</td>
 
     <td>Passive interface</td>
         <td>yes | no; Default: '''no'''</td>
+
         <td>off | on; Default: '''off'''</td>
         <td>Sets the specified interface to passive mode. On passive mode interface, all receiving packets are processed as normal and ripd does not send either multicast or unicast RIP packets</td>
+
         <td>Sets the specified interface to passive mode. On passive mode interface, all receiving packets are processed as normal and ripd does not send either multicast or unicast RIP packets
 +
</td>
 
     </tr>
 
     </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 />
[[Image:Network routing dynamic routes rip access list filters.PNG]]
 
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 307: Line 403:
 
     <tr>
 
     <tr>
 
       <td>Enable</td>
 
       <td>Enable</td>
       <td>yes | no; Default: '''no'''</td>
+
       <td>off | on; Default: '''off'''</td>
 
       <td>Toggles the Access filter ON or OFF</td>
 
       <td>Toggles the Access filter ON or OFF</td>
     </tr>
+
     </tr><tr><td>RIP interface</td><td>RIP interface; Default: '''first interface on list'''
    <tr>
+
</td><td>Applies the rule for the specified interface
      <td>Peer</td>
+
</td></tr><tr>
      <td>bgp peer; Default: '''first peer on list'''</td>
 
      <td>Applies the rule for the specified peer</td>
 
    </tr>
 
    <tr>
 
 
     <td>Action</td>
 
     <td>Action</td>
         <td>Permit | Deny; Default: '''Permit'''</td>
+
         <td>Default: '''Permit'''</td>
         <td>Denies or permits matched entry</td>
+
         <td>Available options:
 +
 
 +
*'''Permit'''
 +
*'''Deny'''
 +
 
 +
Denies or permits matched entry
 +
</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Network</td>
 
     <td>Network</td>
         <td>Any | ip; Default: '''Any'''</td>
+
         <td>Default: '''Any'''</td>
         <td>Applies filter rule for this source network</td>
+
         <td>Applies filter rule for this source network. Available options:
 +
 
 +
*'''Any'''
 +
*'''Custom'''
 +
</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Direction</td>
 
     <td>Direction</td>
         <td>Inbound | Outbound; Default: '''Inbound'''</td>
+
         <td>Default: '''Inbound'''</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>
+
         <td>Available options:
 +
 
 +
*'''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>
Line 337: Line 445:
  
 
====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]]
[[Image:Network routing dynamic routes ospf general.PNG]]
+
<br />
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 348: Line 456:
 
     <tr>
 
     <tr>
 
       <td>Enable</td>
 
       <td>Enable</td>
       <td>yes | no; Default: '''no'''</td>
+
       <td>off | on; Default: '''off'''</td>
 
       <td>Toggles OSPF Protocol ON or OFF</td>
 
       <td>Toggles OSPF Protocol ON or OFF</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Enable vty</td>
 
       <td>Enable vty</td>
       <td>yes | no; Default: '''no'''</td>
+
       <td>off | on; Default: '''off'''</td>
       <td>Toggles vty access from LAN ON or OFF</td>
+
       <td>Toggles vty access ON or OFF</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 363: Line 471:
 
     <tr>
 
     <tr>
 
     <td>Router ID</td>
 
     <td>Router ID</td>
         <td>ip; Default: " "</td>
+
         <td>Default: " "</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 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>
 
     </tr>
 
     </tr>
Line 369: Line 477:
  
 
====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]]
[[Image:Network routing dynamic routes ospf ospf interface.PNG]]
+
<br />
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 380: Line 488:
 
     <tr>
 
     <tr>
 
       <td>Enable</td>
 
       <td>Enable</td>
       <td>yes | no; Default: '''no'''</td>
+
       <td>off | on; Default: off</td>
       <td>Toggles OSPF interface ON or OFF</td>
+
       <td>Toggles OSPF area ON or OFF</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
       <td>Cost</td>
+
       <td>Interface</td>
       <td>integer [1..65535]; Default: '''10'''</td>
+
       <td>network interfaces; Default: '''loopback'''</td>
       <td>The cost value is set to router-LSA’s metric field and used for SPF calculation</td>
+
       <td>Network interface to be used with the RIP interface. Available options:</td>
 
     </tr>
 
     </tr>
 +
</table>
 +
 +
By pressing '''Edit''' button you can find more settings related to '''OSPF Interface'''.
 +
 +
[[File:Networking_RUTX_manual_dynamic_routes_ospf_interface_advanced_v1.png|alt=|border|center]]
 +
 +
<table class="nd-mantable">
 
     <tr>
 
     <tr>
    <td>Hello interval</td>
+
        <th>field name</th>
        <td>integer [1..65535]; Default: '''10'''</td>
+
      <th>value</th>
        <td>Hello packets will be sent at the frequency specified in this field (in seconds)</td>
+
      <th>description</th>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
    <td>Router dead interval</td>
+
      <td>Enable</td>
        <td>integer [1..65535]; Default: '''40'''</td>
+
      <td>off | on; Default: '''off'''</td>
        <td>This value must be the same for all routers attached to a common network</td>
+
      <td>Toggles OSPF area ON or OFF</td>
    </tr>
+
    </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
      <td>Retransmit</td>
+
</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>integer [1..65535]; Default: '''5'''</td>
+
</td></tr><tr><td>Type</td><td>Default: " "</td><td>You can choose different Type. Available options:
      <td>This value is used when re-transmitting Database Description and Link State Request packets</td>
+
 
    </tr>
+
*'''Broadcast'''
    <tr>
+
*'''Nonbroadcast'''
      <td>Priority</td>
+
*'''Point-to-point'''
      <td>integer [0..255]; Default: '''1'''</td>
+
*'''Point-to-multipoint'''
      <td>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 the Designated Router</td>
+
</td></tr><tr><td>Authentication</td><td>Default: '''None'''</td><td>You can use different authentication methods. Available options:
    </tr>
+
 
    <tr>
+
*'''None'''
    <td>Type</td>
+
*'''Password'''
        <td>Broadcast | Nonbroadcast | Point-to-point | Point-to-multipoint; Default: " "</td>
+
*'''MD5 HMAC'''
        <td>Set explicit network type for the specified interface</td>
+
</td></tr></table>
    </tr>
 
    <tr>
 
    <td>Authentication</td>
 
        <td>None | Password | MD5 HMAC; Default: " "</td>
 
        <td>Specifies the authentication mode that should be used for the interface</td>
 
    </tr>
 
</table>
 
  
 
====OSPF Area====
 
====OSPF Area====
----
+
----Below is an example of '''OSPF Area''' settings section.[[File:Networking_RUTX_manual_dynamic_routes_ospf_area_v1.png|alt=|border|center]]
 
+
<br />
[[Image:Network routing dynamic routes ospf area.PNG]]
 
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 433: Line 540:
 
     <tr>
 
     <tr>
 
       <td>Enable</td>
 
       <td>Enable</td>
       <td>yes | no; Default: '''no'''</td>
+
       <td>off | on; Default: '''off'''</td>
 
       <td>Toggles OSPF area ON or OFF</td>
 
       <td>Toggles OSPF area ON or OFF</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Cost</td>
 
       <td>Cost</td>
       <td>[a.b.c.d]; Default: " "</td>
+
       <td>IP;Default: " "</td>
 
       <td>Specifies OSPF area</td>
 
       <td>Specifies OSPF area</td>
 
     </tr>
 
     </tr>
Line 444: Line 551:
  
 
====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 />
[[Image:Network routing dynamic routes ospf networks.PNG]]
 
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 456: Line 562:
 
     <tr>
 
     <tr>
 
       <td>Enable</td>
 
       <td>Enable</td>
       <td>yes | no; Default: '''no'''</td>
+
       <td>off | on; Default: '''off'''</td>
 
       <td>Toggles OSPF network ON or OFF</td>
 
       <td>Toggles OSPF network ON or OFF</td>
 
     </tr>
 
     </tr>
Line 466: Line 572:
 
     <tr>
 
     <tr>
 
     <td>Area</td>
 
     <td>Area</td>
         <td>ospf area; Default: " "</td>
+
         <td>OSPF area; Default: " "</td>
 
         <td>Specifies OSPF area</td>
 
         <td>Specifies OSPF area</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
 +
 +
===EIGRP Protocol===
 +
----
 +
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.
 +
 +
====General====
 +
----
 +
Below is an example of EIGRP '''General''' settings section.<br />
 +
[[File:Networking_RUTX_manual_dynamic_routes_eigrp_general_v1.png|alt=|border|center]]
 +
<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>Toggles EIGRP network 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
 +
</td></tr><tr><td>Router ID</td><td>IP; Default: " "</td><td>'''EIGRP''' router-ID in IP address format</td></tr><tr>
 +
      <td>Network</td>
 +
      <td>IP; Default: " "</td>
 +
      <td>The announcement network</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:
 +
 +
*'''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>Neighbors</td>
 +
        <td>IP; Default: " "</td>
 +
        <td>Neighbour IP addres</td>
 +
    </tr>
 +
</table>
 +
 +
===NHRP Protocol===
 +
----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.
 +
 +
====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">
 +
    <tr>
 +
        <th>field name</th>
 +
      <th>value</th>
 +
      <th>description</th>
 +
    </tr>
 +
    <tr>
 +
      <td>Enable service</td>
 +
      <td>off | on; Default: '''off'''</td>
 +
      <td>Toggles NHRP network ON or OFF</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Enable logging</td>
 +
      <td>off | on; Default: '''off'''</td>
 +
      <td>Toggles NHRP logging ON or OFF</td>
 +
    </tr></table>
 +
 +
====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">
 +
    <tr>
 +
        <th>field name</th>
 +
      <th>value</th>
 +
      <th>description</th>
 +
    </tr>
 +
    <tr>
 +
      <td>Enable</td>
 +
      <td>off | on; Default: '''off'''</td>
 +
      <td>Toggles interface ON or OFF</td>
 +
    </tr></table>
 +
 +
By pressing '''Edit''' button you can find more settings related to '''NHRP Interface.'''
 +
 +
[[File:Networking_RUTX_manual_dynamic_routes_nhrp_advanced_v1.png|alt=|border|center]]
 +
<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'''
 +
*'''Custom'''
 +
</td></tr><tr><td>NBMA</td><td>Default: " "
 +
</td><td>Non-Broadcast Multi-Access(NBMA) network IP address</td></tr><tr><td>Hold-time</td><td>Default: '''7200'''
 +
</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'''
 +
</td><td>Use NHRP over IPsec</td></tr><tr><td>IP address</td><td>IP; Default: " "
 +
</td><td>Network ID of NHRP</td></tr><tr><td>NBMA</td><td>IP; Default: " "
 +
</td><td>IP address of Next-Hop Server</td></tr></table>
 +
 +
[[Category:{{{name}}} WebUI]]

Latest revision as of 13:48, 21 January 2020

Summary

This chapter is an overview of the Routing section in RUTX devices.

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.

Static IPv4 Routes


Below is an example and information about Static IPv4 Routes.

FieldValueDescription
InterfaceDefault: lanThe zone where the target network resides
Target*IPv4; Default: 0.0.0.0The address of the destination network
Netmask*Default: 255.255.255.255A Mask that is applied to the Target to determine to what actual IP addresses the routing rule applies
GatewayIP; Default: 0.0.0.0Defines where the router should send all the traffic that applies to the rule
MetricDefault: 0The metric 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.
MTU[64..9000]; Default: 1500Sets 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 TypeDefault: unicastSelects route type. Each type specifies a different behavior for the route, available options:
  • unicast
  • 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
  • unreachable
  • 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 -
  • -- custom -- -

*Additional notes on Target & Netmask:

You can define a rule that applies to a single IP like this:

  • Target: some IP
  • Netmask: 255.255.255.255

Furthermore, you can define a rules that apply to a range of IPs. Refer to the table below for examples.

TargetNetmaskDescription
192.168.2.0255.255.255.240Applies to IPs in the 192.168.2.0 - 192.168.2.15 range.
192.168.2.240255.255.255.240Applies to IPs in the 192.168.2.240 - 192.168.2.255 range.
192.168.2.161255.255.255.0Applies to IPs in the 192.168.2.0 - 192.168.55.255 range.
192.168.0.0255.255.0.0Applies to IPs in the 192.168.0.0 - 192.168.255.255 range.
192.168.2.161255.255.255.255Only applies to 192.168.2.161.


Static IPv6 Routes


Settings for Static IPv6 routes are the same as for IPv4 only that the target IP and and gateway are different.

Error creating thumbnail: Unable to save thumbnail to destination


Advanced Static Routes

Advanced static routing includes features and concepts that are used in more complex networks.

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

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.

An example of rule editing window and meanings of all the configurations are presented below.

field name value description
Priority Default: auto-assigned Controls the order of the IP rules, by default the priority is auto-assigned so that they are processed in the same order.
Incoming interface Default: Any Specifies the incoming logical interface name
Outgoing interface Default: None Specifies the outgoing logical interface name
Source subnetIPv4; Default: 0.0.0.0Specifies the source subnet to match (CIDR notation)
Destination subnetIPv4; Default: 0.0.0.0Specifies the destination subnet to match (CIDR notation)
TOS Value to MatchDefault: 0 Specifies the TOS value to match in IP headers
Firewall MarkDefault: 0xFF 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
Invert matchesoff | on; Default: off If enabled, the meaning of the match options (Firewall Mark, TOS Value, Source and Destination subnets) is inverted
Matched Traffic ActionDefault: Lookup Table Available options:
  • Lookup table
  • Jump to rule
  • Routing action
Lookup TableDefault: " " The rule target is a table lookup

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.

General Settings


Below is an example of BGP General settings section.

Error creating thumbnail: Unable to save thumbnail to destination


field name value description
Enable off | on; Default: off Toggles the BGP protocol ON or OFF
Enable vty off | on; Default: off Toggles vty access ON or OFF
Import config - Uploads an external BGP configuration

BGP Instance


Below is an example of BGP Instance settings section.

Error creating thumbnail: Unable to save thumbnail to destination


field name value description
Enable off | on; Default: off Toggles the BGP instance ON or OFF
AS Default: " " 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]
BGP router ID Default: " " 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.
Network Default: " " Add an announcement network(s)
Redistribution optionsDefault: " "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:
  • Connected routes
  • Kernel added routes
  • NHRP routes
  • OSPF routes
  • Static routes
  • Custom
Deterministicoff | on; Default: off Compare MED between same AS ignoring their age

BGP Peers


Below is an example of BGP Peers section. You can create a new peer by pressing Add button.

Error creating thumbnail: Unable to save thumbnail to destination


field name value description
Enable off | on; Default: off Toggles the BGP peer ON or OFF
Remote AS Default: " " Neighbour's remote AS
Remote address IP; Default: " " Neighbour's remote IPv4 address

By pressing Edit button you can find more settings related to BGP Peer.


field name value description
Enable off | on; Default: off Toggles BGP Peer ON or OFF
Remote AS Default: " " Neighbour's remote AS
Remote address IP; Default: " " Neighbour's remote IPv4 address
Remote port Default: " " Neighbour's remote port
EBGP Multihop Default: " " Time to Live value
Default originateoff | on; Default: offAnnounce default routes to the peer
DescriptionDefault: " "You can leave notes here

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.

Error creating thumbnail: Unable to save thumbnail to destination
field name value description
Remote AS Default: " " Neighbour's remote AS

By pressing Edit button you can find more settings related to BGP Peer Groups.

Error creating thumbnail: Unable to save thumbnail to destination
field name value description
Enable off | on; Default: off Toggles the BGP Peer-Group ON or OFF
Remote AS Default: " " Neighbour's remote AS
Neighbor address IP; Default: " " Neighbour's remote IPv4 address
Advertisement intervalDefault: " "Delay between updates for a neighbor session
Neighbor configurationDefault: NoneConfigure a neighbor as Route Reflector or Route Server client. Available options:
  • None
  • Route Reflector client
  • Route Server client
Disable next hop calculationoff | on; Default: off Disable the next hop calculation for this group
Inbound soft-reconfigurationoff | on; Default: off Allow inbound soft reconfiguration for this neighbor
Disable connected checkoff | on; Default: off One-hop away EBGP peer using loopback address

Access List Filters


Below is an example of Access List Filters section. You can add a new list by simply pressing Add button.


field name value description
Enable off | on; Default: off Toggles the Access filter ON or OFF
Peer bgp peer; Default: first peer on list Applies the rule for the specified peer
Action Default: Permit Denies or permits matched entry. Available options:
  • Permit
  • Deny
Network Default: Any Applies filter rule for this source network. Available options:
  • Any
  • Custom (IP)
Direction Default: Inbound Available options:
  • 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

RIP Protocol


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.

General


Below is an example of RIP General settings section.

Error creating thumbnail: Unable to save thumbnail to destination


field name value description
Enable off | on; Default: off Toggles RIP Protocol ON or OFF
Enable vty off | on; Default: off Toggles vty access ON or OFF
Import config - Uses imported RIP configurations
Version Default: 2 Specifies the version of RIP. Available options:
  • 1
  • 2
Neighbor Default: " " Neighbour IP addres

RIP Interfaces


Below is an example of RIP Interfaces settings section.


field name value description
Enable off | on; Default: off Toggles RIP Interface ON or OFF
Interface network interfaces; Default: loopback Network interface to be used with the RIP interface
Passive interface off | on; Default: off 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

Access list filters


Below is an example of Access list filters settings section.

Error creating thumbnail: Unable to save thumbnail to destination


field name value description
Enable off | on; Default: off Toggles the Access filter ON or OFF
RIP interfaceRIP interface; Default: first interface on list Applies the rule for the specified interface
Action Default: Permit Available options:
  • Permit
  • Deny

Denies or permits matched entry

Network Default: Any Applies filter rule for this source network. Available options:
  • Any
  • Custom
Direction Default: Inbound Available options:
  • 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

OSPF Protocol


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.

General Settings


Below is an example of OSPF General settings section.


field name value description
Enable off | on; Default: off Toggles OSPF Protocol ON or OFF
Enable vty off | on; Default: off Toggles vty access ON or OFF
Import - Uses imported OSPF configurations
Router ID Default: " " 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

OSPF Interface


Below is an example of OSPF Interface settings section.

Error creating thumbnail: Unable to save thumbnail to destination


field name value description
Enable off | on; Default: off Toggles OSPF area ON or OFF
Interface network interfaces; Default: loopback Network interface to be used with the RIP interface. Available options:

By pressing Edit button you can find more settings related to OSPF Interface.

Error creating thumbnail: Unable to save thumbnail to destination
field name value description
Enable off | on; Default: off Toggles OSPF area ON or OFF
CostDefault: " "The cost value is set to router-LSA’s metric field and used for SPF calculation
Hello IntervalDefault: 10This value controls how frequently (every n seconds) a 'Hello' packet is sent out on the specified interface
Router Dead IntervalDefault: 40This value must be the same for all routers attached to a common network
RetransmitDefault: 5This value is used when re-transmitting Database Description and Link State Request packets
PriorityDefault: 1The 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
TypeDefault: " "You can choose different Type. Available options:
  • Broadcast
  • Nonbroadcast
  • Point-to-point
  • Point-to-multipoint
AuthenticationDefault: NoneYou can use different authentication methods. Available options:
  • None
  • Password
  • MD5 HMAC

OSPF Area


Below is an example of OSPF Area settings section.

Error creating thumbnail: Unable to save thumbnail to destination


field name value description
Enable off | on; Default: off Toggles OSPF area ON or OFF
Cost IP;Default: " " Specifies OSPF area

OSPF Networks


Below is an example of OSPF Networks settings section.

Error creating thumbnail: Unable to save thumbnail to destination


field name value description
Enable off | on; Default: off Toggles OSPF network ON or OFF
Network [a.b.c.d/m]; Default: " " 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
Area OSPF area; Default: " " Specifies OSPF area

EIGRP Protocol


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.

General


Below is an example of EIGRP General settings section.

Error creating thumbnail: Unable to save thumbnail to destination
field name value description
Enable off | on; Default: off Toggles EIGRP network ON or OFF
Enable loggingoff | on; Default: offEnable logging of EIGRP
ASDefault: " "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
Router IDIP; Default: " "EIGRP router-ID in IP address format
Network IP; Default: " " The announcement network
Redistribution optionsDefault: " " 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:
  • Connected routes
  • Kernel added routes
  • NHRP routes
  • OSPF routes
  • Static routes
  • Custom
Neighbors IP; Default: " " Neighbour IP addres

NHRP Protocol


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.

General Settings


Below is an example of NHRP General settings section.

Error creating thumbnail: Unable to save thumbnail to destination


field name value description
Enable service off | on; Default: off Toggles NHRP network ON or OFF
Enable logging off | on; Default: off Toggles NHRP logging ON or OFF

Interfaces


Below is an example of NHRP Interface settings section.

Error creating thumbnail: Unable to save thumbnail to destination


field name value description
Enable off | on; Default: off Toggles interface ON or OFF

By pressing Edit button you can find more settings related to NHRP Interface.

Error creating thumbnail: Unable to save thumbnail to destination
field namevaluedescription
Enableoff | on; Default: offEnables DMVPN client
InterfaceDefault: br-lan Interface which will be using NHRP
Network IDDefault: " " Network ID of NHRP
NHSDefault: " " IP address of Next-Hop Server. Available options:
  • Dynamic
  • Custom
NBMADefault: " " Non-Broadcast Multi-Access(NBMA) network IP address
Hold-timeDefault: 7200 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.
IPsec supportoff | on; Default: off Use NHRP over IPsec
IP addressIP; Default: " " Network ID of NHRP
NBMAIP; Default: " " IP address of Next-Hop Server

[[Category:{{{name}}} WebUI]]