Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

miredo-server(8) [debian man page]

MIREDO-SERVER(8)					      System Manager's Manual						  MIREDO-SERVER(8)

NAME
miredo-server - Teredo server for Unix SYNOPSIS
miredo-server [-c config_file] [-f] [-u user] [server_name] DESCRIPTON
Miredo-server is an Unix daemon program which implements a Teredo server as specified by the "Teredo: Tunneling IPv6 over UDP through NATs" Internet proposed standard (RFC 4380). A Teredo server is required for Teredo clients to setup their IPv6 connectivity through Teredo. A Teredo server must have two global static subsequent IPv4 addresses. It receives packets from Teredo clients and Teredo relays on UDP port 3544. OPTIONS
-c config_file or --config config_file Specify an alternate configuration file for Miredo instead of the default, /etc/miredo/miredo-server.conf. -f or --foreground Do not detach from the console. Run the program in the foreground. -h or --help Display some help and exit. -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. SECURITY
miredo-server requires root privileges to create open a raw IPv6 socket that is used to emit ICMPv6 Echo Request packets. Once its initial- ization is complete, it will setgid, chroot into an empty directory and ultimately setuid (see option -u), so as to decrease the system's exposure to potential security issues. SIGNALS
SIGHUP Force a reload of the daemon. SIGINT, SIGTERM Shutdown the daemon. SIGUSR1, SIGUSR2 Do nothing, might be used in future versions. FILES
/etc/miredo/miredo-server.conf The default configuration file. /var/run/miredo-server.pid The process-id file. SEE ALSO
miredo-server.conf(5), miredo(8), ipv6(7) AUTHOR
Remi Denis-Courmont <remi at remlab dot net> http://www.remlab.net/miredo/ miredo February 2008 MIREDO-SERVER(8)

Check Out this Related 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)
Man Page