NAME

bfdd-beacon - a Bidirectional Forwarding Detection (BFD) beacon daemon.

SYNOPSIS

bfdd-beacon [ options ]

DESCRIPTION

bfdd-beacon is software implementation of the Bidirectional Forwarding Detection (BFD) protocol. When bfdd-beacon is running commands can be issued to the beacon using the bfdd-control(8) utility. It is part of the OpenBFDD package.

OPTIONS

The options parameter can be one or more of the following:

--version

This will print the current version and exit.

--tee

All logging will be sent to stdout in addition to the normal syslog or log file. This is the default in debug builds run with the --nofork option. This option is only applied if used with the --nofork option.

--notee

Logging will not be sent to stdout. This is the default for release builds.

--nofork

Prevents the beacon from running as a daemon. This is useful for debugging.

--control=ip:port

Adds a communication channel to use for communicating with bfdd-beacon(8). ip may be an IPv4 or Ipv6 address. A port must be supplied. This option may appear multiple times, to create multiple control channels. If no --control option is supplied, then two default control channels are created on 127.0.0.1. When specifying an IPv6 ip address, the address must be contained in brackets, to allow for a port specification. For example [::1]:10001. See the PARAMETERS section for more details on specifying an ip address.

--listen=ip

Adds an address on which to listen for new incoming BFD connections. ip may be an IPv4 or Ipv6 address. The IPv4 address of 0.0.0.0.0, or the IPv6 address :: may be used to listen on all available IPv4 or IPv6 interfaces, respectively. This option may appear multiple times, to listen on multiple addresses. If no --listen option is supplied, then bfdd-beacon will listen on all available IPv4 and IPv6 addresses. See the PARAMETERS section for more details on specifying an ip address.

PARAMETERS

Some of the parameters used in the COMMANDS section require some additional explanation.

ip

This parameter describes an ip address. An IPv4 or IPv6 address may be supplied. An IPv4 address muse use dotted quad notation, in the form: "ddd.ddd.ddd.ddd" An IPv6 address can use full notation, in the form: "hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh" or shorthand notation, such as: "hhhh:hhhh::hhhh". Dotted-quad notation may be used for Ipv6 addresses, to specify the final 32 bits. For example ::ffff:192.0.2.128 is equivalent to ::ffff:c000:0280. Link-local addresses must also be followed by an interface name, using the form: "hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh%ifname", where ifname is the name of the interface to which the link local address applies. An interface may only be specified for link-local addresses. Of course, shorthand notation may also be used with link local addresses.

CONTROL

When bfdd-beacon is running commands can be issued to the beacon using the bfdd-control(8) utility. See bfdd-control(8) documentation for more details.

LOGGING

Currently log messages go to syslog. The --tee command can be used to also send log messages to stdout. The identity "bfdd-beacon" is used for all syslog logging. Logging is fully configurable. See bfdd-control(8) documentation for more details.

NOTES

when bfdd-beacon is first started it will not accept any connections. This allows bfdd-beacon to be configured using the bfdd-control(8) utility before any sessions begin. The bfdd-control(8) utility can then be used to start an active session, or to enable passive sessions.

The current implementation of the BFD protocol was tested specifically with the Juniper router's BFD (JUNOS 8.5). Demand mode is not currently supported. Echo mode is not currently supported. Authentication is not supported.

BUGS

No known bugs at this time.

SEE ALSO

bfdd-control(8)

AUTHOR

Jake Montgomery for Dynamic Network Services, Inc.

COPYRIGHT

Copyright (c) 2010-2014, Dynamic Network Services, Inc.