123 lines
4.9 KiB
Mathematica
123 lines
4.9 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_IPMIPPM
|
|
|
|
Component INCLUDE_IPMIPPM {
|
|
NAME IPv4 Proxy Mobility Client
|
|
SYNOPSIS IPv4 Proxy Mobility Client
|
|
MODULES ipmippm.o
|
|
REQUIRES INCLUDE_IPCOM INCLUDE_IPNET INCLUDE_IPMIP4 INCLUDE_IPMIPMN
|
|
CONFIGLETTES ipmippm_config.c
|
|
_CHILDREN FOLDER_MOBILITY_PM
|
|
CFG_PARAMS MIPPM_INTERFACES \
|
|
MIPPM_TUNNEL_TYPE_ENUM \
|
|
MIPPM_HOME_AGENT_ENUM
|
|
}
|
|
|
|
Component INCLUDE_IPMIPPM_FEATURE_EXTENSION {
|
|
NAME IPv4 Proxy Mobile Client Feature Extension Registration Hook
|
|
SYNOPSIS IPv4 Proxy Mobile Client Feature Extension allows you provide \
|
|
an additional registration hook for registration of \
|
|
external functions.
|
|
REQUIRES INCLUDE_IPMIPPM
|
|
_CHILDREN FOLDER_MOBILITY_PM
|
|
CFG_PARAMS MIPPM_FEATURE_INITIALIZATION_HOOK
|
|
}
|
|
|
|
Component INCLUDE_IPMIPPM_PMIPV4_DHCP {
|
|
NAME IPv4 Proxy Mobility Client PMIPv4 DHCP Interoperability
|
|
SYNOPSIS IPv4 Proxy Mobility Client PMIPv4 DHCP Support includes \
|
|
the communication with the integrated DHCP support in the \
|
|
foreign agent
|
|
REQUIRES INCLUDE_IPMIPPM
|
|
_CHILDREN FOLDER_MOBILITY_PM
|
|
CFG_PARAMS MIPPM_PMIPV4_DHCP_CLIENT_PORT_ENUM
|
|
}
|
|
|
|
Component INCLUDE_IPMIPPM_CMD {
|
|
NAME IPv4 Proxy Mobility Client IPCOM commands
|
|
SYNOPSIS Mobile IPv4 Proxy Mobility IPCOM commands
|
|
MODULES ipmippm_cmd_pm.o
|
|
_CHILDREN FOLDER_MOBILITY_PM
|
|
REQUIRES INCLUDE_IPCOM_SHELL_CMD INCLUDE_IPMIPPM
|
|
}
|
|
|
|
Parameter MIPPM_FEATURE_INITIALIZATION_HOOK {
|
|
NAME Proxy Mobile Client Feature Initialization Hook
|
|
SYNOPSIS This is the function hook that you may define in order to \
|
|
register extra functional extensions to the Proxy Mobile Client
|
|
TYPE FUNCPTR
|
|
DEFAULT your_function_here
|
|
}
|
|
|
|
Parameter MIPPM_PMIPV4_DHCP_CLIENT_PORT_ENUM {
|
|
NAME Proxy Mobility Client PMIPv4 DHCP communication port
|
|
SYNOPSIS This parameter specifies what port the proxy mobility client \
|
|
uses for communication. Syntax is <interface>=<client port>. For example \
|
|
"eth0=434"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPPM_INTERFACES {
|
|
NAME Proxy Mobile Client Interface list
|
|
SYNOPSIS Space-separated list of network interface which should be \
|
|
managed by the Proxy Mobility Client \
|
|
E.g., "eth0 eth1"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIPPM_TUNNEL_TYPE_ENUM {
|
|
NAME Proxy Mobile Client Tunnel Type
|
|
SYNOPSIS The type of tunnel negotiated between the client and \
|
|
foreign agent is chosen by setting this configuration \
|
|
option to "ipip", "gre" or "min" for IPIP, GRE or Minimal \
|
|
Encapsulation respectively. If the home agent does not \
|
|
support GRE or MIN, IPIP will be tried. If IPIP is not \
|
|
supported as well, the registration operation will fail and \
|
|
the mobile node must be reconfigured. Syntax for this \
|
|
parameter is <interface>=<tunnel type>. For example \
|
|
"eth0=gre"
|
|
TYPE char *
|
|
DEFAULT "ipip"
|
|
}
|
|
|
|
Parameter MIPPM_HOME_AGENT_ENUM {
|
|
NAME Proxy Mobile Client Home Agent IPv4 Address
|
|
SYNOPSIS The default IPv4 address of the mobile node home agent, \
|
|
which is used unless another is specified in the registration \
|
|
trigger. The syntax for this parameter is \
|
|
<interface>=<IPv4 address>. For example "eth0=10.1.2.3"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
#endif
|