mip6.conf(4)						     Kernel Interfaces Manual						      mip6.conf(4)

NAME

       mip6.conf - Mobile IPv6 Streams Module (mip6mod) configuration file

SYNOPSIS

       (default configuration file)

DESCRIPTION

       is  the	configuration  file for mip6mod(7), the Mobile IPv6 Streams Module.  The Mobile IPv6 administrative tool, mip6admin(1M), reads the
       Mobile IPv6 configuration file and configures The file contains a number of parameters, all of which have default values.  The Mobile  IPv6
       configuration  file does not determine if a system should operate as a Home Agent. See rtradvd(1M) and rtradvd.conf(4) for more information
       about configuring Home Agents.

       You can use the Mobile IPv6 configuration tool, mip6config(1M), to create, edit, or verify Mobile IPv6 configuration files.

   Syntax
       The basic structure of this configuration file consists of a series of lines, each line providing the value for one configuration parameter
       in the form of

       The  '#' character comments out the rest of the line. The set of legal choices for parameter_value depends greatly on which parameter-label
       is being assigned. The restrictions are included in the parameter-label descriptions below. Repeating a parameter-label in  the	configura-
       tion file is illegal.

   Parameter Labels and Values
       The logging level. Note that
		      also  logs  messages that are logged at higher levels. For example, for a logging level of also logs messages for levels and
		      log_level must be one of the following (from highest to lowest levels):

		      Catastrophic conditions that should be corrected immediately, for example,
				exceeding memory space.

		      Error conditions, for example, binding cache full.

		      Warnings, for example, dynamic configuration changes.

		      Informative messages, for example, creation of a binding.

		      Messages that are useful for debugging and troubleshooting purposes, for
				example, addition of mobility route.

		      The default is

       The number of mip6mod instances to start for processing messages with
		      Mobility Header.	num_instances must be in the range [1..N], where N is the number of processors on the system.  The  number
		      of processor on the system can be determined by various commands, for example,

		      The default is

       The maximum number of Home Agent and Correspondent Node binding cache entries
		      can  support.   max_binding_cache_entries  must  be an integer in the range [1..100000] and must be greater than or equal to
		      max_home_bindings.

		      The default is or max_home_bindings, whichever is higher.

       The maximum number of Home Agent binding cache entries
		      can support.  max_home_bindings must be an integer in the range [1..100000] and must be less  than  or  equal  to  max_bind-
		      ing_cache_entries.

		      The default is or max_binding_cache_entries, whichever is lower.

       The maximum lifetime (in seconds) allocated to binding cache entries.
		      max_binding_lifetime must be an integer in the range [1..262140].

		      The default is

       The advice time (in seconds) in the Binding Refresh Advice option.
		      includes	the  Binding  Refresh Advice option in the Binding Acknowledgement message only if is the Home Agent to the Mobile
		      Node. The Binding Refresh Advice option advises the Mobile Node how many seconds prior to the expiration of the current reg-
		      istration  that it should re-register.  binding_refresh_advice_interval must be an integer in the range [0..262140] and must
		      be less than max_binding_lifetime.  The value disables the inclusion of the Binding Refresh Advice  option  in  the  Binding
		      Acknowledgement message.

		      The default is

       The number of seconds prior to the expiration of the binding when
		      sends  the  Binding  Refresh  Request message to the Mobile Node.  sends the Binding Refresh Request message only if it is a
		      Correspondent Node to the Mobile Node. The Binding Refresh Request message prompts the Mobile Node to re-register as soon as
		      possible.   binding_refresh_request_threshold  must  be  an  integer  in	the range [0..420] and must be less than max_bind-
		      ing_lifetime.  A value of disables the sending of the Binding Refresh Request message.

		      The default is

       The number of error messages sent before error message rate is controlled.
		      error_rate_limit_threshold must be an integer in the range [1..32].

		      The default is

       The maximum rate at which error messages are sent when error rate is
		      controlled. Use an integer in the range [10..9990]. Note that smaller values are faster rates, and the  value  will  be  the
		      shortest duration (in milliseconds) between error messages.  max_error_rate must be faster than min_error_limit.

		      The default is however, if min_error_rate is faster than 100, the default is 10 milliseconds faster than min_error_rate.

       The minimum rate at which error messages are sent when error rate is
		      controlled.  Use	an  integer in the range [20..10000]. Note that smaller values are faster rates, and the value will be the
		      longest duration (in milliseconds) between error messages.  min_error_rate must be slower than max_error_rate.

		      The default is however, if max_error_rate is slower than 1000, the default is 10 milliseconds slower than max_error_rate.

FILES

       default configuration file.

       Startup configuration file.

       MUX ID file.

SEE ALSO

       top(1), mip6admin(1M), mip6config(1M), rtradvd(1M), rtradvd.conf(4), mip6mod(7).

       IETF Document	   Mobility Support in IPv6
       IETF Document	   Using IPsec to Protect Mobile IPv6 Signaling between Mobile Nodes and Home Agents

																      mip6.conf(4)