570 lines
23 KiB
Mathematica
570 lines
23 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
|
|
--------------------
|
|
01b,14jul08,tlu Fix a module name to fix the component greyed out in WB
|
|
01i,11may08,jho created.
|
|
*/
|
|
|
|
#ifdef _WRS_CONFIG_COMPONENT_IPMIP6MN
|
|
|
|
Component INCLUDE_IPMIP6MN {
|
|
NAME IPv6 Mobile Node
|
|
SYNOPSIS IPv6 Mobile Node
|
|
REQUIRES INCLUDE_IPCOM INCLUDE_IPCOM_USE_INET6 INCLUDE_IPMIP6 SELECT_IPMIP6MN
|
|
MODULES ipmip6mn.o
|
|
CONFIGLETTES ipmip6mn_config.c
|
|
CFG_PARAMS MIP6MN_NETWORK_ENUM \
|
|
MIP6MN_INTERFACES \
|
|
MIP6MN_HOMEAGENTS \
|
|
MIP6MN_HOME_ADDRESS \
|
|
MIP6MN_LIFETIME \
|
|
MIP6MN_REG_TIMEOUT \
|
|
MIP6MN_NAI_MN
|
|
}
|
|
|
|
Component INCLUDE_IPMIP6MN_CMD {
|
|
NAME IPv6 Mobile Node IPCOM commands
|
|
SYNOPSIS IPv6 Mobile Node IPCOM commands.
|
|
MODULES ipmip6mn_cmd_mn6.o
|
|
REQUIRES INCLUDE_IPCOM_SHELL_CMD INCLUDE_IPMIP6MN
|
|
}
|
|
|
|
Selection SELECT_IPMIP6MN_NEMO {
|
|
NAME Ipv6 Mobile Node Mobile Router Features
|
|
SYNOPSIS Ipv6 Mobile Node Mobile Router Features
|
|
COUNT 0-
|
|
CHILDREN INCLUDE_IPMIP6MN_NEMO \
|
|
INCLUDE_IPMIP6MN_NEMO_RADVD
|
|
DEFAULTS INCLUDE_IPMIP6MN_NEMO \
|
|
INCLUDE_IPMIP6MN_NEMO_RADVD
|
|
}
|
|
|
|
Selection SELECT_IPMIP6MN_DUAL_STACK_NEMO {
|
|
NAME Ipv6 Mobile Node Dual Stack Mobile Router Features
|
|
SYNOPSIS Ipv6 Mobile Node Dual Stack Mobile Router Features
|
|
COUNT 0-
|
|
CHILDREN INCLUDE_IPMIP6MN_DUAL_STACK_NEMO \
|
|
INCLUDE_IPMIP6MN_DUAL_STACK_NEMO_DHCP_SERVER
|
|
DEFAULTS INCLUDE_IPMIP6MN_DUAL_STACK_NEMO \
|
|
INCLUDE_IPMIP6MN_DUAL_STACK_NEMO_DHCP_SERVER
|
|
}
|
|
|
|
Selection SELECT_IPMIP6MN {
|
|
NAME Ipv6 Mobile Node Components
|
|
SYNOPSIS Ipv6 Mobile Node Components
|
|
COUNT 0-
|
|
REQUIRES INCLUDE_IPMIP6MN
|
|
_CHILDREN FOLDER_MOBILITY_V6
|
|
CHILDREN INCLUDE_IPMIP6MN \
|
|
INCLUDE_IPMIP6MN_CMD \
|
|
INCLUDE_IPMIP6MN_IPSEC \
|
|
INCLUDE_IPMIP6MN_DUAL_STACK \
|
|
INCLUDE_IPMIP6MN_SERVICE_SELECTION \
|
|
INCLUDE_IPMIP6MN_SERVICE_VENDOR_EXTENSION \
|
|
INCLUDE_IPMIP6MN_MOBILE_PREFIX_RENUMBER_SUPPORT \
|
|
INCLUDE_IPMIP6MN_FEATURE_EXTENSION \
|
|
SELECT_IPMIP6MN_NEMO \
|
|
SELECT_IPMIP6MN_DUAL_STACK_NEMO
|
|
DEFAULTS INCLUDE_IPMIP6MN \
|
|
INCLUDE_IPMIP6MN_CMD \
|
|
INCLUDE_IPMIP6MN_SERVICE_SELECTION \
|
|
INCLUDE_IPMIP6MN_DUAL_STACK
|
|
}
|
|
|
|
Component INCLUDE_IPMIP6MN_FEATURE_EXTENSION {
|
|
NAME IPv6 Mobile Node Feature Extension
|
|
SYNOPSIS This feature should be included if one wants to add \
|
|
a new feature to the mobile node v6, and have the \
|
|
feature hook being registered during initialization.
|
|
REQUIRES INCLUDE_IPMIP6MN
|
|
CFG_PARAMS MIP6MN_FEATURE_INITIALIZATION_HOOK
|
|
}
|
|
|
|
|
|
Component INCLUDE_IPMIP6MN_SERVICE_SELECTION {
|
|
NAME IPv6 Mobile Node Service Selection Support
|
|
SYNOPSIS IPv6 Mobile Node Service Selection Support
|
|
REQUIRES INCLUDE_IPMIP6MN
|
|
CFG_PARAMS MIP6MN_SERVICE_SELECTION
|
|
}
|
|
|
|
Component INCLUDE_IPMIP6MN_SERVICE_VENDOR_EXTENSION {
|
|
NAME IPv6 Mobile Node Generic Vendor Extension Support
|
|
SYNOPSIS IPv6 Mobile Node Generic Vendor Extension Support
|
|
REQUIRES INCLUDE_IPMIP6MN
|
|
CFG_PARAMS MIP6MN_SERVICE_VENDOR_EXTENSION_ENUM
|
|
}
|
|
|
|
|
|
Component INCLUDE_IPMIP6MN_MOBILE_PREFIX_RENUMBER_SUPPORT {
|
|
NAME IPv6 Mobile Node Mobile Prefix Renumbering Support
|
|
SYNOPSIS IPv6 Mobile Node Mobile Prefix Renumbering Support
|
|
REQUIRES INCLUDE_IPMIP6MN
|
|
CFG_PARAMS MIP6MN_MOBILE_PREFIX_RENUMBER_FROM_CONFIGURED \
|
|
MIP6MN_MOBILE_PREFIX_RENUMBER_FROM_INTERFACE
|
|
}
|
|
|
|
Component INCLUDE_IPMIP6MN_IPSEC {
|
|
NAME IPv6 Mobile Node Security Parameters
|
|
SYNOPSIS IPv6 Mobile Node Security Parameters
|
|
REQUIRES INCLUDE_IP_SECURITY INCLUDE_IPMIP6MN
|
|
CFG_PARAMS MIP6MN_SA_AUTH_MODE \
|
|
MIP6MN_SA_AUTH_KEY MIP6MN_SA_ENC_MODE MIP6MN_SA_ENC_KEY \
|
|
MIP6MN_SA_AUTH_MODE_LIST MIP6MN_SA_AUTH_KEY_LIST \
|
|
MIP6MN_SA_ENC_MODE_LIST MIP6MN_SA_ENC_KEY_LIST \
|
|
MIP6MN_IPSEC_MH_ENABLED MIP6MN_IPSEC_MH_SPI_IN \
|
|
MIP6MN_IPSEC_MH_SPI_OUT MIP6MN_IPSEC_PAYLOAD_ENABLED \
|
|
MIP6MN_IPSEC_PAYLOAD_SPI_IN MIP6MN_IPSEC_PAYLOAD_SPI_OUT
|
|
}
|
|
|
|
Component INCLUDE_IPMIP6MN_DUAL_STACK {
|
|
NAME IPv6 Mobile Node Dual Stack Support
|
|
SYNOPSIS IPv6 Mobile Node Dual Stack Support
|
|
REQUIRES INCLUDE_IPMIP6MN
|
|
CFG_PARAMS MIP6MN_INET_HOMEADDRESS \
|
|
MIP6MN_INET_FORCEIPV4UDPENCAPSULATION \
|
|
MIP6MN_INET_IPV4UDPENCAPSULATIONNATTIMEOUT
|
|
}
|
|
|
|
Component INCLUDE_IPMIP6MN_DUAL_STACK_NEMO {
|
|
NAME IPv6 Mobile Node Dual Stack Mobile Router Support
|
|
SYNOPSIS IPv6 Mobile Node Dual Stack Mobile Router Support
|
|
REQUIRES INCLUDE_IPMIP6MN_DUAL_STACK SELECT_IPMIP6MN_DUAL_STACK_NEMO
|
|
CFG_PARAMS MIP6MN_NEMO_INET_INGRESS
|
|
}
|
|
|
|
Component INCLUDE_IPMIP6MN_DUAL_STACK_NEMO_DHCP_SERVER {
|
|
NAME IPv6 Mobile Node Dual Stack Mobile Router DHCP Server
|
|
SYNOPSIS IPv6 Mobile Node NEMO Dual Stack DHCP Server enabled the \
|
|
internal DHCP server for providing nodes connected to the \
|
|
ingress interface with INET addresses using DHCP. Unless \
|
|
you implement your own solution, this option should be \
|
|
enabled when using Dual Stack Mobile Router support.
|
|
REQUIRES INCLUDE_IPMIP6MN_DUAL_STACK INCLUDE_IPMIP6MN_DUAL_STACK_NEMO
|
|
CFG_PARAMS MIP6MN_NEMO_INET_DHCP_SERVER_OFFER_TIMEOUT \
|
|
MIP6MN_NEMO_INET_DHCP_SERVER_OPTION
|
|
}
|
|
|
|
Component INCLUDE_IPMIP6MN_NEMO {
|
|
NAME IPv6 Mobile Node Mobile Router Support
|
|
SYNOPSIS IPv6 Mobile Node Mobile Router Support
|
|
REQUIRES INCLUDE_IPMIP6MN SELECT_IPMIP6MN_NEMO
|
|
CFG_PARAMS MIP6MN_NEMO_MODE \
|
|
MIP6MN_NEMO_INGRESS
|
|
}
|
|
|
|
Component INCLUDE_IPMIP6MN_NEMO_RADVD {
|
|
NAME IPv6 Mobile Node Mobile Router Router Advertisement Support
|
|
SYNOPSIS IPv6 Mobile Node Mobile Router Router Router Advertisement \
|
|
Support allows the Mobile Node to automatically configure \
|
|
RADVD on ingress interface. If this option is disabled, you \
|
|
will need to configure RADVD manually.
|
|
REQUIRES INCLUDE_IPMIP6MN_NEMO
|
|
CFG_PARAMS MIP6MN_NEMO_RADVD_MANAGED \
|
|
MIP6MN_NEMO_RADVD_OTHER
|
|
}
|
|
|
|
Component INCLUDE_IPMIP6MN_CMD {
|
|
NAME IPv6 Mobile Node IPCOM commands
|
|
SYNOPSIS IPv6 Mobile Node IPCOM commands.
|
|
MODULES ipmip6mn_cmd_mn6.o
|
|
REQUIRES INCLUDE_IPCOM_SHELL_CMD INCLUDE_IPMIP6MN
|
|
}
|
|
|
|
/* INCLUDE_IPMIP6MN configuration parameters */
|
|
Parameter MIP6MN_NETWORK_ENUM {
|
|
NAME Network enumeration
|
|
SYNOPSIS The mobile node configuration always start with the \
|
|
network enumeration. The network enumeration tells the \
|
|
system what configurations are available and should be \
|
|
activated.
|
|
TYPE char *
|
|
DEFAULT "windriver"
|
|
}
|
|
|
|
Parameter MIP6MN_INTERFACES {
|
|
NAME Interface list
|
|
SYNOPSIS The interface list specifies what interfaces \
|
|
should be used for a particular network configuration.The \
|
|
format of this configuration parameter is a comma separated \
|
|
list of interface names. E.g. "eth0,eth1"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6MN_HOMEAGENTS {
|
|
NAME Home Agent List
|
|
SYNOPSIS Specifies what home agents should be used for a particular \
|
|
network configuration in the form of a comma separated list \
|
|
of homeagents in the form \
|
|
"[<priority>/]<INET6 Home Agent>[/<INET Home Agent>]" If no \
|
|
home agents are specified, the Mobile Node will resort to \
|
|
Dynamic Home Agent Address Discovery (DHAAD). A home agent with \
|
|
higher priority is always used before one with lower. In the \
|
|
case of equal priorities it will be randomly decided. \
|
|
If DSMIPv6 is beingused, you may also specify an IPv4 address \
|
|
for the home agent for use with DSMIPv6 IPv4 care-of addresses. \
|
|
E.g. "5/3ffe:302:111:3::1;1=4/3ffe:302:111:3::6" \
|
|
DSMIPv6 example."5/3ffe:302:111:3::1/10.1.2.3"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6MN_HOME_ADDRESS {
|
|
NAME Home address
|
|
SYNOPSIS The address the mobile node has on this particular home \
|
|
network. The address is specified in two parts separated \
|
|
by "/". The first part is the IPv6 home address and the \
|
|
second the prefix length. E.g. "3ffe:302:111:3::4/64".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6MN_LIFETIME {
|
|
NAME Requested binding lifetime
|
|
SYNOPSIS Specifies the requested binding lifetime (in seconds) for \
|
|
this mobile node network. The binding lifetime is determined \
|
|
by the home agent, but it may never be larger than the value \
|
|
specified here. It determines how long a binding will live \
|
|
without having to be refreshed.
|
|
TYPE char *
|
|
DEFAULT "120"
|
|
}
|
|
|
|
Parameter MIP6MN_REG_TIMEOUT {
|
|
NAME Initial Registration Timeout
|
|
SYNOPSIS Specifies the amount of time (in milliseconds) to wait for \
|
|
the initial binding acknowledgement from the home agent. \
|
|
The initial binding acknowledgement may take additional time \
|
|
compared to subsequent ones, due to the requirement to \
|
|
verify address usability.
|
|
TYPE char *
|
|
DEFAULT "1500"
|
|
}
|
|
|
|
Parameter MIP6MN_SA_AUTH_MODE {
|
|
NAME Security association auth mode
|
|
SYNOPSIS Specifies the security association configuration that the \
|
|
mobile node should use for a particular mobile node and \
|
|
traffic.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6MN_SA_AUTH_KEY {
|
|
NAME Security association auth key
|
|
SYNOPSIS Specifies the security association configuration that the \
|
|
mobile node should use for a particular mobile node and \
|
|
traffic.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6MN_SA_ENC_MODE {
|
|
NAME Security association enc mode
|
|
SYNOPSIS Specifies the security association configuration that the \
|
|
mobile node should use for a particular mobile node and \
|
|
traffic.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6MN_SA_ENC_KEY {
|
|
NAME Security association enc key
|
|
SYNOPSIS Specifies the security association configuration that the \
|
|
mobile node should use for a particular mobile node and \
|
|
traffic.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6MN_SA_AUTH_MODE_LIST {
|
|
NAME Security association auth mode list
|
|
SYNOPSIS Specifies the security association configuration that the \
|
|
mobile node should use for a particular mobile node and \
|
|
traffic. This parameter is specified in the form of \
|
|
"<spi_value>=<value>", each separated from the other \
|
|
by a semicolon. E.g. "0=SHA1;1=PADL"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6MN_SA_AUTH_KEY_LIST {
|
|
NAME Security association auth key list
|
|
SYNOPSIS Specifies the security association configuration that the \
|
|
mobile node should use for a particular mobile node and \
|
|
traffic. This parameter is specified in the form of \
|
|
"<spi_value>=<value>", each separated from the other \
|
|
by a semicolon. E.g. "0=HMACSHA196;1=Private".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6MN_SA_ENC_MODE_LIST {
|
|
NAME Security association enc mode list
|
|
SYNOPSIS Specifies the security association configuration that the \
|
|
mobile node should use for a particular mobile node and \
|
|
traffic. This parameter is specified in the form of \
|
|
"<spi_value>=<value>", each separated from the other \
|
|
by a semicolon. E.g. "0=3DES;1=3DES".
|
|
TYPE char *
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6MN_SA_ENC_KEY_LIST {
|
|
NAME Security association enc key list
|
|
SYNOPSIS Specifies the security association configuration that the \
|
|
mobile node should use for a particular mobile node and \
|
|
traffic. This parameter is specified in the form of \
|
|
"<spi_value>=<value>", each separated from the other \
|
|
by a semicolon. E.g. "0=3DES-CBC".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6MN_IPSEC_MH_ENABLED {
|
|
NAME Enable mobile header signaling
|
|
SYNOPSIS Enable security for the Mobility Header signalling using \
|
|
IPSEC in transport mode. In order to provide this security, \
|
|
the MIP6MN_IPSEC_MH_SPI_IN and MIP6MN_IPSEC_MH_SPI_OUT \
|
|
security association must also be specified.
|
|
TYPE char *
|
|
DEFAULT "0"
|
|
}
|
|
|
|
Parameter MIP6MN_IPSEC_MH_SPI_IN {
|
|
NAME IPSec MH SPI In
|
|
SYNOPSIS Specifies the IPSec SPI In for Mobility Header signalling.
|
|
TYPE char *
|
|
DEFAULT "200"
|
|
}
|
|
|
|
Parameter MIP6MN_IPSEC_MH_SPI_OUT {
|
|
NAME IPSec MH SPI Out
|
|
SYNOPSIS Specifies the IPSec SPI In for Mobility Header signalling.
|
|
TYPE char *
|
|
DEFAULT "201"
|
|
}
|
|
|
|
Parameter MIP6MN_IPSEC_PAYLOAD_ENABLED {
|
|
NAME Enable payload data protection
|
|
SYNOPSIS Enable payload data protection for any data tunneled to \
|
|
and from the home agent using IPSEC. The SPI specified \
|
|
here MUST be different from those specified for Mobility \
|
|
Header Signalling Security. This is due to the fact that \
|
|
the Mobility Header Signalling Security is a static SA \
|
|
where the end points do not move upon movement, while the \
|
|
payload security is dependent on the CoA currently being \
|
|
used. In order to provide this security, the security \
|
|
association for MIP6MN_IPSEC_PAYLOAD_SPI_IN and \
|
|
MIP6MN_IPSEC_PAYLOAD_SPI_OUT must also be specified.
|
|
TYPE char *
|
|
DEFAULT "0"
|
|
}
|
|
|
|
Parameter MIP6MN_IPSEC_PAYLOAD_SPI_IN {
|
|
NAME IPSec Payload SPI In
|
|
SYNOPSIS Specifies the IPSec payload SPI In for payload data \
|
|
protection.
|
|
TYPE char *
|
|
DEFAULT "204"
|
|
}
|
|
|
|
Parameter MIP6MN_IPSEC_PAYLOAD_SPI_OUT {
|
|
NAME IPSec Payload SPI Out
|
|
SYNOPSIS Specifies the IPSec payload SPI Out for payload data \
|
|
protection.
|
|
TYPE char *
|
|
DEFAULT "205"
|
|
}
|
|
|
|
Parameter MIP6MN_NEMO_MODE {
|
|
NAME NEMO Mode
|
|
SYNOPSIS Specifies whether or not NEMO should run in explicit or \
|
|
implicit mode. Valid values are "explicit","implicit" and \
|
|
"disabled". If MIP6MN_NEMO_INGRESS has been configured, \
|
|
MIP6MN_NEMO_MODE will default to "explicit". If no nemo \
|
|
configuration is available, the nemo mode is always "disabled" \
|
|
regardless of setting.
|
|
TYPE char *
|
|
DEFAULT "explicit"
|
|
}
|
|
|
|
Parameter MIP6MN_NEMO_INGRESS {
|
|
NAME NEMO Ingress Interface Configuration
|
|
SYNOPSIS Specifies the INGRESS interfaces and their corresponding \
|
|
prefixes. Syntax is <interface name1>=<prefix1>/<prefixlen1>, \
|
|
<prefix2>/<prefixlen2>; <interface name2>=<prefix3>/<prefixlen3>
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6MN_NAI_MN {
|
|
NAME Mobile Node Network Access Identifier
|
|
SYNOPSIS The mobile node network access identifier provides the \
|
|
user identity of the connecting node to other mobility \
|
|
resources that the mobile node contacts. The format of the \
|
|
NAI should be user@domain.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6MN_NEMO_INET_INGRESS {
|
|
NAME INET DSMIPv6 NEMO Ingress Interface Configuration
|
|
SYNOPSIS Specifies the INET DSMIPV6 INGRESS interfaces and their corresponding \
|
|
inet prefixes. Syntax is <interface name1>=<prefix1>/<prefixlen1>, \
|
|
<prefix2>/<prefixlen2>; <interface name2>=<prefix3>/<prefixlen3>. \
|
|
For example eth0=10.1.2.0/24. If the address 0.0.0.0 is specified \
|
|
it will request the home agent to dynamically allocate a prefix.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6MN_NEMO_INET_DHCP_SERVER_OFFER_TIMEOUT {
|
|
NAME INET DSMIPV6 NEMO DHCP Server Offer Timeout
|
|
SYNOPSIS This item specifies the time interval in seconds the DHCP \
|
|
server will reserve an offered lease before making it \
|
|
available for other nodes to allocate.
|
|
TYPE char *
|
|
DEFAULT "10"
|
|
}
|
|
|
|
Parameter MIP6MN_NEMO_INET_DHCP_SERVER_OPTION {
|
|
NAME INET DSMIPV6 NEMO DHCP Server Options
|
|
SYNOPSIS This item defines the extra DHCP options that should be \
|
|
provided during DHCP negotiation. The syntax is \
|
|
<type>.<code>=<value>. <type> is one of bool,u8,u16,u32,ip,\
|
|
ip_pair and string. The type specifies how the following \
|
|
values should be parsed. Type string will not parse the value \
|
|
in any way, only add the entire value to the DHCP option. If \
|
|
more than one space separated value is provided, they will \
|
|
be added in an array fashion to the DHCP option. <code> is \
|
|
the DHCP option code as defined by IANA. For example \
|
|
"ip.6=10.1.2.3 10.2.3.3" will add a DNS server option with \
|
|
two servers.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6MN_INET_HOMEADDRESS {
|
|
NAME INET DSMIPV6 Homeaddress
|
|
SYNOPSIS Specify the IPv4 INET DSMIPv6 home address to be used by the mobile\
|
|
node. If the specified address is 0.0.0.0, the mobile node \
|
|
will request the home agent to dynamically allocate an \
|
|
address that the mobile node may use.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6MN_SERVICE_SELECTION {
|
|
NAME Service Selection
|
|
SYNOPSIS Specify the service selection that this mobile node should \
|
|
request
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6MN_NEMO_RADVD_MANAGED {
|
|
NAME NEMO RADVD Managed Flag
|
|
SYNOPSIS Enable or disable the MANAGED flag for RADVD.
|
|
TYPE char *
|
|
DEFAULT "false"
|
|
}
|
|
|
|
Parameter MIP6MN_NEMO_RADVD_OTHER {
|
|
NAME NEMO RADVD Other Config Flag
|
|
SYNOPSIS Enable or disable the Other configuration flag for RADVD.
|
|
TYPE char *
|
|
DEFAULT "false"
|
|
}
|
|
|
|
Parameter MIP6MN_MOBILE_PREFIX_RENUMBER_FROM_CONFIGURED {
|
|
NAME Mobile Prefix Renumber from Configuration
|
|
SYNOPSIS Enable or disable renumber from configuration functionality. \
|
|
If enabled, the mobile node will derive any new home addresses \
|
|
using the previously configured home address and the newly \
|
|
provided mobile prefix.
|
|
TYPE char *
|
|
DEFAULT "false"
|
|
}
|
|
|
|
Parameter MIP6MN_MOBILE_PREFIX_RENUMBER_FROM_INTERFACE {
|
|
NAME Mobile Prefix Renumber from Interface
|
|
SYNOPSIS Enable or disable renumber from configuration functionality. \
|
|
If enabled, the mobile node will derive any new home addresses \
|
|
by forming a home address based on an interface and the provided \
|
|
mobile prefix. Valid values are true, false or an interface \
|
|
name. If an interface has been specified, that interface will \
|
|
be used to form the address. Otherwise any currently available \
|
|
interface may be used.
|
|
TYPE char *
|
|
DEFAULT "false"
|
|
}
|
|
|
|
Parameter MIP6MN_FEATURE_INITIALIZATION_HOOK {
|
|
NAME Mobile Node Service Initialization Hook
|
|
SYNOPSIS This is the function hook that you may define in order to \
|
|
register extra functional extensions to the mobile node.\
|
|
extensions, this is the function you should change to point \
|
|
to your initialization routine.
|
|
TYPE FUNCPTR
|
|
DEFAULT your_function_here
|
|
}
|
|
|
|
Parameter MIP6MN_INET_FORCEIPV4UDPENCAPSULATION {
|
|
NAME Force INET DSMIPv6 UDP encapsulation
|
|
SYNOPSIS If set to "true", this configuration item will indicate to\
|
|
the mobile node that UDP encapsulation should be forced. If\
|
|
the home agent disallows forced UDP encapsulation, the \
|
|
mobile node will attempt registration without it after \
|
|
receiving the appropriate error message.
|
|
TYPE char *
|
|
DEFAULT "false"
|
|
}
|
|
|
|
Parameter MIP6MN_INET_IPV4UDPENCAPSULATIONNATTIMEOUT {
|
|
NAME INET DSMIPv6 UDP NAT Timeout Value
|
|
SYNOPSIS This parameter specifies in seconds for how long any NAT \
|
|
bindings is expected to survive. If the Mobile Node uses \
|
|
NAT to communicate with the Home Agent, this parameter \
|
|
will configure the maximum timeout the Mobile Node will \
|
|
wait before refreshing the binding.
|
|
TYPE char *
|
|
DEFAULT "110"
|
|
}
|
|
|
|
Parameter MIP6MN_SERVICE_VENDOR_EXTENSION_ENUM {
|
|
NAME Generic Vendor Extension Configuration
|
|
SYNOPSIS If configured, will add Vendor Extension options to the \
|
|
registration messages. The Generic vendor extension feature \
|
|
does not do anything beyond providing the information in the \
|
|
binding update. Extra features or functionalities acting upon \
|
|
the vendor extensions are beyond the current scope of this \
|
|
product. The format of the configuration parameter is a semi-colon\
|
|
separated list of <SMI Number>.<SubType>=<value1>[,<valueN>]. \
|
|
SMI Number is the IANA assigned SMI number. Subtype is the \
|
|
vendor specified subtype. Value is defined as a string, or as \
|
|
a comma separated array of hexadecimal numbers. The number of \
|
|
hexadecimal figures in the value will define how the value is \
|
|
interpreted. For example 0xaa is 1 byte, 0x00aa is two bytes, \
|
|
0x0000aa will be interpreted as a four byte value. Values \
|
|
larger than 1 byte will be converted to network byte order.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
#endif
|