ifconfig.1m (2011 09)
i
ifconfig(1M) ifconfig(1M)
manually configures secondary interfaces.
To disable communication through a specific IP address on an autoconfigured secondary interface, that
secondary interface should be marked down, not removed or overwritten with a different IP address. If
that interface is removed or overwritten, the host will reconfigure another secondary interface with the
same IP address when it receives the next router advertisement. Alternatively, the router can be
configured to stop advertising the prefix that corresponds to the offending IP address.
Anycast addresses can only be manually configured and their configuration will overwrite any manual or
auto-configured address on the secondary interface.
IPv6 interface flags displayed:
An IPv6 interface may have four new flags that are not present on an IPv4 interface:
TUNNEL,
AUTO,
ONLINK, and ANYCAST. The TUNNEL
flag is set for the tunnel interfaces. The AUTO flag is set for
autoconfigured secondary interfaces. The
ONLINK flag is set for interfaces with IP addresses that can be
reached without going through a router. The ANYCAST
flag is set for secondary interfaces configured
with an anycast address.
Examples:
Stateless address autoconfiguration with link-local address
ifconfig lan0 inet6 up
Manual configuration for a primary interface with link-local address
ifconfig lan0 inet6 fe80::1 up
Manual configuration for a secondary interface with link-local address
ifconfig lan0:1 inet6 fe80::3 up
Manual configuration for a secondary interface with global address
ifconfig lan0:3 inet6 2222::4 up
Manual configuration for a secondary interface with an anycast address
ifconfig lan0:4 inet6 3ffe::3 anycast up
Tunnel interface configuration:
HP-UX supports "IP6-in-IP" configured tunnels as specified in RFC 4213, "IP-in-IP6" and "IP6-in-IP6"
configured tunnels as specified in RFC 2473, and 6to4 automatic tunnel as specified in RFC 3056.
IP6-in-IP tunnel interface configuration
"IP6-in-IP" configured tunnel allows dual stack IPv6/IPv4 nodes to communicate over an IPv4 infrastruc-
ture, by encapsulating the IPv6 packet inside an IPv4 header. The tunnel configuration must be done on
both the local (tunnel entry-point) system and the remote (tunnel exit-point) system. "IP6-in-IP" tunnels
can be configured as shown below:
ifconfig iptu0 inet6 tunnel ip6inip [source_link-local_address]
\
[destination_link-local_address]
tsrc tunnel_local_IPv4_address
\
tdst tunnel_remote_IPv4_address up
The source and destination link-local IPv6 addresses of the tunnel interface are optional; if they are not
specified, they will be autoconfigured based on the tunnel_local_IPv4_address and
tunnel_remote_IPv4_address, respectively.
The tunnel_local_IPv4_address should be an address configured on the local system, and
tunnel_remote_IPv4_address should be an address configured on the remote system.
Example. On the local system:
# ifconfig iptu0 inet6 tunnel ip6inip tsrc 192.168.1.1 \
tdst 192.168.2.2 up
Example. On the remote system:
# ifconfig iptu0 inet6 tunnel ip6inip tsrc 192.168.2.2 \
tdst 192.168.1.1 up
If multiple tunnels are configured with the same tunnel_local_IPv4_address, autoconfiguration of only
the first tunnel will succeed. Other tunnels should be manually configured with link-local addresses.
Manual link-local addresses can be assigned to the tunnel interface as shown below:
HP-UX 11i Version 3: September 2011 − 5 − Hewlett-Packard Company 5