FRR-RIPD(8)

📦
version 10.7.1 · 23 versions
, in ubuntu stonking

👑 FRR-RIPD — the ripd(8) glow-up 💖

okay bestie, sit down, grab your boba, because we're talking about frr-ripd — a RIP routing engine for use with FRRouting — and honestly? she's that girl. this page is the manual page for section 8, and it's giving "daemon with main character energy." let's get into it ✨

✨ NAME ✨

frr-ripd — a RIP routing engine for use with FRRouting. periodt.

🌸 SYNOPSIS 🌸

ripd [-h] [-v]

ripd [-d|-t|-dt] [-C] [-f config-file] [-i pid-file] [-z zclient-path]
[-u user] [-g group] [-A vty-addr] [-P vty-port] [-M module[:options]]
[-N pathspace] [--vty_socket vty-path] [--moduledir module-path]

🦋 DESCRIPTION 🦋

ripd is a routing component that works with the FRRouting routing engine. she does RIP things. she's part of the squad. that's the vibe 💅

🎀 OPTIONS 🎀

OPTIONS available for the ripd command — yes, all of them, we're not skipping a single one, bestie ✨

🙈 HELP AND VERSION 🙈

  • -h, --help — prints a short description of the daemon's command line options. your "what even is this" button.
  • -v, --version — prints version and build information for the daemon. the receipts, the credentials, the whole résumé 🔥
okay so important: both of these options inhibit normal operation and will immediately exit. like, she's not sticking around to chat, she gives you the answer and leaves. iconic behavior honestly.

🧚 PROCESS CONTROL 🧚

These options control background operation — aka "do you want me loud and in your face, or do you want me lurking in the shadows":

  • -d, --daemon — launches the process in background/daemon mode, forking and detaching from the terminal. she's going off the grid, but like, responsibly.

The parent process will delay its exit until the daemon/child has finished its initialization and has entered its main loop. This is important for zebra startup because the other daemons will attempt to connect to zebra. A return from zebra -d guarantees its readiness to accept these connections. (translation: she doesn't ghost until she's actually ready to receive texts 💌)

  • -t, --terminal — opens an interactive VTY session on the terminal, allowing for both state and configuration operations. Note that the terminal starts operating after startup has completed and the configuration file has been loaded. patience, bestie, she's getting ready 🎀

The process will exit when end of file is detected on the terminal. It is possible to daemonize a process started with -t (but without -d) by sending SIGQUIT to the process (normally mapped to a ^ keypress.)

The combination of --daemon and --terminal will delay the daemon from going into background until the terminal session ends (by end of file.) no cap.

If the process receives SIGINT (e.g. a Ctrl+C keypress) in this mode, it will exit instead of daemonizing.

It is safe to suspend (SIGTSTP / Ctrl+Z) the terminal session opened by the previous two options; this will only stop the terminal but not the protocol daemon itself (which runs in a separate second process.) so pause her, she's still working behind the scenes 💅

🌈 CONFIGURATION AND PATHS 🌈

The following options control configuration and file system locations for frr processes — the "where do you live and what do you wear" section:

  • -f, --config_file config-file — specify a configuration file to be used instead of the default /etc/frr/<daemon>.conf file.
Note that the daemon will attempt to write to this file if the write file command is issued on its VTY interface or through vtysh. she edits her own diary, okay? mind your business 😭
  • -C, --dryrun — load the configuration file and check its validity, then exit. a vibe check, then dipping.
  • -i, --pid_file pid-file — output a pid file to a location other than the default /var/run/frr/<daemon>.pid.
  • -z, --socket zclient-path — override the path of the ZAPI socket used to communicate between zebra and the various protocol daemons. The default is /var/run/frr/zserv.api. The value of this option must be the same across all daemons. everyone has to be in the same group chat, fr fr.
  • -N, --pathspace pathspace — insert pathspace into all default paths, changing the defaults to:
/etc/frr/pathspace/<daemon>.conf
/var/run/frr/pathspace/<daemon>.pid
/var/run/frr/pathspace/<daemon>.vty
/var/run/frr/pathspace/zserv.api

The . and / characters will not be accepted in pathspace, but the empty string will be accepted. (yes, empty string is valid, she contains multitudes 💜)

Note that this only changes the respective defaults — it has no effect on the respective path if the -f, -i, -z or --vty_socket options are used. don't come for her defaults if you literally just overrode them.

The purpose of this option is to easily group all file system related bits together for running multiple fully-separate "logical routers" on a system, particularly with Linux network namespaces. Groups of daemons running with distinct pathspace values will be completely unaware of each other and not interact in any way. parallel universes, bestie, they literally don't know each other exist 🦋

This option does not do any system setup (like network namespaces.) This must be done by the user, for example by running:

ip netns exec namespace <daemon> -N namespace

💜 PROCESS CREDENTIALS 💜

  • -u, --user user — (default: frr)
  • -g, --group group — (default: frr)

Change the user/group which the daemon will switch to.

  • -S, --skip_runas — skip setting the process effective user and group.

Note that there is an additional group, frrvty, which controls group ownership of the VTY sockets. The name of this group cannot currently be changed, and user must be a member of this group. no exceptions, bestie, it's the rules 💅

⭐ VTY SETUP ⭐

These following options control the daemon's VTY (interactive command line) interface. The interface is available over TCP, using the telnet protocol, as well as through the vtysh frontend. yes, she has multiple personalities and they all slay.

  • -A, --vty_addr vty-addr — specify an IP/IPv6 address to bind the TCP VTY interface to. It is generally recommended to specify ::1 or 127.0.0.1. For reasons of backwards compatibility, the default is to listen on all interfaces. (she's an oversharer by default, ok?? set your boundaries with ::1 or 127.0.0.1 🫶)
  • -P, --vty_port vty-port — override the daemon's default TCP VTY port (each daemon has a different default value upwards of 2600, listed below.) Specifying 0 disables the TCP VTY interface. quiet mode, love that for her.

Default ports are::

zebra           2601
ripd            2602
ripngd          2603
ospfd           2604
bgpd            2605
ospf6d          2606
isisd           2608
babeld          2609
nhrpd           2610
pimd            2611
ldpd            2612
eigrpd          2613
pbrd            2615
staticd         2616
bfdd            2617
fabricd         2618
vrrpd           2619

Port 2607 is used for ospfd's Opaque LSA API. (2607 is spoken for, don't even try it 💀)

  • --vty_socket vty-path — overrides the directory used for the <daemon>.vty sockets. vtysh connects to these sockets in order to access each daemon's VTY. Default: /var/run/frr[/<pathspace>]
NB: Unlike the other options, this option specifies a directory, not a full path. read it twice, bestie, it matters.

This option is primarily used by the SNAP packaging system, its semantics may change. It should not be necessary in most other scenarios. niche but valid 💅

🌸 MODULE LOADING 🌸

frr supports optional dynamically loadable modules, although these can only be loaded at startup. The set of available modules may vary across distributions and packages, and modules may be available for installation as separate packages. mix and match, collect them all, pokémon energy ✨

  • -M, --module module[:options] — load a module named module, optionally passing options to it.

If there is a / character in module, the value is assumed to be a pathname to a module.

If there is no / character, the module directory (see next option) is searched first for a module named "<daemon>_<module>.so", then for "<module>.so". This allows for a module to exist in variations appropriate for particular daemons, e.g. zebra_snmp and bgp_snmp, with the correct one selected by -M snmp. she picks the right fit for the right occasion, it's called range 🎀

The meaning of options is specific to the module being loaded. Most modules currently ignore it. (they're not ignoring you on purpose, they're just busy 😭)

Modules are loaded in the order as listed on the command line. This is not generally relevant.

  • --moduledir module-path — look for modules in the module-path directory instead of the default /usr/lib/frr/modules. (This path is not affected by the -N option.) she does her own thing.

The list of loaded modules can be inspected at runtime with the show modules VTY command. go check on them, they'd love that 🫶

💖 FILES 💖

  • /usr/lib/frr/ripd — the default location of the ripd binary. her home address.
  • /etc/frr/ripd.conf — the default location of the ripd config file. her wardrobe.
  • $(PWD)/ripd.log — if the ripd process is configured to output logs to a file, then you will find this file in the directory where you started ripd. her diary, but only when she's in journaling mode.

🔥 WARNING 🔥

This man page is intended to be a quick reference for command line options. The definitive document is the info file frr latest or the documentation available on the project website at https://frrouting.org/.

bestie, this is the trailer, not the whole movie. for the full lore, go read the info file. no cap.

🩺 DIAGNOSTICS 🩺

The daemon may log to standard output, to a VTY, to a log file, or through syslog to the system logs. FRR supports many debugging options, see the Info file, web docs or source for details. she communicates in many love languages 💅

👑 SEE ALSO 👑

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) https://frrouting.org/

the whole friend group. go say hi 🦋

🐛 BUGS 🐛

FRR eats bugs for breakfast. If you have food for the maintainers, please email <<dev@lists.frrouting.org>>. genuinely, they want your bug reports, it's not a trap 🙈

2017, FRR

okay and for the cute sign-off bestie: this whole thing is from the latest release, dated Sep 22, 2026, filed under FRR-RIPD(8) 🎀 that's the page, that's the version, that's the date — slay, you read the whole thing, I'm so proud of you, go config something iconic 💅✨

📦 where this page comes from