 |
» |
|
|
|
The following section describes the manual configuration process
for HP-UX 11i v2 IPv6. Configuring
a Primary Interface | |
To configure an IPv6 link-local address for a primary
interface, edit the IPV6_INTERFACE[0] statement in the /etc/rc.config.d/netconf-ipv6 file to specify the interface name and the interface
state, either up or down. The interface name must be the name of the physical
interface card, as reported by lanscan. To manually specify a link-local address for the primary interface,
note that the universal/local “U” bit must be
set to 0. That implies, that the manually configured address for
the primary interface must match the pattern FE80::xMxx:xxxx:xxxx:xxxx
where x are hexadecimal digits, and M is either 0, 1, 4, 5, 8, 9,
C, or D. (To be more specific, break M down to the bit level and
thus, M = yy0y, where y can be 0 or 1.) A sample netconf-ipv6 file entry is as follows: IPV6_INTERFACE[0]=”lan0”
IPV6_INTERFACE_STATE[0]=”up”
IPV6_LINK_LOCAL_ADDRESS[0]= “fe80::1” |
Note that if you do not specify a link-local address, then
as described earlier in the autoconfiguration section, a link-local
address is automatically configured for the primary interface based
on the interface’s 48-bit MAC address. Configuring
Secondary Interfaces | |
If no IPv6 Router on the LAN advertises network prefixes,
you can add secondary interface entries to the /etc/rc.config.d/netconf-ipv6 file. Editing the netconf-ipv6 file allows you to identify the network interface
name, IPv6 address, and prefix length and also to add entries to the
network routing table. A sample netconf-ipv6 file entry is as follows: IPV6_SECONDARY_INTERFACE_NAME[1]="lan0:1"
IPV6_ADDRESS[1]="2345::5432"
IPV6_PREFIXLEN[1]="64"
IPV6_SECONDARY_INTERFACE_STATE[1]="up"
DHCPV6_ENABLE[1]=0 |
Always set DHCPV6_ENABLE to 0. For more information about specifying interface names for
multiple interfaces, refer to Chapter 6 “ IPv6
Addressing and Concepts”. Configuring
a Default IPv6 Route | |
In the absence of router advertisements, you can add the default
IPv6 router information
to the /etc/rc.config.d/netconf-ipv6 file. The routing configuration parameters have
an index value, [x], that groups the routing parameters together. A sample netconf-ipv6 file entry is as follows: IPV6_DESTINATION[0]="default"
IPV6_GATEWAY[0]="2008:7:6:5:4:3:2:1"
IPV6_ROUTE_COUNT[0]="1"
IPV6_ROUTE_ARGS[0]="" |
Tunneling | |
TOUR 2.0 provides
several important changes to tunneling from in base (default) HP-UX
11i v2 IPv6. If you have previously set up any tunneling on your
HP-UX 11i v2 system(s) you will need to be aware of these differences.
Highlights of these changes are: Configured
tunneling is point-to-point with an address assigned to both tunnel
endpoints. As a result, you can no longer use the route command to configure a tunnel. You must use ifconfig and /etc/rc.config.d/netconf-ipv6, and be aware that the tunneling parameters have changed. Starting with TOUR 2.0, the
HP-UX server can be configured as a router in both point-to-point
configured tunnels and in point-to-multipoint “6to4” tunnels.
Prior to TOUR 2.0, the HP-UX 11i v2 node would only perform as a “6to4” host” not
as a “6to4” router. Parameters for “6to4” router
configuration are in ifconfig and in /etc/rc.config.d/netconf-ipv6. Automatic tunneling using
the IPv4-compatible address is not supported.
The following sections provides basic examples for configuring
an IP6-in-IP tunnel and a “6to4” tunnel. For more
information including additional optional tunnel parameters not
mentioned in these examples, refer to the /etc/rc.config.d/netconf-ipv6 file and the ifconfig(1M) man page that ship with HP-UX 11i v2 TOUR 2.0. For more information on the tunneling mechanisms supported
in TOUR 2.0 refer to the section on “Tunneling”, in Chapter 7 “IPv6
Software and Interface Technology”,
later in this Guide. | | | |  | NOTE: SAM has not been enhanced to support the tunneling enhancements available
with TOUR 2.0. | | | | |
Creating
an IP6-in-IP Point-to-Point Configured TunnelIf you regularly expect to exchange data between isolated
IPv6 networks over an IPv4 network, you may want to create a configured
IP6-in-IP tunnel. IP6-in-IP tunnels can be set up as host->host;
host->router; router->host or router->router.
In TOUR 2.0 the HP-UX 11i v2 node, can perform the role of a host
or router. A sample netconf-ipv6 file entry, for configuring the HP-UX 11i v2 IPv6 node
is as follows: TUN_INTERFACE_NAME[0]=”iptu0”
TUN_TYPE[0]=”ip6inip”
TUN_LOCAL_ADDRESS[0]=””
TUN_REMOTE_ADDRESS[0]=””
TUN_ENCAP_SRC_ADDRESS[0]=”15.1.1.1”
TUN_ENCAP_DST_ADDRESS[0]=”15.2.2.2”
TUN_INTERFACE_STATE[0]=”up” This example minimizes the number of variables that need to
be specified. For example, TUN_LOCAL_ADDRESS[0] was not specified since
the IPv6 link-local address for this value can be automatically configured
based on the TUN_ENCAP_SRC_ADDRESS[0] value. Similarly, the IPv6
link-local TUN_REMOTE_ADDRESS can be automatically configured based
on the TUN_ENCAP_DST_ADDRESS. Creating
a “6to4” Point-to-Multipoint Configured Tunnel“6to4” offers a point-to-multipoint router-to-router
tunneling mechanism for traffic going between IPv6 domains over
an IPv4 network. One of the advantages of “6to4” over configured
tunneling is that the source router can talk to any other “6to4” router
without the need for any manual configuration on the destination
router. Thus, “6to4” tunnels do not suffer the
scalability problem that configured tunnels do. A sample netconf-ipv6 file entry to configure a “6to4” tunnel
is as follows: TUN_INTERFACE_NAME[1]=”iptu1”
TUN_TYPE[1]=”6to4”
TUN_ENCAP_SRC_ADDRESS[1]=”15.13.1.2”
TUN_INTERFACE_STATE[1]=”up” In this example, the TUN_LOCAL_ADDRESS[1] was not specified since the the “6to4” address
for this value can be automatically configured based on the TUN_ENCAP_SRC_ADDRESS[1] value. For example, if the TUN_ENCAP_SRC_ADDRESS is 15.13.1.2, the “6to4” prefix is 2002:0f0d:0102,
which can be combined with an interface identifier of “1” to
form the “6to4” address 2002:0f0d:0102::1. The TUN_REMOTE_ADDRESS[1] parameter must not be
specified since“6to4” is an automatic point-to-multipoint
tunnel. The remote end-point of the tunnel will be determined based
on routing information. Similarly, the TUN_ENCAP_DST_ADDRESS[1] parameter, must not be specified since the destination
address will be automatically derived from the destination “6to4” address. Enabling
rtradvd (Router
Advertiser Daemon) | |
When rtradvd is configured, it sends router advertisement messages
to a local LAN periodically, and, when requested, by a node sending
a router solicitation message. Refer to the rtradvd(1M) man page for more information. Configuration for rtradvd is set, on a per interface basis, by editing the /etc/rtradvd.conf file. The rtradvd.conf file allows for setting global defaults as well
as interface specific settings for both interface options and prefixinfo
specific options. Refer to the rtradvd.conf(4) man page for more information. Required Steps: To configure the HP-UX
system to run rtradvd, and enable the Router Advertisement functionality,
the following steps must be taken: the /etc/rtradvd.conf file must be edited as needed; the “private” interface
flag must be cleared (“-private” for each enabled interface)
and the rtradvd daemon must be enabled. More specifically: Edit the /etc/rtradvd.conf file as needed The example below shows the minimum configuration needed to send
router advertisement packets containing the prefix 2008:65::/64 on lan0. #example begins
defaults {
AdvSendAdvertisement on ;
};
interface lan0 {
prefixinfo 2008:65::/64 {
};
};
#example ends |
For more examples, refer to the rtradvd.conf(4) man page. Edit the /etc/rc.config.d/netconf-ipv6 file to
enable rtradvd to start up at boot. Also, clear the "private"
interface flag (-private), on the appropriate interface(s) to disable
stateless address autoconfiguration using prefixes received in router
advertisements. The default is "private", and when set to "private"
the interface will autoconfigure addresses using prefixes received
in router advertisements. For more information, refer to the
relevant commented text in the /etc/rc.config.d/netconf-ipv6 file that is included with HP-UX 11i v2 IPv6 bundled
as part of TOUR 2.0. A sample netconf-ipv6 file entry, which clears the private flag and enables rtradvd, is as follows: IPV6_INTERFACE[0]=”lan0”
IPV6_INTERFACE_STATE[0]=”up”
IPV6_INTERFACE_FLAG[0]= “-private”
#
#
RTRADVD=1 |
Activating
netconf-ipv6 file Configuration | |
You can activate the netconf-ipv6 configuration
in one of the following ways: Or alternatively, by executing the ifconfig and route commands, as
needed, to make equivalent configuration settings.
Example
ifconfig and route Commands | |
HP recommends editing the /etc/rc.config.d/netconf-ipv6 file to preserve IPv6 interface and address configurations
across system reboots. For reference, the commands equivalent to
the netconf-ipv6 edits described earlier are listed below. Refer
to the ifconfig(1M) and route(1M) man pages for more information. To
configure a primary interface, enter:To
configure a secondary interface, enter:ifconfig lan0:1 inet6 2345::5432 up |
To
add a default IPv6 route, enter: route inet6 add net default 2008:7:6:5:4:3:2:1 |
To
create an IP6-in-IP tunnel, enter:ifconfig iptu0 inet6 tunnel ip6inip tsrc 192.1.1.1 tdst 192.2.2.2 up |
|
Printable version
