zebra man page

zebra — a routing manager for use with associated Quagga components.


zebra [ -bdhklrv ] [ -f config-file ] [ -i pid-file ] [ -P port-number ] [ -A vty-address ] [ -u user ] [ -g group ]


zebra is a routing manager that implements the zebra route engine. zebra supports RIPv1, RIPv2, RIPng, OSPF, OSPF6, IS-IS, BGP4+, and BGP4-.


Options available for the zebra command:

-b, --batch

Runs in batch mode, zebra parses its config and exits.

-d, --daemon

Runs in daemon mode, forking and exiting from tty.

-f, --config-file config-file

Specifies the config file to use for startup. If not specified this option will likely default to /usr/local/etc/zebra.conf.

-g, --group group

Specify the group to run as. Default is quagga.

-h, --help

A brief message.

-i, --pid_file pid-file

When zebra starts its process identifier is written to pid-file.  The init system uses the recorded PID to stop or restart zebra.  The likely default is /var/run/zebra.pid.

-k, --keep_kernel

On startup, don't delete self inserted routes.

-P, --vty_port port-number

Specify the port that the zebra VTY will listen on. This defaults to 2601, as specified in /etc/services.

-A, --vty_addr vty-address

Specify the address that the zebra VTY will listen on. Default is all interfaces.

-u, --user user

Specify the user to run as. Default is quagga.

-r, --retain

When the program terminates, retain routes added by zebra.

-s, --nl-bufsize netlink-buffer-size

Set netlink receive buffer size. There are cases where zebra daemon can't handle flood of netlink messages from kernel. If you ever see "recvmsg overrun" messages in zebra log, you are in trouble.

Solution is to increase receive buffer of netlink socket. Note that kernel < 2.6.14 doesn't allow to increase it over maximum value defined in /proc/sys/net/core/rmem_max. If you want to do it, you have to increase maximum before starting zebra.

Note that this affects Linux only.

-v, --version

Print the version and exit.



The default location of the zebra binary.


The default location of the zebra config file.


If the zebra process is config'd to output logs to a file, then you will find this file in the directory where you started zebra.


This man page is intended to be a quick reference for command line options. The definitive document is the Info file Quagga.


The zebra process may log to standard output, to a VTY, to a log file, or through syslog to the system logs. zebra supports many debugging options, see the Info file, or the source for details.

See Also

bgpd(8), ripd(8), ripngd(8), ospfd(8), ospf6d(8), isisd(8), vtysh(1)


zebra eats bugs for breakfast. If you have food for the maintainers try http://bugzilla.quagga.net


See http://www.zebra.org and http://www.quagga.net or the Info file for an accurate list of authors.

Referenced By

babeld(8), bgpd(8), isisd(8), ospf6d(8), ospfd(8), ripd(8), ripngd(8), vtysh(1), zebra_selinux(8).

25 November 2004 Zebra daemon Version 0.97.3