| United States-English |
|
|
|
![]() |
HP-UX Reference > iifconfig(1M)HP-UX 11i Version 1: September 2005 |
|
NAMEifconfig — configure network interface parameters SYNOPSISifconfig interface [address_family] [address [dest_address]] [parameters] ifconfig interface [address_family] DESCRIPTIONThe first form of the ifconfig command assigns an address to a network interface and/or configures network interface parameters. ifconfig must be used at boot time to define the network address of each interface present on a machine. It can also be used at other times to redefine an interface's address or other operating parameters. If the address_family is not specified, the address family defaults to IPv4. The second form of the command, without address_family, displays the current configuration for interface. If address_family is not specified, ifconfig reports the details on all supported address families. Only a user with appropriate privileges can modify the configuration of a network interface. All users can run the second form of the command. Argumentsifconfig recognizes the following arguments:
Interface NamingThe 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 encapsulation. The lanscan command can be used to display the interface name and ppa number of each interface that is associated with a network card (see 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.) IP Index NumberMultiple IP addresses assigned to the same interface may be in different subnets. An example of an interface 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. A primary interface is an interface whose IP index number is zero. A secondary interface is an interface whose IP index number is non-zero. Loopback InterfaceThe loopback interface (lo0) is automatically configured when the system boots with the TCP/IP software. The IP address and netmask of the primary IPv4 loopback interface are 127.0.0.1 and 255.0.0.0, respectively. The IP address and prefix of the primary IPv6 loopback interface are ::1 and 128 respectively. The user is not permitted to change the address of the primary loopback interface (lo0:0). It is permissible to assign other IP addresses to lo0 with non-zero IP index numbers (lo0:1, lo0:2, etc). This allows a system to have a "system IP" address that is available as long as one interface remains usable. Supernets(inet only) A supernet is a collection of smaller networks. Supernetting is a technique of using the netmask to aggregate a collection of smaller networks into a supernet. This technique is particularly useful when the limit of 254 hosts per class C network is too restrictive. In those situations a netmask containing only a portion of the network part may be applied to the hosts in these networks to form a supernet. This supernet netmask should be applied to those interfaces that connect to the supernet using the ifconfig command. For example, a host can configure its interface to connect to a class C supernet, 192.6, by configuring an IP address of 192.6.1.1 and a netmask of 255.255.0.0 to its interface. IPv6 Interfacesinet6 must be specified when an IPv6 interface is configured. The address for an IPv6 interface can either be a hostname present in the host name database (see hosts(4)), or an address in the IPv6 colon notation. Stateless Address Auto-configuration: Unlike IPv4 interfaces, IPv6 interfaces can be configured without an address and/or a prefix. Stateless address autoconfiguration requires no manual configuration of hosts, minimal (if any) configuration of routers, and no additional servers. A primary interface (lanX:0) is automatically assigned a link-local address by the system when the interface is configured. A link-local address comprises the well-known link-local prefix FE80::0 and the interface identifier, which is typically 64 bits long and is based on EUI-64 identifiers. The link-local address allows automatic discovery of other hosts and routers on the same link, using the Neighbor Discovery Protocol (see NDP(7P)). The link-local address can be used as the source address to communicate with other nodes when no routers are present. If a router on the local link advertises prefixes in router advertisements, the host autoconfigures its secondary interfaces and its default gateway. The address of an autoconfigured secondary interface is formed by prepending the prefix received from the router to the interface identifier, the same interface identifier that is used in forming the primary interface. Manual Address Configuration: IPv6 interfaces can also be configured with manually assigned addresses and/or prefixes. A primary interface must be configured with a link-local address and the prefix must not be specified. The prefix is always 10. The universal/local bit, the U bit, of the interface identifier must be 0, per section 2.5.1 of RFC 2373. Accordingly, a manually assigned address for a primary interface must have the following pattern: FE80::xMxx:xxxx:xxxx:xxxx where x is any hexadecimal digit, and M must be 0, 1, 4, 5, 8, 9, C, or D. When a primary interface is configured with a manually assigned address, secondary interfaces will be autoconfigured if the host receives prefixes from router advertisements. The addresses on the secondary interfaces will be derived from the interface identifier portion of manually configured address in the primary interface. When a secondary interface is configured with a manually assigned address, and if the user chooses an IP index number that has been used for an autoconfigured secondary interface, the manual configuration overwrites the autoconfiguration. When this happens, network connectivity through the overwritten autoconfigured IP address is temporarily lost. At a later time, when the host receives the next router advertisement, the host will bring up another secondary interface with a different IP index number, but with the same IP address, and network connectivity through that IP address is restored. Normally, a user can avoid this by checking used IP index numbers. However, there is always a possibility that address autoconfiguration due to router advertisement is happening concurrently while the user 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. Tunneling interface: The tunneling interface, tu0, enables both automatic and configured tunneling when it is marked up. Tunneling allows dual stack IPv6/IPv4 nodes to communicate over IPv4 routing infrastructures, by encapsulating the IPv6 packet inside an IPv4 packet. In automatic tunneling, the tunnel endpoint address is determined by the IPv4-compatible destination address of the IPv6 packet being tunneled. In configured tunneling, the tunnel endpoint address is configured by the user (see route(1m)). IPv6 interface flags displayed: An IPv6 interface may have three new flags that are not present in an IPv4 interface: TUNNEL, AUTO, and ONLINK. The TUNNEL flag is set for the tunnel interface (tu0). 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. Examples:
DIAGNOSTICSMessages indicate if the specified interface does not exist, the requested address is unknown, or the user is not privileged and tried to alter an interface's configuration. SEE ALSOnetstat(1), lanscan(1M), route(1M), inet(3N), inet6(3N), hosts(4), routing(7), NDP(7P). IP VErsion 6 Addressing Architecture, RFC2373, Hinden, Derring. |
||||||||||||||||||||||||||||
|
|||||||||||||||