rdnssd(8) [debian man page]

RDNSSD(8)						      System Manager's Manual							 RDNSSD(8)

NAME

       rdnssd - IPv6 Recursive DNS Server discovery Daemon

SYNOPSIS

       rdnssd [-f] [-H merge-hook] [-r resolv-file] [-p pidfile] [-u username]

DESCRIPTON

       rdnssd  is a daemon program providing client-side support for DNS configuration using the Recursive DNS Server (RDNSS) option, as described
       in RFC 5006.  Its purpose is to supply IPv6 DNS resolvers through stateless autoconfiguration, carried by Router Advertisements.

       rdnssd parses RDNSS options and keeps track of resolvers to write nameservers entries to a resolv.conf(5) configuration file.  By  default,
       it  writes its own separate file, and may call an external hook to merge it with the main /etc/resolv.conf. This is aimed at easing coexis-
       tence with concurrent daemons, especially IPv4 ones, updating /etc/resolv.conf too.

       On Linux, since version 2.6.24, rdnssd takes advantage of a new netlink interface, forwarding RDNSS options  validated  by  the	kernel	to
       userland.  Otherwise, it merely listens to all ICMPv6 traffic through a raw socket.

OPTIONS

       -f or --foreground
	      Do not detach from the console. Run the program in the foreground.

       -H merge-hook or --merge-hook merge-hook
	      Execute this hook whenever resolv.conf is updated. If this option is not specified, then no hook will be called.

       -h or --help
	      Display some help and exit.

       -p pidfile or --pidfile pidfile
	      Override the location of the pidfile.

       -r resolv-file or --resolv-file resolv-file
	      Set the path to the generated resolv.conf file.

       -u username or --user username
	      Override the user that the program will run as. By default, it runs as nobody.

       -V or --version
	      Display program version and license and exit.

FILES

       /etc/rdnssd/merge-hook
	      A basic merge hook shipped with rdnssd, to be called with the -H option.

       /var/run/rdnssd/resolv.conf
	      The default resolv.conf(5) file that rdnssd writes its configuration to.

       /var/run/rdnssd.pid
	      The process-id file.

BUGS

       rdnssd  does  not  keep track of the lifetimes of the routers associated with some DNS resolvers, whereas it should to strictly comply with
       RFC 5006.

       When rdnssd uses a raw socket instead of the netlink kernel interface, it does not validate received Neighbor Discovery traffic in any way.
       For  example,  it  will always consider Router Advertisement packets, whereas it should not if the host is configured as a router. When the
       netlink interface is used, such validation is done by the kernel.

SEE ALSO

       resolv.conf(5), rdisc6(8), ipv6(7)

AUTHOR

       Pierre Ynard <linkfanel at yahoo.fr>

       $Id: rdnssd.8-in 575 2007-12-29 21:55:43Z linkfanel $

       http://www.remlab.net/ndisc6/

rdnssd					       $Date: 2007-12-29 23:55:43 +0200 (Sat, 29 Dec 2007) $					 RDNSSD(8)

DHCPCD-RUN-HOOKS(8)					    BSD System Manager's Manual 				       DHCPCD-RUN-HOOKS(8)

NAME

     dhcpcd-run-hooks -- DHCP client configuration script

DESCRIPTION

     dhcpcd-run-hooks is used by dhcpcd(8) to run any system and user defined hook scripts.  System hook scripts are found in
     /lib/dhcpcd/dhcpcd-hooks and the user defined hooks are /etc/dhcpcd.enter-hook.  and /etc/dhcpcd.exit-hook.  The default install supplies
     hook scripts for configuring /etc/resolv.conf and the hostname.  Your distribution may have included other hook scripts to say configure ntp
     or ypbind.  A test hook is also supplied that simply echos the dhcp variables to the console from DISCOVER message.

     Each time dhcpcd-run-hooks is invoked, $interface is set to the interface that dhcpcd is run on and $reason is to the reason why
     dhcpcd-run-hooks was invoked.  DHCP information to be configured is held in variables starting with the word new_ and old DHCP information to
     be removed is held in variables starting with the word old_.  dhcpcd can display the full list of variables it knows how about by using the
     -V, --variables argument.

     Here's a list of reasons why dhcpcd-run-hooks could be invoked:

     PREINIT	   dhcpcd is starting up and any pre-initialisation should be done.

     CARRIER	   dhcpcd has detected the carrier is up.  This is generally just a notification and no action need be taken.

     INFORM	   dhcpcd informed a DHCP server about it's address and obtained other configuration details.

     BOUND	   dhcpcd obtained a new lease from a DHCP server.

     RENEW	   dhcpcd renewed it's lease.

     REBIND	   dhcpcd has rebound to a new DHCP server.

     REBOOT	   dhcpcd successfully requested a lease from a DHCP server.

     IPV4LL	   dhcpcd failed to contact any DHCP servers but did obtain an IPV4LL address.

     STATIC	   dhcpcd has been configured with a static configuration which has not been obtained from a DHCP server.

     3RDPARTY	   dhcpcd is monitoring the interface for a 3rd party to give it an IP address.

     TIMEOUT	   dhcpcd failed to contact any DHCP servers but was able to use an old lease.

     EXPIRE	   dhcpcd's lease or state expired and it failed to obtain a new one.

     RELEASE	   dhcpcd's lease was released back to the DHCP server for re-use.

     NAK	   dhcpcd received a NAK from the DHCP server.	This should be treated as EXPIRE.

     NOCARRIER	   dhcpcd lost the carrier.  The cable may have been unplugged or association to the wireless point lost.

     FAIL	   dhcpcd failed to operate on the interface.  This normally happens when dhcpcd does not support the raw interface, which means
		   it cannot work as a DHCP or ZeroConf client.  Static configuration and DHCP INFORM is still allowed.

     STOP	   dhcpcd stopped running on the interface.

     DUMP	   dhcpcd has been asked to dump the last lease for the interface.

     TEST	   dhcpcd received an OFFER from a DHCP server but will not configure the interface.  This is primarily used to test the variables
		   are filled correctly for the script to process them.

     ROUTERADVERT  dhcpcd has received an IPv6 Router Advertisment, or one has expired.

FILES

     When dhcpcd-run-hooks runs, it loads /etc/dhcpcd.enter-hook and any scripts found in /lib/dhcpcd/dhcpcd-hooks in a lexical order and then
     finally /etc/dhcpcd.exit-hook

SEE ALSO

     dhcpcd(8)

AUTHORS

     Roy Marples <roy@marples.name>

BUGS

     Please report them to
	   http://roy.marples.name/projects/dhcpcd

SECURITY CONSIDERATIONS

     Little validation of DHCP options is done in dhcpcd itself.  Instead, it is up to the hooks to handle any validation needed.  To this end,
     some helper functions are provided, such as valid_domainname as used by the 20-resolv.conf hook to ensure that the hostname is not set to an
     invalid value.  valid_path is also provided, but is currently unused by a stock hook script.

BSD
								  March 19, 2012							       BSD