frrouting/frr

The FRRouting Protocol Suite

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 26 minutes ago
Added to GitGenius on September 16th, 2026
Created on December 15th, 2016
Open Issues & Pull Requests: 806 (+0)
GitHub issues: Enabled
Number of forks: 1,617
Total Stargazers: 4,298 (+0)
Total Subscribers: 149 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 16.1 hours
Mean response time: 18.5 days
90th percentile: 19.2 days
Tracked items: 883

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 17% of issues opened in the past year have never received a reply. 95% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "unsupported-version" is answered fastest, typically in about 3 hours, while "autoclose" waits about 3 days. 34% of tracked open issues have had no activity in three months. 67% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 213
New in 7 days: 20
Closed in 7 days: 15
Avg open age: 448 days
Stale 30+ days: 166
Stale 90+ days: 105

Recent activity

Opened in 7 days: 20
Closed in 7 days: 15
Comments in 7 days: 6
Events in 7 days: 17

Top labels

  • triage (586)
  • bgp (165)
  • bug (50)
  • bfd (16)
  • enhancement (15)
  • unsupported-version (14)
  • autoclose (12)
  • zebra (10)

Detailed Description

FRRouting is a routing protocol suite that implements multiple dynamic routing protocols for Unix-like systems. The project provides a unified platform for running protocols including BGP, OSPF, IS-IS, RIP, EIGRP, PIM, BABEL, and others, allowing operators to deploy advanced routing functionality on standard Linux and BSD systems rather than relying solely on proprietary router hardware.

The tool solves the problem of needing flexible, open-source routing capabilities by offering implementations of industry-standard protocols in a modular architecture. Each protocol runs as a separate daemon that communicates through a central zebra daemon, which manages the kernel routing table. This design allows operators to enable only the protocols they need and to mix and match routing technologies within a single system. The suite supports advanced features across multiple protocol families, including MPLS, EVPN, and policy-based routing.

Organizations running software-defined networks, network appliances, or custom routing infrastructure should consider this tool. It suits deployments where operators need standards-compliant routing without vendor lock-in, particularly in environments already built on Linux or BSD. The project is appropriate for both small networks experimenting with routing protocols and large-scale deployments requiring sophisticated multi-protocol routing. Those building network operating systems or containerized routing solutions will find the modular protocol architecture particularly valuable.

The project maintains steady development activity with regular commits addressing protocol improvements, bug fixes, and feature additions across its protocol implementations. Work spans multiple protocol families simultaneously, indicating active maintenance of the entire suite rather than focus on any single routing protocol. The codebase receives ongoing attention to compatibility and standards compliance, with contributions flowing consistently across different functional areas of the routing stack.