mipd(1M)																  mipd(1M)

NAME

       mipd - Mobile IPv4 mobility agent daemon

SYNOPSIS

       config_file_name ]

DESCRIPTION

       implements  the Home Agent and Foreign Agent functions as described in RFC 3344 - IP Mobility Support for IPv4.	can act as a Home Agent, a
       Foreign Agent, or combined Home Agent/Foreign Agent on any Ethernet network interface on the system.  also  supports  the  following  stan-
       dards:

       RFC 1256       ICMP Router Discovery Messages
       RFC 1853       IP in IP Tunneling RFC 2003 IP Encapsulation within IP
       RFC 2794       Mobile IP Network Access Identifier Extension for IPv4
       RFC 3012       Mobile IPv4 Challenge/Response Extensions

       In addition, implements:

       draft-ietf-diameter-base-08	  Diameter Base Protocol
       draft-ietf-diameter-mobileip-08	  Diameter Mobile IPv4 Application
       draft-ietf-mobileip-optim-11.txt   Route Optimization in Mobile IP
       draft-ietf-mobileip-aaa-key-10	  AAA Registration Keys for Mobile IP

       cannot  run  without  a configuration file.  It is recommended that user should use the command to create the configuration file.  If it is
       desired to create configuration file by hand, see the mipd.conf(4) manual page for details about file format and syntax.

   Options
       recognizes the following command-line options and arguments:

       Specifies the name of the configuration file.

			     Default is

       Changes the syslog logging level for
			     logs messages to the system syslog file, by default.  The user can use the program to view logging  messages  entered
			     by  The  logging  levels  are shown in ascending order.  Lower logging levels include all higher levels.  The default
			     syslog logging level is which includes messages.  A definition of each class is shown below.

			     These messages include unrecoverable error conditions such as fatal
				      configuration errors and daemon initialization errors.

			     These messages include recoverable error conditions such as various
				      Mobile Node registration failure (i.e. failure to retrieve link layer address from registration packets  and
				      Mobile-Home authentication errors).

			     These messages provide notification to the user such as dropped packets
				      due to unsupported features, no system resources.

			     These messages provide detailed event logging for
				      debugging and troubleshooting purposes.

   Signal Processing
       The following signal may used to control

       Graceful shutdown.  On receipt of a
		      attempts	a graceful shutdown.  Mobile IP resources such as tunnels between the Home Agent and the Care-of Addresses will be
		      destroyed.  All active Proxy ARP entries, created when the Mobile Nodes were away from home, will be deleted from  the  Home
		      Agent. Mobile Node host specific route entries along with their ARP entries will also be deleted from the Foregin Agent.

   Logging and Tracing
       uses  to log error messages into The netTL(1M) formatter, netfmt(1M), has been modified to recognize Mobile IPv4 control messages and IP/IP
       encapsulated packets.  To trace Agent Solicitation and Agent Advertisement messages, use the subsystem ID to capture  those  ICMP  packets.
       To  trace  Registrations  Request  and Registration Reply messages, use the subsystem ID with port 434 specified in the filter options.	To
       trace IP/IP encapsulated datagrams in the tunnel, use the subsystem ID.

   Auto-Start
       Normally, the daemon is automatically started during system boot-up time.  To start during boot-up, set the variable  to  1  in	the  file.
       Make  sure  the variable is set to 0 since and (Route Optimization daemon, see miprod(1M) for details) cannot run on the same system.  Edit
       the variable if you need to change the default configuration file path/name.  can also be manually started and stopped by  using  the  com-
       mand.

   Internal Operation
       can  be	configured  (see  mipd.conf(4))  to operate in AAA-mode or in normal-mode.  In AAA-mode, can act as either a Home Agent or Foreign
       Agent on all interfaces, but not both.  It can process registrations from Mobile Nodes that  are  AAA-aware  and  non-AAA  aware.   Non-AAA
       Mobile  Nodes  are  those  that	implement  only the Mobile IP base protocol per RFC3344.  AAA Mobile Nodes implement RFC2794, RFC3012, and
       draft-ietf-mobileip-aaa-key-10 on top of RFC3344.

       A Home Agent tracks the mobility binding of the Mobile Nodes that are roaming around in the Internet.  A Foreign  Agent	offers	a  Care-of
       Address	to  the  visiting  Mobile Node.  A Mobile Node may use a co-located Care-of Address instead of a Foreign Agent Care-of Address. In
       both cases, a tunnel will always be established between the Home Agent and the Mobile Node's Care-of Address for routing datagrams that are
       destined  to the Mobile Node's home address.  supports reverse tunnels, as well as Mobile Nodes that use a Foreign Agent Care-of Address or
       a Co-located Care-of Address.

       Both Home Agent and Foreign Agent broadcast (or multicast) Agent Advertisement messages on a periodic basis which announce  their  presence
       to  any	listening Mobile Node.	Agents also listen for Agent Solicitation message and reply back with unicast Agent Advertisement message.
       Agent Solicitation and Advertisement messages are modified versions of the ICMP Router Discovery Messages  (see	RFC  1256)  with  Mobility
       Agent Advertisement Extensions and Prefix-Length Extension added.

       A  Foreign  Agent  operating in AAA-mode will also include an Agent Advertisement Challenge extension per RFC3012.  This informs the Mobile
       Node that the Foreign Agent can authenticate the Mobile Node and is capable of processing requests via the AAA protocol.  For Mobile  Nodes
       that  include  the  Mobile-AAA  or  Mobile-Foreign authentication extension, the Foreign Agent will reject the request if a valid challenge
       extension is not included in the request.

       Foreign Agents process Registration Request messages from Mobile Nodes by first performing various compliance checks against  the  Request.
       For requests that require processing via AAA, the Foreign Agent creates a Diameter Mobile IP request (AMR), and sends it to the AAA server.
       This request is handled by the AAA protocol and is eventually forwarded to the Home Agent as the Diameter HAR (Home Agent Request) message.
       If  the	Foreign Agent is not operating in AAA-mode, or determines that the registration request does not require the AAA protocol for pro-
       cessing, it will then forward the request directly to the Home Agent.

       Upon receiving a HAR, the Home Agent processes the request and sends a corresponding Diameter Mobile IP reply (HAA) to the AAA server.  The
       AAA protocol will eventually forward this message to the Foreign Agent as a Diameter AMA message.

       Upon  receiving	a Registration Request message directly from a Foreign Agent or a Mobile Node using a co-located Care-of Address, the Home
       Agent checks for a valid Mobile-Home Authentication Extension within the message to authenticate the identity of the Mobile Node.  A Regis-
       tration Reply message is then sent back to the Foreign Agent, or directly to the Mobile Node's co-located Care-of Address.

       Home  Agent  operating  in AAA-mode can also handle requests from Mobile Nodes (using co-located Care-of Address) that require AAA for pro-
       cessing.  For such requests, the Home Agent sends an AMR message to the AAA server, and the AAA server responds with a  AMA  message.   The
       Home  Agent  then  processes the request sent by the Mobile Node.  Such requests are not expected to include the Mobile-Home authentication
       extension.

       If the Registration Request message (HAR or non-AAA) passes all the checks, the Home Agent adds the Mobile Node to its Mobility Binding ta-
       ble  and  then creates a point-to-point IP-over-IP tunnel between the Home Agent and the Care-of Address.  After the tunnel is created, the
       Home Agent performs Proxy ARP on behalf of the Mobile Node in order to attract and intercept datagrams that  are  destined  to  the  Mobile
       Node's  permanent home address.	These packets are then encapsulated using IP Encapsulation within IP method (see RFC 2003) and tunneled to
       the target Care-of Address where the encapsulated packets will be decapsulated and forwarded to the Mobile Node.  The  tunnel,  along  with
       its  associated entry in the Mobility Binding table or Visitor List, is deleted when the Registration Lifetime expires.	Registration Life-
       time is configurable via a parameter in the configuration file.

       Upon receiving a successful reply (either an AMA message from AAA server or a registration reply directly from the Home Agent) for a  pend-
       ing request, the Foreign Agent adds an entry for the Mobile Node in its Visitor List and creates a point-to-point IP-over-IP tunnel between
       the Care-of Address and the Home Agent.	The Foreign Agent will then forward the reply to the Mobile Node.

       When a Mobile Node returns to its home network, it will send a special de-Registration Request message with its home address placed in  the
       Care-of	Address  field.   If  the  de-Registration  Request passes all the checks, the Home Agent dismantles the tunnel and its associated
       Mobility Binding entry.	Proxy ARP for the Mobile Node will then be disabled and a Gratuitous ARP with the Mobile Node's MAC  address  will
       be  sent out on the home network on behalf of the Mobile Node.  The Visitor List entry in the Foreign Agent will be deleted when the Regis-
       tration Lifetime expires.

       Non-AAA registration requests and replies messages are sent and received by via UDP port 434.

       Foreign Agent and Home Agent support Foreign-Home authentication as described in RFC3344.  A  Foreign  Agent  operating	in  AAA-mode  will
       request	Foreign-Home  keys via the AMR message if the Foreign Agent does not have keys to the Home Agent.  Static Foreign-Home keys cannot
       be configured on

       in AAA-mode also supports dynamic Home Agent allocation and Home Address discovery via the  Diameter  Protocol.	 Address  Pools  for  home
       address	allocation  can be configured for each interface offering Home Agent service (see mipd.conf(4)).  Note that home addresses alloca-
       tions are logged under the level.  does not support home address or home agent discovery in non-AAA mode.

       Foreign Agent and Home Agent operating in AAA-mode support the Diameter Session Termination and Abort messages. Upon expiration of  a  ses-
       sion,  they will send a Session Termination Request (STR) message to the AAA server.  Upon receiving an Abort Session Request (ASR) message
       from the AAA server, they will terminate the session.

   AAA Registration Keys
       When invoked in AAA mode, reads AAA key extension types and subtypes definitions from The daemon uses definitions in this file  to  process
       and  build  AAA Generalized Key Request and Reply Extensions.  If this file does not exist, uses the values defined in draft 10 of the IETF
       AAA Registration Keys for Mobile IP specification (draft-ietf-mobileip-aaa-key-10).  The AAA key type and subtype values may vary  in  dif-
       ferent  drafts  of the specification. Users may have to change the definitions to match the values for the draft version implemented by the
       Mobile Node clients.

FILES

       default agent configuration file.

       AAA key types and subtypes configuration file.

       auto-start configuration file.

       process ID of the currently running

AUTHORS

       was originally developed by Carnegie Mellon University to run on the FreeBSD platform and was ported to	HP-UX  by  Hewlett-Packard.   This
       software is copyright 1995,1996 by Carnegie Mellon University.

SEE ALSO

       mipadmin(1M), mipconfig(1M), mipd.conf(4), miproconfig(1M), miprod(1M), miprod.conf(4).

																	  mipd(1M)