FRR is a fork of the well-known Quagga router. FRR is managed under the Linux Foundation.
For Ubuntu, .deb packages are available from https://deb.frrouting.org. Since Quagga and FRR cannot be installed simultaneously, be aware that Quagga .deb packages will be removed.
The FRRZebra Service must always be enabled. This service runs the main zebrad daemon which manages the common FRR configuration. Specific routing protocols, such as OSPFv2 or RIP, can be enabled by clicking on their respective service buttons. Template router configurations will appear in the FRRZebra Service and specific interface or router configuration commands can be customized in the common FRRZebra configuration file.
To interact with FRR routers in CORE, the FRRVTYSH service will also need to be enabled.
zebra is an IP routing manager. It provides kernel routing table updates, interface lookups, and redistribution of routes between different routing protocols.
- FRRZebra configuration commands can be on docs.frrouting.org link
vtysh provides a combined frontend to all FRR daemons in a single combined session. It should be enabled so that the live router shell is enabled for routers created in CORE.
Border Gateway Protocol (BGP, version 4) is one of the Exterior Gateway Protocols and the de facto standard interdomain routing protocol. BGP-4 is described in RFC 1771 and updated by RFC 4271. RFC 2858 adds multiprotocol support to BGP-4.
- FRRBGP configuration commands can be found on docs.frrouting.org link
Babel is an interior gateway protocol that is suitable both for wired networks and for wireless mesh networks. Babel has been described as ‘RIP on speed’ – it is based on the same principles as RIP, but includes a number of refinements that make it react much faster to topology changes without ever counting to infinity, and allow it to perform reliable link quality estimation on wireless links. Babel is a double-stack routing protocol, meaning that a single Babel instance is able to perform routing for both IPv4 and IPv6. FRR implements Babel as described in RFC 6126.
- FRRBabel configuration commands can be found on docs.frrouting.org link
EIGRP – Routing Information Protocol is widely deployed interior gateway routing protocol. EIGRP was developed in the 1990’s. EIGRP is a distance-vector protocol and is based on the DUAL algorithms. As a distance-vector protocol, the EIGRP router send updates to its neighbors as networks change, thus allowing the convergence to a known topology. EIGRP is described in RFC7868
- FRREIGRP configuration commands can be found on docs.frrouting.org link
ISIS is a routing protocol which is described in ISO10589, RFC 1195, RFC 5308. ISIS is an IGP. Compared with RIP, ISIS can provide scalable network support and faster convergence times like OSPF. ISIS is widely used in large networks such as ISP and carrier backbone networks.
- FRRISIS configuration commands can be found on docs.frrouting.org link
OSPF version 2 is a routing protocol which is described in RFC 2328. OSPF is an IGP. Compared with RIP, OSPF can provide scalable network support and faster convergence times. OSPF is widely used in large networks such as ISP backbone and enterprise networks.
- FRROSPFv2 configuration commands can be found on docs.frrouting.org link
ospf6d is a daemon support OSPF version 3 for IPv6 network. OSPF for IPv6 is described in RFC 2740.
- FRR OSPFv3 configuration commands can be found on docs.frrouting.org link
FRRPIM Service PIM – Protocol Independent Multicast pimd supports pim-sm as well as igmp v2 and v3. pim is vrf aware and can work within the context of vrf’s in order to do S,G mrouting. Additionally PIM can be used in the EVPN underlay network for optimizing forwarding of overlay BUM (broadcast/unicast/multicast) traffic.
- FRRPIM configuration commands can be found on docs.frrouting.org link
RIP – Routing Information Protocol is widely deployed interior gateway protocol. RIP was developed in the 1970s at Xerox Labs as part of the XNS routing protocol. RIP is a distance-vector protocol and is based on the Bellman-Ford algorithms. As a distance-vector protocol, RIP router send updates to its neighbors periodically, thus allowing the convergence to a known topology. In each update, the distance to any given network will be broadcast to its neighboring router. ripd supports RIP version 2 as described in RFC2453 and RIP version 1 as described in RFC1058.
- FRRRIP configuration commands can be found on docs.frrouting.org link
ripngd supports the RIPng protocol as described in RFC 2080. It’s an IPv6 reincarnation of the RIP protocol.
- FRRRIPNG configuration commands can be found on docs.frrouting.org link