sun.com docs.sun.com My Sun Worldwide Sites

Previous Previous     Contents     Index     Next Next

ProcedureHow to Configure the Advertisements Section

Advertisements Section provides descriptions of the labels and values that are used in this section.

  • Edit the /etc/inet/mipagent.conf file and add or change the following lines by using the values that are required for your configuration.

    [Advertisements interface]
         HomeAgent = <yes/no>
         ForeignAgent = <yes/no>
         PrefixFlags = <yes/no>
         AdvertiseOnBcast = <yes/no>
         RegLifetime = n
         AdvLifetime = n
         AdvFrequency = n
         ReverseTunnel = <yes/no/FA/HA/both>
         ReverseTunnelRequired = <yes/no/FA/HA>


    Note - You must include a different Advertisements section for each interface on the local host that provides Mobile IP services.


ProcedureHow to Configure the GlobalSecurityParameters Section

GlobalSecurityParameters Section provides descriptions of the labels and values that are used in this section.

  • Edit the /etc/inet/mipagent.conf file and add or change the following lines by using the values that are required for your configuration:

    [GlobalSecurityParameters]
         MaxClockSkew = n
         HA-FAauth = <yes/no>
         MN-FAauth = <yes/no>
         Challenge = <yes/no>
         KeyDistribution = files

ProcedureHow to Configure the Pool Section

Pool Section provides descriptions of the labels and values that are used in this section:

  1. Edit the /etc/inet/mipagent.conf file

  2. Add or change the following lines by using the values that are required for your configuration:

    [Pool pool-identifier]
         BaseAddress = IP-address
         Size = size

ProcedureHow to Configure the SPI Section

SPI Section provides descriptions of the labels and values that are used in this section.

  1. Edit the /etc/inet/mipagent.conf file.

  2. Add or change the following lines by using the values that are required for your configuration:

    [SPI SPI-identifier]
         ReplayMethod = <none/timestamps>
         Key = key


    Note - You must include a different SPI section for each security context that is deployed.


ProcedureHow to Configure the Address Section

Address Section provides descriptions of the labels and values that are used in this section.

  1. Edit the /etc/inet/mipagent.conf file.

  2. Add or change the following lines by using the values that are required for your configuration:

    • For a mobile node, use the following:

      [Address address]
           Type = node
           SPI = SPI-identifier

    • For an agent, use the following:

      [Address address]
           Type = agent
           SPI = SPI-identifier
           IPsecRequest = action {properties} [: action {properties}]
           IPsecReply = action {properties} [: action {properties}]
           IPsecTunnel = action {properties} [: action {properties}]

      where action and {properties} are any action and associated properties that are defined in the ipsec(7P) man page.


      Note - The SPI that is configured previously corresponds to the MD5 protection mechanism that is required by RFC 2002. The SPI that is configured previously does not correspond to the SPI that is used by IPsec. For more information about IPsec, see Chapter 19, IP Security Architecture (Overview) and Chapter 20, Configuring IPsec (Tasks). Also see the ipsec(7P) man page.


    • For a mobile node that is identified by its NAI, use the following:

      [Address NAI]
           Type = Node
           SPI = SPI-identifier
           Pool = pool-identifier

    • For a default mobile node, use the following:

      [Address Node-Default]
           Type = Node
           SPI = SPI-identifier
           Pool = pool-identifier

Modifying the Mobile IP Configuration File (Task Map)

Task

Description

For Instructions

Modify the General section.

Uses the mipagentconfig change command to change the value of a label in the General section of the Mobile IP configuration file.

How to Modify the General Section 

Modify the Advertisements section.

Uses the mipagentconfig change command to change the value of a label in the Advertisements section of the Mobile IP configuration file.

How to Modify the Advertisements Section 

Modify the GlobalSecurityParameters section.

Uses the mipagentconfig change command to change the value of a label in the GlobalSecurityParameters section of the Mobile IP configuration file.

How to Modify the GlobalSecurityParameters Section 

Modify the Pool section.

Uses the mipagentconfig change command to change the value of a label in the Pool section of the Mobile IP configuration file.

How to Modify the Pool Section 

Modify the SPI section.

Uses the mipagentconfig change command to change the value of a label in the SPI section of the Mobile IP configuration file.

How to Modify the SPI Section 

Modify the Address section.

Uses the mipagentconfig change command to change the value of a label in the Address section of the Mobile IP configuration file.

How to Modify the Address Section 

Add or delete parameters.

Uses the mipagentconfig add or delete commands to add new parameters, labels, and values or to delete existing ones in any section of the Mobile IP configuration file.

How to Add or Delete Configuration File Parameters 

Display the current settings of parameter destinations.

Uses the mipagentconfig get command to display current settings of any section of the Mobile IP configuration file.

How to Display Current Parameter Values in the Configuration File 

Modifying the Mobile IP Configuration File

This section shows you how to modify the Mobile IP configuration file by using the mipagentconfig command. This section also shows you how to display the current settings of parameter destinations.

Configuring the Mobility IP Agent provides a conceptual description of the mipagentconfig command's usage. You can also review the mipagentconfig(1M) man page.

Previous Previous     Contents     Index     Next Next
Company Info Contact Terms of Use Privacy Copyright 1994-2007 Sun Microsystems, Inc.