An ospfv2 routing engine for use with quagga routing software.
ospfd [ -dhlv ] [ -f config-file ] [ -i pid-file ] [ -P port-number ] [ -A vty-address ] [ -u user ] [ -g group ]
ospfd is a routing component that works with the Quagga routing engine.
Options available for the ospfd command:
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/ospfd.conf.
-g, --group group
Specify the group to run as. Default is quagga.
A brief message.
-i, --pid_file pid-file
When ospfd starts its process identifier is written to pid-file. The init system uses the recorded PID to stop or restart ospfd. The likely default is /var/run/ospfd.pid.
-P, --vty_port port-number
Specify the port that the ospfd VTY will listen on. This defaults to 2604, as specified in /etc/services.
-A, --vty_addr vty-address
Specify the address that the ospfd VTY will listen on. Default is all interfaces.
-u, --user user
Specify the user to run as. Default is quagga.
Enable OSPF apiserver. Default is disabled.
Print the version and exit.
The default location of the ospfd binary.
The default location of the ospfd config file.
If the ospfd process is config'd to output logs to a file, then you will find this file in the directory where you started ospfd.
This man page is intended to be a quick reference for command line options. The definitive document is the Info file Quagga.
The ospfd process may log to standard output, to a VTY, to a log file, or through syslog to the system logs. ospfd supports many debugging options, see the Info file, or the source for details.
ospfd 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.