753 lines
31 KiB
Mathematica
753 lines
31 KiB
Mathematica
/* 00comp_ipnet_mobility.cdf - IPNet Mobility configuration file */
|
|
|
|
/*
|
|
* Copyright (c) 2006-2007 Wind River Systems, Inc.
|
|
*
|
|
* The right to copy, distribute or otherwise make use of this software
|
|
* may be licensed only pursuant to the terms of an applicable Wind River
|
|
* license agreement. No license to Wind River intellectual property rights
|
|
* is granted herein. All rights not licensed by Wind River are reserved
|
|
* by Wind River.
|
|
*/
|
|
|
|
/*
|
|
modification history
|
|
--------------------
|
|
01j,11oct07,jho MIPFA_SPI_SECRET_LIST parameter change
|
|
01i,03oct07,jho RADIUS and DIAMETER CDF mappings
|
|
01f,27feb07,kch Added MIPMN_IPSEC_PROTECTED configuration parameter for
|
|
mobile node. Also renamed MIPMN_IFNAME_LIST to MIPMN_IFNAME
|
|
since only one interface can be configured at any time in
|
|
the mobile node (WIND00089286).
|
|
01e,23jan06,tlu Fix MIP CDF defects (85299, 85297, 85290)
|
|
01d,25nov06,kch Added MIPHA_IF_NAT_T_KEEPALIVE_LIST configuration parameter.
|
|
01c,23sep06,kch Fixed IPCOM shell commands description.
|
|
01b,26aug06,kch Added support for configuration parameters.
|
|
01a,22may06,kch created.
|
|
*/
|
|
|
|
#ifdef _WRS_CONFIG_COMPONENT_IPMIPFA
|
|
|
|
|
|
Component INCLUDE_IPMIPFA {
|
|
NAME IPv4 Foreign Agent
|
|
SYNOPSIS IPv4 Foreign Agent
|
|
MODULES ipmipfa.o
|
|
REQUIRES INCLUDE_IPCOM INCLUDE_IPNET INCLUDE_IPMIP4
|
|
_CHILDREN FOLDER_MOBILITY_FA
|
|
CONFIGLETTES ipmipfa_config.c
|
|
CFG_PARAMS MIPFA_IFNAME_LIST \
|
|
MIPFA_REG_LIFETIME \
|
|
MIPFA_HA_SA_ADDRESS_LIST \
|
|
MIPFA_HA_SA_LOOKUP_REQUIRE \
|
|
MIPFA_FA_SA_ADDRESS_LIST \
|
|
MIPFA_SPI_SECRET_LIST \
|
|
MIPFA_LLH_NBR_IP_LIST \
|
|
MIPFA_LLH_NBR_BSSID_LIST \
|
|
MIPFA_IF_ADDRESS_LIST \
|
|
MIPFA_IF_ADV_INTERVAL_LIST \
|
|
MIPFA_IF_ADV_ADDRESS_LIST \
|
|
MIPFA_IF_ADV_LIFETIME_LIST \
|
|
MIPFA_IF_CHALLENGE_LIST \
|
|
MIPFA_IF_MN_AUTH_ENABLED_LIST \
|
|
MIPFA_IF_LLH_PRE_ENABLED_LIST \
|
|
MIPFA_IF_LLH_POST_ENABLED_LIST \
|
|
MIPFA_IF_LLH_BET_LIFETIME_LIST \
|
|
MIPFA_IF_NAT_T_ENABLED_LIST \
|
|
MIPFA_IF_FORCED_NAT_T_ENABLED_LIST \
|
|
MIPFA_IF_NAT_T_KEEPALIVE_LIST \
|
|
MIPFA_IF_NAT_T_TUNNEL_TYPE_LIST \
|
|
MIPFA_IF_TUNNEL_REVERSE_LIST \
|
|
MIPFA_IF_IPIP_TUNNEL_ENABLED_LIST \
|
|
MIPFA_IF_GRE_TUNNEL_ENABLED_LIST \
|
|
MIPFA_IF_MINENC_TUNNEL_ENABLED_LIST\
|
|
MIPFA_IF_TUNNEL_REORDERING_LIST \
|
|
MIPFA_IF_REVOCATION_ENABLED_LIST \
|
|
MIPFA_IF_REVOCATION_INFORM_LIST
|
|
}
|
|
|
|
|
|
Component INCLUDE_IPMIPFA_AAA_RADIUS {
|
|
NAME IPv4 Foreign Agent AAA Radius Support
|
|
SYNOPSIS IPv4 Foreign Agent AAA Radius Support
|
|
REQUIRES INCLUDE_IPMIPFA INCLUDE_IPRADIUS
|
|
_CHILDREN FOLDER_MOBILITY_FA
|
|
CFG_PARAMS MIPFA_AAA_RADIUS_ACCOUNTING \
|
|
MIPFA_AAA_RADIUS_ACCOUNTING_ADDRESS \
|
|
MIPFA_AAA_RADIUS_ACCOUNTING_PORT \
|
|
MIPFA_AAA_RADIUS_ACCOUNTING_SECRET \
|
|
MIPFA_AAA_RADIUS_ACCESS \
|
|
MIPFA_AAA_RADIUS_ACCESS_ADDRESS \
|
|
MIPFA_AAA_RADIUS_ACCESS_PORT \
|
|
MIPFA_AAA_RADIUS_ACCESS_SECRET \
|
|
MIPFA_AAA_RADIUS_ACCESS_REQUIRE \
|
|
MIPFA_AAA_RADIUS_ACCESS_TIME_INTERVAL \
|
|
MIPFA_AAA_RADIUS_LOCAL_ADDRESS
|
|
}
|
|
|
|
Component INCLUDE_IPMIPFA_AAA_DIAMETER {
|
|
NAME IPv4 Foreign Agent AAA Diameter Support
|
|
SYNOPSIS IPv4 Foreign Agent AAA Diameter Support
|
|
REQUIRES INCLUDE_IPMIPFA INCLUDE_IPDIAMETERC
|
|
_CHILDREN FOLDER_MOBILITY_FA
|
|
CFG_PARAMS MIPFA_AAA_DIAMETER_ACCESS \
|
|
MIPFA_AAA_DIAMETER_ACCESS_ADDRESS \
|
|
MIPFA_AAA_DIAMETER_ACCESS_REALM \
|
|
MIPFA_AAA_DIAMETER_ACCESS_HOSTNAME \
|
|
MIPFA_AAA_DIAMETER_ACCESS_FA_HA_SPI \
|
|
MIPFA_AAA_DIAMETER_ACCESS_PORT \
|
|
MIPFA_AAA_DIAMETER_ACCESS_TIME_INTERVAL \
|
|
MIPFA_AAA_DIAMETER_ACCESS_REQUIRE
|
|
}
|
|
|
|
Component INCLUDE_IPMIPFA_PMIPV4 {
|
|
NAME IPv4 Foreign Agent PMIPv4
|
|
SYNOPSIS IPv4 Foreign Agent PMIPv4 Support
|
|
_CHILDREN FOLDER_MOBILITY_FA
|
|
REQUIRES INCLUDE_IPMIPFA
|
|
}
|
|
|
|
Component INCLUDE_IPMIPFA_PMIPV4_DHCP {
|
|
NAME IPv4 Foreign Agent PMIPv4 DHCP
|
|
SYNOPSIS IPv4 Foreign Agent PMIPv4 DHCP Support includes \
|
|
the DHCP handling for non-mobile nodes as well \
|
|
as communication with the PMIPv4 Client
|
|
REQUIRES INCLUDE_IPMIPFA
|
|
_CHILDREN FOLDER_MOBILITY_FA
|
|
CFG_PARAMS MIPFA_PMIPV4_DHCP_SERVER \
|
|
MIPFA_PMIPV4_DHCP_SPI_MN_HA \
|
|
MIPFA_PMIPV4_DHCP_SPI_MN_HA_SECRET \
|
|
MIPFA_PMIPV4_DHCP_CLIENT_ADDRESS \
|
|
MIPFA_PMIPV4_DHCP_CLIENT_PORT \
|
|
MIPFA_PMIPV4_DHCP_SERVER_OVERRIDE \
|
|
MIPFA_PMIPV4_DHCP_HOME_AGENT_ADDRESS \
|
|
MIPFA_PMIPV4_DHCP_PORT \
|
|
MIPFA_PMIPV4_DHCP_DOMAIN
|
|
}
|
|
|
|
Component INCLUDE_IPMIPFA_FEATURE_EXTENSION {
|
|
NAME IPv4 Foreign Agent Feature Extension Registration Hook
|
|
SYNOPSIS IPv4 Foreign Agent Feature Extension allows you provide \
|
|
an additional registration hook for registration of \
|
|
external functions.
|
|
REQUIRES INCLUDE_IPMIPFA
|
|
_CHILDREN FOLDER_MOBILITY_FA
|
|
CFG_PARAMS MIPFA_FEATURE_INITIALIZATION_HOOK
|
|
}
|
|
|
|
|
|
Component INCLUDE_IPMIPFA_CMD {
|
|
NAME IPv4 Foreign Agent IPCOM commands
|
|
SYNOPSIS Mobile IPv4 Foreign Agent IPCOM commands
|
|
MODULES ipmipfa_cmd_fa.o
|
|
_CHILDREN FOLDER_MOBILITY_FA
|
|
REQUIRES INCLUDE_IPCOM_SHELL_CMD INCLUDE_IPMIPFA
|
|
}
|
|
|
|
|
|
/******************** Configuration Parameters *****************************/
|
|
|
|
Parameter MIPFA_PMIPV4_DHCP_SERVER {
|
|
NAME PMIPv4 DHCP Server
|
|
SYNOPSIS This parameter specifies the default DHCP server we should relay \
|
|
DHCP requets to. Syntax is <interface>=<dhcp address>. For \
|
|
example "eth0=10.1.1.1"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_PMIPV4_DHCP_SERVER_OVERRIDE {
|
|
NAME PMIPv4 DHCP Server Override
|
|
SYNOPSIS This parameter specifies DHCP Override should be used. If specified \
|
|
ALL foreign agents in this proxy mobility domain must have identical \
|
|
DHCP Server Override configurations. The value for this parameter \
|
|
is an INET address that will be used as DHCP server address when \
|
|
communication with proxy mobility clients. Syntax is \
|
|
<interface>=<dhcp server override address>. For \
|
|
example "eth0=10.1.1.2"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_PMIPV4_DHCP_SPI_MN_HA {
|
|
NAME PMIPv4 DHCP Mobile-Home SPI Number
|
|
SYNOPSIS This parameter specifies the default Mobile-Home SPI number \
|
|
to be used by proxy mobility to authenticate towards the \
|
|
home agent. Syntax is <interface>=<number>. For example \
|
|
"eth0=1002"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_PMIPV4_DHCP_SPI_MN_HA_SECRET {
|
|
NAME PMIPv4 DHCP Mobile-Home SPI Secret
|
|
SYNOPSIS This parameter specifies the default Mobile-Home SPI secret \
|
|
to be used by proxy mobility to authenticate towards the \
|
|
home agent. Syntax is <interface>=<secret>. For example \
|
|
"eth0=test0"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_PMIPV4_DHCP_CLIENT_ADDRESS {
|
|
NAME PMIPv4 DHCP Proxy Mobility Client Address
|
|
SYNOPSIS This parameter specifies where the default proxy mobility client \
|
|
is located. Syntax is <interface>=<client address>. For example \
|
|
"eth0=127.0.0.1"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_PMIPV4_DHCP_HOME_AGENT_ADDRESS {
|
|
NAME PMIPv4 DHCP Proxy Mobility Default Home Agent Address
|
|
SYNOPSIS This parameter specifies the default home agent address to \
|
|
be used in proxy mobility. Syntax is \
|
|
<interface>=<home agent address>. For example "eth0=10.0.0.1"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
|
|
Parameter MIPFA_PMIPV4_DHCP_CLIENT_PORT {
|
|
NAME PMIPv4 DHCP Proxy Mobility Client Port
|
|
SYNOPSIS This parameter specifies what port the default proxy mobility client \
|
|
uses. Syntax is <interface>=<client port>. For example \
|
|
"eth0=434"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_PMIPV4_DHCP_PORT {
|
|
NAME PMIPv4 DHCP Communication Port
|
|
SYNOPSIS This parameter specifies what port the foreign agent will use when \
|
|
communicating with the proxy mobility agent. By default this port \
|
|
is unspecified and randomly selected by the foreign agent. \
|
|
Syntax is <interface>=<port>. For example "eth0=4343"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_PMIPV4_DHCP_DOMAIN {
|
|
NAME PMIPv4 DHCP Proxy Mobility Domain
|
|
SYNOPSIS This parameter specifies what domain should be appended to a NAI \
|
|
when proxy mobility automatically creates one, if it itw as not \
|
|
provided in the DHCP negotiation. Syntax is \
|
|
<interface>=<domain>. For example "eth0=windriver.com"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_FEATURE_INITIALIZATION_HOOK {
|
|
NAME Foreign Agent Feature Initialization Hook
|
|
SYNOPSIS This is the function hook that you may define in order to \
|
|
register extra functional extensions to the Foreign Agent
|
|
TYPE FUNCPTR
|
|
DEFAULT your_function_here
|
|
}
|
|
|
|
|
|
/* INCLUDE_IPMIPFA configuration parameters */
|
|
Parameter MIPFA_IFNAME_LIST {
|
|
NAME Foreign agent Interface
|
|
SYNOPSIS Specifies the network interface which should be managed \
|
|
by the mobile IP foreign agent implementation. This is \
|
|
a space-separated list of one or more interfaces, i.e. "eth0".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_REG_LIFETIME {
|
|
NAME Registration lifetime
|
|
SYNOPSIS Specifies how long a mobile node binding is kept active \
|
|
before it is deleted, unless the mobile node have \
|
|
reregistered before the time is up. Value given in seconds.
|
|
TYPE char *
|
|
DEFAULT "360"
|
|
}
|
|
|
|
Parameter MIPFA_AAA_DIAMETER_ACCESS {
|
|
NAME Diameter Access Support
|
|
SYNOPSIS If specified, the foreign agent will use Diameter access-request \
|
|
support. Values are enabled(1) and disabled(0)
|
|
TYPE char *
|
|
DEFAULT "disabled"
|
|
}
|
|
|
|
Parameter MIPFA_AAA_DIAMETER_ACCESS_ADDRESS {
|
|
NAME Diameter Access server address
|
|
SYNOPSIS Diameter access server address. The address of the Diameter server\
|
|
the foreign agent should send its access-requests to.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_AAA_DIAMETER_ACCESS_PORT {
|
|
NAME Diameter Access server port
|
|
SYNOPSIS Diameter access server port The port used on the Diameter access\
|
|
server
|
|
TYPE char *
|
|
DEFAULT "1812"
|
|
}
|
|
|
|
Parameter MIPFA_AAA_DIAMETER_ACCESS_REQUIRE {
|
|
NAME Diameter Access Required
|
|
SYNOPSIS This key specifies whether or not MN-AAA is required to be \
|
|
present in the registration request.
|
|
TYPE char *
|
|
DEFAULT "false"
|
|
}
|
|
|
|
Parameter MIPFA_AAA_DIAMETER_ACCESS_TIME_INTERVAL {
|
|
NAME Diameter Access Time Interval
|
|
SYNOPSIS If specified, specifies that timeout in seconds that may elapse \
|
|
before attempting a new AAA authentication, given that the \
|
|
mobile node provides other authentication credentials \
|
|
(such as MN-FA authentication extension). If not specified, or \
|
|
set to "0", the foreign agent will always do AAA \
|
|
authentication when a AAA extension is present.
|
|
TYPE char *
|
|
DEFAULT "0"
|
|
}
|
|
|
|
Parameter MIPFA_AAA_DIAMETER_ACCESS_REALM {
|
|
NAME Diameter Destination Realm
|
|
SYNOPSIS Specifies the destination realm used when sending access-requsts \
|
|
to the Diameter servers. I.e. "windriver.com"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_AAA_DIAMETER_ACCESS_HOSTNAME {
|
|
NAME Diameter Destination Hostname
|
|
SYNOPSIS This configuration item specifies the optional destination \
|
|
hostname parameter which may be attached to all outgoing \
|
|
access-requests to the Diameter servers. I.e. \
|
|
"diameter.windriver.com"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_AAA_DIAMETER_ACCESS_FA_HA_SPI {
|
|
NAME Diameter Foreign-Home Key Generation
|
|
SYNOPSIS This configuration item specifies the SPI to be used for \
|
|
key generation of the security association between the \
|
|
foreign agent and home agent. If this entry is specified, \
|
|
and set to a value different from 0, dynamic key generation \
|
|
will be used in order to generate the FA-HA key during mobile \
|
|
node AAA authentication.
|
|
TYPE char *
|
|
DEFAULT "0"
|
|
}
|
|
|
|
Parameter MIPFA_AAA_RADIUS_ACCESS {
|
|
NAME RADIUS Access Support
|
|
SYNOPSIS If specified, the foreign agent will use RADIUS access-request \
|
|
support. Values are enabled(1) and disabled(0)
|
|
TYPE char *
|
|
DEFAULT "disabled"
|
|
}
|
|
|
|
Parameter MIPFA_AAA_RADIUS_ACCESS_ADDRESS {
|
|
NAME RADIUS Access server address
|
|
SYNOPSIS Radius access server address. The address of the RADIUS server\
|
|
the foreign agent should send its access-requests to.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_AAA_RADIUS_ACCESS_PORT {
|
|
NAME RADIUS Access server port
|
|
SYNOPSIS Radius access server port The port used on the RADIUS access\
|
|
server
|
|
TYPE char *
|
|
DEFAULT "1812"
|
|
}
|
|
|
|
Parameter MIPFA_AAA_RADIUS_ACCESS_SECRET {
|
|
NAME RADIUS Access server secret
|
|
SYNOPSIS Radius access server secret This is the secret required to\
|
|
be used to gain access to the RADIUS server.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_AAA_RADIUS_ACCESS_REQUIRE {
|
|
NAME RADIUS Access Required
|
|
SYNOPSIS This key specifies whether or not MN-AAA is required to be \
|
|
present in the registration request.
|
|
TYPE char *
|
|
DEFAULT "false"
|
|
}
|
|
|
|
Parameter MIPFA_AAA_RADIUS_ACCESS_TIME_INTERVAL {
|
|
NAME RADIUS Access Time Interval
|
|
SYNOPSIS If specified, specifies that timeout in seconds that may elapse \
|
|
before attempting a new AAA authentication, given that the \
|
|
mobile node provides other authentication credentials \
|
|
(such as MN-FA authentication extension). If not specified, or \
|
|
set to "0", the foreign agent will always do AAA \
|
|
authentication when a AAA extension is present.
|
|
TYPE char *
|
|
DEFAULT "0"
|
|
}
|
|
|
|
Parameter MIPFA_AAA_RADIUS_ACCOUNTING {
|
|
NAME RADIUS Accounting Support
|
|
SYNOPSIS If enabled, the foreign agent will send accounting information.\
|
|
to the specified RADIUS server. Values are true(1) and \
|
|
false(0)
|
|
TYPE char *
|
|
DEFAULT "false"
|
|
}
|
|
|
|
Parameter MIPFA_AAA_RADIUS_ACCOUNTING_ADDRESS {
|
|
NAME RADIUS Accounting server address
|
|
SYNOPSIS Radius accounting server address. The address of the RADIUS \
|
|
server the foreign agent should send its accounting to.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_AAA_RADIUS_ACCOUNTING_PORT {
|
|
NAME RADIUS Accounting server port
|
|
SYNOPSIS Radius accounting server port The port used on the RADIUS \
|
|
accounting server
|
|
TYPE char *
|
|
DEFAULT "1813"
|
|
}
|
|
|
|
Parameter MIPFA_AAA_RADIUS_ACCOUNTING_SECRET {
|
|
NAME RADIUS Accounting server secret
|
|
SYNOPSIS Radius accounting server secret This is the secret required to\
|
|
be used to gain access to the RADIUS server.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_AAA_RADIUS_LOCAL_ADDRESS {
|
|
NAME RADIUS local address
|
|
SYNOPSIS Radius local address. The address we will bind locally to \
|
|
prior to communicating with any RADIUS server.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
|
|
Parameter MIPFA_LLH_NBR_IP_LIST {
|
|
NAME Low Latency Handoff neighbor address
|
|
SYNOPSIS List of LLH neighbors known to this foreign agent. Multiple \
|
|
neighbors may be specified separated by a semicolon, and for \
|
|
each neighbor you must specify the solicit/timeout values used \
|
|
for this particular host. <address/network>=<solicit/advertise> \
|
|
E.g. "10.1.2.45=10/20;10.2.2.0/24=20/40"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_LLH_NBR_BSSID_LIST {
|
|
NAME Low Latency Handoff neighbor BSSID
|
|
SYNOPSIS List of LLH neighbor BSSID's known to this foreign agent. Multiple \
|
|
neighbors may be specified separated by a semicolon, and for \
|
|
each neighbor you must specify IP address this particular BSSID \
|
|
corresponds to. <bssid>=<ip address>. E.g. \
|
|
"1111=10.1.2.45;1112=10.2.2.1"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
|
|
Parameter MIPFA_HA_SA_ADDRESS_LIST {
|
|
NAME Foreign - Home security association list
|
|
SYNOPSIS Security associations to use between FA and HA. This parameter \
|
|
is specified for each HA in the form of \
|
|
"<HA address>[/<prefix>]=<SPI>", each separated from the other \
|
|
by a semicolon. Set "<HA address>" to "any" to enable \
|
|
foreign-home authentication to all home agents. If the HA IP \
|
|
address is not found and no "any" entry exists, no foreign-home \
|
|
authentication will be used. For example, setting \
|
|
"10.1.2.42=1002" enables foreign-home authentication using \
|
|
SPI 1002 between this FA and HA using IP Address 10.1.2.42. \
|
|
Setting "any=1002" enables foreign-home authentication to \
|
|
all home agents using SPI 1002. Setting "10.1.2.0/24=1004" \
|
|
indicates that all home agents in the 10.1.2.0/24 network \
|
|
should be using SPI 1004.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_HA_SA_LOOKUP_REQUIRE {
|
|
NAME Foreign - Home security association reverse lookup
|
|
SYNOPSIS Reverse lookup any foreign-home security association used \
|
|
in communication with the home agent and verify that the SPI \
|
|
is indeed the SPI that should have been used, and not just that \
|
|
the calculated hash is correct.
|
|
TYPE char *
|
|
DEFAULT "0"
|
|
}
|
|
|
|
|
|
Parameter MIPFA_FA_SA_ADDRESS_LIST {
|
|
NAME Foreign - Foreign security association list
|
|
SYNOPSIS Security Associations to use between FA and FA. This parameter \
|
|
is specified for each FA in the form of \
|
|
"<FA address>[/<prefix>]=<SPI>", each separated from the other \
|
|
by a semicolon. Set "<FA address>" to "any" to enable \
|
|
foreign-foreign authentication to all foreign agents. If the \
|
|
FA IP address is not found and no "any" entry exists, no \
|
|
foreign-foreign authentication will be used. For example, \
|
|
setting "10.1.2.42=1002" enable foreign-foreign authentication \
|
|
using SPI 1002 between this FA and FA using IP Address \
|
|
10.1.2.42. Setting "any=1002" enables foreign-foreign \
|
|
authentication to all foreign agents using SPI 1002. Setting \
|
|
"10.1.1.0/24=1002" indicates that the entire network \
|
|
10.1.1.0/24 should be using 1002 SPI.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_SPI_SECRET_LIST {
|
|
NAME SPI-Secret List
|
|
SYNOPSIS List of Security Parameter Index (SPI). Foreign agents can \
|
|
configure multiple SPIs for use with many different home \
|
|
agents. Each SPI have exactly one secret. The secret length \
|
|
may be up to 16 bytes and need not be printable. The SPI is \
|
|
specifed in the form of "<SPI>=<value>", each separated \
|
|
from the other by a semicolon. E.g. "1000=test0", \
|
|
"1000=test0;1001=test1".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_IF_ADDRESS_LIST {
|
|
NAME Interface FA address
|
|
SYNOPSIS Interface FA address in the form of "<ifname>=<address>", \
|
|
each separated from the other by a semicolon. Set to \
|
|
"0.0.0.0" to read IPv4 address at boot. If set to \
|
|
"255.255.255.255", no RtAdv will be sent but registration \
|
|
replies will be processed if matching a sent request. \
|
|
E.g., "eth0=0.0.0.0".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_IF_ADV_INTERVAL_LIST {
|
|
NAME RtAdv interval
|
|
SYNOPSIS The interval (in seconds) at which the agent will send router \
|
|
advertisements on this interface specified in the form of \
|
|
"<ifname>=<value>", each separated from the other by a \
|
|
semicolon. If set to 0, the agent will not send any router \
|
|
advertisements, also, none of the otheradv_ sysvars need \
|
|
to be set. The default value of 10 is good for testing \
|
|
purposes, whereas the RFC suggests about a value of a third \
|
|
of the ICMP router advertisement lifetime. This value \
|
|
can be set to 0 or high if mobile nodes have other means of \
|
|
detecting entry to new subnets, such as wireless AP \
|
|
indication. E.g. "eth0=10".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_IF_ADV_ADDRESS_LIST {
|
|
NAME RtAdv destination IP address
|
|
SYNOPSIS Specifies the destination address of outgoing router \
|
|
advertisement messages from the agent. This parameter is \
|
|
configurable on a per-interface basis in the form of \
|
|
"<ifname>=<value>", each separated from the other by a \
|
|
semicolon. E.g. "eth0=224.0.0.11".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_IF_ADV_LIFETIME_LIST {
|
|
NAME RtAdv lifetime
|
|
SYNOPSIS Specifies the lifetime (in seconds) of advertisement \
|
|
messages from the agent. This parameter is configurable on \
|
|
a per-interface basis in the form of "<ifname>=<value>", \
|
|
each separated from the other by a semicolon. E.g. "eth0=300".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_IF_CHALLENGE_LIST {
|
|
NAME Interface Challenge
|
|
SYNOPSIS Enable(1)/disable(0) RFC3012 challenges for an interface. \
|
|
This parameter is configurable on a per-interface basis \
|
|
in the form of "<ifname>=<value>", each separated from the \
|
|
other by a semicolon. E.g. "eth0=1".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_IF_MN_AUTH_ENABLED_LIST {
|
|
NAME Interface Mobile Node authentication
|
|
SYNOPSIS Enable(1)/Disable(0) forcing of mobile nodes to use \
|
|
Mobile-Foreign authentication. This parameter is configurable \
|
|
on a per-interface basis in the form of "<ifname>=<value>", \
|
|
each separated from the other by a semicolon. E.g. "eth0=0".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_IF_LLH_PRE_ENABLED_LIST {
|
|
NAME Enable pre-registration
|
|
SYNOPSIS Enables(1) or Disables(0) PRE-REGISTRATION Low Latency \
|
|
Handoffs for an interface. This parameter is configurable \
|
|
on a per-interface basis in the form of "<ifname>=<value>", \
|
|
each separated from the other by a semicolon. E.g. "eth0=1".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_IF_LLH_POST_ENABLED_LIST {
|
|
NAME Enable post-registration
|
|
SYNOPSIS Enables(1) or Disables(0) POST-REGISTRATION Low Latency \
|
|
Handoffs for an interface. This parameter is configurable \
|
|
on a per-interface basis in the form of "<ifname>=<value>", \
|
|
each separated from the other by a semicolon. E.g. "eth0=0".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_IF_LLH_BET_LIFETIME_LIST {
|
|
NAME BET registration lifetime
|
|
SYNOPSIS Specifies the default value of the BET lifetime when POST \
|
|
registration is in effect. The BET lifetime is the value the \
|
|
FA will try to negotiate for the BET tunnel, and it is also \
|
|
used as the default value when the tunnel lifetime is being \
|
|
extended. This parameter is configurable on a per-interface \
|
|
basis in the form of "<ifname>=<value>", each separated \
|
|
from the other by a semicolon. E.g. "eth0=5"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_IF_NAT_T_ENABLED_LIST {
|
|
NAME Enable NAT-T
|
|
SYNOPSIS Enables or disables NAT Traversal according to RFC3519. \
|
|
This parameter is configurable on a per-interface basis \
|
|
in the form of "<ifname>=<value>", each separated from the \
|
|
other by a semicolon. E.g. "eth0=1".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_IF_FORCED_NAT_T_ENABLED_LIST {
|
|
NAME Enable forced NAT-T
|
|
SYNOPSIS Enables forcing of NAT traversal (RFC 3519), regardless \
|
|
what the home agent NAT detection decides. This parameter \
|
|
is configurable on a per-interface basis in the form of \
|
|
"<ifname>=<value>", each separated from the other by a \
|
|
semicolon. E.g. "eth0=0"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_IF_NAT_T_KEEPALIVE_LIST {
|
|
NAME NAT-T keepalive
|
|
SYNOPSIS Decides the keepalive timeout (in seconds) to use for \
|
|
NAT Traversal ICMP keepalive messages in order to maintain \
|
|
a NAT device UDP port mapping. This parameter is \
|
|
configured on a per-interface basis in the form of \
|
|
"<ifname>=<timeout>", each separated from the other by a \
|
|
semicolon. E.g. "eth0=120"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_IF_NAT_T_TUNNEL_TYPE_LIST {
|
|
NAME NAT-T forced tunnel type
|
|
SYNOPSIS Allows for specifying a different tunnel type if NAT \
|
|
traversal is used. Ordinarily, the tunnel type specified \
|
|
by the mobile node is used, but the foreign agent may \
|
|
override it for NAT Traversal tunneling, if for example \
|
|
only IPIP is specified to work. Allowed values are "min", \
|
|
"gre" and "ipi". If not specified or empty, the mobile \
|
|
nodes configuration will take presedence. This parameter is \
|
|
configured on a per-interface basis in the form of \
|
|
"<ifname>=<type>", each separated from the other by a \
|
|
semicolon. E.g. "eth0=ipip"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_IF_TUNNEL_REVERSE_LIST {
|
|
NAME Interface Reverse Tunneling
|
|
SYNOPSIS Disabled(0)/Optional(1)/Required(2) usage of reverse \
|
|
tunneling for an interface. If it is disabled, any node \
|
|
trying to request reverse tunneling will be disallowed. If \
|
|
optional, the node itself will be allowed to decide. If \
|
|
required the reverse tunneling bit must be set. This \
|
|
parameter can be configured on a per-interface basis in \
|
|
the form of "<ifname>=<value>", each separated from the \
|
|
other by a semicolon. E.g. "eth0=1".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_IF_TUNNEL_REORDERING_LIST {
|
|
NAME Interface Tunnel Reordering
|
|
SYNOPSIS Disabled(0)/Enabled(1) tunnel reordering. When enabled, any \
|
|
tunneltype such as GRE that supports it will guarantee in-order\
|
|
packet delivery. Syntax is "<ifname>=<value>", and it can \
|
|
be configured on an interface basis, each separated by a \
|
|
semicolon. E.g. "eth0=disabled;eth1=enabled"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_IF_IPIP_TUNNEL_ENABLED_LIST {
|
|
NAME Interface IPIP tunneling
|
|
SYNOPSIS Enable(1)/Disable(0) usage of IPIP tunneling for an interface. \
|
|
This parameter is configurable on a per-interface basis \
|
|
in the form of "<ifname>=<value>", each separated from the \
|
|
other by a semicolon. E.g. "eth0=1".
|
|
TYPE char *
|
|
DEFAULT "1"
|
|
}
|
|
|
|
Parameter MIPFA_IF_GRE_TUNNEL_ENABLED_LIST {
|
|
NAME Interface GRE tunneling
|
|
SYNOPSIS Enable(1)/Disable(0) usage of GRE tunneling for an interface. \
|
|
This parameter is configurable on a per-interface basis \
|
|
in the form of "<ifname>=<value>", each separated from the \
|
|
other by a semicolon. E.g. "eth0=1".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_IF_MINENC_TUNNEL_ENABLED_LIST {
|
|
NAME Interface MIN Encap tunneling
|
|
SYNOPSIS Enable(1)/Disable(0) usage of Minimal encapsulation \
|
|
tunneling for an interface. This parameter is configurable \
|
|
on a per-interface basis in the form of "<ifname>=<value>", \
|
|
each separated from the other by a semicolon. E.g. "eth0=1".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
|
|
Parameter MIPFA_IF_REVOCATION_ENABLED_LIST {
|
|
NAME Revocation Support
|
|
SYNOPSIS Enable(1)/Disable(0) usage of registration revocation \
|
|
for an interface. This parameter is configurable \
|
|
on a per-interface basis in the form of "<ifname>=<value>", \
|
|
each separated from the other by a semicolon. E.g. "eth0=1".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPFA_IF_REVOCATION_INFORM_LIST {
|
|
NAME Revocation Inform configuration Support
|
|
SYNOPSIS Disable(0)/Optional(1)/Require(2) that a mobile node be \
|
|
informed by a registration revocation. If 0, the mobile node \
|
|
will never be notified. If 1, the foreign agent leaves it \
|
|
to the home agent to decide. If 2, it will always inform. This \
|
|
parameter is configurable on a per-interface basis in the form \
|
|
of "<ifname>=<value>", each separated from the other by a \
|
|
semicolon. E.g. "eth0=1".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
#endif
|