=== RIP === .. sidebar:: Contents .. contents:: :depth: 2 :local: This chapter covers some aspects related to the :osdx:cfg:`protocols rip` which is a feature that allows users to **manage and monitor** the RIP protocol. RIP (Routing Information Protocol) is a distance-vector routing protocol described in RFC 2453 (RIPv2). RIP uses hop count as a routing metric to determine the best path to a destination network, with a maximum of 15 hops. It is one of the oldest routing protocols and is commonly used in small to medium-sized networks. RIP routers periodically broadcast their entire routing table to neighboring routers. Each router updates its own routing table based on the information received, selecting routes with the lowest hop count. Routes with a hop count of 16 are considered unreachable and are removed from the routing table. Configuration ============= The RIP protocol can be configured either using :osdx:cfg:`protocols rip` or in an interface using `interfaces * * ip rip`, for example, :osdx:cfg:`interfaces dummy * ip rip` or :osdx:cfg:`interfaces ethernet * ip rip`. In OSDx, the RIP configuration allows various parameters to be set to fine-tune the protocol's behavior. An explanation of each configurable parameter in :osdx:cfg:`protocols rip` configuration is provided below: * ``default-distance``: Administrative distance for RIP routes. Values range from 1 to 255. * ``default-information``: Control distribution of default route. * ``originate``: Distribute a default route to RIP neighbors. * ``default-metric``: Metric of redistributed routes. Values range from 1 to 16. * ``distribute-list``: Filter networks in routing updates. * ``interface``: Apply filtering to a specific interface. * ``prefix-list``: Filter using a prefix-list. * ``in``: Prefix-list to apply to input packets. * ``out``: Prefix-list to apply to output packets. * ``prefix-list``: Filter using a prefix-list globally. * ``in``: Prefix-list to apply to input packets. * ``out``: Prefix-list to apply to output packets. * ``interface``: Interface name. Enables RIP on the specified interface so that the router can provide network information to other RIP routers through this interface. * ``route-map``: Route-map to filter route updates on the interface. * ``in``: Route-map to filter incoming route updates. * ``out``: Route-map to filter outgoing route updates. * ``neighbor``: Specifies the IP address of a neighboring router for directed RIP updates instead of multicast. * ``network``: RIP network. Specifies the networks on which RIP is enabled. If an interface has an address within the defined network range, RIP is activated on that interface. * ``network-distance``: Specifies a source network with a custom administrative distance. * ``distance``: Administrative distance for the network. Values range from 1 to 255. * ``passive``: Suppress routing updates on interface(s). Passive interfaces receive RIP updates but do not send them. * ``all``: Suppress routing updates on all interfaces. * ``interface``: Suppress routing updates on a specific interface. Cannot coexist with ``all``. * ``interface-exclude``: Exclude an interface from suppression when using ``all``. * ``redistribute``: Redistribute information from another routing protocol. This parameter includes the following arguments: ``bgp``, ``connected``, ``kernel``, ``ospf`` and ``static``. These arguments include ``metric``, the metric for redistributed routes (1-16); and ``route-map``, a route map reference. * ``route``: RIP static routes. Specifies a static route to be advertised through RIP. * ``timers``: RIP timer values. All three timers must be configured together. * ``update``: Routing table update timer in seconds. This is the interval between periodic routing updates. Default is 30 seconds. * ``timeout``: Routing information timeout timer in seconds. This is the time after which a route is considered invalid if no update is received. Default is 180 seconds. * ``garbage-collection``: Garbage collection timer in seconds. This is the time a route remains in the routing table after being marked as invalid before it is removed. Default is 120 seconds. An explanation of each configurable parameter of RIP in an interface configuration is provided below: * ``authentication``: RIP interface authentication. Only one authentication method can be configured per interface. * ``message-digest``: MD5 authentication parameters. Includes a ``key-id`` (1-255) and an ``encrypted-password``. * ``encrypted-password``: Plain text authentication using an encrypted password. * ``split-horizon``: Split horizon parameters. Split horizon prevents routing loops by not advertising routes back through the interface on which they were learned. * ``disable``: Disable split horizon on the specified interface. * ``poison-reverse``: Enable poison reverse for split horizon. When enabled, routes learned from an interface are advertised back with a metric of 16 (unreachable). Cannot be enabled together with ``disable``. Monitoring ========== To monitor the status and configuration of RIP protocol, you can use the following commands: * :osdx:op:`protocols rip show` to monitor RIP protocol. .. _rip_examples: Examples ======== :doc:`Here ` you can find examples related to RIP. Command Summary =============== .. osdx:cmdtree:: cfg protocols rip interfaces bridge * ip rip interfaces bridge * vif * ip rip interfaces dummy * ip rip interfaces ethernet * ip rip interfaces ethernet * vif * ip rip interfaces openvpn * ip rip interfaces tunnel * ip rip interfaces vxlan * ip rip interfaces wlan * ip rip .. osdx:cmdtree:: op protocols rip show