mipagentconfig(1M)

Name

mipagentconfig– configure Mobility IP Agent

Synopsis

/sbin/mipagentconfig [-fconfigfile] commanddest
[parameters]...

Description

The mipagentconfig utility is used to configure the Mobility IP Agent. mipagentconfig allows the user to change settings. The mipagentconfig user can also add and delete mobility clients, Pools, and SPIs in the mobility agent configuration
file.

Options

The following options are supported:

-fconfigfile

Use the specified configuration file instead of the system default, /etc/inet/mipagent.conf.

Operands

The command operand, as well as the parameters for each command are described below. See mipagent.conf(4) for the default
values of the configuration operands that are described here.

add

This command adds advertisement parameters, security parameters, SPIs, or addresses to the configuration file, based on the destination dest.

add AddressipAddressattr_value

Add the specified ipAddress with the specified SPI. To add an NAI address, you must specify
the Pool.

add advdevice

Enable home and foreign agent functionality on the specified interface.

add advdeviceAdvLifetimeseconds

Add AdvLifetime to the specified device.

add advdeviceRegLifetimeseconds

Add RegLifetime to the specified device.

add advdeviceAdvFrequencyseconds

Add AdvFrequency to the specified device.

add advdeviceAdvInitCountcount

Add initial unsolicited advertisement count. count should be a small integer.

Do not limit unsolicited advertisement. The advertisement should take place periodically at the frquency specified by AdvFrequency.

add advdeviceHomeAgentyes | no

Add the HomeAgent flag to the specified device.

add advdeviceForeignAgentyes | no

Add the ForeignAgent flag to the specified device.

add advdevicePrefixLengthExtyes | no

Add the PrefixLengthExt flag to the specified device.

add advdeviceNAIExtyes | no

Add the NAIExt flag to the specified device.

add advdeviceChallengeyes | no

Add the Challenge flag to the specified device.

add advdeviceReverseTunnelno | neitherfahayes | both

Add the level of ReverseTunnel support that is indicated to the specified device. Possible values include:

no

Do not support ReverseTunnel as either a foreign agent or a home agent on this device. Does not advertise reverse tunneling nor accept a registration requesting reverse tunnel support on this device.

neither

Do not support ReverseTunnel as either a foreign agent or a home agent on this device. Do not advertise reverse tunneling or accept a registration that requests reverse tunnel support on this device.

fa

When the foreign agent processes a registration request received on this device, check to see if the mobile node requests that a reverse tunnel be set up to its home agent. If so, perform the necessary encapsulation of datagrams to the mobile
node's home agent as described in RFC 3024. This means that a mobile node must see the agent advertising reverse tunnel support, so the reverse tunnel bit is advertised in the agent advertisement on this device.

ha

When the home agent processes a registration request received on this device, check to see if the mobile node requests that a reverse tunnel be set up from its care-of address. If so, perform the necessary decapsulation as described in RFC 3024. This does not mean the home agent is advertising support of reverse tunneling on this device. Mobile nodes are only interested in the advertisement flags if mobile nodes are going to use foreign agent services. Moreover, reverse tunnels by definition originate at the care-of address.
HA support is therefore only of interest to the owner of the care-of address.

yes

Whenever the mobility agent is processing a registration request received on this device, check to see if the mobile node is requesting that a reverse tunnel be set up. If so, apply RFC 3024 as appropriate, either
as an encapsulating foreign agent, or as a decapsulating home agent, depending on how this mobility agent is servicing the specific mobile node. As a result, the mobility agent advertises reverse tunnel support on this device.

both

Whenever the mobility agent is processing a registration request received on this device, check to see if the mobile node is requesting that a reverse tunnel be set up. If so, apply RFC 3024 as appropriate, either
as an encapsulating foreign agent, or a decapsulating home agent, depending on how this mobility agent services the specific mobile node. As a result, the mobility agent advertises reverse tunnel support on this device.

Add the requirement that the ReverseTunnel flag be set in any registration request received on the indicated device. Possible values include:

no

Reverse tunneling is not required by the mipagent on this device.

neither

Reverse tunneling is not required by the mipagent on this device.

fa

The ReverseTunnel flag is required to be set in registration requests received by the foreign agent on this device.

ha

The ReverseTunnel flag is required to be set in registration requests received by the home agent on this device.

yes

The ReverseTunnel flag is required to be set in all registration requests received by either home and or foreign agents on this device.

both

The ReverseTunnel flag is required to be set in all registration requests received by either home and or foreign agents on this device.

addPoolnumberstartAddrlength

Add the specified Pool with the specified start addresses and length.

addSPInumberreplayKey

Add the specified SPI with the given replay type and key. The replay type can have a value of none or timestamps.

addHA-FAAuthyes | no

Add the HA-FAAuth flag.

addMN-FAAuthyes | no

Add the MN-FAAuth flag.

addMaxClockSkewseconds

Add the MaxClockSkew.

addKeyDistributiontype

Add the KeyDistribution type. The only value for KeyDistribution that is supported at this time is file.

change

Depending on the destination dest, this command will change advertisement parameters, security parameters, SPIs, or addresses in the configuration file. Any of the above destinations are valid.

delete

Depending on the destination dest, this command will delete advertisement parameters, security parameters, SPIs, or addresses from the configuration file. Any destination discussed above is
valid.

get

Display all of the parameters associated with dest. Any destination discussed above is valid.

Examples

Example 1 Adding an SPI, a Pool, and a Mobile Node and Requiring Reverse Tunneling on a Device to the configfile

The following example adds an SPI, a Pool, a mobile node, and requires reverse tunneling for the foreign agent in the configfile. First, the SPI of 250 is added. Then, a Pool of 200 addresses starting
at 192.168.168.1 is added. joe@mobile.com is added with an SPI of 250 and using Pool 1. Finally, reverse tunneling is required for the foreign agent on device eri0.

Example 2 Adding Dynamic Interface Mobility Support on PPP Interfaces

The following example adds dynamic interface mobility support on PPP interfaces. Note that in some shells the backslash (\) escape character is required to bypass the expansion of the asterix (“*”) and pass the “*” character to mipagentconfig. The example also indicates that all the new PPP interfaces offer reverse tunnel service.

Example 3 Adding IPsec Policies to an Agent-Peer Entry

The following example adds IPsec policies to an existing mobility agent entry, then displays the configuration for the mobility agent peer. The backslash (\) character denotes a line continuation for the formatting of this example.