mip6mod(7) [hpux man page]
mip6mod(7) Miscellaneous Information Manual mip6mod(7) NAME
mip6mod - Mobile IPv6 STREAMS Module SYNOPSIS
Use the mip6admin utility to start, stop, configure, and manage (see for details). User applications should not use directly. DESCRIPTION
a kernel-resident STREAMS module for Mobile IPv6, implements the Correspondent Node and Home Agent functionality. The STREAMS moudle is responsible for processing and generating all Mobile IPv6 Mobility Header messages: Binding Update (BU), Binding Acknowledgement (BA), Binding Refresh Request (BRR), Binding Error (BE), Home Test Init (HoTI), Care-of Test Init (CoTI), Home Test (HoT), Care-of Test (CoT). The following Mobile IPv6 ICMPv6 messages are handled by the IPv6 Router Advertisement Daemon, Mobile Prefix Solicitation/Advertisement (MPS/MPA), Dynamic Home Agent Discovery Request/Reply (DHAAD Request/Reply). When the system is configured as a Correspondent Node, supports Route Optimization using the Return Routability Procedure. During the Return Routability Procedure, the Correspondent Node and the Mobile Node exchange HoTI/HoT and CoTI/CoT messages in order to establish a binding management key (Kbm) for authenticating the BU and BA messages. You can configure to send out BRR messages when the remaining lifetime of the binding entry drops below the system-configured BRR threshhold value (see for details) When the system is configured as a Home Agent, the IPv6 Router Advertisement Daemon ( ) must alos be running on the system to provide home link prefix information to Multiple home links are supported if the correct home link prefixes are configured on each home link interface. On a Home Agent, IPsec is used to proctect the signalling messages (i.e. BU, BA, HoTI, HoT, MPS, and MPA) between the Mobile Node and the Home Agent. If IPsec ESP is used, the Alternate Care-of Address option must be included within the BU message as the ESP protocol will not be able to protect the Care-of Address (i.e. source address) in the IPv6 header. For troubleshooting purpose, IPsec authentication can be turned off on via to allow Home Agent to accept plain BU messages from the Mobile Node without out IPsec AH or ESP protection. You can configure to include Binding Refresh Advice (BRA) option within the Binding Acknowledgement from the Home Agent when the remaining lifetime of the binding entry drops below the system-configured BRA interval value (see for details). For better performance on high-end systems, multiple instances of can be configured to run on the system processing Mobility Header mes- sages in parallel (see for details). For diagnostics purposes, supports five different levels of diagnostic message logging (i.e. ALERT, ERROR, WARN, INFO, and DEBUG) via the standard mechanism. By default, the system is configured to log at ERROR level. NOTE
provides Mobile IPv6 server functionality (i.e. Home Agent and Correspondent Node). does not provide Mobile Node functionality which is not required on server. AUTHOR
was developed by HP. SEE ALSO
mip6admin(1M), mip6config(1M), rtradvd(1M), syslog(3C) IETF Document Mobility Support in IPv6 IETF Document Using IPsec to Protect Mobile IPv6 Signaling between Mobile Nodes and Home Agents mip6mod(7)
Check Out this Related Man Page
mipd.conf(4) Kernel Interfaces Manual mipd.conf(4) NAME
mipd.conf - Mobile IPv4 Mobility Agent daemon configuration file SYNOPSIS
(default configuration file) DESCRIPTION
When invoked, the IPv4 Mobility Agent daemon, reads its configuration information from (by default). The IPv4 Mobility Agent daemon can act as a Home Agent (HA) or a Foreign Agent (FA). can be configured to act as combined Home Agent and Foreign Agent only if it is not operating in AAA mode (see below). The content of this file will determine what kind of Mobility Agent functions the daemon will perform. Syntax The basic structure of the configuration file consists of sections, each delimited by curly braces in the form of . . . Each section generally contains a series of lines; each line providing the value for one configuration option in the form of For most part, white space is ignored and '#' comments out the rest of the line. Some labels require multiple values be provided on a sin- gle line, and these values must typically be separated by spaces. The set of legal values depends greatly on which label is being assigned. This configuration file consists of three mandatory sections in the following order: and All three sections are required although they may be empty depending on the optional fields entered and the mobility services (eg. Home Agent or Foreign Agent) being configured for the Mobile IP Agent daemon. The main Section The section must always come first. Fields within the section are: This field is optional and is used by Foreign Agent only. It indicates how long (in seconds) to keep a registration Request for Foreign Agent that hasn't had a matching Regis- tration Reply yet. The default vault for this field is 5.0 seconds. This field accepts floating number. This field is optional and is used by both Home Agent and Foreign Agent. It indicates the value of the ICMP code field of the router advertisement inside the Mobile IP Agent Advertisement message. There are two possible value for this field: This mobility agent handles common traffic -- that is, it acts as a router for IP datagrams not necessarily related to mobile nodes. This mobility agent does not route common traffic other than IP datagrams received from a registered mobile node. The default value for this field is 16. WARNING: Some Mobile Node implementations are known to be confused by advertisements with an ICMP code of 0. This field is required for to operate in AAA mode. It provides the Fully Qualified Domain Name of the host on which is started. This name is used to build the AAA identity for This field is required for to operate in AAA mode. It provides the Fully Qualified Domain Name of the AAA server that serves This name should be resolved via a DNS lookup. Note: The and fields are required for to operate in AAA mode. If one of these fields is omitted or if both the fields are omitted, the daemon would operate in non-AAA mode. This field is optional. It specified the port number on which the AAA server listens for connections. The default value is 1812. The keys Section The section contains a list of authentication keys between two mobility entities. Currently, only Mobile Node-Home Agent and Correspondent Node-Home Agent keys are supported. Hence, this section is required for a HA configuration and is empty for a Foreign Agent only configu- ration. Each entry in this section is entered in the following format: These field are: IP_Address is the IP address of either a Mobile Node or a Correspondent Node. spi is the Security Parameter Index (SPI) value, a 32-bit integer in the range 256 - 2147483647. The SPI does not have to be unique on the Home Agent and must match the SPI configured on the Mobile Node or Correspondent Node. algo is the hashing algorithm used for this security association. Accepted algorithms are hmac-md5 and md5. tstamp indicates that timestamps are used for replay protection. key is the authentication key, a total of 16 bytes. Each byte is entered as two hex digits. Each byte is separated by a space. WARNING: Do not enter more than one key entry for each Mobile Node or Correspondent Node. The ether Section The section contains network interface parameters for Mobile IP. If you have more than one network interface in your machine, you must duplicate this section and fill out one for each interface that you intend to provide Mobile IP service(s). It is incorrect to specify more than one interface name in this section. Fields within the section are: This field is required and contains the name of the network interface that provides mobility service(s). This field is required and indicates the mobility service(s) this interface will offer. It will affect the setting of the H and F flags within the Agent Advertisement Exten- sion. to offer Home Agent mobility service to offer Foreign Agent mobility service to offer both Home Agent and Foreign Agent mobility services. Note that this is not permitted when is configured to act in AAA-mode (see for more info). This field is required and contains the primary address of the interface. This address serves two purposes: 1) As the Home Agent address (if Home Agent service is offered) 2) As the source address that Agent Advertisement messages will have on both the Home Agent and Foreign Agent. If Home Agent service is provided on this interface, Mobile Nodes with their home network on this interface's subnet should be configured to use this interface's primary address as their Home Agent address. This field is required and contains the netmask associated with the primary-addr field. This field is required and contains the address that Agent Advertisement messages is broadcasted/multicasted to. It must be either 255.255.255.255 (the limited-broadcast address) or 225.0.0.1 (multicast address for the all systems on this link). This field is optional and indicates the interval (in seconds) between two consecutive Agent Advertisement messages. It SHOULD be no longer than 1/3 of ICMP Router Advertisement Lifetime below. The default value of this field is 1 second. This field accepts floating point number. This field is optional and contains the Lifetime value (in seconds) within the ICMP Router Advertisement. The default value for this field is 1800 seconds (30 minutes) per RFC 1256. This field is optional and contains the maximum Registration Lifetime (in seconds) allowed within the Mobility Agent Advertisement Extension of a Registration Request. Registrations requesting a longer lifetime than this value will be rejected by the Foreign Agent. The default value of this field is 300 seconds (5 minutes). Note: max-reg-lifetime has no relation with the router-lifetime. This field is optional and contains the Router Address and its associated Preference Level within the ICMP Router Advertisement portion of the Agent Advertisement message. The pref- erence_level must be a number within the range 1 to Number_of_Routers. Higher preference level means more preferable. Repeat this field for as many routers as you want to advertise. A maximum of eight routers can be entered. This field is related with the router field above and contains the netmasks of the corresponding routers advertised above. Hence, make sure that you repeat this field for as many routers as you advertised above. The router netmask is used by the Mobility Agent to compute the Prefix-Lengths within the Prefix-Length Extension inside Agent Advertisement message. The Prefix-Lengths may be used by some Mobile Nodes as part of their move detection algorithm. WARNING: RFC 3344 requires that the number of router netmasks be the same as the number of routers. Some Mobile Nodes are known to re-register constantly if the numbers are not matched. This field is related to the above service field and contains the Care-of Address within the Agent Advertisement Extension. This field is required if you have configured Foreign Agent service on this interface. Note: The Care-of Address is not necessarily the same as the primary address of the interface. In fact, if the machine has multiple interfaces, usually the Care-of Address should be the primary address of the fastest/best connected interface. You can provide multiple Care-of Addresses by repeating this field. A maximum of eight Care-of Addresses can be entered. This field is optional and can be used to configure a pool of addresses from which this Home Agent (if configured) can allocate home addresses. The field can be repeated as many times as needed. IP_address is the first address in the pool, and the pool would consist of num_addresses number of IP addresses starting from IP_address. The default value for num_addresses is 1. This field is optional and can be used to specify the size of the challenge window maintained by this Foreign Agent (if configured). The maximum size accepted is 8. The default value is set to 2. FILES
default configuration file AUTHOR
was originally developed by Carnegie Mellon University with changes made by Hewlett-Packard to port to HP-UX. SEE ALSO
mipadmin(1M), mipconfig(1M), mipd.conf(4). RFC 3344 IP mobility Support for IPv4 RFC 1256 ICMP Router Discovery Messages RFC 1853 IP in IP Tunneling RFC 2003 IP Encapsulation within IP mipd.conf(4)