Lines Matching refs:DHCP

47   - RFCs 2131 and 2132: IPv4 DHCP
52   - dhcpagent(1M): Solaris DHCP client
53   - dhcpinfo(1): Solaris DHCP parameter utility
88   interface under DHCP's control.  It also represents the shared state
89   with the DHCP server that granted the address, the address itself,
93   that are under DHCP control.  IP interfaces not under DHCP control
103   timers.  The name of the logical IP interface under DHCP's control
128   dhcp_pkt; "packet.h").  PKT is just the RFC 2131 DHCP packet
153   DHCPv6 naturally has some commonality with IPv4 DHCP, but also has
156   Unlike IPv4 DHCP, DHCPv6 relies on link-local IP addresses to do its
159   means that, unlike IPv4 DHCP, DHCPv6 does not need to obtain a lease
163   IPv4 DHCP expects some messages from the server to be broadcast.
169   With IPv4 DHCP, a single address plus configuration options is
184   IPv4 DHCP leaves many of the retransmit decisions up to the client,
195   mistakes from IPv4 DHCP have been fixed: DHCPv6 doesn't carry a
207   Otherwise, DHCPv6 is similar to IPv4 DHCP.  The same overall
245   DHCP state information along with the LIF information.
264   IPv4 DHCP will have one such structure per state machine, while
300   DHCP operation on lease expiry.  Otherwise, the lease is the owner
308   For IPv4 DHCP, the new linkage is straightforward.  Using the same
328   1), because IPv4 DHCP controls a single address allocation per state
356   Note also that with IPv4 DHCP, the lease points to the LIF that's
389   highly specific to IPv4 DHCP -- they have no means to handle nested
391   DHCP_OPT structure which is specific to IPv4 DHCP -- and are
460   bound only after DHCP reaches BOUND state -- that is, when it
484   DHCP implementation.  I've observed no such problems in extensive
498   DHCP instances on that PIF are bound.  In fact, the current
565   First, there are the RENEWING and REBINDING states.  For IPv4 DHCP,
579   simplify the states to be nearly identical to IPv4 DHCP.
648   IPv4 DHCP has only minimal need for persistent state, beyond the
735   For the first function, in.ndpd needs to use the same DHCP control
761   DHCP, DHCPv6 does not give the netmask or prefix length along with
1099   Zones currently cannot address any IP interfaces by way of DHCP.
1111   values with IPv4 DHCP, which would quickly solve the problem of
1112   using DHCP for IPv4 address assignment in non-global zones as well.
1213     - Fix known bugs in DHCP filtering