The procedure asks whether you want to create a host configuration
file based on the choices you have made.
Create IPv6 Host configuration file?
Please enter YES or NO [YES]:
|
If you are not satisfied with the configuration, enter N and press
Return. The utility ends immediately without changing any of the
current configuration files.
If you are satisfied with the
configuration, enter Y and press Return. The TCPIP$IP6_SETUP command
procedure creates a configuration file called
SYS$SYSTEM:TCPIP$INET6_CONFIG.DAT. When you restart TCP/IP Services, a
process called TCPIP$ND6HOST will be started automatically.
2.5.2 DNS Domain Name and Address Registration
After you shut down TCP/IP Services and before you restart it, you can
use the TCPIP$ND6HOST process to register the host's domain name and
address in the DNS.
The TCPIP$ND6HOST process receives and processes IPv6 router
advertisement (RA) packets of the neighbor discovery protocol. This
enables a system to autoconfigure itself without manual intervention.
With this version of TCP/IP Services, you can also enable DNS
registration.
To enable host name and address registration, enter the following
command:
$ DEFINE /SYSTEM TCPIP$ND6D_ENABLE_DDNS 1
|
The domain name to be registered is obtained using the
gethostname()
call.
To update the zone, TCPIP$ND6HOST sends dynamic updates to the primary
master name server. To determine the master name server, a query for
the zone's SOA record is sent to the name server specified in the DNS
resolver configuration. To display this information, use the TCP/IP
management command SHOW NAME. The name of the primary master server is
stored in the SOA MNAME field.
To make use of this feature, you must enable dynamic updates. By
default, dynamic updates are rejected by DNS servers. For information
about allowing dynamic updates, see the BIND Chapter of the
HP TCP/IP Services for OpenVMS Management guide.
2.6 Configuring an IPv6 Router
Before running the TCPIP$IP6_SETUP command procedure, make sure that
you have configured your system for IPv4 by running TCPIP$CONFIG.
You must also enable forwarding by setting the
ipv6forwarding and ipv6router
attributes of the kernel
inet
subsystem to 1. You set these attributes temporarily by entering the
following
sysconfig
commands:
$ sysconfig -r inet ipv6forwarding=1
$ sysconfig -r inet ipv6router=1
|
See the HP TCP/IP Services for OpenVMS Tuning and Troubleshooting manual to modify these attributes permanently.
2.6.1 Running TCPIP$IP6_SETUP to Configure Router
To configure your system as an IPv6 router, do the following:
- Invoke the TCPIP$IP6_SETUP command procedure by entering the
following command:
$ @SYS$MANAGER:TCPIP$IP6_SETUP
|
The utility displays information about the IPv6 network
configuration procedure and tells you that you can configure the system
as either an IPv6 host or an IPv6 router.
- Choose to configure the system as an IPv6 router by responding to
the following prompt:
Configure this system as an IPv6 router? [NO]:
|
If you want to configure the system as an IPv6 router, enter Y and
press Return.
- Indicate whether you want this system to function as a 6to4 border
router:
Configure this system as a 6to4 Border IPv6 router? [NO]:
|
To operate as a 6to4 border router, the IPv6 site to which this
system is attached must have at least one valid, globally unique IPv4
address and must be configured on a network segment attacheded to the
wide-area IPv4 network.
If you do not want the system to function
as a 6to4 border router, press Return. The procedure goes to step 8.
If you want the system to function as a 6to4 border router, enter Y
and press Return.
- Indicate whether you want to configure a 6to4 interface on the
border router system:
Configure a 6to4 interface? [NO]:
|
To communicate with other 6to4 sites over an IPv4 wide-area network
without tunneling or to communicate with native IPv6 sites using 6to4
relay routers, you need to configure a 6to4 interface.
If you do
not want to configure a 6to4 interface, press Return. The procedure
goes to step 8. If you want to configure a 6to4 interface, enter Y and
press Return. You'll be prompted for further information in subsequent
steps.
- Enter this node's IPv4 address:
Enter this node's IPv4 address:
|
Enter the IPv4 address for your system and press Return. A 6to4
site prefix is automatically generated and displayed.
- Indicate whether you want the system to have connectivity to native
IPv6 sites:
Connectivity to native IPv6 sites? [NO]:
|
A relay router is needed to connect your system to native IPv6
sites. If a relay router is not specified, your system can connect to
other 6to4 sites but not to native IPv6 sites.
If you do not want
your system to connect to native IPv6 sites, press Return. The
procedure goes to step 8.
If you want your system to connect to
native IPv6 sites, enter Y and press Return.
- Indicate the address of a relay router:
Enter 6to4 address of a 6to4 Relay Router [2002:C058:6301::]:
|
Press Return to use the default relay router anycast address. Or
enter another 6to4 relay router address, then press Return. The
procedure goes to step 8.
- Answer the prompts about configuring each interface on your system.
The procedure displays the following questions:
Do you want to enable IPv6 on this interface?
Enable IPv6 on interface WE0? [YES]:
|
Press Return if you want to enable IPv6 on this interface; enter N
if you do not.
- Answer the prompts about enabling IPv6 routing on each interface on
your system. The procedure displays the following questions:
Do you want to enable IPv6 routing on this interface?
Enable IPv6 routing on interface WE0? [YES]:
|
Press Return if you want to enable IPv6 routing on this interface;
enter N if you do not.
- Indicate whether you want the router to run the RIPng protocol on
the designated interface by responding to the following prompt:
Enable RIPng on interface WE0? [YES]:
|
If you want the router to run the RIPng protocol, press Return;
enter N and press Return if you do not.
- Indicate whether you want the router to advertise an IPv6 address
prefix for the LAN on the designated interface, by responding to the
following prompt:
Address prefix to advertise on interface WE0?:
|
If you want the router to advertise an IPv6 address prefix, enter a
64-bit address prefix for the interface and press Return. The procedure
repeats the same prompt. You can enter as many additional prefixes as
you want for the interface. When you are finished, enter Done and press
Return.
If you do not want the router to advertise an IPv6 address
prefix on the designated interface, enter Done and press Return.
If
there are additional interfaces on your system, the procedure returns
to steps 8 through 11 for each interface. Once you have configured all
interfaces, the procedure goes to step 12.
- Indicate whether you want to configure an automatic tunnel by
responding to the following prompt:
Configure an IPv6 over IPv4 automatic tunnel interface? [NO]:
|
If you want to configure an automatic tunnel, enter Y and press
Return; if not, press Return.
- Indicate whether you want to create a configured tunnel or
additional configured tunnels by responding to the following prompt:
Create a configured tunnel? [NO]:
|
If you want to create a configured tunnel, enter Y and press
Return. You will be prompted for source and destination addresses in
steps 14 and 15.
If you do not want to create a configured tunnel
or if you have finished adding a series of configured tunnels, press
Return. The procedure goes to step 20.
- If you chose to create a configured tunnel, enter the tunnel's
source IPv4 address in response to the following prompt:
Source IPv4 address of tunnel IT0?:
|
Enter an IPv4 address in the standard format (
xx.xx.xx.xx
) and press Return.
- Enter the tunnel's destination IPv4 address in response to the
following prompt:
Destination IPv4 address of tunnel IT0?:
|
Enter an IPv4 address in the following format (
xx.xx.xx.xx
) and press Return.
- Indicate whether you want to enable IPv6 routing on the interface
by reponding to the following prompt:
Enable IPv6 routing on interface IT0? [YES]:
|
If you want to enable IPv6 routing on the interface, press Return;
if not, enter N and press Return.
- Indicate whether you want to enable RIPng on the interface by
responding to the following prompt:
Enable RIPng on interface IT0? [YES]:
|
Press Return if you want to enable RIPng protocol on this
interface; enter N and press Return if you do not.
- Indicate whether you want the host to use an IPv6 address prefix on
the tunnel interface by responding to the following prompt:
Address prefix to advertise on interface IT0?:
|
If you want the host to use an IPv6 address prefix because a
router is not advertising a global address prefix, enter the prefix and
press Return. Enter as many prefixes as you want. When you are finished
entering prefixes for the interface, enter Done and press Return.
If you do not want the host to use an IPv6 address prefix on the tunnel
interface, enter Done and press Return.
- Indicate whether you want to create another configured tunnel by
responding to the following prompt:
Create another configured tunnel? [NO]:
|
If you want to create another configured tunnel, enter Y and press
Return. The procedure returns to step 13.
If you do not want to
create another configured tunnel, press Return.
- The TCPIP$IP6_SETUP command procedure displays the configuration
information and asks you to indicate whether you want to update the
current startup procedures with the new configuration information.
Create IPv6 Router configuration files?
Please enter YES or NO [YES]:
|
If you are not satisfied with the configuration, enter N and press
Return. The utility ends immediately without changing any of the
current configuration files.
If you are satisfied with the
configuration, enter Y and press Return. The TCPIP$IP6_SETUP command
procedure creates a configuration file called
SYS$SYSTEM:TCPIP$INET6_CONFIG.DAT and a router configuration file
called SYS$SYSTEM:TCPIP$IP6RTRD.CONF, both with default values. When
you restart HP TCP/IP Services for OpenVMS, the TCIPI$IP6RTRD process starts
automatically.
2.6.2 TCPIP$IP6RTRD.CONF Configuration File
At startup, the TCPIP$IP6RTRD process reads the TCPIP$IP6RTRD.CONF file
to obtain data needed to send router advertisement and RIPng messages.
The TCPIP$IP6RTRD.CONF file is created when TCPIP$IP6_SETUP is run, if
the system is configured as a router. Initially, the link interface and
advertised prefix are inserted, and other default values are used.
The TCPIP$IP6RTRD.CONF file consists of structured information for each
interface in the following format:
interface interface-name {
# interface keyword-value pairs, one per line
Prefix prefix/length {
# prefix keyword-value pairs, one per line
}
}
|
Comments begin with the pound sign (#) and continue to the end of the
line. Accepted and default values for the interface keywords and prefix
keywords are listed in Section 2.6.2.1 and Section 2.6.2.2. Section 2.6.2.3
contains a sample configuration file.
2.6.2.1 Interface Keyword Information for TCPIP$IP6RTRD.CONF
The following basic keywords are defined in RFC 2461 for IPv6 operation:
- AdvCurHopLimit
Specifies the value to be placed in the Cur Hop
Limit field in the Router Advertisement messages sent by the router.
The value 0 (zero) means unspecified (by this router). Valid values are
any nonnegative integer. The default is 64.
- AdvDefaultLifetime
Specifies a time, in seconds, that is
placed in the Router Lifetime field in the router advertisement. Valid
values are between 0 or MaxRtrAdvInterval and 9000, inclusive. The
default is 1800 seconds.
- AdvLinkMTU
Specifies a nonnegative integer value to be placed
in MTU options sent by the router. The default is 0.
- AdvManagedFlag
Enables (1) or disables (0) the setting of a
flag in the "Managed address configuration" flag field in the router
advertisement. The default is 0.
- AdvOtherConfigFlag
Enables (1) or disables (0) the setting of
a flag in the "Other stateful configuration" flag field in the router
advertisement. The default is 0.
- AdvReachableTime
Specifies a time, in milliseconds, that is
placed in the Reachable Time field in router advertisement messages.
Valid values are between 0 and 3,600,000 (1 hour), inclusive. The
default is 0 milliseconds.
- AdvRetransTimer
Specifies a nonnegative integer value to be
placed in the Retrans Timer field in the router advertisement. The
default is 0 (zero).
- AdvSendAdvertisements
Enables (yes) or disables (no) the
sending of periodic Router Advertisements and responding to Router
Solicitations. The default is yes.
- MaxRtrAdvInterval
Specifies the maximum time, in seconds,
between sending unsolicited multicast router advertisements from the
interface. Valid values are between 4 and 1800 seconds, inclusive. The
default is 600 seconds.
- MinRtrAdvInterval
Specifies the minimum time, in seconds,
between sending unsolicited multicast router advertisements from the
interface. Valid values are between 3 and .75 * MaxRtrAdvInterval. The
default is 200 seconds.
The following additional interface keywords are accepted:
- AdvSendLinkLayerAddress
Enables (yes) or disables (no) the
sending of the interface link-layer address option in outgoing router
advertisements. The default is yes.
- AdvSendSiteLocal
Enables (yes) or disables (no) the sending
of site local prefixes in outgoing router advertisements. The default
is no.
- PoisonReverse
Enables (1) or disables (0) the Poisoned
Reverse algorithm as specified in RFC 2080. The default is 1.
- ripng
Enables (yes) or disables (no) participation in RIPng
on the interface. If enabled, RIPng updates are sent on the interface,
and received RIPng updates are processed as defined in RFC 2080. You
cannot specify yes for automatic tunnels (the tun0 interface). The
default is yes (except for tun0).
- SplitHorizon
Enables (1) or disables (0) the Split Horizon
algorithm as specified in RFC 2080. The default is 1.
2.6.2.2 Address-Prefix Keyword Information for TCPIP$IP6RTRD.CONF
Each address prefix to be configured on the interface must be defined
within a prefix block that begins with the keyword Prefix followed by
the prefix and length (separated by a slash [/] and optionally followed
by an additional address-prefix information block of keyword-value
pairs).
The following address prefix keywords and values are defined in RFC
2461:
- AdvAutonomousFlag
Enables (1) or disables (0) the setting of
the Autonomous Flag field in the Prefix Information option. The default
is 1.
- AdvOnLinkFlag
Enables (1) or disables (0) the setting of the
on-link flag field in outgoing router advertisements. The default is 1.
- AdvPreferredLifetime
Specifies the preferred lifetime of the
address prefix, in seconds, to be placed in outgoing router
advertisements. The default is 604800 seconds, or 7 days.
- AdvValidLifetime
Specifies the valid lifetime of the address
prefix, in seconds, to be placed in outgoing router advertisements. The
default is 2592000 seconds, or 30 days.
The following address prefix keywords and values are defined in RFC
2080:
- RouteMetric
Specifies a value that represents the total cost
of getting a datagram from the router to a destination. Valid values
are between 1 and 16, inclusive. The default is 1.
- RouteTag
Specifies a integer that is assigned to a route and
must be preserved and readvertised with a route. The default is 0.
In addition, you can specify the following address-prefix keywords:
- ConfigureThisPrefix
The TCPIP$IP6RTRD process will configure
the advertised prefix on the interface if ConfigureThisPrefix is
specified and set to 1, or if ConfigureThisPrefix is not specified and
AdvAutonomousFlag is set to 1.
The prefix is not autoconfigured in
all other cases. Valid values are 0 and 1. The default value is the
value of AdvAutonomousFlag.
- Gateway
Specifies an IPv6 address to use as an off-link route
to a gateway. You can use this mechanism to set up default routes.
- SendInAdvertisement
Enables (yes) or disables (no) the sending
of the address prefix in routine advertisements. The default is yes.
Each address to be configured on the interface must be defined within a
address block that begins with the keyword Address followed by the IPv6
address and optionally followed by an additional address information
block of keyword-value pairs. The address value is the 128-bit IPv6
address, as follows:
In this format, each x is the hexadecimal value of a 16-bit piece of
the address. An IPv6 address typically consists of a 64-bit prefix
followed by a 64-bit interface identifier.
You can specify the following address keywords and values:
- Anycast
Configures (yes) or unconfigures (no) the specified
address as an anycast address. The default is no.
- ConfigureThisAddress
Configures (yes) or unconfigures (no)
the specified address on the interface. The default is yes.
- Gateway
Specifies an IPv6 address to use as an off-link route
to a host. You can use this mechanism to set up host routes.
The following address keywords and values are defined in RFC 2080:
- RouteMetric
Specifies a value that represents the total cost
of getting a datagram from the router to a destination. Valid values
are between 1 and 16, inclusive. The default is 1.
- RouteTag
Specifies a integer that is assigned to a route and
must be preserved and readvertised with a route. The default is 0.
For related information, see the following RFCs:
- RFC 2461, Neighbor Discovery for IP version 6 (IPv6), Narten, T.;
Nordmark, E., Simpson W. A., December 1998
- RFC 2462, IPv6 Stateless Address Autoconfiguration, Thompson, S.;
Narten, T., December 1998
- RFC 2080, RIPng for IPv6, Malkin, G., Minnear, R., January 1997
2.6.2.3 Editing the Router Configuration File
The SYS$SYSTEM:TCPIP$IP6RTRD.CONF file contains the configuration data
needed to send router advertisement messages. This file is created when
TCPIP$IP6_SETUP is run (if the system is configured as a router). The
link interface and advertised prefix are inserted, and other default
values are used.
You can modify this file as appropriate for your network, for example,
when using multiple prefix values. Example 2-1 shows a sample
configuration file.
Example 2-1 Sample TCPIP$IP6RTRD.CONF
File |
#
# Sample ip6rtrd configuration file
#
interface WE0 {
MaxRtrAdvInterval 600
MinRtrAdvInterval 200
AdvManagedFlag 0
AdvOtherConfigFlag 0
AdvLinkMTU 1500
AdvReachableTime 0
AdvRetransTimer 0
AdvMaxHopLimit 64
AdvDefaultLifetime 1800
Prefix dec:1::/64 {
AdvValidLifetime 1200
AdvPreferredLifetime 600
AdvOnLinkFlag 1
AdvAutonomousFlag 1
}
}
|