This section explains how to plan for Mobile IP and create the /etc/inet/mipagent.conffile.
When you configure the mipagent.conf file for the first time, you need to perform the following tasks:
Depending on your organization's requirements for its hosts, determine what functionality your Mobile IP agent can provide:
Create the /etc/inet/mipagent.conf file and specify the settings you require by using the procedures that are described in this section. You can also copy one of the following files to /etc/inet/mipagent.conf and modify it according to your requirements:
For foreign agent functionality, copy /etc/inet/mipagent.conf.fa-sample.
For home agent functionality, copy /etc/inet/mipagent.conf.ha-sample.
For both foreign agent and home agent functionality, copy /etc/inet/mipagent.conf-sample.
You can reboot your system to invoke the boot script that starts the mipagent daemon. Or, you can also start mipagent by typing the following command:
# /etc/inet.d/mipagent start |
Assume the Primary Administrator role, or become superuser, on the system where you want to enable Mobile IP.
The Primary Administrator role includes the Primary Administrator profile. To create the role and assign the role to a user, see Chapter 2, Working With the Solaris Management Console (Tasks), in System Administration Guide: Basic Administration.
Create the /etc/inet/mipagent.conf file by using one of the following options:
Add or change configuration parameters in the /etc/inet/mipagent.conf file to conform to your configuration requirements.
The remaining procedures in this section describe the steps to modify sections in /etc/inet/mipagent.conf.
If you copied one of the sample files in the /etc/inet directory, you can omit this procedure because the sample file contains this entry. General Section provides descriptions of the labels and values that are used in this section.
Edit the /etc/inet/mipagent.conf file and add the following lines:
[General] Version = 1.0 |
The /etc/inet/mipagent.conf file must contain this entry.
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> |
You must include a different Advertisements section for each interface on the local host that provides Mobile IP services.
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 |
Pool Section provides descriptions of the labels and values that are used in this section:
Edit the /etc/inet/mipagent.conf file
Add or change the following lines by using the values that are required for your configuration:
[Pool pool-identifier] BaseAddress = IP-address Size = size |
SPI Section provides descriptions of the labels and values that are used in this section.
Edit the /etc/inet/mipagent.conf file.
Add or change the following lines by using the values that are required for your configuration:
[SPI SPI-identifier] ReplayMethod = <none/timestamps> Key = key |
You must include a different SPI section for each security context that is deployed.
Address Section provides descriptions of the labels and values that are used in this section.
Edit the /etc/inet/mipagent.conf file.
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 |
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 |