RuggedCom RuggedRouter RX1100 - Manual (Page 160)

17. Configuring Dynamic Routing
Revision 1.14.3 160 RX1000/RX1100™
17. Configuring Dynamic Routing
17.1. Introduction
This chapter familiarizes the user with:
• Enabling the Dynamic Routing Suite
• Enabling and starting OSPF, RIP, and BGP
• Configuring OSPF, RIP, and BGP
• Obtaining OSPF, RIP, and BGP Status
• OSPF and VRRP
17.1.1. Quagga, RIP, OSPF, and BGP
Dynamic routing is provided by the Quagga suite of routing protocol daemons. Quagga provides three
daemons for managing routing, the core, ripd, ospfd, and bgpd.
The core daemon handles interfacing with the kernel to maintain the router's routing table and to
check link statuses. It tells RIP, OSPF, and BGP what state links are in, what routes are in the routing
table, and some information about the interfaces.
The ripd, ospfd, and bgpd daemons handle communications with other routers using the RIPv2,
OSPFv2, and BGP protocols respectively, and decide which routers are preferred to forward to for
each network route known to the router.
In complex legacy networks, RIP, OSPF, and BGP may be active on the same router at the same
time. Typically, however, one of them is employed.
17.1.2. BGP Fundamentals
The Border Gateway Protocol (BGP, RFC 4271) is a robust and scalable routing protocol. BGP is
designed to manage a routing table of up to 90000 routes, and is therefore used in large networks, or
among groups of networks which have common administrative and routing policies. If BGP is used to
exchange routing information between different networks, it is called Exterior BGP (EBGP); Interior
BGP (IBGP) is used to exchange routing information between routers within the same network.
17.1.3. RIP Fundamentals
The Routing Information Protocol determines the best path for routing IP traffic over a TCP/IP network
based on the number of hops between any two routers. It uses the shortest route available to a given
network as the route to use for sending packets to that network.
The RuggedRouter RIP daemon (ripd) is an RFC1058 compliant implementation of RIP support RIP
version 1 and 2. RIP version 1 is limited to obsolete class based networks, while RIP version 2 supports
subnet masks as well as simple authentication for controlling which routers to accept route exchanges
with.
RIP uses network and neighbor entries to control which routers it will exchange routes with. A network
is either a subnet or a physical (broadcast-capable) network interface. Any router that is part of that