JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Working With DHCP in Oracle Solaris 11.1     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information


1.  About DHCP (Overview)

2.  Administering the ISC DHCP Service

3.  Configuring and Administering the DHCP Client

About the DHCP Client

The DHCP Administrative Model

MAC Address and Client ID

Differences Between DHCPv4 and DHCPv6

DHCP Protocol Details

Logical Interfaces

Option Negotiation

Configuration Syntax

DHCP Client Startup

DHCPv6 Communication

How DHCP Client Protocols Manage Network Configuration Information

How the DHCPv4 Client Manages Network Configuration Information

How the DHCPv6 Client Manages Network Configuration Information

DHCP Client Shutdown

Enabling and Disabling a DHCP Client

How to Enable a DHCP Client

How to Disable a DHCP Client

DHCP Client Administration

ipadm Command Options Used With the DHCP Client

Setting DHCP Client Configuration Parameters

For DHCPv4

For DHCPv4 and DHCPv6

DHCP Client Systems With Multiple Network Interfaces

DHCPv4 Client Host Names

How to Enable a DHCPv4 Client to Request a Specific Host Name

DHCP Client Systems and Name Services

DHCP Client Event Scripts

4.  DHCP Commands and Files (Reference)


DHCP Client Systems With Multiple Network Interfaces

The DHCP client can simultaneously manage several different interfaces on one system. The interfaces can be physical interfaces or logical interfaces. Each interface has its own IP address and lease time. If more than one network interface is configured for DHCP, the client issues separate requests to configure them. The client maintains a separate set of network configuration parameters for each interface. Although the parameters are stored separately, some of the parameters are global in nature. The global parameters apply to the system as a whole, rather than to a particular network interface.

The host name, NIS domain name, and time zone are examples of global parameters. Global parameters usually have different values for each interface. However, only one value can be used for each global parameter associated with each system. To be sure that there is only one answer to a query for a global parameter, only the parameters for the primary network interface are used.

The DHCP client manages leases for logical interfaces and physical interfaces identically, except for the following limitation on logical interfaces: the DHCP client does not manage the default routes that are associated with logical interfaces.

The Oracle Solaris kernel associates routes with physical interfaces, not logical interfaces. When a physical interface's IP address is established, the necessary default routes should be placed in the routing table. If DHCP is used subsequently to configure a logical interface associated with that physical interface, the necessary routes should already be in place. The logical interface uses the same routes.

When a lease expires on a physical interface, the DHCP client removes the default routes that are associated with the interface. When a lease expires on a logical interface, the DHCP client does not remove the default routes associated with the logical interface. The associated physical interface and possibly other logical interfaces might need to use the same routes.

If you need to add or remove default routes that are associated with a DHCP-controlled interface, you can use the DHCP client event script mechanism. See DHCP Client Event Scripts.