FRR(1)

💖 FRR(1) — bestie's guide to frr 💖

okay so real quick, this whole page is from the FRR manual, section 1 (that's the "commands you actually type" section, iykyk). sit down, grab a strawberry 🍓, and let's get into it.

---

✨ NAME ✨

frr — it's a systemd interaction script. that's the whole vibe. it's the little buddy you poke to make systemd do stuff with FRR. 🎀

---

🌸 SYNOPSIS 🌸

frr [ start ]

frr [ stop ]

frr [ reload ]

frr [ restart ]

frr [ status ]

literally that's it. one word after the command. so simple, so elegant, we love her. 💅

---

🦋 DESCRIPTION 🦋

frr is a systemd interaction script for the FRRouting routing engine. that's the whole job description. it's the middleman between you and systemd so you don't have to go systemctl-ing around everywhere and risk a typo. main character energy for a script that's like 5 lines long, honestly. 👑

---

✨ OPTIONS ✨

here's everything you can hand to frr. no hidden ones, no secret menu, this is the full list fr fr:

• start — starts the FRR daemons that are enabled. only the enabled ones, bestie, not every daemon that's technically installed.
• stop — stops the enabled FRR daemons. same deal, enabled ones only.
• reload — reloads the configuration files that you modified. if you edited a config, this is your girl.
• restart — stops literally all the running daemons and then restarts them. the full reset button. 💀
• status — shows you the status of all the daemons. like a vibe check but for your routing daemons 🌈

not me just listing options in alphabetical-ish order as the man page does. slay.

---

⚠️ WARNING ⚠️

okay listen, this is important and I'm not gonna sugarcoat it:

this man page is meant to be a quick reference for command line options. it is not the definitive document. the definitive document is the info file frr latest or the documentation up on the project website at <https://frrouting.org/>.

so if you're about to do something spicy with routing config, go read the real docs. this page is the snack, not the meal. 🫶

---

🩺 DIAGNOSTICS 🩺

where does the daemon yell into the void? pick your fighter, it may log:

• to standard output
• to a VTY
• to a log file
• through syslog to the system logs

also, FRR supports many debugging options — like, a lot. for the details, go check the Info file, the web docs, or the source itself. the source always has the tea. 💜

---

👀 SEE ALSO 👀

go read these next, they're all part of the same little family:

frr-zebra(8), vtysh(1), frr-ripd(8), frr-ripngd(8), frr-ospfd(8), frr-ospf6d(8), frr-bgpd(8), frr-isisd(8), frr-babeld(8), frr-nhrpd(8), frr-pimd(8), frr-pbrd(8), frr-ldpd(8), frr-eigrpd(8), frr-staticd(8), frr-fabricd(8), frr-vrrpd(8), mtracebis(8), and of course <https://frrouting.org/> 🌐

one for every protocol because FRR said "why choose" 💅

---

🐛 BUGS 🐛

FRR eats bugs for breakfast. iconic behavior honestly. if you've got food for the maintainers — meaning you found a bug and want to tell them about it — please email dev@lists.frrouting.org. they will absolutely devour your bug report. 🙈

---

📜 Copyright 📜

2017, FRR

---

aaaand that's the page, bestie!! 🎀 before you go: this was the latest version of the page, dated Sep 22, 2026, from the FRR manual. so if the date looks like it's from the future, no it doesn't, mind your business 💖 ok bye, go start some daemons, you got this 🦋✨