FRR runs a daemon per protocol, and mgmtd is still rewriting their configuration
The FRRouting Protocol Suite
At a glance
- What is it?
- A C routing suite carrying sixteen IPv4 and IPv6 protocols, three maintenance releases cut within two minutes, and a work in progress daemon that pushes YANG configuration to the others over a northbound API.
- Who is it for?
- FRR fits an operator who needs BGP, OSPF, IS-IS, or a multicast stack from one package set with per-file license clarity, and who is comfortable reading the feature matrix before assuming a protocol exists on their platform. Hold off if you need EIGRP or NHRP outside an alpha, or if a stable configuration interface matters more to you than the newer one, because the mgmtd path is unfinished and the legacy path is still there beside it.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly C, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- FRRouting/frr4,373 ★ · +70
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| FRRouting/frr | 4.3k | 4.4k |
70 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Sixteen protocols, two of them still alpha
The protocol list is the project's real scope statement, and it is worth reading closely because two entries carry a qualifier. BGP, OSPFv2, OSPFv3, RIPv1, RIPv2, RIPng, IS-IS, PIM in its SM, DM, SSM and MSDP modes, LDP, BFD, Babel, PBR, OpenFabric and VRRP are the settled set. EIGRP and NHRP are both marked alpha. PIM alone expands into four named variants, which makes it the broadest single entry, and Babel and OpenFabric sit alongside the mainstream interior and exterior protocols as a deliberate choice rather than an omission. The qualifier that matters most is not on any single protocol: not every protocol or feature is available on every platform, and the project points at a feature matrix in the user guide for that answer rather than trying to keep the list honest inline.
A directory per daemon, beside the pieces that are not daemons
The tree makes the one-daemon-per-protocol structure literal. Each protocol family has its own top-level directory next to the ones you would guess: `bgpd/` for BGP, `ospfd/` and `ospf6d/` for the two OSPF versions, `ripd/` and `ripngd/` for the two RIP variants, `isisd/`, `pimd/`, `ldpd/`, `babeld/`, `pbrd/`, `vrrpd/`, `bfdd/`, `eigrpd/`, `nhrpd/`, plus `pathd/`, `sharpd/`, `staticd/` and `qpb/`. Around them sit the parts that are not routing daemons: `zebra/` holds the shared routing table layer, `lib/` and `include/` carry the shared code, `m4/` carries the autoconf macros, and `vtysh/` is the integrated shell. The build surface is visible too, with `configure.ac`, `Makefile.am`, `bootstrap.sh`, `buildtest.sh`, `config.version.in` and `stamp-h.in`, which is the conventional GNU autotools layout rather than anything modern. Two directories sit oddly against a C project: `python/` and a set of dotfiles for `.flake8`, `.pylintrc` and `.isort.cfg`.
mgmtd replaces the legacy config path and is not finished
One daemon in that tree is changing how the others are configured, and the project says so directly. The `mgmtd/` daemon applies YANG configuration to the routing protocol daemons through the northbound API, instead of each daemon only having its own legacy configuration path. Three qualifications sit around that sentence and each one matters. It is labelled work in progress. Not all daemons are migrated yet. And the expectation of ongoing changes is stated outright. The `yang/` directory at the tree root is the visible counterpart to the promise, holding the models the northbound API is built on. Both the legacy per-daemon path and the mgmtd path are present, which is the honest state of a migration that is under way rather than finished.
Three maintenance branches published in the same minute
The three most recent releases were cut within roughly two minutes of each other on 2026-08-31: frr-10.6.2, frr-10.5.5 and frr-10.4.5. Read as a maintenance policy rather than a coincidence, it says the project ships patch releases for three supported lines at once, which is the behaviour you want when the same daemon set runs across mixed distribution versions and you cannot upgrade every site on the same day. The last push to the repository came later still, on 2026-11-02, so the tag activity is not the end of the story. Source tarballs are published from the releases page rather than from the default branch, which is the mechanism behind those tags: the tree you read on master is ahead of every tarball on the releases page.
Packages live on two project mirrors, and the build steps live on another site
There is no install command anywhere in this repository's front page: the package repositories and the build instructions are both hosted elsewhere. Pre-built APT packages for Debian and its derivatives sit at `deb.frrouting.org`, and RPM packages for RHEL, Fedora and related distributions sit at `rpm.frrouting.org`, both run by the project rather than by a distribution. Source tarballs come from the releases page. Building from source is documented in a developer guide, in a separate documentation project from the user guide, which is the split to notice when you are looking for the difference between operating the suite and modifying it. Once installed, the front page defers entirely to the user guide for how to use it, so the practical sequence is: pick a mirror or a tarball, then read the user guide.
Per-file SPDX identifiers under a GPLv2+ default and a separate docs license
The licensing is layered, and the front page is careful about saying so. Per-file licenses use SPDX identifiers, with `COPYING` and `doc/licenses/` holding the detail. The combined work is generally understood to be distributable under the GNU General Public License version 2 or later, and the wording is deliberately hedged: generally understood, with `COPYING` given as the place to read for details. Documentation is carved out under a separate custom permissive license, again pointing back to `COPYING` for the background. No license is asserted in the repository's license metadata field, so the machine-readable answer and the prose answer are not the same shape, which is another reason to read the files rather than the badge. For a suite that vendors or links code from elsewhere, per-file SPDX identifiers are the mechanism that lets you answer the question per component.
Security reports go to a list address, written so it survives scrapers
Security issues have their own channel and the address is deliberately obfuscated in the plain text block that carries it:
security [at] lists.frrouting.orgThe bracketed `at` is the usual way of keeping a harvested address from being useful, and the destination is a mailing list rather than a tracker or a private form. That matters for a routing suite specifically: a vulnerability in a routing daemon is often only reachable after a crafted packet, which is exactly the class of finding that benefits from being reported privately to a list rather than filed publicly against the issue tracker. The address shares the `lists.frrouting.org` host with the project's public discussion lists, so the same infrastructure carries both.
Development, operations and announcements run on three separate lists
The public mailing infrastructure is split by audience rather than pooled. Development traffic goes to `[email protected]`, users and operators to `[email protected]`, and announcements to `[email protected]`, with the list index, subscription details and archives all reachable from the same host. Chat runs on Slack, where new members join through an invite link published on the community page rather than by open signup. Contributions are routed through a developer documentation set that separates submitting patches and enhancements from commit guidelines, which tells you the project expects the message format to be part of the review. The front page closes by welcoming contributions of any size.
Editorial conclusion
FRR fits an operator who needs BGP, OSPF, IS-IS, or a multicast stack from one package set with per-file license clarity, and who is comfortable reading the feature matrix before assuming a protocol exists on their platform. Hold off if you need EIGRP or NHRP outside an alpha, or if a stable configuration interface matters more to you than the newer one, because the mgmtd path is unfinished and the legacy path is still there beside it. Before deploying, check which of your platform and daemon pairs the matrix actually covers, and read COPYING plus doc/licenses/ rather than assuming one license covers the tree and the manuals.
Frequently asked questions
What does FRR stand for?
FRR is the short form of FRRouting, the project that implements and manages IPv4 and IPv6 routing protocols. The repository is FRRouting/frr, the suite description is The FRRouting Protocol Suite, and the project website is frrouting.org.
How do I install FRR on Ubuntu?
The project publishes pre-built APT packages for Debian and its derivatives at deb.frrouting.org, and RPM packages for RHEL, Fedora and related distributions at rpm.frrouting.org. Source tarballs are on the releases page, and build instructions for supported platforms are in the developer documentation.
What is frrouting frr?
It is a C suite of routing protocol daemons covering BGP, OSPFv2 and v3, RIPv1 and v2, RIPng, IS-IS, PIM, LDP, BFD, Babel, PBR, OpenFabric and VRRP, plus EIGRP and NHRP marked alpha. Each protocol family has its own daemon directory in the tree, with `zebra/` holding the shared routing table layer.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/frrouting-frr)Star history chart for your README
[](https://hysenlabs.com/projects/frrouting-frr)Was this useful?