ripd


The Routing Information Protocol (RIP) is a legendary protocol. It is a very simple distance-vector routing protocol. `ripd' supports RIP version 2 as described in RFC2453 and RIP version 1 as described in RFC1058. RIP is a "distance-vector" protocol and is based on the "Bellman-Ford" algorithms. The RIP protocol was developed in the 1970s at Xerox Labs as part of the XNS routing protocol. As a distance-vector protocol, routers running RIP will send updates to its neighbors, thus allowing the convergence to a known topology. In each update, the distance of any given router will be broadcast to its neighbor.

Menu
Invoking ripd
ripd Configuration
Filtering RIP Routes
ripd route-map
ripd Terminal Mode Commands
ripd Debug Commands

Invoking ripd


ripd invocation options. Common options that can be specified (See also Common Invocation Options.).

The following points are important to consider when using ripd:

The user must have the capability to bind to port 521, generally this means that it (the user) must have superuser priviliges.

The netmask features of ripd supports both version 1 and version 2 of RIP. Version 1 of RIP originally contained no netmask information. In RIP version 1, network classes were originally used to determine the size of the netmask. Class A networks use 8 bits of mask, Class B networks use 16 bits of masks, while Class C networks use 24 bits of mask. Today, the most widely used method of a network mask is assigned to the packet on the basis of the interface that received the packet. Version 2 of RIP supports a variable length subnet mask (VLSM). By extending the subnet mask, the mask can be divided and reused. Each subnet can be used for different purposes such as large to middle size LANs and WAN links. Zebra ripd does not support the non-sequential netmasks that are included in RIP Version 2.

In a case of similar information with the same prefix and metric, the old information will be suppressed. Ripd does not currently support equal cost multipath routing.

ripd Configuration


How to announce RIP routes.

If you want to specify RIP only static routes:

There are four timer commands in RIP. One is:

Filtering RIP Routes


RIP routes can be filtered by a distribute-list.

ripd route-map

Usage of ripd's route-map support.

Optional argument route-map MAP-NAME is added to each redistribute statement.

redistribute static [route-map MAP_NAME]
redistribute connected [route-map MAP_NAME]

Cisco applies a route-map before routes will be exported to rip route table. In current Zebra's test implementation, ripd applies a route-map after routes listed in the route table and before routes will be announced to interface (something like output filter). I think it is not so clear, but it is draft and it may be changed at future.

Route-map statement Route Map is needed to use route-map functionality.

Route-map's match statement.

Route-map's set statement

ripd Terminal Mode Commands


To display RIP routes.

ripd Debug Commands


Debug for RIP protocol.