LDPD(8) BSD System Manager's Manual LDPD(8)NAME
ldpd -- Label Distribution Protocol Daemon
SYNOPSIS
ldpd [-DdfhW] [-c config_file] [-p port]
DESCRIPTION
ldpd is a utility used to automatically distribute labels between two MPLS LSRs almost conforming to RFC3036. Right now it is in BETA stage
and many features are not implemented or may not work. As a security measure you SHOULD filter the LDP well-known (646) TCP and UDP ports
using your favourite packet filter before starting ldpd. Also this is the current measure used to filter neighbours. You should see some
logs reported via syslog(3) interface.
You can increase the log verbosity using the -W and -D flags. Also you can telnet to the control port (default: 2626) and use this interface
in order to get informations about protocol, neighbours etc. but also to set runtime parameters. The required password is the same as the
root password.
ldpd computes existing routes and tries to match them on MPLS labels announced by other LDP peers. This means that ``normal'' routes will be
changed into tagged routes, and MPLS routing table will be populated. It will also announce its mappings to its peers. ldpd will listen on
a route socket and compute the necessary changes in order to change untagged routes into tagged routes. This means that one may use one's
favourite dynamic routing protocol daemon without modifications.
The options are as follows:
-c config_file Specifies a path to the config file. Default: /etc/ldpd.conf - see ldpd.conf(5) for configuration file format.
-D Enable debug mode.
-d Don't use route interception code.
-f Run in foreground. Use STDOUT for warning and debug messages.
-h Outputs supported flags.
-p port Changes the TCP control port (default: 2626).
-W Enable output of warning messages.
SEE ALSO
LDP Specification, RFC, 3036, January 2001.
LDP Applicability, RFC, 3037, January 2001.
HISTORY
The ldpd command appeared in NetBSD 6.0.
BUGS
ldpd supports only IPv4 and doesn't implement Path Vector and Hop Count TLVs.
BSD July 7, 2011 BSD
Check Out this Related Man Page
ramd(1M)ramd(1M)NAME
ramd - Route Administration Manager Daemon (RAMD) for IPv6
SYNOPSIS
config_file] trace_options] [trace_file]
DESCRIPTION
is a routing daemon that manages routing for IPv6. handles RIPng, BGP, and IS-IS routing protocols. and are referred to as routing dae-
mons.
can be configured using the configuration file Upon startup, reads the configuration file and spawns the routing daemons, if it is config-
ured. However, the command-line option trace_file is applicable only to
maintains a routing table in user space and synchronizes it with the HP-UX kernel routing table. periodically checks the kernel interface
table and the route table for any updates or changes. It notifies the corresponding daemons about the updates.
Options
supports the following command-line options:
Parses the configuration file for syntax errors and terminates exits with a status 0 if the configuration file contains no errors. If the
configuration file contains errors, exits with a non-zero value. prints the configuration file errors, if any, to the standard output.
Specifies that
runs as a normal process and not as a daemon process.
Parses the configuration file for syntax errors and terminates
It leaves a dump file, if the configuration file does not have any syntax errors.
Specifies an alternate configuration file to be used by
By default, uses
Specifies that
does not modify the kernel forwarding table.
Suppresses the
messages of and routing daemons. Using this option, can suppress the informational messages that are normally printed to the stan-
dard output, and log error messages through syslogd(1M). By default, errors are logged in
Specifies a comma-separated list of trace options to
be enabled during startup. A space cannot be entered between this option and its arguments.
This option can be used to trace events that occur before the configuration file is parsed, such as determining the interface con-
figuration and reading routes from the kernel.
See the ramd.conf(4) manpage for information on tracing and valid trace options.
The trace options, cannot be specified with the command-line option.
trace_file
Specifies the name of the file used by the daemon to log tracing information.
Signal Processing
The following signals are used to control
Specifies to reread the configuration file. reads the configuration file and reconfigures its policies. also checks if it must start
and stop the protocol daemons.
Specifies that the current state of
is written to
Graceful shutdown.
On receipt of attempts a graceful shutdown.
removes all protocol routes from the HP-UX 11i v1 kernel routing table on receiving Interface routes and static routes remain
with the retain option. can be used to terminate with all the routes intact. It may be necessary to repeat the once or twice
if delays its termination.
Toggle tracing.
If tracing is enabled, suspends tracing and closes the trace file. If tracing is disabled, opens the trace file and initiates
tracing. This is useful for moving trace files.
signal cannot be used, if does not enable tracing in the configuration file.
Checks for interface changes.
On receipt of rescans the kernel interface list for changes.
EXAMPLES
To use an alternate configuration file for instead of the default configuration file, invoke as follows:
To log tracing related information to the trace options and invoke as follows :
logs the trace information that is related to the configuration file and the kernel interface table, in the log file
AUTHOR
was developed by Future software Ltd.
SEE ALSO netstat(1), ifconfig(1M), ram_monitor(1M), rdc(1M), fork(2), ramd.conf(4).
ramd(1M)