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

From Teltonika Networks Wiki
(Created page with "==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 n...")
 
Line 78: Line 78:
  
 
[[Category:{{{name}}} Network section]]
 
[[Category:{{{name}}} Network section]]
 +
<!--
 +
 +
 +
 +
 +
==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.[[File:Networking_RUTX_manual_dynamic_routes_bgp_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</td>
 +
      <td>off | on; Default: '''off'''</td>
 +
      <td>Toggles the BGP protocol ON or OFF</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Enable vty</td>
 +
      <td>off | on; Default: '''off'''</td>
 +
      <td>Toggles vty access ON or OFF</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Import config</td>
 +
        <td>-</td>
 +
        <td>Uploads an external BGP configuration</td>
 +
    </tr>
 +
</table>
 +
 +
====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 />
 +
 +
<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 instance ON or OFF</td>
 +
    </tr>
 +
    <tr>
 +
      <td>AS</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>
 +
    </tr>
 +
    <tr>
 +
    <td>BGP router ID</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>
 +
    </tr>
 +
    <tr>
 +
    <td>Network</td>
 +
        <td>Default: " "</td>
 +
        <td>Add an announcement network(s)</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>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>
 +
        <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 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>
 +
</table>
 +
 +
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>
 +
 +
====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">
 +
    <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 Access filter ON or OFF</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Peer</td>
 +
      <td>bgp peer; Default: '''first peer on list'''</td>
 +
      <td>Applies the rule for the specified peer</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Action</td>
 +
        <td>Default: '''Permit'''</td>
 +
        <td>Denies or permits matched entry. Available options:
 +
 +
*'''Permit'''
 +
*'''Deny'''
 +
</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Network</td>
 +
        <td>Default: '''Any'''</td>
 +
        <td>Applies filter rule for this source network. Available options:
 +
 +
*'''Any'''
 +
*'''Custom (IP)'''
 +
</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Direction</td>
 +
        <td>Default: '''Inbound'''</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>
 +
</table>
 +
 +
===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.[[File:Networking_RUTX_manual_dynamic_routes_rip_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</td>
 +
      <td>off | on; Default: '''off'''</td>
 +
      <td>Toggles RIP Protocol ON or OFF</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Enable vty</td>
 +
      <td>off | on; Default: '''off'''</td>
 +
      <td>Toggles vty access ON or OFF</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Import config</td>
 +
        <td>-</td>
 +
        <td>Uses imported RIP configurations</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Version</td>
 +
        <td>Default: '''2'''</td>
 +
        <td>Specifies the version of RIP. Available options:
 +
 +
*'''1'''
 +
*'''2'''
 +
</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Neighbor</td>
 +
        <td>Default: " "</td>
 +
        <td>Neighbour IP addres</td>
 +
    </tr>
 +
</table>
 +
 +
====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 />
 +
 +
<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 RIP Interface ON or OFF</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Interface</td>
 +
      <td>network interfaces; Default: '''loopback'''</td>
 +
      <td>Network interface to be used with the RIP interface</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Passive interface</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>
 +
    </tr>
 +
</table>
 +
 +
====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 />
 +
 +
<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 Access filter ON or OFF</td>
 +
    </tr><tr><td>RIP interface</td><td>RIP interface; Default: '''first interface on list'''
 +
</td><td>Applies the rule for the specified interface
 +
</td></tr><tr>
 +
    <td>Action</td>
 +
        <td>Default: '''Permit'''</td>
 +
        <td>Available options:
 +
 +
*'''Permit'''
 +
*'''Deny'''
 +
 +
Denies or permits matched entry
 +
</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Network</td>
 +
        <td>Default: '''Any'''</td>
 +
        <td>Applies filter rule for this source network. Available options:
 +
 +
*'''Any'''
 +
*'''Custom'''
 +
</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Direction</td>
 +
        <td>Default: '''Inbound'''</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>
 +
</table>
 +
 +
===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.[[File:Networking_RUTX_manual_dynamic_routes_ospf_general_v1.png|alt=|center|border|1139x1139px]]
 +
<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 OSPF Protocol ON or OFF</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Enable vty</td>
 +
      <td>off | on; Default: '''off'''</td>
 +
      <td>Toggles vty access ON or OFF</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Import</td>
 +
        <td>-</td>
 +
        <td>Uses imported OSPF configurations</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Router ID</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>
 +
    </tr>
 +
</table>
 +
 +
====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 />
 +
 +
<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 OSPF area ON or OFF</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Interface</td>
 +
      <td>network interfaces; Default: '''loopback'''</td>
 +
      <td>Network interface to be used with the RIP interface. Available options:</td>
 +
    </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>
 +
        <th>field name</th>
 +
      <th>value</th>
 +
      <th>description</th>
 +
    </tr>
 +
    <tr>
 +
      <td>Enable</td>
 +
      <td>off | on; Default: '''off'''</td>
 +
      <td>Toggles OSPF area 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
 +
</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></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></tr><tr><td>Type</td><td>Default: " "</td><td>You can choose different Type. Available options:
 +
 +
*'''Broadcast'''
 +
*'''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'''
 +
*'''Password'''
 +
*'''MD5 HMAC'''
 +
</td></tr></table>
 +
 +
====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 />
 +
 +
<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 OSPF area ON or OFF</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Cost</td>
 +
      <td>IP;Default: " "</td>
 +
      <td>Specifies OSPF area</td>
 +
    </tr>
 +
</table>
 +
 +
====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 />
 +
 +
<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 OSPF network ON or OFF</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Network</td>
 +
      <td>[a.b.c.d/m]; Default: " "</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>
 +
    </tr>
 +
    <tr>
 +
    <td>Area</td>
 +
        <td>OSPF area; Default: " "</td>
 +
        <td>Specifies OSPF area</td>
 +
    </tr>
 +
</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>
 +
 +
-->

Revision as of 14:19, 7 May 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.


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

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

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