ifconfig.1m (2011 09)

i
ifconfig(1M) ifconfig(1M)
tsrc addr Specify the source addr of the tunnel. This is the source address in the
encapsulating (outer) header. It should be an unicast address configured
on an interface in the tunnel entry-point node. For tunnel types
ipinip6 and ip6inip6, the addr should be an IPv6 address. For tun-
nel types ip6inip and 6to4, the addr should be an IPv4 address.
arp (inet only) Enable the user of the Address Resolution Protocol in map-
ping between network level addresses and link level addresses (default).
If an interface already had the Address Resolution Protocol disabled, the
user must "unplumb" the interface before it can be enabled for Address
Resolution Protocol.
-arp (inet only) Disable the use of the Address Resolution Protocol. If an
interface already had the Address Resolution Protocol enabled, the user
must "unplumb" the interface before it can be disabled for Address Reso-
lution Protocol.
plumb Setup the Streams plumbing needed for TCP/IP for a primary interface
name. (See the Interface Naming subsection given below.). By default,
the plumb operation is done automatically when an IP address is
specified for an interface.
unplumb Tear down the Streams plumbing for a primary interface name. (See the
Interface Naming subsection given below.) Secondary interface does not
require "plumbing". A secondary IPv4 interface can be removed by
assigning an IP address of 0.0.0.0 to it. Remove a secondary IPv6 inter-
face by assigning an IP address of :: to it.
force (It is supported only when HP-UX Secure Resource Partitions is installed
and enabled with system style containers (refer to srp(5))).
Mark an interface with "force" flag. The "force" flag initiates the feature
of pushing local communication(communication within the host) on the
wire.
In order to initiate local-local communication on wire, "force" flag needs
to be set and user needs to add special route to reach this interface via
gateway from the other end point of the local-local communication. (For
information, see "route(1M)" for adding special routes).
local-local communication is never pushed on the wire in the absence of
special routes.
-force (It is supported only when HP-UX Secure Resource Partitions is installed
and enabled with system style containers (refer to srp(5))).
It is used to disable the feature of pushing local communication on wire.
This is the default behavior.
Interface Naming
The interface name associated with a network card is composed of the name of the interface (e.g.
lan or
snap ), the ppa number which identifies the card instance for this interface, and an optional IP index
number which allows the configuration of multiple IP addresses for an interface. For LAN cards, the
interface name lan will be used to designate Ethernet encapsulation and snap for IEEE 802.3 encapsu-
lation. The nwmgr and lanscan commands can be used to display the interface name and ppa number
of each interface that is associated with a network card (see nwmgr(1M) and lanscan (1M)).
IPv4 and IPv6 interfaces can coexist over the same physical network interface device using the same
naming scheme. IPv6 interfaces are configured using the "inet6" ifconfig subcommand. (See the IPv6
subsection given below.)
The tunnel interface names should be
iptu* for "IP6-in-IP" tunnels and 6to4 tunnels. Example:
iptu0, iptu1. The tunnel interface names should be ip6tu* for "IP-in-IP6" tunnels and "IP6-in-IP6"
tunnels. Example: ip6tu0, ip6tu1.
IP Index Number
Multiple IP addresses assigned to the same interface may be in different subnets. An example of an inter-
face name without an IP index number is
lan0. An example of an interface name with a IP index
number is lan0:1. Note: specifying lan0:0 is equivalent to lan0.
HP-UX 11i Version 3: September 2011 3 Hewlett-Packard Company 3