|
|
| Line 1: |
Line 1: |
| − | ==Summary==
| + | {{Template:Networking_rut9xx_rut2xx_manual_routing |
| − | | + | | name = RUT230 |
| − | This chapter is an overview of the Routing section in RUT devices.
| + | | series = RUT2xx |
| − | | + | }} |
| − | ==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.
| |
| − | | |
| − | | |
| − | [[Image:Network routing static routes.PNG]]
| |
| − | | |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>field name</th>
| |
| − | <th>value</th>
| |
| − | <th>description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Routing table</td>
| |
| − | <td>Main | WAN | WAN2 | WAN3; Default: '''WAN'''</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>
| |
| − | | |
| − | '''*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.:
| |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>field name</th>
| |
| − | <th>value</th>
| |
| − | <th>description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>192.168.55.161</td>
| |
| − | <td>255.255.255.255</td>
| |
| − | <td>Only applies to 192.168.55.161'''</td>
| |
| − | </tr>
| |
| − | <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.15</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>
| |
| − | <td>192.168.55.161</td>
| |
| − | <td>255.255.255.0</td>
| |
| − | <td>192.168.55.0 - 192.168.55.255</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>192.168.0.0</td>
| |
| − | <td>255.255.0.0</td>
| |
| − | <td>192.168.0.0 - 192.168.255.255</td>
| |
| − | </tr>
| |
| − | </table>
| |
| − | | |
| − | ===Static IPv6 Routes=== | |
| − | ----
| |
| − | Settings for Static IPv6 routes are similar to IPv4.
| |
| − | | |
| − | [[Image:Networking rut2xx manual static ipv6 routes.png|border]]
| |
| − | | |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>field name</th>
| |
| − | <th>value</th>
| |
| − | <th>description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Interface</td>
| |
| − | <td>Wired WAN IPv6 | Mobile WAN IPv6 | Wi-Fi IPv6; Default: '''Wired WAN IPv6'''</td>
| |
| − | <td>Defines which interface will be used</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Target</td>
| |
| − | <td>Default: " "</td>
| |
| − | <td>The address of the destination network</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>IPv6-Gateway</td>
| |
| − | <td>ipv6; 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>
| |
| − | | |
| − | ===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.
| |
| − | | |
| − | [[Image:Network routing static routes static arp entries.PNG]]
| |
| − | | |
| − | ==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====
| |
| − | ----
| |
| − | | |
| − | [[Image:Network routing dynamic routes bgp general.PNG]]
| |
| − | | |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>field name</th>
| |
| − | <th>value</th>
| |
| − | <th>description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Enable</td>
| |
| − | <td>yes | no; Default: '''no'''</td>
| |
| − | <td>Toggles the BGP protocol ON or OFF</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Enable vty</td>
| |
| − | <td>yes | no; Default: '''no'''</td>
| |
| − | <td>Toggles vty access from LAN ON or OFF</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Import config</td>
| |
| − | <td>-</td>
| |
| − | <td>Uploads an external BGP configuration</td>
| |
| − | </tr>
| |
| − | </table>
| |
| − | | |
| − | ====BGP Instance====
| |
| − | ----
| |
| − | | |
| − | [[Image:Network routing dynamic routes bgp instance.PNG]]
| |
| − | | |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>field name</th>
| |
| − | <th>value</th>
| |
| − | <th>description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Enable</td>
| |
| − | <td>yes | no; Default: '''no'''</td>
| |
| − | <td>Toggles the BGP instance ON or OFF</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>AS</td>
| |
| − | <td>integer: " "</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>string; 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>string; Default: " "</td>
| |
| − | <td>Add an announcement network(s)</td>
| |
| − | </tr>
| |
| − | </table>
| |
| − | | |
| − | ====BGP Peers====
| |
| − | ----
| |
| − | | |
| − | [[Image:Network routing dynamic routes bgp peers.PNG]]
| |
| − | | |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>field name</th>
| |
| − | <th>value</th>
| |
| − | <th>description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Enable</td>
| |
| − | <td>yes | no; Default: '''no'''</td>
| |
| − | <td>Toggles the BGP peer ON or OFF</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Remote AS</td>
| |
| − | <td>integer: " "</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>
| |
| − | | |
| − | ====Access List Filters====
| |
| − | ----
| |
| − | | |
| − | [[Image:Network routing dynamic routes bgp access list filters.PNG]]
| |
| − | | |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>field name</th>
| |
| − | <th>value</th>
| |
| − | <th>description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Enable</td>
| |
| − | <td>yes | no; Default: '''no'''</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>Permit | Deny; Default: '''Permit'''</td>
| |
| − | <td>Denies or permits matched entry</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Network</td>
| |
| − | <td>Any | ip; Default: '''Any'''</td>
| |
| − | <td>Applies filter rule for this source network</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Direction</td>
| |
| − | <td>Inbound | Outbound; 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>
| |
| − | </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====
| |
| − | ----
| |
| − | | |
| − | [[Image:Network routing dynamic routes rip general.PNG]]
| |
| − | | |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>field name</th>
| |
| − | <th>value</th>
| |
| − | <th>description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Enable</td>
| |
| − | <td>yes | no; Default: '''no'''</td>
| |
| − | <td>Toggles RIP Protocol ON or OFF</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Enable vty</td>
| |
| − | <td>yes | no; Default: '''no'''</td>
| |
| − | <td>Toggles vty access from LAN ON or OFF</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Import config</td>
| |
| − | <td>-</td>
| |
| − | <td>Uses imported RIP configurations</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Version</td>
| |
| − | <td>2 | 1; Default: '''2'''</td>
| |
| − | <td>Specifies the version of RIP</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Neighbor</td>
| |
| − | <td>ip; Default: " "</td>
| |
| − | <td>Neighbour IP addres</td>
| |
| − | </tr>
| |
| − | </table>
| |
| − | | |
| − | ====RIP Interfaces====
| |
| − | ----
| |
| − | | |
| − | [[Image:Network routing dynamic routes rip rip interfaces.PNG]]
| |
| − | | |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>field name</th>
| |
| − | <th>value</th>
| |
| − | <th>description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Enable</td>
| |
| − | <td>yes | no; Default: '''no'''</td>
| |
| − | <td>Toggles RIP Interface ON or OFF</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Interface</td>
| |
| − | <td>network interface; Default: '''no'''</td>
| |
| − | <td>Network interface to be used with the RIP interface</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Passive interface</td>
| |
| − | <td>yes | no; Default: '''no'''</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====
| |
| − | ----
| |
| − | | |
| − | [[Image:Network routing dynamic routes rip access list filters.PNG]]
| |
| − | | |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>field name</th>
| |
| − | <th>value</th>
| |
| − | <th>description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Enable</td>
| |
| − | <td>yes | no; Default: '''no'''</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>Permit | Deny; Default: '''Permit'''</td>
| |
| − | <td>Denies or permits matched entry</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Network</td>
| |
| − | <td>Any | ip; Default: '''Any'''</td>
| |
| − | <td>Applies filter rule for this source network</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Direction</td>
| |
| − | <td>Inbound | Outbound; 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>
| |
| − | </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====
| |
| − | ----
| |
| − | [[Image:Network routing dynamic routes ospf general.PNG]]
| |
| − | | |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>field name</th>
| |
| − | <th>value</th>
| |
| − | <th>description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Enable</td>
| |
| − | <td>yes | no; Default: '''no'''</td>
| |
| − | <td>Toggles OSPF Protocol ON or OFF</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Enable vty</td>
| |
| − | <td>yes | no; Default: '''no'''</td>
| |
| − | <td>Toggles vty access from LAN ON or OFF</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Import config</td>
| |
| − | <td>-</td>
| |
| − | <td>Uses imported OSPF configurations</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Router ID</td>
| |
| − | <td>ip; 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====
| |
| − | ----
| |
| − | [[Image:Network routing dynamic routes ospf ospf interface.PNG]]
| |
| − | | |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>field name</th>
| |
| − | <th>value</th>
| |
| − | <th>description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Enable</td>
| |
| − | <td>yes | no; Default: '''no'''</td>
| |
| − | <td>Toggles OSPF interface ON or OFF</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Cost</td>
| |
| − | <td>integer [1..65535]; Default: '''10'''</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>integer [1..65535]; Default: '''10'''</td>
| |
| − | <td>Hello packets will be sent at the frequency specified in this field (in seconds)</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Router dead interval</td>
| |
| − | <td>integer [1..65535]; 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>integer [1..65535]; 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>integer [0..255]; Default: '''1'''</td>
| |
| − | <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>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Type</td>
| |
| − | <td>Broadcast | Nonbroadcast | Point-to-point | Point-to-multipoint; Default: " "</td>
| |
| − | <td>Set explicit network type for the specified interface</td>
| |
| − | </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====
| |
| − | ----
| |
| − | | |
| − | [[Image:Network routing dynamic routes ospf area.PNG]]
| |
| − | | |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>field name</th>
| |
| − | <th>value</th>
| |
| − | <th>description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Enable</td>
| |
| − | <td>yes | no; Default: '''no'''</td>
| |
| − | <td>Toggles OSPF area ON or OFF</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Cost</td>
| |
| − | <td>[a.b.c.d]; Default: " "</td>
| |
| − | <td>Specifies OSPF area</td>
| |
| − | </tr>
| |
| − | </table>
| |
| − | | |
| − | ====OSPF Networks====
| |
| − | ----
| |
| − | | |
| − | [[Image:Network routing dynamic routes ospf networks.PNG]]
| |
| − | | |
| − | <table class="nd-mantable">
| |
| − | <tr>
| |
| − | <th>field name</th>
| |
| − | <th>value</th>
| |
| − | <th>description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>Enable</td>
| |
| − | <td>yes | no; Default: '''no'''</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>
| |
| − | | |
| − | [[Category:RUT230 WebUI]]
| |
