814 lines
39 KiB
Mathematica
814 lines
39 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_IPMIP6HA
|
|
|
|
Component INCLUDE_IPMIP6HA {
|
|
NAME IPv6 Home Agent
|
|
SYNOPSIS IPv6 Home Agent
|
|
REQUIRES INCLUDE_IPCOM INCLUDE_IPCOM_USE_INET6 INCLUDE_IPMIP6 SELECT_IPMIP6HA
|
|
MODULES ipmip6ha.o
|
|
CONFIGLETTES ipmip6ha_config.c
|
|
CFG_PARAMS MIP6HA_LIFETIME_ENUM \
|
|
MIP6HA_INTERFACES \
|
|
MIP6HA_INTERFACE_ADDRESS_ENUM \
|
|
MIP6HA_REFRESH_ENUM \
|
|
MIP6HA_TUNNEL_IP6IP6_ENUM \
|
|
MIP6HA_BINDING_REVOCATION_MIN_DELAY_ENUM \
|
|
MIP6HA_BINDING_REVOCATION_MAX_RETRIES_ENUM
|
|
}
|
|
|
|
Component INCLUDE_IPMIP6HA_DUAL_STACK {
|
|
NAME IPv6 Home Agent Dual Stack Support
|
|
SYNOPSIS IPv6 Home Agent Dual Stack Support
|
|
REQUIRES INCLUDE_IPMIP6HA
|
|
CFG_PARAMS MIP6HA_INET_INTERFACE_ADDRESS_ENUM \
|
|
MIP6HA_INET_ACCEPT_FORCED_IPV4_UDP_ENCAPSULATION_REQUEST_ENUM \
|
|
MIP6HA_INET_FORCE_IPV4_UDP_ENCAPSULATION_ENUM \
|
|
MIP6HA_INET_IPV4_UDP_ENCAPSULATION_NAT_TIMEOUT \
|
|
MIP6HA_INET_TUNNEL_IPIP_ENUM \
|
|
MIP6HA_INET_TOPOLOGY_ADDRESS_RESERVATION \
|
|
MIP6HA_INET_POOL_ENUM \
|
|
MIP6HA_INET_ACL_HOMEADDRESS_ENUM \
|
|
MIP6HA_INET_ACL_POOL_ENUM \
|
|
MIP6HA_INET_ACL_LIMIT_HOMEADDRESS_ENUM \
|
|
MIP6HA_INET_ACL_LIMIT_PD_ENUM
|
|
}
|
|
|
|
Component INCLUDE_IPMIP6HA_MOBILE_ROUTER {
|
|
NAME IPv6 Home Agent Mobile Router Support
|
|
SYNOPSIS IPv6 Home Agent Mobile Router Support
|
|
REQUIRES INCLUDE_IPMIP6HA
|
|
CFG_PARAMS MIP6HA_MOBILE_ROUTER_ACL_PD_ENUM
|
|
}
|
|
|
|
|
|
Component INCLUDE_IPMIP6HA_MOBILE_ROUTER_DUAL_STACK {
|
|
NAME IPv6 Home Agent Mobile Router Dual Stack Support
|
|
SYNOPSIS IPv6 Home Agent Mobile Router Dual Stack Support
|
|
REQUIRES INCLUDE_IPMIP6HA_DUAL_STACK INCLUDE_IPMIP6HA_MOBILE_ROUTER
|
|
CFG_PARAMS MIP6HA_MOBILE_ROUTER_INET_ACL_PD_ENUM
|
|
}
|
|
|
|
|
|
Component INCLUDE_IPMIP6HA_LMA {
|
|
NAME IPv6 Home Agent LMA Support
|
|
SYNOPSIS IPv6 Home Agent LMA Support
|
|
REQUIRES INCLUDE_IPMIP6HA
|
|
CFG_PARAMS MIP6HA_LMA_TUNNEL_IP6IP6_ENUM \
|
|
MIP6HA_LMA_TUNNEL_GRE_ENUM \
|
|
MIP6HA_LMA_POOL_ENUM \
|
|
MIP6HA_LMA_ACL_PD_ENUM \
|
|
MIP6HA_LMA_ACL_POOL_ENUM \
|
|
MIP6HA_LMA_ACL_LIMIT_ENUM \
|
|
MIP6HA_LMA_MIN_DELAY_BEFORE_BCE_DELETE_ENUM \
|
|
MIP6HA_LMA_MAX_DELAY_BEFORE_NEW_BCE_ASSIGN_ENUM \
|
|
MIP6HA_LMA_TIMESTAMP_VALIDITY_WINDOW_ENUM \
|
|
MIP6HA_LMA_MOBILE_NODE_GENERATED_TIMESTAMP_IN_USE_ENUM \
|
|
MIP6HA_LMA_HEARTBEAT_ENABLED_ENUM \
|
|
MIP6HA_LMA_HEARTBEAT_INTERVAL_ENUM \
|
|
MIP6HA_LMA_MISSING_HEARTBEATS_ALLOWED_ENUM \
|
|
MIP6HA_LMA_MAG_ENUM \
|
|
MIP6HA_LMA_FIXED_MAG_LINKLOCAL_ADDRESS_ON_ALL_ACCESS_LINKS_ENUM \
|
|
MIP6HA_LMA_REVOKE_PREVIOUS_MAG_ENUM
|
|
}
|
|
|
|
Component INCLUDE_IPMIP6HA_LMA_DHCP_SERVER {
|
|
NAME IPv6 Home Agent LMA DHCP Server Support
|
|
SYNOPSIS IPv6 Home Agent LMA DHCP Server Support
|
|
REQUIRES INCLUDE_IPMIP6HA_LMA
|
|
CFG_PARAMS MIP6HA_LMA_DHCP_SERVER_SERVER_ENUM \
|
|
MIP6HA_LMA_DHCP_SERVER_SERVER_PREFERRED_ENUM \
|
|
MIP6HA_LMA_DHCP_SERVER_SERVER_VALID_ENUM
|
|
}
|
|
|
|
|
|
Component INCLUDE_IPMIP6HA_LMA_DUAL_STACK {
|
|
NAME IPv6 Home Agent LMA Dual Stack Support
|
|
SYNOPSIS IPv6 Home Agent LMA Dual Stack Support
|
|
REQUIRES INCLUDE_IPMIP6HA_DUAL_STACK INCLUDE_IPMIP6HA_LMA
|
|
CFG_PARAMS MIP6HA_LMA_INET_TUNNEL_IPIP_ENUM \
|
|
MIP6HA_LMA_INET_TUNNEL_GRE_ENUM \
|
|
MIP6HA_LMA_INET_TOPOLOGY_DHCP_OPTION_ENUM \
|
|
MIP6HA_LMA_INET_ACL_HOMEADDRESS_ENUM \
|
|
MIP6HA_LMA_INET_ACL_POOL_ENUM
|
|
}
|
|
|
|
Component INCLUDE_IPMIP6HA_LMA_DUAL_STACK_DHCP_SERVER {
|
|
NAME IPv6 Home Agent LMA Dual Stack Internal DHCP Server Support
|
|
SYNOPSIS IPv6 Home Agent LMA Dual Stack Internal DHCP Server includes \
|
|
the integrated DHCP server feature.
|
|
REQUIRES INCLUDE_IPMIP6HA_LMA_DUAL_STACK
|
|
CFG_PARAMS MIP6HA_LMA_INET_DHCP_SERVER_ENUM
|
|
}
|
|
|
|
|
|
Component INCLUDE_IPMIP6HA_FEATURE_EXTENSION {
|
|
NAME IPv6 Home Agent Feature Extension
|
|
SYNOPSIS This feature should be included if one wants to add \
|
|
a new feature to the home agent v6, and have the \
|
|
feature hook being registered during initialization.
|
|
REQUIRES INCLUDE_IPMIP6HA
|
|
CFG_PARAMS MIP6HA_FEATURE_INITIALIZATION_HOOK
|
|
}
|
|
|
|
Selection SELECT_IPMIP6HA {
|
|
NAME Ipv6 Home Agent Components
|
|
SYNOPSIS Ipv6 Home Agent Components
|
|
COUNT 0-
|
|
REQUIRES INCLUDE_IPMIP6HA
|
|
_CHILDREN FOLDER_MOBILITY_V6
|
|
CHILDREN INCLUDE_IPMIP6HA \
|
|
INCLUDE_IPMIP6HA_CMD \
|
|
INCLUDE_IPMIP6HA_DUAL_STACK \
|
|
INCLUDE_IPMIP6HA_MOBILE_ROUTER \
|
|
INCLUDE_IPMIP6HA_MOBILE_ROUTER_DUAL_STACK \
|
|
INCLUDE_IPMIP6HA_FEATURE_EXTENSION \
|
|
INCLUDE_IPMIP6HA_LMA \
|
|
INCLUDE_IPMIP6HA_LMA_DHCP_SERVER \
|
|
INCLUDE_IPMIP6HA_LMA_DUAL_STACK \
|
|
INCLUDE_IPMIP6HA_LMA_DUAL_STACK_DHCP_SERVER
|
|
DEFAULTS INCLUDE_IPMIP6HA \
|
|
INCLUDE_IPMIP6HA_CMD \
|
|
INCLUDE_IPMIP6HA_MOBILE_ROUTER \
|
|
INCLUDE_IPMIP6HA_MOBILE_ROUTER_DUAL_STACK \
|
|
INCLUDE_IPMIP6HA_DUAL_STACK \
|
|
INCLUDE_IPMIP6HA_LMA \
|
|
INCLUDE_IPMIP6HA_LMA_DHCP_SERVER \
|
|
INCLUDE_IPMIP6HA_LMA_DUAL_STACK \
|
|
INCLUDE_IPMIP6HA_LMA_DUAL_STACK_DHCP_SERVER
|
|
}
|
|
|
|
Component INCLUDE_IPMIP6HA_CMD {
|
|
NAME IPv6 Home Agent IPCOM commands
|
|
SYNOPSIS IPv6 Home Agent IPCOM commands.
|
|
MODULES ipmip6ha_cmd_ha6.o
|
|
REQUIRES INCLUDE_IPCOM_SHELL_CMD INCLUDE_IPMIP6HA
|
|
}
|
|
|
|
/* INCLUDE_IPMIP6HA configuration parameters */
|
|
Parameter MIP6HA_LIFETIME_ENUM {
|
|
NAME Interface lifetime specification
|
|
SYNOPSIS The maximum lifetime in seconds allowed on this interface. A \
|
|
value of "0" means that any lifetime may be accepted. For \
|
|
ordinary non-proxy registrations, the maximum lifetime value \
|
|
is still limited by the home address prefix lifetime as \
|
|
advertised by the routers. Format for this configuration item \
|
|
is a semi-colon separated list of interfaces and lifetime values \
|
|
as specified by the following format string \
|
|
"<ifname1>=<lifetime1>;<ifnameN>=<lifetimeN>"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_REFRESH_ENUM {
|
|
NAME Interface refresh indication
|
|
SYNOPSIS This configuration item specifies the refresh indicator that \
|
|
the home agent should provide, if any. The value may range \
|
|
between 0 and 100, which is per cent of the granted lifetime. \
|
|
A value of 0 disables the refresh indicator. The refresh \
|
|
indicator tells the registering node how long it should wait \
|
|
before refreshing its binding. If no refresh indicator value \
|
|
has been specified for an interface, it is considered having \
|
|
a value of 0. Format for this configuration item \
|
|
is a semi-colon separated list of interfaces and refresh values \
|
|
as specified by the following format string \
|
|
"<ifname1>=<refresh1>;<ifnameN>=<refreshN>"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_INTERFACES {
|
|
NAME Interface list
|
|
SYNOPSIS The interface list specifies what interfaces \
|
|
should be configured for home agent operation. This \
|
|
parameter is a comma separated list of interfaces such \
|
|
as "<ifname1>,<ifname2>" etc.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_INTERFACE_ADDRESS_ENUM {
|
|
NAME Interface address configuration
|
|
SYNOPSIS Each enabled interface must have an assigned v6 address that \
|
|
will be used during communication with registering nodes. If \
|
|
no address has been specified for an enabled interface, the \
|
|
home agent will attempt to resolve the address and use the \
|
|
first global IPv6 address it locates on the specified \
|
|
interface. This configuration parameter is specified by using \
|
|
a semi-colon separated list of interface names and addresses, as \
|
|
specified by the format string \
|
|
"<ifname1>=<address1>;<ifnameN>=<addressN>"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_TUNNEL_IP6IP6_ENUM {
|
|
NAME Home Agent IPv6 tunneling
|
|
SYNOPSIS This configuration item specifies whether or not IPv6 tunneling \
|
|
is allowed by the home agent. This configuration item should \
|
|
not be disabled unless the home agent is only doing Proxy Mobility,\
|
|
or is only reachable by means of IPv4. This configuration \
|
|
parameter is specified by using a semi-colon separated list of \
|
|
interface names and disabled/enabled values, as specified by \
|
|
the format string \
|
|
"<ifname1>=<enabled|disabled>;<ifnameN>=<enabled|disabled>"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_MOBILE_ROUTER_ACL_PD_ENUM {
|
|
NAME Mobile Router Prefix Delegation Access Control
|
|
SYNOPSIS This configuration item determines how prefixes are allocated \
|
|
to the registrering node when Mobile Router. The specified prefixes \
|
|
indicates what prefixes are to be used for Mobile Router \
|
|
registrations. Syntax for this configuration item is: \
|
|
<nai|hoa=<prefix1>/prefixlen1>[,<prefixN>/<prefixlenN>] \
|
|
A Mobile Router example for this entry would be: \
|
|
"mr-user@windriver.com=3ffe:1::/64,3ffe:2::/64" or \
|
|
"3ffe:10::1=3ffe:1::/64,3ffe:2::/64"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_TUNNEL_IP6IP6_ENUM {
|
|
NAME LMA IPv6 tunneling
|
|
SYNOPSIS This configuration item specifies whether or not IPv6 tunneling \
|
|
is allowed by the LMA for proxy mobility. By default all \
|
|
interfaces enables IPv6 tunneling. This configuration parameter \
|
|
is specified by using a semi-colon separated list of interface \
|
|
names and disabled/enabled values, as specified by the format \
|
|
string "<ifname1>=<enabled|disabled>;<ifnameN>=<enabled|disabled>"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_TUNNEL_GRE_ENUM {
|
|
NAME LMA IPv6 GRE tunneling
|
|
SYNOPSIS This configuration item specifies whether IPv6 GRE tunneling \
|
|
is allowed by the LMA for Proxy Mobility. By default all \
|
|
interfaces enables GRE. This configuration parameter is \
|
|
specified by using a semi-colon separated list of interface \
|
|
names and disabled/enabled values, as specified by the format string \
|
|
"<ifname1>=<enabled|disabled>;<ifnameN>=<enabled|disabled>"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_POOL_ENUM {
|
|
NAME LMA Prefix Allocation Pool definitions
|
|
SYNOPSIS This configuration item defines a LMA pool allocation \
|
|
object, from which MAGs may allocate v6 prefixes for use \
|
|
by nodes located in their networks. The format of the \
|
|
configuration parameter is \
|
|
<pool name1>=<pool definition1>[;<pool nameN>=<pool definitionN>] \
|
|
<pool definition> has the form <prefix>/<prefix length>/<chunk size> \
|
|
where <prefix> is the prefix we will be allocating chunks from, \
|
|
<prefix length> is the size of the entire prefix, while <chunk size> \
|
|
determines the size of the allocated prefix. For example, \
|
|
"WR-POOL=3ffe::/48/64" will be allocating 64 bit chunks from \
|
|
the prefix 3ffe::/48.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_ACL_PD_ENUM {
|
|
NAME Proxy Mobility Prefix Delegation Access Control
|
|
SYNOPSIS This configuration item determines how prefixes are allocated \
|
|
to the registrering node when Proxy Mobility is used. \
|
|
The explicitly specified prefixes \
|
|
indicates what prefixes are to be used for Proxy Mobility \
|
|
registrations using the specified NAI. Syntax for this \
|
|
configuration item is: \
|
|
<nai|domain=<prefix1>/prefixlen1>[,<prefixN>/<prefixlenN> \
|
|
An example would be: "pm-user@windriver.com=3ffe:3::/64". A \
|
|
domain example specifying available prefixes for a domain \
|
|
would be: "@windriver.com=3ffe:4::/64,3ffe:5::/64,3ffe:6::/64"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_ACL_POOL_ENUM {
|
|
NAME Proxy Mobility Pool Access Control
|
|
SYNOPSIS This configuration item determines what pool to be used in order\
|
|
to allocate prefixes to a specified NAI or domain.\
|
|
Syntax for this configuration item is: <nai|domain=<pool name> \
|
|
An example would be: "pm-user@windriver.com=WR-POOL". A domain \
|
|
example specifying a pool for a domain would be: \
|
|
"@windriver.com=WR-POOL"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_ACL_LIMIT_ENUM {
|
|
NAME Proxy Mobility Prefix Allocation Limit Access Control
|
|
SYNOPSIS This configuration item determines the maximum number of \
|
|
prefix which a specific NAI or domain may allocate from \
|
|
the Home Agent. If no LIMIT is specified for a given \
|
|
user or domain, it will resort to "1". \
|
|
Syntax for this configuration item is: <nai|domain=<limit> \
|
|
An example would be: "pm-user@windriver.com=3". A domain example \
|
|
specifying available prefixes for a domain would be: \
|
|
"@windriver.com=2"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
|
|
Parameter MIP6HA_LMA_MIN_DELAY_BEFORE_BCE_DELETE_ENUM {
|
|
NAME Proxy Mobility Minimum Delay before BCE Delete
|
|
SYNOPSIS This variable specifies the amount of time in milliseconds the \
|
|
local mobility anchor MUST wait before it deletes a Binding \
|
|
Cache entry of a mobile node, upon receiving a Proxy Binding \
|
|
Update message from a mobile access gateway with a lifetime \
|
|
value of 0. During this wait time, if the local mobility \
|
|
anchor receives a Proxy Binding Update for the same mobility \
|
|
binding, with a lifetime value greater than 0, then it must \
|
|
update the binding cache entry with the accepted binding \
|
|
values. By the end of this wait-time, if the local \
|
|
mobility anchor did not receive any valid Proxy Binding \
|
|
Update message for that mobility binding, it MUST delete the \
|
|
Binding Cache entry. This delay essentially ensures a \
|
|
mobile node's Binding Cache entry is not deleted too quickly \
|
|
and allows some time for the new mobile access gateway to \
|
|
complete the signaling for the mobile node. \
|
|
The format for this configuration item is a semi-colon \
|
|
separated list of "<ifname>=<timeout>". \
|
|
If no value has been specified for a given interface, \
|
|
a value of "10000" will be used.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_MAX_DELAY_BEFORE_NEW_BCE_ASSIGN_ENUM {
|
|
NAME Proxy Mobility Max Delay Before New BCE Assign
|
|
SYNOPSIS This variable specifies the amount of time in milliseconds the \
|
|
local mobility anchor MUST wait for the de-registration message \
|
|
for an existing mobility session before it decides to create a \
|
|
new mobility session.The format for this configuration item is \
|
|
a semi-colon separated list of "<ifname>=<timeout>". \
|
|
If no value has been specified for a given interface, \
|
|
a value of "1500" will be used.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_TIMESTAMP_VALIDITY_WINDOW_ENUM {
|
|
NAME Proxy Mobility Timestamp Validity Window
|
|
SYNOPSIS This variable specifies the maximum amount of time difference \
|
|
in milliseconds between the timestamp in the received Proxy \
|
|
Binding Update message and the current time of day on the \
|
|
local mobility anchor, that is allowed by the local mobility \
|
|
anchor for thereceived message to be considered valid.\
|
|
The format for this configuration item is \
|
|
a semi-colon separated list of "<ifname>=<validity timeout>". \
|
|
If no value has been specified for a given interface, \
|
|
a value of "300" will be used.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_MOBILE_NODE_GENERATED_TIMESTAMP_IN_USE_ENUM {
|
|
NAME Proxy Mobility Mobile Node Generated Timestamp In Use
|
|
SYNOPSIS This flag indicates whether or not the mobile-node-generated \
|
|
timestamp approach is in use in that Proxy Mobile IPv6 domain. \
|
|
When the value for this flag is set to 1, the local mobility \
|
|
anchors and mobile access gateways in that Proxy Mobile IPv6 \
|
|
domain MUST apply the mobile node generated timestamp \
|
|
considerations. Syntax for this parameter is a semi-colon \
|
|
separated list of "<ifname>=<0|1>". By default this \
|
|
feature is turned off.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_HEARTBEAT_ENABLED_ENUM {
|
|
NAME Proxy Mobility HEARTBEAT
|
|
SYNOPSIS This configuration option specifies whether or not the Heartbeat \
|
|
feature is enabled for the specified interface. If no \
|
|
configuration is provided, the feature is turned off. \
|
|
The format for this configuration item is \
|
|
a semi-colon separated list of "<ifname>=<enabled|disabled>".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_HEARTBEAT_INTERVAL_ENUM {
|
|
NAME Proxy Mobility HEARTBEAT_INTERVAL
|
|
SYNOPSIS This variable is used to set the time interval in seconds \
|
|
between two consecutive Heartbeat Request messages. The \
|
|
default value is 60 seconds. It SHOULD NOT be set to less \
|
|
than 30 seconds.The format for this configuration item is \
|
|
a semi-colon separated list of "<ifname>=<interval>".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_MISSING_HEARTBEATS_ALLOWED_ENUM {
|
|
NAME Proxy Mobility MISSING_HEARTBEATS_ALLOWED
|
|
SYNOPSIS This variable indicates the maximum number of consecutive \
|
|
Heartbeat Request messages that a PMIPv6 node can miss before \
|
|
concluding that the peer PMIPv6 node is not reachable. The \
|
|
default value for this variable is 3.\
|
|
The format for this configuration item is a semi-colon \
|
|
separated list of "<ifname>=<misses>".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_MAG_ENUM {
|
|
NAME Proxy Mobility Mobility Access Gateway Definitions
|
|
SYNOPSIS This configuration item specifies what Mobility Access \
|
|
Gateways should be permanently added to the MAG database, \
|
|
and whether or not they support HeartBeat. The LMA will \
|
|
send an unsolicited HeartBeat response to each HeartBeat \
|
|
enabled MAG during startup and reconfiguration. \
|
|
The format for this configuration item is a semi-colon \
|
|
separated list of "<MAG address>=<enabled|disabled>" where \
|
|
<MAG Address> has the form <MAG INET6 Address>[/<MAG INET Address>]
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_REVOKE_PREVIOUS_MAG_ENUM {
|
|
NAME Proxy Mobility Automatic Revocation of Previous MAG
|
|
SYNOPSIS This feature specifies whether or not the LMA will revoke \
|
|
bindings from previous MAGs when a new registration and \
|
|
care-of address has been registered. By default this parameter \
|
|
is enabled. This configuration parameter is specified by using \
|
|
a semi-colon separated list of interface names and timeout \
|
|
values, as specified by the format string \
|
|
"<ifname1>=<enabled|disabled>;<ifnameN>=<enabled|disabled>"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
|
|
|
|
Parameter MIP6HA_LMA_FIXED_MAG_LINKLOCAL_ADDRESS_ON_ALL_ACCESS_LINKS_ENUM {
|
|
NAME Proxy Mobility Fixed MAG LinkLocal Address On All Access Links
|
|
SYNOPSIS This variable indicates the link-local address value that all \
|
|
the mobile access gateways SHOULD use on any of the access \
|
|
links shared with any of the mobile nodes in that Proxy Mobile \
|
|
IPv6 domain. If this variable is initialized to ALL_ZERO value,\
|
|
itimplies the use of fixed link-local address mode is not \
|
|
enabled for that Proxy Mobile IPv6 domain. ALL_ZERO is \
|
|
specified by omitting the configuration or specifying the \
|
|
address as "::". The format for this configuration item is a \
|
|
semi-colon separated list of "<ifname>=<link local addresss>".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_DHCP_SERVER_SERVER_ENUM {
|
|
NAME Proxy Mobility IPDHCPv6 Support
|
|
SYNOPSIS This configuration item enabled IPDHCPS6 server support \
|
|
for the specified interfaces. IPDHCPS6 must be included \
|
|
in the build for this parameter to be available.. \
|
|
The format for this configuration item is a semi-colon \
|
|
separated list of "<ifname>=<enabled|disabled>".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_DHCP_SERVER_SERVER_PREFERRED_ENUM {
|
|
NAME Proxy Mobility IPDHCPv6 Preferred Lifetime Configuration
|
|
SYNOPSIS This configuration item specifies the preferred lifetime in \
|
|
seconds to be used by the IPDHCPS6 server during DHCP \
|
|
negotiations. If no configuration is provided, this value \
|
|
will default to "10000". \
|
|
The format for this configuration item is a semi-colon \
|
|
separated list of "<ifname>=<preferred lifetime in seconds>".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_DHCP_SERVER_SERVER_VALID_ENUM {
|
|
NAME Proxy Mobility IPDHCPv6 Valid Lifetime Configuration
|
|
SYNOPSIS This configuration item specifies the valid lifetime in \
|
|
seconds to be used by the IPDHCPS6 server during DHCP \
|
|
negotiations. If no configuration is provided, this value \
|
|
will default to "10000". \
|
|
The format for this configuration item is a semi-colon \
|
|
separated list of "<ifname>=<valid lifetime in seconds>".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_INET_TUNNEL_IPIP_ENUM {
|
|
NAME INET LMA v4 IPIP tunneling
|
|
SYNOPSIS This configuration item specifies whether or not v4 IPIP tunneling \
|
|
is allowed by the LMA for proxy mobility. By default all \
|
|
interfaces enables IPIP tunneling. This configuration parameter \
|
|
is specified by using a semi-colon separated list of interface \
|
|
names and disabled/enabled values, as specified by the format \
|
|
string "<ifname1>=<enabled|disabled>;<ifnameN>=<enabled|disabled>"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_INET_TUNNEL_GRE_ENUM {
|
|
NAME INET LMA v4 GRE tunneling
|
|
SYNOPSIS This configuration item specifies whether v4 GRE tunneling \
|
|
is allowed by the LMA for Proxy Mobility. By default all \
|
|
interfaces enables GRE. This configuration parameter is \
|
|
specified by using a semi-colon separated list of interface \
|
|
names and disabled/enabled values, as specified by the format string \
|
|
"<ifname1>=<enabled|disabled>;<ifnameN>=<enabled|disabled>"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_INET_TOPOLOGY_DHCP_OPTION_ENUM {
|
|
NAME INET LMA Network Topology DHCP Configuration
|
|
SYNOPSIS Specify the DHCP options that are valid for various network \
|
|
segments. The syntax is <type>.<code>.<network>=<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.0.0.0/8=10.1.2.3 10.2.3.3" \
|
|
will add a DNS server option with two servers valid for the \
|
|
network segment 10.0.0.0/8. Some DHCP options do have alias \
|
|
names, where the most common are "router", "subnet_mask" and \
|
|
"dns". So, a valid configuration is also \
|
|
"router.10.0.0.0/8=10.1.2.3" which would add 10.1.2.3 as a \
|
|
default router for the network segment 10.0.0.0/8. You \
|
|
MUST add a router and a subnet_mask option for the appropriate \
|
|
networks, when using v4 address assignments in Proxy Mobility, \
|
|
since the specification requires that information to be provided. \
|
|
This configuration parameter is specified by using a semi-colon \
|
|
separated list of network topology configurations and values,\
|
|
such as: "<type>.<code>.<network>/<prefix length>=<value>" or \
|
|
"<alias>.<network>/<prefix length>=<value>"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_INET_ACL_HOMEADDRESS_ENUM {
|
|
NAME INET LMA Home Address Assignment Access Control
|
|
SYNOPSIS This configuration item determines what INET home address may \
|
|
be allocated by a specific NAI. Syntax for this \
|
|
configuration item is: \
|
|
<nai>=<INET hoa>/prefixlen> \
|
|
An example for this entry would be: \
|
|
"mr-user@windriver.com=10.0.1.1/24"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
|
|
Parameter MIP6HA_LMA_INET_ACL_POOL_ENUM {
|
|
NAME INET LMA Pool Allocation Access Control
|
|
SYNOPSIS This configuration item determines what INET pool may be used \
|
|
by a specific NAI or DOMAIN for INET home address Syntax for \
|
|
this configuration item is: <nai|domain>=<pool name> \
|
|
An example for this entry would be: \
|
|
"mr-user@windriver.com=WR-INET_POOL"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_LMA_INET_DHCP_SERVER_ENUM {
|
|
NAME INET LMA Integrated DHCP Server Support
|
|
SYNOPSIS This configuration item determines if the intergrated DHCP \
|
|
server is enabled or disabled. The integrated DHCP server \
|
|
provides DHCP functionality for DHCP requests relayed by the \
|
|
MAG for proxy mobile nodes. The DHCP options provided by \
|
|
the server is decided by MIP6HA_LMA_INET_TOPOLOGY_DHCP_OPTION_ENUM. \
|
|
The format of this entry is a semi-colon separated list of \
|
|
<ifname>=<enabled|disabled>, such as "eth0=disabled". By \
|
|
default, the integrated DHCP server is not enabled.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
|
|
|
|
Parameter MIP6HA_INET_INTERFACE_ADDRESS_ENUM {
|
|
NAME INET Interface address configuration
|
|
SYNOPSIS Each enabled interface may have an assigned v4 address that \
|
|
will be used during communication with registering nodes. If \
|
|
no address has been specified for an enabled interface, the \
|
|
home agent will attempt to resolve the address and use the \
|
|
first IPv4 address it locates on the specified \
|
|
interface. This configuration parameter is specified by using \
|
|
a semi-colon separated list of interface names and addresses, \
|
|
as specified by the format string \
|
|
"<ifname1>=<address1>;<ifnameN>=<addressN>"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_INET_ACCEPT_FORCED_IPV4_UDP_ENCAPSULATION_REQUEST_ENUM {
|
|
NAME INET Accept Forced IPv4 UDP Encapsulation Request
|
|
SYNOPSIS This flag indicates whether or not the local mobility anchor/ \
|
|
home agent should accept IPv4 UDP encapsulation request for \
|
|
the mobile node's data traffic, even if there is no NAT \
|
|
detected in the path. The default value for this flag is set \
|
|
to value of 0, indicating that the LMA/HA MUST NOT accept IPv4 \
|
|
UDP encapsulation request when NAT is not detected in the path.\
|
|
When the value for this flag is set to value of 1, the LMA/HA \
|
|
MUST accept IPv4 UDP encapsulation request even when NAT is not \
|
|
detected in the path. This configuration parameter is specified \
|
|
by using a semi-colon separated list of interface names and \
|
|
flags, as specified by the format string \
|
|
"<ifname1>=<0|1>;<ifnameN>=<0|1>
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_INET_FORCE_IPV4_UDP_ENCAPSULATION_ENUM {
|
|
NAME INET Force IPv4 UDP Encapsulation
|
|
SYNOPSIS This boolean parameter specifies whether or not the LMA/HA will \
|
|
force UDP encapsulation for Ipv4 tunneled frames. This \
|
|
parameter is by default false. This configuration parameter is \
|
|
specified by using a semi-colon separated list of interface \
|
|
names and boolean values as specified by the format string \
|
|
"<ifname1>=<true|false>;<ifnameN>=<true|false>".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_INET_IPV4_UDP_ENCAPSULATION_NAT_TIMEOUT {
|
|
NAME INET IPv4 UDP Encapsulation NAT Timeout
|
|
SYNOPSIS This parameter specifies in seconds the estimated time a NAT \
|
|
binding will remain valid within this domain. If specified as \
|
|
0xFFFFFFFF a binding never times out, 0 allows the requesting \
|
|
node to to determine the timeout value. The default value is \
|
|
110. This configuration parameter is specified by using a \
|
|
semi-colon separated list of interface names and timeout values \
|
|
as specified by the format string \
|
|
"<ifname1>=<timeout1>;<ifnameN>=<timeoutN>".
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
|
|
Parameter MIP6HA_INET_TUNNEL_IPIP_ENUM {
|
|
NAME INET Home Agent v4 IPIP tunneling
|
|
SYNOPSIS This configuration item specifies whether or not v4 IPIP tunneling \
|
|
is allowed by the home agent. By default, IPIP is always enabled. \
|
|
This configuration parameter is specified by using a semi-colon \
|
|
separated list of interface names and disabled/enabled values, \
|
|
as specified by the format string \
|
|
"<ifname1>=<enabled|disabled>;<ifnameN>=<enabled|disabled>"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_INET_TOPOLOGY_ADDRESS_RESERVATION {
|
|
NAME INET Network Topology Address Reservation
|
|
SYNOPSIS Specify the v4 address and prefixes that MUST not be allocated \
|
|
to any MAG or DSMIPv6 node. \
|
|
This configuration parameter is specified by specifying a \
|
|
comma separated list of addresses or prefixes such as: \
|
|
"<address1>[/<prefix length1>][,<addressN>[/<prefix lengthN>]]"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_INET_POOL_ENUM {
|
|
NAME INET Prefix and Home Address Allocation Pool definitions
|
|
SYNOPSIS This configuration item defines an INET pool allocation \
|
|
object, from which MAGs or INET enabled mobile nodes may \
|
|
allocate v4 prefixes and home addresses.The format of the \
|
|
configuration parameter is \
|
|
<pool name1>=<pool definition1>[;<pool nameN>=<pool definitionN>] \
|
|
<pool definition> has the form: \
|
|
<INET prefix>/<prefix length>/<chunk size> \
|
|
or an inclusive range such as: \
|
|
<INET prefix start>-<INET prefix end>/<prefix length>/<chunk size> \
|
|
where <INET prefix> is the prefix we will be allocating chunks from, \
|
|
<prefix length> is number of bits in the netmask, while <chunk size> \
|
|
determines the size of the allocated prefix. For example, \
|
|
"WR-INET-POOL=10.0.0.0/24/32" will be allocating single \
|
|
addresses bit from the network 10.0.0.0/24. Another example is: \
|
|
"WR-INET-POOL=10.0.0.1-10.0.0.3/24/32" which will provide \
|
|
addresses 10.0.0.1, 10.0.0.2 and 10.0.0.3 for allocation. \
|
|
For prefix allocations, a pool rule could read: \
|
|
"WR-INET-POOL=10.0.0.0/8/24" which would allocate 24 bit segments \
|
|
of the 10.0.0.0/8 network. If you need to reserve addresses \
|
|
in the pool, see MIP6HA_INET_TOPOLOGY_ADDRESS_RESERVATION.
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_MOBILE_ROUTER_INET_ACL_PD_ENUM {
|
|
NAME INET Mobile Router Prefix Delegation Access Control
|
|
SYNOPSIS This configuration item determines how prefixes are allocated \
|
|
to the registrering node when Mobile Router. The specified prefixes \
|
|
indicates what prefixes are to be used for Mobile Router \
|
|
registrations. Syntax for this configuration item is: \
|
|
<nai|hoa>=<INET prefix1>/prefixlen1>[,<prefixN>/<INET prefixlenN>] \
|
|
A Mobile Router example for this entry would be: \
|
|
"mr-user@windriver.com=10.0.1.0/24,10.0.2.0/24" or \
|
|
"3ffe:10::1=10.0.1.0/24,10.0.2.0/24"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_INET_ACL_HOMEADDRESS_ENUM {
|
|
NAME INET Home Address Assignment Access Control
|
|
SYNOPSIS This configuration item determines what INET home addresses may \
|
|
be allocated by a specific Home Address or NAI. Syntax for this \
|
|
configuration item is: \
|
|
<nai|hoa>=<INET hoa1>/prefixlen1>[,<INET hoaN>/<prefixlenN>] \
|
|
An example for this entry would be: \
|
|
"mr-user@windriver.com=10.0.1.1/24"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_INET_ACL_POOL_ENUM {
|
|
NAME INET Pool Allocation Access Control
|
|
SYNOPSIS This configuration item determines what INET pool may be used \
|
|
by a specific Home Address, NAI or DOMAIN for INET home address \
|
|
or prefix allocations. Syntax for this configuration item is: \
|
|
<nai|hoa|domain>=<pool name> \
|
|
An example for this entry would be: \
|
|
"mr-user@windriver.com=WR-INET_POOL"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_INET_ACL_LIMIT_HOMEADDRESS_ENUM {
|
|
NAME INET Home Address Allocation Limit Access Control
|
|
SYNOPSIS This configuration item determines the number of INET Home \
|
|
Addresses may be allocated by a specific NAI, domain or \
|
|
Home Address. The default value is "1". The format for this \
|
|
entry is <nai|domain|hoa>=<limit>. \
|
|
An example for this entry would be: \
|
|
"mr-user@windriver.com=2"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_INET_ACL_LIMIT_PD_ENUM {
|
|
NAME INET Prefix Delegation Limit Access Control
|
|
SYNOPSIS This configuration item determines the number of INET Prefixes \
|
|
that may be allocated by a specific NAI, domain or \
|
|
Home Address. The default value is "0". The format for this \
|
|
entry is <nai|domain|hoa>=<limit>. \
|
|
An example for this entry would be: \
|
|
"mr-user@windriver.com=1"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
|
|
Parameter MIP6HA_FEATURE_INITIALIZATION_HOOK {
|
|
NAME Home Agent Service Initialization Hook
|
|
SYNOPSIS This is the function hook that you may define in order to \
|
|
register extra functional extensions to the Home Agent.
|
|
TYPE FUNCPTR
|
|
DEFAULT your_function_here
|
|
}
|
|
|
|
Parameter MIP6HA_BINDING_REVOCATION_MIN_DELAY_ENUM {
|
|
NAME Home Agent Minimum Delay Between BRI messages (MINDelayBRIs)
|
|
SYNOPSIS This variable specifies the delay time in milliseconds before \
|
|
the revoking mobility entity retransmits a BRI message. The \
|
|
default is 1000 ms but not less than 500 ms.\
|
|
This configuration parameter is specified by using a semi-colon \
|
|
separated list of interface names and timeout values, as \
|
|
specified by the format string \
|
|
"<ifname1>=<milliseconds>;<ifnameN>=<milliseconds>"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
Parameter MIP6HA_BINDING_REVOCATION_MAX_RETRIES_ENUM {
|
|
NAME Home Agent BRI Maximum Number of Retries (BRIMaxRetriesNumber)
|
|
SYNOPSIS This variable specifies the maximum Number of times a mobility \
|
|
entity can retransmit a Binding Revocation Indication message \
|
|
before receiving a Binding Revocation Acknowledgement message. \
|
|
The default value for this parameter is 1. \
|
|
This configuration parameter is specified by using a semi-colon \
|
|
separated list of interface names and retransmit values, as \
|
|
specified by the format string \
|
|
"<ifname1>=<retransmits>;<ifnameN>=<retransmits>"
|
|
TYPE char *
|
|
DEFAULT ""
|
|
}
|
|
|
|
#endif
|