It’s our pleasure to start the week off announcing the release of FRRouting to the open community. We worked closely with several other partners to make this launch happen and we’ll be integrating it with our products in upcoming releases. It’s a constant priority of ours to ensure we are contributing, maintaining and inspiring contributions to the community, and this release truly provides a solution that will be welcomed from many industries.

The following post was originally published on the Linux Foundation’s blog. They have graciously given us permission to republish, as the post does a fantastic job of describing the release. We’ve added a few sentences at the end to tie it all together. We hope you enjoy.

One of the most exciting parts of being in this industry over the past couple of decades has been witnessing the transformative impact that open source software has had on IT in general and specifically on networking. Contributions to various open source projects have fundamentally helped bring the reliability and economics of web-scale IT to organizations of all sizes. I am happy to report the community has taken yet another step forward with FRRouting.

FRRouting (FRR) is an IP routing protocol suite for Unix platforms which includes protocol daemons for BGP, IS-IS, LDP, OSPF, PIM, and RIP, and the community is working to make this the best routing protocol stack available.

FRR is rooted in the Quagga project and includes the fundamentals that made Quagga so popular. Plus it has a ton of recent enhancements that greatly improve on that foundation.

Here’s a bird’s eye view of some things the team has been busy working on:

  • 32-bit route tags were added to BGP and OSPFv2/v3, improving route policy maintenance and increasing interoperability in multivendor environments;
  • Update-groups and nexthop tracking enable BGP to scale to ever-increasing environments;
  • BGP add-path provides users with the ability to advertise service reachability in richly connected networks;
  • The addition of RFC 5549 to BGP provides IPv4 connectivity using IPv6 native infrastructure, enabling customers to build IPv6-centric networks;
  • Virtual routing and forwarding (VRF) enables BGP users to operate isolated routing domains such as those used by web application infrastructures, hosting providers, and Internet Service Providers;
  • EVPN type 5 routes allow customers with layer 2 data centers to exchange subnet information using BGP EVPN;
  • PIM-SM and MSDP enable enterprise applications that rely on IP multicast to use FRR;
  • Static LSPs along with LDP enable architects to use MPLS to engineer network data flow;
  • An overhaul of the CLI infrastructure and new unit test infrastructure improves the ongoing development and quality of FRR; and
  • Enabling IETF NVO3 network virtualization control allows users to build standards-based interoperable network virtualization overlays.

The protocol additions above are augmented by SnapCraft packaging and support for JSON outputs, both of which improve the operationalization of FRR.

Pretty cool stuff huh? The contributors designed FRR to streamline the routing protocol stack and to make network engineers’ lives that much easier. Businesses can use FRR for connecting hosts, virtual machines, and containers to the network; advertising network service endpoints; network switching and routing; and Internet access/peering routers.

Contributors from 6WIND, Architecture Technology Corporation, Cumulus Networks, LabN Consulting, NetDEF (OpenSourceRouting), Volta Networks, and other companies have been working on integrating their advancements and want to invite you to participate in the FRRouting community to help shape the future of networking.

As you can see from the original post, this is an exciting project that required dedicated collaboration between contributors. Cumulus Networks is planning to integrate FRRouting into Cumulus Linux as the default routing suite. Look for it in a release coming soon. Also, at that time, FRRouting will become the software package for routing on the host, so you’ll have more robust layer 3 routing throughout your data center. In the meantime, head on over to GitHub to access FRR today.