Manual:Routing/RIP: Difference between revisions

From MikroTik Wiki
Jump to navigation Jump to search
No edit summary
mNo edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Versions|2.9, v3, v4}}
{{Versions|2.9, v3, v4 +}}


<div class=manual>
<div class=manual>


<h2>Summary</h2>
==Summary==
<p>
<p>
MikroTik RouterOS implements RIP Version 1 (RFC 1058) and Version 2 (RFC 2453). RIP enables routers in an autonomous system to exchange routing information. It always uses the best path (the path with the fewest number of hops (i.e. routers)) available.
MikroTik RouterOS implements RIP Version 1 (RFC 1058) and Version 2 (RFC 2453). RIP enables routers in an autonomous system to exchange routing information. It always uses the best path (the path with the fewest number of hops (i.e. routers)) available.
Line 10: Line 10:
<br />
<br />


<h2>General</h2>
==General==
<p><b>Sub-menu:</b> <code>/routing rip</code></p>
<p id="shbox"><b>Sub-menu:</b> <code>/routing rip</code></p>


<br />
<br />
Line 73: Line 73:
</table>
</table>


<h3>Note</h3>
<br />
<p>
 
{{ Note |
The maximum metric of RIP route is 15. Metric higher than 15 is considered 'infinity' and routes with such metric are considered unreachable. Thus RIP cannot be used on networks with more than 15 hops between any two routers, and using redistribute metrics larger that 1 further reduces this maximum hop count.
The maximum metric of RIP route is 15. Metric higher than 15 is considered 'infinity' and routes with such metric are considered unreachable. Thus RIP cannot be used on networks with more than 15 hops between any two routers, and using redistribute metrics larger that 1 further reduces this maximum hop count.
</p>
}}
<br />
<br />


<h2>Interface</h2>
==Interface==
<p><b>Sub-menu:</b> <code>/routing rip interface</code></p>
<p id="shbox"><b>Sub-menu:</b> <code>/routing rip interface</code></p>


<br />
<br />
Line 129: Line 130:
<br />
<br />


<h2>Keys</h2>
==Keys==
<p><b>Sub-menu:</b> <code>/routing rip keys</code></p>
<p id="shbox"><b>Sub-menu:</b> <code>/routing rip keys</code></p>
<br />
<br />


Line 165: Line 166:
<br />
<br />


<h2>Network</h2>
==Network==
<p><b>Sub-menu:</b> <code>/routing rip network</code></p>
<p><b>Sub-menu:</b> <code>/routing rip network</code></p>
<br />
<br />
Line 187: Line 188:
<br />
<br />


<h2>Neighbor</h2>
==Neighbor==
<p><b>Sub-menu:</b> <code>/routing rip neighbor</code></p>
<p id="shbox"><b>Sub-menu:</b> <code>/routing rip neighbor</code></p>
<br />
<br />


Line 210: Line 211:




<h2>Route</h2>
==Route==
<p><b>Sub-menu:</b> <code>/routing rip route</code></p>
<p id="shbox"><b>Sub-menu:</b> <code>/routing rip route</code></p>


<br />
<br />
Line 246: Line 247:
</div>
</div>


[[Category:Manual]]
<br />
[[Category:Unfinished]]
{{cont}}
 
[[Category:Manual|R]]
[[Category:Unfinished|R]]

Latest revision as of 12:05, 30 April 2010

Applies to RouterOS: 2.9, v3, v4 +

Summary

MikroTik RouterOS implements RIP Version 1 (RFC 1058) and Version 2 (RFC 2453). RIP enables routers in an autonomous system to exchange routing information. It always uses the best path (the path with the fewest number of hops (i.e. routers)) available.


General

Sub-menu: /routing rip


Property Description
distribute-default (always | if-installed | never; Default: never) specifies how to distribute default route.
redistribute-static (yes | no; Default: no) if enabled, redistribute static routes to neighbor routers
redistribute-connected (yes | no; Default: no) if enabled, redistribute connected routes to neighbor routers
redistribute-ospf (yes | no; Default: no) if enabled, redistribute OSPF routes to neighbor routers
redistribute-bgp (yes | no; Default: no) if enabled, redistribute BGP routes to neighbor routers
metric-default (integer; Default: 1) specifies metric for default route
metric-static (integer; Default: 1) specifies metric for static routes
metric-connected (integer; Default: 1) specifies metric for connected routes
metric-ospf (integer; Default: 1) specifies metric (the number of hops) for the routes learned via OSPF protocol
metric-bgp (integer; Default: 1) specifies metric (the number of hops) for the routes learned via BGP protocol
update-timer (time; Default: 30s) specifies frequency of RIP updates
timeout-timer (time; Default: 3m) specifies time interval after which the route is considered invalid
garbage-timer (time; Default: 2m) specifies time interval after which the invalid route will be dropped from neighbor router table


Note: The maximum metric of RIP route is 15. Metric higher than 15 is considered 'infinity' and routes with such metric are considered unreachable. Thus RIP cannot be used on networks with more than 15 hops between any two routers, and using redistribute metrics larger that 1 further reduces this maximum hop count.



Interface

Sub-menu: /routing rip interface


Property Description
interface (string | all; Default: all) interface on which RIP runs. If set to 'all' settings will be applied to all interfaces
send (v1 | v1-2 | v2; Default: v2) specifies RIP protocol update versions to distribute
receive (v1 | v1-2 | v2; Default: v1-2) specifies RIP protocol update versions the router will be able to receive
passive (yes | no; Default: no) if enabled, do not send routing packets via this interface, only receive
authentication (none | simple | md5; Default: none) specifies authentication method to use on RIP messages
authentication-key (string; Default: "") specifies authentication key
key-chain (string; Default: "") chain name for MD5 authentication passwords
in-prefix-list (string; Default: "") name of the filtering prefix list for received routes
out-prefix-list (string; Default: "") name of the filtering prefix list for advertised routes


Keys

Sub-menu: /routing rip keys


MD5 authentication key chains.


Property Description
chain (string; Default: "") chain name to place this key in. If a chain with the specified name does not exist it will be automatically created
key (string; Default: "") authentication key. Maximal length 16 characters
key-id (integer:0..255; Default: ) key identifier. This number is included in MD5 authenticated RIP messages, and determines witch key to use to check authentication for a specific message.
from-date (date; Default: tomorrow system date) key is valid from this date
from-time (time; Default: 00:00:00) key is valid until this time in the specified date


Network

Sub-menu: /routing rip network


To start the RIP protocol, you have to define the networks on which RIP will run.


Property Description
network (IP prefix; Default: ) the network prefix. RIP will be enabled on all interfaces that has at least one address falling within this range. Note that the network prefix of the address is used for this check (i.e. not the local address). For PtP interfaces this means the address of the remote endpoint.


Neighbor

Sub-menu: /routing rip neighbor


This submenu is used to define a neighboring routers to exchange routing information with. Normally there is no need to add the neighbors, if multicasting is working properly within the network. If there are problems with exchanging routing information, neighbor routers can be added to the list. It will force the router to exchange the routing information with the neighbor using regular unicast packets.


Property Description
address (IP address; Default: 0.0.0.0) IP address of neighboring router



Route

Sub-menu: /routing rip route


Read only properties:

Property Description
dst-address (IP prefix) destination network
gateway (IP address) last gateway on the route to destination
metric (integer) distance vector length to the destination network
from (IP address) specifies the IP address of the router from which the route was received
timeout (time) for valid RIP routes (metric < 16): time until the route will expire. For routes with metric 16: time until advertising of the route will be stopped



[ Top | Back to Content ]