ip6rtrd.conf man page on OSF1

Man page or keyword search:  
man Server   12896 pages
apropos Keyword Search (all sections)
Output format
OSF1 logo
[printable version]

ip6rtrd.conf(4)						       ip6rtrd.conf(4)

NAME
       ip6rtrd.conf - IPv6 router daemon (ip6rtrd) configuration file

DESCRIPTION
       The  ip6rtrd.conf  file contains configuration information that is read
       by the ip6rtrd daemon at initialization time. This file contains state‐
       ments  that control information sent in router advertisements and RIPng
       messages.

       The ip6rtrd.conf file  consists	of  structured	information  for  each
       interface in the following format: interface interface-name {
	  # interface keyword-value pairs, one per line
	  Prefix prefix/length {
	      # prefix keyword-value pairs, one per line
	  }
	  Address address {
	      # address keyword-value pairs, one per line
	  } }

       Comments	 begin with the number sign (#) and continue to the end of the
       line.

   Basic Interface Keywords
       The following basic keywords are defined in RFC 2461  for  IPv6	opera‐
       tion:  Specifies	 the  value to be placed in the Cur Hop Limit field in
       the Router Advertisement messages sent  by  the	router.	 The  value  0
       (zero)  means  unspecified  (by this router). Valid values are any non-
       negative integer. The default is 0.  Specifies a time, in seconds, that
       is  placed  in  the  Router Lifetime field in the Router Advertisement.
       Valid values are between 0 or MaxRtrAdvInterval	and  9000,  inclusive.
       The default is 1800 seconds.  Specifies a non-negative integer value to
       be placed in MTU options sent by the router. The default is 0.  Enables
       (1)  or disables (0) the setting of a flag in the "Managed address con‐
       figuration" flag field in the Router Advertisement. The default	is  0.
       Enables	(1) or disables (0) the setting of a flag in the "Other state‐
       ful configuration" flag field in the Router Advertisement. The  default
       is  0.  Specifies a time, in milliseconds, that is placed in the Reach‐
       able Time field in Router  Advertisement	 messages.  Valid  values  are
       between 0 and 3,600,000 (1 hour), inclusive. The default is 0 millisec‐
       onds.  Specifies a non-negative integer	value  to  be  placed  in  the
       Retrans	Timer  field  in  the  Router  Advertisement. The default is 0
       (zero).	Enables (yes) or disables (no) the sending of periodic	Router
       Advertisements  and  responding to Router Solicitations. The default is
       yes.  Specifies the maximum time, in  seconds,  between	sending	 unso‐
       licited	multicast Router Advertisements from the interface. Valid val‐
       ues are between 4 and 1800 seconds, inclusive. The default is 600  sec‐
       onds.   Specifies  the  minimum time, in seconds, between sending unso‐
       licited multicast Router Advertisements from the interface. Valid  val‐
       ues  are between 3 and .75 * MaxRtrAdvInterval. The default is 200 sec‐
       onds.

   Additional Interface Keywords
       The following additional interface keywords are accepted: Enables (yes)
       or disables (no) the sending of the interface link-layer address option
       in outgoing router advertisements. The default is yes.	Enables	 (yes)
       or  disables (no) the sending of site local prefixes in outgoing router
       advertisements. The default is no.  Enables (1)	or  disables  (0)  the
       Poisoned	 Reverse algorithm as specified in RFC 2080. The default is 1.
       Enables (yes) or disables (no) participation in RIPng on the interface.
       If enabled, RIPng updates are sent on the interface, and received RIPng
       updates are processed as defined in RFC 2080. You  cannot  specify  yes
       for  automatic tunnels (the tun0 interface). The default is yes (except
       for tun0).  Enables (1) or disables (0) the Split Horizon algorithm  as
       specified in RFC 2080. The default is 1.

   Mobility Management Keywords
       For mobility management, the following interface keywords are accepted:
       Enables (1) or disables (0) the setting of a flag in the	 "Home	Agent"
       flag field in the Router Advertisement, which indicates that the router
       sending this Router Advertisement is also functioning as a Mobile  IPv6
       home  agent  on this link. The default is 0.  Enables (yes) or disables
       (no) the processing of Dynamic Home  Agent  Address  Discovery  Request
       messages.   The	default	 is  yes.  Specifies the maximum time, in mil‐
       liseconds, allowed between sending unsolicited multicast Router	Adver‐
       tisements  from	the  interface.	 The range of valid values are from 70
       milliseconds (.07 seconds) to  1500  milliseconds  (1.5	seconds).  The
       default is 0.  Specifies the minimum time allowed between sending unso‐
       licited multicast Router Advertisements from  the  interface,  in  mil‐
       liseconds.  The range of valid values is from 30 milliseconds (.03 sec‐
       onds) to .75 * MaxRtrAdvIntervalMsec. The default is 0.	Enables	 (yes)
       or disables (no) the processing of Mobile Prefix Solicitation messages.
       The default is yes.  Enables (yes) or disables (no) the sending	of  an
       Advertisement  Interval	option	in  the outoing Router Advertisements,
       which indicates the interval at which the sending  router  sends	 unso‐
       licited multicast Router Advertisements.	 The default is no.

       For  example,  to  support  mobility  and specify a maximum and minimum
       Router Advertisement (RA) interval of .2 to .5 seconds, a typical  con‐
       figuration would specify the following: interface interface-name {
	  MinRtrAdvInterval 0
	  MinRtrAdvIntervalMsec 200
	  MaxRtrAdvInterval 1
	  MaxRtrAdvIntervalMsec 500 }

   Address Prefix Information
       Each  address  prefix to be configured on the interface must be defined
       within a prefix block that begins with the keyword Prefix  followed  by
       the  prefix  and	 length (separated by a slash (/)) and optionally fol‐
       lowed by an additional address prefix  information  block  of  keyword-
       value pairs.

       The  following  address	prefix	keywords and values are defined in RFC
       2461: Enables (1) or disables (0) the setting of	 the  Autonomous  Flag
       field  in the Prefix Information option. The default is 1.  Enables (1)
       or disables (0) the setting of  the  on-link  flag  field  in  outgoing
       router advertisements. The default is 1.	 Specifies the preferred life‐
       time of the address prefix, in seconds, to be placed in outgoing router
       advertisements.	The default is 604800 seconds, or 7 days.  Enables (1)
       or disables (0) the setting of the Router Flag field in outgoing router
       advertisements.	This  indicates	 that the Prefix field, in addition to
       advertising the	indicated  prefix,  contains  a	 complete  IP  address
       assigned	 to  the  sending router. This keyword and value is defined in
       draft-ietf-mobileip-ipv6-24.txt. The default is 0.  Specifies the valid
       lifetime	 of  the  address prefix, in seconds, to be placed in outgoing
       router advertisements. The default is 2592000 seconds, or 30 days.

       The following address prefix keywords and values	 are  defined  in  RFC
       2080:  Specifies	 a  value  that represents the total cost of getting a
       datagram from the router to a destination. Valid values are  between  1
       and  16,	 inclusive.  The  default  is  1.  Specifies a integer that is
       assigned to a route and must  be	 preserved  and	 readvertised  with  a
       route. The default is 0.

       In addition, you can specify the following address prefix keywords: The
       ip6rtrd daemon will configure the advertised prefix on the interface if
       ConfigureThisPrefix  is	specified and set to yes, or if ConfigureThis‐
       Prefix is not specified and AdvAutonomousFlag is set to 1.

	      The prefix is not auto-configured in all other cases. Valid val‐
	      ues  are	yes and no. The default action is the action specified
	      by AdvAutonomousFlag.  Specifies an IPv6 address to  use	as  an
	      off-link	route  to a gateway. You can use this mechanism to set
	      up default routes.  Enables (yes) or disables (no) this  address
	      prefix  as  one  for which the system will offer Home Agent ser‐
	      vices. The default is no.	 Enables (yes) or  disables  (no)  the
	      sending  of  the	address	 prefix in routing advertisements. The
	      default is yes.

   Address Information
       Each address to be configured on the interface must be defined within a
       address block that begins with the keyword Address followed by the IPv6
       address and optionally followed by an  additional  address  information
       block  of  keyword-value	 pairs.	 The address value is the 128-bit IPv6
       address, as follows: x:x:x:x:x:x:x:x In this  format,  each  x  is  the
       hexadecimal  value  of  a  16-bit piece of the address. An IPv6 address
       typically consists of a 64-bit prefix followed by  a  64-bit  interface
       identifier.

       You  can	 specify the following address keywords and values: Configures
       (yes) or unconfigures (no) the specified address as an anycast address.
       The default is no.  Configures (yes) or unconfigures (no) the specified
       address on the interface.  The  default	is  yes.   Specifies  an  IPv6
       address	to use as an off-link route to a host. You can use this mecha‐
       nism to set up host routes.

       The following address keywords and values  are  defined	in  RFC	 2080:
       Specifies  a value that represents the total cost of getting a datagram
       from the router to a destination. Valid values are between  1  and  16,
       inclusive. The default is 1.  Specifies a integer that is assigned to a
       route and must be preserved and readvertised with a route. The  default
       is 0.

RELATED INFORMATION
       Daemons: ip6rtrd(8).

       RFC 2461, Neighbor Discovery for IP version 6 (IPv6), Narten, T., Nord‐
       mark, E., Simpson W. A. December 1998

       RFC 2462,  IPv6	Stateless  Address  Autoconfiguration,	Thompson,  S.,
       Narten, T. December 1998

       RFC 2080, RIPng for IPv6, Malkin, G., Minnear, R. January 1997.

       draft-ietf-mobileip-ipv6-24.txt,	 Mobility  Support  in	IPv6, Johnson,
       David B., Perkins, Charles. February 2003 delim off

							       ip6rtrd.conf(4)
[top]
                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 
More information is available in HTML format for server OSF1

List of man pages available for OSF1

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net