Routing: Difference between revisions

From Teltonika Networks Wiki
No edit summary
Line 137: Line 137:
| style="text-align: left; vertical-align: top;" | string; Default: " "
| style="text-align: left; vertical-align: top;" | string; Default: " "
| style="text-align: left; vertical-align: top;" | Add an announcement network(s)
| style="text-align: left; vertical-align: top;" | Add an announcement network(s)
|-
|}
====BGP Peers====
----
[[Image:Network routing dynamic routes bgp peers.PNG]]
{| class="wikitable"
|+
! style="width: 250px; background: black; color: white;"  | Field name
! style="width: 250px; background: black; color: white;"  | Value
! style="width: 1200px; background: black; color: white;" | Description
|-
! style="text-align: left; vertical-align: top;" | Enable
| style="text-align: left; vertical-align: top;" | yes {{!}} no; Default: '''no'''
| style="text-align: left; vertical-align: top;" | Toggles the BGP peer ON or OFF
|-
! style="text-align: left; vertical-align: top;" | Remote AS
| style="text-align: left; vertical-align: top;" | integer: " "
| style="text-align: left; vertical-align: top;" | Neighbor's remote AS
|-
! style="text-align: left; vertical-align: top;" | Remote address
| style="text-align: left; vertical-align: top;" | ip; Default: " "
| style="text-align: left; vertical-align: top;" | Neighbor's remote IPv4 address
|-
|}
====Access List Filters====
----
[[Image:Network routing dynamic routes bgp access list filters.PNG]]
{| class="wikitable"
|+
! style="width: 250px; background: black; color: white;"  | Field name
! style="width: 250px; background: black; color: white;"  | Value
! style="width: 1200px; background: black; color: white;" | Description
|-
! style="text-align: left; vertical-align: top;" | Enable
| style="text-align: left; vertical-align: top;" | yes {{!}} no; Default: '''no'''
| style="text-align: left; vertical-align: top;" | Toggles the Access filter ON or OFF
|-
! style="text-align: left; vertical-align: top;" | Peer
| style="text-align: left; vertical-align: top;" | bgp peer: '''first peer on list
| style="text-align: left; vertical-align: top;" | Applies the rule for the specified peer
|-
! style="text-align: left; vertical-align: top;" | Action
| style="text-align: left; vertical-align: top;" | Permit {{!}} Deny; Default: '''Permit'''
| style="text-align: left; vertical-align: top;" | Denies or permits matched entry
|-
! style="text-align: left; vertical-align: top;" | Network
| style="text-align: left; vertical-align: top;" | Any {{!}} ip; Default: '''Any'''
| style="text-align: left; vertical-align: top;" | Applies filter rule for this source network
|-
! style="text-align: left; vertical-align: top;" | Direction
| style="text-align: left; vertical-align: top;" | Inbound {{!}} Outbound; Default: '''Inbound'''
| style="text-align: left; vertical-align: top;" | 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===
----
[[Image:Network routing dynamic routes rip general.PNG]]
{| class="wikitable"
|+
! style="width: 250px; background: black; color: white;"  | Field name
! style="width: 250px; background: black; color: white;"  | Value
! style="width: 1200px; background: black; color: white;" | Description
|-
! style="text-align: left; vertical-align: top;" | Enable
| style="text-align: left; vertical-align: top;" | yes {{!}} no; Default: '''no'''
| style="text-align: left; vertical-align: top;" | Toggles RIP Protocol ON or OFF
|-
! style="text-align: left; vertical-align: top;" | Enable vty
| style="text-align: left; vertical-align: top;" | yes {{!}} no; Default: '''no'''
| style="text-align: left; vertical-align: top;" | Toggles vty access from LAN ON or OFF
|-
! style="text-align: left; vertical-align: top;" | Import config
| style="text-align: left; vertical-align: top;" | -
| style="text-align: left; vertical-align: top;" | Uses imported RIP configurations
|-
! style="text-align: left; vertical-align: top;" | Version
| style="text-align: left; vertical-align: top;" | 2 {{!}} 1; Default: '''2'''
| style="text-align: left; vertical-align: top;" | Specifies the version of RIP
|-
! style="text-align: left; vertical-align: top;" | Neighbor
| style="text-align: left; vertical-align: top;" | ip; Default: " "
| style="text-align: left; vertical-align: top;" | Neighbor IP address
|-
|-
|}
|}

Revision as of 09:18, 13 November 2017

Summary

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

Static Leases

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.


Field name Value Description
Routing table Main | WAN | WAN2 | WAN3; Default: WAN Defines which table will be used for the route in question
Interface LAN | WAN(wired) | WAN2(Mobile) | WAN3(WiFi) | VPN instances; Default: WAN(wired) The zone where the target network resides
Destination address* ip; Default: 0.0.0.0 The address of the destination network
Netmask* ip; Default: 0.0.0.0 A Mask that is applied to the Target to determine to what actual IP addresses the routing rule applies
Gateway ip; Default: " " Defines where the router should send all the traffic that applies to the rule
Metric integer; Default: 0 A Metric is used as a sorting measure. If a packet about to be routed fits two rules, the one with the higher metric is applied

*Additional notes on Destination & Netmask:

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

IP Netmask Description
192.168.55.161 255.255.255.255 Only applies to 192.168.55.161
192.168.55.0 255.255.255.0 Applies to IPs in the 192.168.55.0 - 192.168.55.255 range
192.168.55.240 255.255.255.240 192.168.55.240 - 192.168.55.255
192.168.55.161 255.255.255.0 192.168.55.0 - 192.168.55.255
192.168.0.0 255.255.0.0 192.168.0.0 - 192.168.255.255

Static ARP entries


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.

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


Field name Value Description
Enable yes | no; Default: no Toggles the BGP protocol ON or OFF
Enable vty yes | no; Default: no Toggles vty access from LAN ON or OFF
Import config - Uploads an external BGP configuration

BGP Instance


Field name Value Description
Enable yes | no; Default: no Toggles the BGP instance ON or OFF
AS integer: " " 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 string; 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 string; Default: " " Add an announcement network(s)

BGP Peers


Field name Value Description
Enable yes | no; Default: no Toggles the BGP peer ON or OFF
Remote AS integer: " " Neighbor's remote AS
Remote address ip; Default: " " Neighbor's remote IPv4 address

Access List Filters


Field name Value Description
Enable yes | no; Default: no Toggles the Access filter ON or OFF
Peer bgp peer: first peer on list Applies the rule for the specified peer
Action Permit | Deny; Default: Permit Denies or permits matched entry
Network Any | ip; Default: Any Applies filter rule for this source network
Direction Inbound | Outbound; Default: Inbound 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


Field name Value Description
Enable yes | no; Default: no Toggles RIP Protocol ON or OFF
Enable vty yes | no; Default: no Toggles vty access from LAN ON or OFF
Import config - Uses imported RIP configurations
Version 2 | 1; Default: 2 Specifies the version of RIP
Neighbor ip; Default: " " Neighbor IP address