]>
Commit | Line | Data |
---|---|---|
0efdf0fe | 1 | .. _rip: |
42fc5d26 QY |
2 | |
3 | *** | |
4 | RIP | |
5 | *** | |
6 | ||
7 | RIP -- Routing Information Protocol is widely deployed interior gateway | |
c1a54c05 QY |
8 | protocol. RIP was developed in the 1970s at Xerox Labs as part of the |
9 | XNS routing protocol. RIP is a :term:`distance-vector` protocol and is | |
10 | based on the :term:`Bellman-Ford` algorithms. As a distance-vector | |
42fc5d26 | 11 | protocol, RIP router send updates to its neighbors periodically, thus |
c1a54c05 | 12 | allowing the convergence to a known topology. In each update, the |
d1e7591e | 13 | distance to any given network will be broadcast to its neighboring |
42fc5d26 QY |
14 | router. |
15 | ||
16 | *ripd* supports RIP version 2 as described in RFC2453 and RIP | |
17 | version 1 as described in RFC1058. | |
18 | ||
0efdf0fe | 19 | .. _starting-and-stopping-ripd: |
42fc5d26 QY |
20 | |
21 | Starting and Stopping ripd | |
22 | ========================== | |
23 | ||
c1a54c05 QY |
24 | The default configuration file name of *ripd*'s is :file:`ripd.conf`. When |
25 | invocation *ripd* searches directory |INSTALL_PREFIX_ETC|. If :file:`ripd.conf` | |
26 | is not there next search current directory. | |
42fc5d26 | 27 | |
c1a54c05 QY |
28 | RIP uses UDP port 520 to send and receive RIP packets. So the user must have |
29 | the capability to bind the port, generally this means that the user must have | |
30 | superuser privileges. RIP protocol requires interface information maintained by | |
31 | *zebra* daemon. So running *zebra* is mandatory to run *ripd*. Thus minimum | |
32 | sequence for running RIP is like below: | |
42fc5d26 QY |
33 | |
34 | :: | |
35 | ||
42fc5d26 QY |
36 | # zebra -d |
37 | # ripd -d | |
a8c90e15 | 38 | |
42fc5d26 QY |
39 | |
40 | Please note that *zebra* must be invoked before *ripd*. | |
41 | ||
c1a54c05 QY |
42 | To stop *ripd*. Please use:: |
43 | kill `cat /var/run/ripd.pid` | |
44 | ||
d1e7591e | 45 | Certain signals have special meanings to *ripd*. |
42fc5d26 | 46 | |
07a17e6d QY |
47 | +-------------+------------------------------------------------------+ |
48 | | Signal | Action | | |
49 | +=============+======================================================+ | |
50 | | ``SIGHUP`` | Reload configuration file :file:`ripd.conf`. | | |
51 | | | All configurations are reset. All routes learned | | |
52 | | | so far are cleared and removed from routing table. | | |
53 | +-------------+------------------------------------------------------+ | |
54 | | ``SIGUSR1`` | Rotate the *ripd* logfile. | | |
55 | +-------------+------------------------------------------------------+ | |
56 | | ``SIGINT`` | | | |
57 | | ``SIGTERM`` | Sweep all installed routes and gracefully terminate. | | |
58 | +-------------+------------------------------------------------------+ | |
42fc5d26 | 59 | |
c1a54c05 | 60 | *ripd* invocation options. Common options that can be specified |
0efdf0fe | 61 | (:ref:`common-invocation-options`). |
42fc5d26 | 62 | |
42fc5d26 | 63 | |
0efdf0fe | 64 | .. _rip-netmask: |
42fc5d26 QY |
65 | |
66 | RIP netmask | |
67 | ----------- | |
68 | ||
c1a54c05 QY |
69 | The netmask features of *ripd* support both version 1 and version 2 of RIP. |
70 | Version 1 of RIP originally contained no netmask information. In RIP version 1, | |
71 | network classes were originally used to determine the size of the netmask. | |
72 | Class A networks use 8 bits of mask, Class B networks use 16 bits of masks, | |
73 | while Class C networks use 24 bits of mask. Today, the most widely used method | |
74 | of a network mask is assigned to the packet on the basis of the interface that | |
75 | received the packet. Version 2 of RIP supports a variable length subnet mask | |
76 | (VLSM). By extending the subnet mask, the mask can be divided and reused. Each | |
77 | subnet can be used for different purposes such as large to middle size LANs and | |
78 | WAN links. FRR *ripd* does not support the non-sequential netmasks that are | |
79 | included in RIP Version 2. | |
80 | ||
81 | In a case of similar information with the same prefix and metric, the old | |
82 | information will be suppressed. Ripd does not currently support equal cost | |
83 | multipath routing. | |
42fc5d26 | 84 | |
0efdf0fe | 85 | .. _rip-configuration: |
42fc5d26 QY |
86 | |
87 | RIP Configuration | |
88 | ================= | |
89 | ||
c1a54c05 | 90 | .. clicmd:: router rip |
42fc5d26 | 91 | |
c1a54c05 QY |
92 | The `router rip` command is necessary to enable RIP. To disable RIP, use the |
93 | `no router rip` command. RIP must be enabled before carrying out any of the | |
94 | RIP commands. | |
42fc5d26 | 95 | |
42fc5d26 | 96 | |
c1a54c05 | 97 | Disable RIP. |
42fc5d26 | 98 | |
c1a54c05 | 99 | .. clicmd:: network NETWORK |
42fc5d26 | 100 | |
42fc5d26 | 101 | |
c1a54c05 QY |
102 | Set the RIP enable interface by NETWORK. The interfaces which have addresses |
103 | matching with NETWORK are enabled. | |
42fc5d26 | 104 | |
c1a54c05 QY |
105 | This group of commands either enables or disables RIP interfaces between |
106 | certain numbers of a specified network address. For example, if the network | |
107 | for 10.0.0.0/24 is RIP enabled, this would result in all the addresses from | |
108 | 10.0.0.0 to 10.0.0.255 being enabled for RIP. The `no network` command will | |
109 | disable RIP for the specified network. | |
42fc5d26 | 110 | |
c1a54c05 | 111 | .. clicmd:: network IFNAME |
42fc5d26 | 112 | |
42fc5d26 | 113 | |
c1a54c05 QY |
114 | Set a RIP enabled interface by IFNAME. Both the sending and |
115 | receiving of RIP packets will be enabled on the port specified in the | |
116 | `network ifname` command. The `no network ifname` command will disable | |
117 | RIP on the specified interface. | |
42fc5d26 | 118 | |
c1a54c05 | 119 | .. clicmd:: neighbor A.B.C.D |
42fc5d26 | 120 | |
42fc5d26 | 121 | |
c1a54c05 QY |
122 | Specify RIP neighbor. When a neighbor doesn't understand multicast, this |
123 | command is used to specify neighbors. In some cases, not all routers will be | |
124 | able to understand multicasting, where packets are sent to a network or a | |
125 | group of addresses. In a situation where a neighbor cannot process multicast | |
126 | packets, it is necessary to establish a direct link between routers. The | |
127 | neighbor command allows the network administrator to specify a router as a | |
128 | RIP neighbor. The `no neighbor a.b.c.d` command will disable the RIP | |
129 | neighbor. | |
42fc5d26 | 130 | |
c1a54c05 QY |
131 | Below is very simple RIP configuration. Interface `eth0` and interface which |
132 | address match to `10.0.0.0/8` are RIP enabled. | |
a8c90e15 | 133 | |
9eb95b3b | 134 | .. code-block:: frr |
42fc5d26 | 135 | |
c1a54c05 QY |
136 | ! |
137 | router rip | |
138 | network 10.0.0.0/8 | |
139 | network eth0 | |
140 | ! | |
42fc5d26 | 141 | |
42fc5d26 | 142 | |
c1a54c05 | 143 | .. clicmd:: passive-interface (IFNAME|default) |
42fc5d26 | 144 | |
42fc5d26 | 145 | |
c1a54c05 QY |
146 | This command sets the specified interface to passive mode. On passive mode |
147 | interface, all receiving packets are processed as normal and ripd does not | |
148 | send either multicast or unicast RIP packets except to RIP neighbors | |
149 | specified with `neighbor` command. The interface may be specified as | |
150 | `default` to make ripd default to passive on all interfaces. | |
42fc5d26 | 151 | |
c1a54c05 | 152 | The default is to be passive on all interfaces. |
42fc5d26 | 153 | |
c1a54c05 | 154 | .. clicmd:: ip split-horizon |
42fc5d26 | 155 | |
42fc5d26 | 156 | |
c1a54c05 QY |
157 | Control split-horizon on the interface. Default is `ip split-horizon`. If |
158 | you don't perform split-horizon on the interface, please specify `no ip | |
159 | split-horizon`. | |
42fc5d26 | 160 | |
0efdf0fe | 161 | .. _rip-version-control: |
42fc5d26 QY |
162 | |
163 | RIP Version Control | |
164 | =================== | |
165 | ||
c1a54c05 QY |
166 | RIP can be configured to send either Version 1 or Version 2 packets. The |
167 | default is to send RIPv2 while accepting both RIPv1 and RIPv2 (and replying | |
168 | with packets of the appropriate version for REQUESTS / triggered updates). The | |
d1e7591e QY |
169 | version to receive and send can be specified globally, and further overridden on |
170 | a per-interface basis if needs be for send and receive separately (see below). | |
42fc5d26 | 171 | |
c1a54c05 QY |
172 | It is important to note that RIPv1 cannot be authenticated. Further, if RIPv1 |
173 | is enabled then RIP will reply to REQUEST packets, sending the state of its RIP | |
174 | routing table to any remote routers that ask on demand. For a more detailed | |
0efdf0fe | 175 | discussion on the security implications of RIPv1 see :ref:`rip-authentication`. |
42fc5d26 | 176 | |
c1a54c05 | 177 | .. clicmd:: version VERSION |
42fc5d26 | 178 | |
c1a54c05 QY |
179 | Set RIP version to accept for reads and send. ``VERSION`` can be either 1 or |
180 | 1. | |
42fc5d26 | 181 | |
c1a54c05 | 182 | Disabling RIPv1 by specifying version 2 is STRONGLY encouraged, |
0efdf0fe | 183 | :ref:`rip-authentication`. This may become the default in a future release. |
42fc5d26 | 184 | |
c1a54c05 | 185 | Default: Send Version 2, and accept either version. |
42fc5d26 | 186 | |
c1a54c05 | 187 | .. clicmd:: ip rip send version VERSION |
42fc5d26 | 188 | |
c1a54c05 | 189 | VERSION can be ``1``, ``2``, or ``1 2``. |
42fc5d26 | 190 | |
c1a54c05 QY |
191 | This interface command overrides the global rip version setting, and selects |
192 | which version of RIP to send packets with, for this interface specifically. | |
193 | Choice of RIP Version 1, RIP Version 2, or both versions. In the latter | |
194 | case, where ``1 2`` is specified, packets will be both broadcast and | |
195 | multicast. | |
42fc5d26 | 196 | |
c1a54c05 | 197 | Default: Send packets according to the global version (version 2) |
42fc5d26 | 198 | |
c1a54c05 | 199 | .. clicmd:: ip rip receive version VERSION |
42fc5d26 | 200 | |
c1a54c05 | 201 | VERSION can be ``1``, ``2``, or ``1 2``. |
42fc5d26 | 202 | |
c1a54c05 QY |
203 | This interface command overrides the global rip version setting, and selects |
204 | which versions of RIP packets will be accepted on this interface. Choice of | |
205 | RIP Version 1, RIP Version 2, or both. | |
42fc5d26 | 206 | |
c1a54c05 | 207 | Default: Accept packets according to the global setting (both 1 and 2). |
42fc5d26 | 208 | |
1e31580f | 209 | |
0efdf0fe | 210 | .. _how-to-announce-rip-route: |
42fc5d26 QY |
211 | |
212 | How to Announce RIP route | |
213 | ========================= | |
214 | ||
1e31580f | 215 | .. clicmd:: redistribute <babel|bgp|connected|eigrp|isis|kernel|openfabric|ospf|sharp|static|table> [metric (0-16)] [route-map WORD] |
42fc5d26 | 216 | |
1e31580f | 217 | Redistribute routes from other sources into RIP. |
42fc5d26 | 218 | |
1e31580f | 219 | If you want to specify RIP only static routes: |
42fc5d26 | 220 | |
c1a54c05 | 221 | .. clicmd:: default-information originate |
42fc5d26 | 222 | |
c1a54c05 | 223 | .. clicmd:: route A.B.C.D/M |
42fc5d26 | 224 | |
42fc5d26 | 225 | |
c1a54c05 QY |
226 | This command is specific to FRR. The `route` command makes a static route |
227 | only inside RIP. This command should be used only by advanced users who are | |
228 | particularly knowledgeable about the RIP protocol. In most cases, we | |
229 | recommend creating a static route in FRR and redistributing it in RIP using | |
230 | `redistribute static`. | |
42fc5d26 | 231 | |
0efdf0fe | 232 | .. _filtering-rip-routes: |
42fc5d26 QY |
233 | |
234 | Filtering RIP Routes | |
235 | ==================== | |
236 | ||
237 | RIP routes can be filtered by a distribute-list. | |
238 | ||
c1a54c05 | 239 | .. clicmd:: distribute-list ACCESS_LIST DIRECT IFNAME |
42fc5d26 | 240 | |
c1a54c05 QY |
241 | You can apply access lists to the interface with a `distribute-list` command. |
242 | ACCESS_LIST is the access list name. DIRECT is ``in`` or ``out``. If DIRECT | |
243 | is ``in`` the access list is applied to input packets. | |
42fc5d26 | 244 | |
c1a54c05 QY |
245 | The `distribute-list` command can be used to filter the RIP path. |
246 | `distribute-list` can apply access-lists to a chosen interface. First, one | |
247 | should specify the access-list. Next, the name of the access-list is used in | |
248 | the distribute-list command. For example, in the following configuration | |
249 | ``eth0`` will permit only the paths that match the route 10.0.0.0/8 | |
42fc5d26 | 250 | |
9eb95b3b | 251 | .. code-block:: frr |
42fc5d26 | 252 | |
c1a54c05 QY |
253 | ! |
254 | router rip | |
255 | distribute-list private in eth0 | |
256 | ! | |
257 | access-list private permit 10 10.0.0.0/8 | |
258 | access-list private deny any | |
259 | ! | |
a8c90e15 | 260 | |
42fc5d26 | 261 | |
c1a54c05 | 262 | `distribute-list` can be applied to both incoming and outgoing data. |
42fc5d26 | 263 | |
c1a54c05 | 264 | .. clicmd:: distribute-list prefix PREFIX_LIST (in|out) IFNAME |
42fc5d26 | 265 | |
c1a54c05 QY |
266 | You can apply prefix lists to the interface with a `distribute-list` |
267 | command. PREFIX_LIST is the prefix list name. Next is the direction of | |
268 | ``in`` or ``out``. If DIRECT is ``in`` the access list is applied to input | |
269 | packets. | |
42fc5d26 | 270 | |
0efdf0fe | 271 | .. _rip-metric-manipulation: |
42fc5d26 QY |
272 | |
273 | RIP Metric Manipulation | |
274 | ======================= | |
275 | ||
c1a54c05 | 276 | RIP metric is a value for distance for the network. Usually |
42fc5d26 | 277 | *ripd* increment the metric when the network information is |
c1a54c05 | 278 | received. Redistributed routes' metric is set to 1. |
42fc5d26 | 279 | |
c1a54c05 | 280 | .. clicmd:: default-metric (1-16) |
42fc5d26 | 281 | |
42fc5d26 | 282 | |
c1a54c05 QY |
283 | This command modifies the default metric value for redistributed routes. |
284 | The default value is 1. This command does not affect connected route even if | |
285 | it is redistributed by *redistribute connected*. To modify connected route's | |
286 | metric value, please use ``redistribute connected metric`` or *route-map*. | |
287 | *offset-list* also affects connected routes. | |
42fc5d26 | 288 | |
c1a54c05 | 289 | .. clicmd:: offset-list ACCESS-LIST (in|out) |
42fc5d26 | 290 | |
c1a54c05 | 291 | .. clicmd:: offset-list ACCESS-LIST (in|out) IFNAME |
42fc5d26 | 292 | |
42fc5d26 | 293 | |
0efdf0fe | 294 | .. _rip-distance: |
42fc5d26 QY |
295 | |
296 | RIP distance | |
297 | ============ | |
298 | ||
c1a54c05 | 299 | Distance value is used in zebra daemon. Default RIP distance is 120. |
42fc5d26 | 300 | |
c1a54c05 | 301 | .. clicmd:: distance (1-255) |
42fc5d26 | 302 | |
42fc5d26 | 303 | |
c1a54c05 | 304 | Set default RIP distance to specified value. |
42fc5d26 | 305 | |
c1a54c05 | 306 | .. clicmd:: distance (1-255) A.B.C.D/M |
42fc5d26 | 307 | |
42fc5d26 | 308 | |
c1a54c05 QY |
309 | Set default RIP distance to specified value when the route's source IP |
310 | address matches the specified prefix. | |
42fc5d26 | 311 | |
c1a54c05 | 312 | .. clicmd:: distance (1-255) A.B.C.D/M ACCESS-LIST |
42fc5d26 | 313 | |
42fc5d26 | 314 | |
c1a54c05 QY |
315 | Set default RIP distance to specified value when the route's source IP |
316 | address matches the specified prefix and the specified access-list. | |
42fc5d26 | 317 | |
11ab5329 | 318 | .. _rip-route-map: |
42fc5d26 QY |
319 | |
320 | RIP route-map | |
321 | ============= | |
322 | ||
323 | Usage of *ripd*'s route-map support. | |
324 | ||
325 | Optional argument route-map MAP_NAME can be added to each `redistribute` | |
326 | statement. | |
327 | ||
9eb95b3b | 328 | .. code-block:: frr |
42fc5d26 | 329 | |
9eb95b3b QY |
330 | redistribute static [route-map MAP_NAME] |
331 | redistribute connected [route-map MAP_NAME] | |
332 | ..... | |
42fc5d26 | 333 | |
a8c90e15 | 334 | |
c1a54c05 QY |
335 | Cisco applies route-map _before_ routes will exported to rip route table. In |
336 | current FRR's test implementation, *ripd* applies route-map after routes are | |
337 | listed in the route table and before routes will be announced to an interface | |
338 | (something like output filter). I think it is not so clear, but it is draft and | |
339 | it may be changed at future. | |
42fc5d26 | 340 | |
0efdf0fe | 341 | Route-map statement (:ref:`route-map`) is needed to use route-map |
42fc5d26 QY |
342 | functionality. |
343 | ||
c1a54c05 | 344 | .. clicmd:: match interface WORD |
42fc5d26 | 345 | |
c1a54c05 QY |
346 | This command match to incoming interface. Notation of this match is |
347 | different from Cisco. Cisco uses a list of interfaces - NAME1 NAME2 ... | |
348 | NAMEN. Ripd allows only one name (maybe will change in the future). Next - | |
349 | Cisco means interface which includes next-hop of routes (it is somewhat | |
350 | similar to "ip next-hop" statement). Ripd means interface where this route | |
351 | will be sent. This difference is because "next-hop" of same routes which | |
352 | sends to different interfaces must be different. Maybe it'd be better to | |
353 | made new matches - say "match interface-out NAME" or something like that. | |
42fc5d26 | 354 | |
c1a54c05 | 355 | .. clicmd:: match ip address WORD |
42fc5d26 | 356 | |
c1a54c05 | 357 | .. clicmd:: match ip address prefix-list WORD |
42fc5d26 | 358 | |
c1a54c05 | 359 | Match if route destination is permitted by access-list. |
42fc5d26 | 360 | |
c1a54c05 | 361 | .. clicmd:: match ip next-hop WORD |
42fc5d26 | 362 | |
c1a54c05 | 363 | .. clicmd:: match ip next-hop prefix-list WORD |
42fc5d26 | 364 | |
c1a54c05 QY |
365 | Match if route next-hop (meaning next-hop listed in the rip route-table as |
366 | displayed by "show ip rip") is permitted by access-list. | |
42fc5d26 | 367 | |
c1a54c05 | 368 | .. clicmd:: match metric (0-4294967295) |
42fc5d26 | 369 | |
c1a54c05 QY |
370 | This command match to the metric value of RIP updates. For other protocol |
371 | compatibility metric range is shown as (0-4294967295). But for RIP protocol | |
372 | only the value range (0-16) make sense. | |
42fc5d26 | 373 | |
c1a54c05 | 374 | .. clicmd:: set ip next-hop A.B.C.D |
42fc5d26 | 375 | |
c1a54c05 QY |
376 | This command set next hop value in RIPv2 protocol. This command does not |
377 | affect RIPv1 because there is no next hop field in the packet. | |
42fc5d26 | 378 | |
c1a54c05 | 379 | .. clicmd:: set metric (0-4294967295) |
42fc5d26 | 380 | |
c1a54c05 QY |
381 | Set a metric for matched route when sending announcement. The metric value |
382 | range is very large for compatibility with other protocols. For RIP, valid | |
383 | metric values are from 1 to 16. | |
42fc5d26 | 384 | |
0efdf0fe | 385 | .. _rip-authentication: |
42fc5d26 QY |
386 | |
387 | RIP Authentication | |
388 | ================== | |
389 | ||
390 | RIPv2 allows packets to be authenticated via either an insecure plain | |
391 | text password, included with the packet, or via a more secure MD5 based | |
d50b2aa0 | 392 | :abbr:`HMAC (keyed-Hashing for Message AuthentiCation)`, |
42fc5d26 QY |
393 | RIPv1 can not be authenticated at all, thus when authentication is |
394 | configured `ripd` will discard routing updates received via RIPv1 | |
395 | packets. | |
396 | ||
a8c90e15 | 397 | However, unless RIPv1 reception is disabled entirely, |
0efdf0fe | 398 | :ref:`rip-version-control`, RIPv1 REQUEST packets which are received, |
42fc5d26 | 399 | which query the router for routing information, will still be honoured |
a8c90e15 | 400 | by `ripd`, and `ripd` WILL reply to such packets. This allows |
42fc5d26 QY |
401 | `ripd` to honour such REQUESTs (which sometimes is used by old |
402 | equipment and very simple devices to bootstrap their default route), | |
403 | while still providing security for route updates which are received. | |
404 | ||
405 | In short: Enabling authentication prevents routes being updated by | |
406 | unauthenticated remote routers, but still can allow routes (I.e. the | |
407 | entire RIP routing table) to be queried remotely, potentially by anyone | |
408 | on the internet, via RIPv1. | |
409 | ||
410 | To prevent such unauthenticated querying of routes disable RIPv1, | |
0efdf0fe | 411 | :ref:`rip-version-control`. |
42fc5d26 | 412 | |
c1a54c05 | 413 | .. clicmd:: ip rip authentication mode md5 |
42fc5d26 | 414 | |
42fc5d26 | 415 | |
c1a54c05 | 416 | Set the interface with RIPv2 MD5 authentication. |
42fc5d26 | 417 | |
c1a54c05 | 418 | .. clicmd:: ip rip authentication mode text |
42fc5d26 | 419 | |
42fc5d26 | 420 | |
c1a54c05 | 421 | Set the interface with RIPv2 simple password authentication. |
42fc5d26 | 422 | |
c1a54c05 | 423 | .. clicmd:: ip rip authentication string STRING |
42fc5d26 | 424 | |
42fc5d26 | 425 | |
c1a54c05 QY |
426 | RIP version 2 has simple text authentication. This command sets |
427 | authentication string. The string must be shorter than 16 characters. | |
42fc5d26 | 428 | |
c1a54c05 | 429 | .. clicmd:: ip rip authentication key-chain KEY-CHAIN |
42fc5d26 | 430 | |
42fc5d26 | 431 | |
d1e7591e | 432 | Specify Keyed MD5 chain. |
42fc5d26 | 433 | |
9eb95b3b | 434 | .. code-block:: frr |
42fc5d26 | 435 | |
9eb95b3b QY |
436 | ! |
437 | key chain test | |
438 | key 1 | |
439 | key-string test | |
440 | ! | |
441 | interface eth1 | |
442 | ip rip authentication mode md5 | |
443 | ip rip authentication key-chain test | |
444 | ! | |
a8c90e15 | 445 | |
42fc5d26 | 446 | |
0efdf0fe | 447 | .. _rip-timers: |
42fc5d26 QY |
448 | |
449 | RIP Timers | |
450 | ========== | |
451 | ||
c1a54c05 | 452 | .. clicmd:: timers basic UPDATE TIMEOUT GARBAGE |
42fc5d26 | 453 | |
42fc5d26 | 454 | |
c1a54c05 QY |
455 | RIP protocol has several timers. User can configure those timers' values |
456 | by `timers basic` command. | |
42fc5d26 | 457 | |
c1a54c05 | 458 | The default settings for the timers are as follows: |
42fc5d26 | 459 | |
c1a54c05 QY |
460 | - The update timer is 30 seconds. Every update timer seconds, the RIP |
461 | process is awakened to send an unsolicited Response message containing | |
462 | the complete routing table to all neighboring RIP routers. | |
463 | - The timeout timer is 180 seconds. Upon expiration of the timeout, the | |
464 | route is no longer valid; however, it is retained in the routing table | |
465 | for a short time so that neighbors can be notified that the route has | |
466 | been dropped. | |
467 | - The garbage collect timer is 120 seconds. Upon expiration of the | |
468 | garbage-collection timer, the route is finally removed from the routing | |
469 | table. | |
42fc5d26 | 470 | |
c1a54c05 QY |
471 | The ``timers basic`` command allows the the default values of the timers |
472 | listed above to be changed. | |
42fc5d26 | 473 | |
42fc5d26 | 474 | |
0efdf0fe | 475 | .. _show-rip-information: |
42fc5d26 QY |
476 | |
477 | Show RIP Information | |
478 | ==================== | |
479 | ||
480 | To display RIP routes. | |
481 | ||
c1a54c05 | 482 | .. clicmd:: show ip rip |
42fc5d26 | 483 | |
c1a54c05 | 484 | Show RIP routes. |
42fc5d26 QY |
485 | |
486 | The command displays all RIP routes. For routes that are received | |
487 | through RIP, this command will display the time the packet was sent and | |
c1a54c05 | 488 | the tag information. This command will also display this information |
42fc5d26 QY |
489 | for routes redistributed into RIP. |
490 | ||
c1a54c05 | 491 | .. clicmd:: show ip rip status |
42fc5d26 | 492 | |
c1a54c05 | 493 | The command displays current RIP status. It includes RIP timer, |
d1e7591e | 494 | filtering, version, RIP enabled interface and RIP peer information. |
42fc5d26 QY |
495 | |
496 | :: | |
497 | ||
c1a54c05 QY |
498 | ripd> **show ip rip status** |
499 | Routing Protocol is "rip" | |
500 | Sending updates every 30 seconds with +/-50%, next due in 35 seconds | |
501 | Timeout after 180 seconds, garbage collect after 120 seconds | |
502 | Outgoing update filter list for all interface is not set | |
503 | Incoming update filter list for all interface is not set | |
504 | Default redistribution metric is 1 | |
505 | Redistributing: kernel connected | |
506 | Default version control: send version 2, receive version 2 | |
507 | Interface Send Recv | |
508 | Routing for Networks: | |
509 | eth0 | |
510 | eth1 | |
511 | 1.1.1.1 | |
512 | 203.181.89.241 | |
513 | Routing Information Sources: | |
514 | Gateway BadPackets BadRoutes Distance Last Update | |
a8c90e15 | 515 | |
42fc5d26 QY |
516 | |
517 | RIP Debug Commands | |
518 | ================== | |
519 | ||
520 | Debug for RIP protocol. | |
521 | ||
c1a54c05 | 522 | .. clicmd:: debug rip events |
42fc5d26 | 523 | |
c1a54c05 QY |
524 | Shows RIP events. Sending and receiving packets, timers, and changes in |
525 | interfaces are events shown with *ripd*. | |
42fc5d26 | 526 | |
c1a54c05 | 527 | .. clicmd:: debug rip packet |
42fc5d26 | 528 | |
c1a54c05 QY |
529 | Shows display detailed information about the RIP packets. The origin and |
530 | port number of the packet as well as a packet dump is shown. | |
42fc5d26 | 531 | |
c1a54c05 | 532 | .. clicmd:: debug rip zebra |
42fc5d26 | 533 | |
c1a54c05 QY |
534 | This command will show the communication between *ripd* and *zebra*. The |
535 | main information will include addition and deletion of paths to the kernel | |
536 | and the sending and receiving of interface information. | |
42fc5d26 | 537 | |
c1a54c05 | 538 | .. clicmd:: show debugging rip |
42fc5d26 | 539 | |
c1a54c05 | 540 | Shows all information currently set for ripd debug. |
42fc5d26 | 541 |