DHCPD: Difference between revisions
→top: has multiple releases |
m →top: typo |
||
| Line 12: | Line 12: | ||
| discontinued = |
| discontinued = |
||
| frequently updated = yes <!-- Release version update? Don't edit this page, just click on the version number! --> |
| frequently updated = yes <!-- Release version update? Don't edit this page, just click on the version number! --> |
||
| multiple |
| multiple releases = yes |
||
| programming language = |
| programming language = |
||
| operating system = [[Berkeley Software Distribution | BSD]], [[Linux]], [[Solaris (operating system) | Solaris]] |
| operating system = [[Berkeley Software Distribution | BSD]], [[Linux]], [[Solaris (operating system) | Solaris]] |
||
Revision as of 08:19, 13 June 2014
| Developer(s) | Simon Kelley |
|---|---|
| Initial release | 1999 |
| Repository | |
| Operating system | BSD, Linux, Solaris |
| Type | DHCP server |
| License | ISC License |
| Website | www |
dhcpd (an abbreviation for "DHCP daemon") is the name of a program that operates as a daemon on a server to provide Dynamic Host Configuration Protocol (DHCP) service to a network [1]
Clients may solicit an IP address (IP) from a DHCP server when they need one. The DHCP server then offers the "lease" of an IP address to the client, which the client is free to request or ignore. If the client requests it and the server acknowledges it, then the client is permitted to use that IP address for the "lease time" specified by the server. At some point before the lease expires, the client must re-request the same IP address if it wishes to continue to use it.[2]
Issued IP addresses are tracked by dhcpd through a record in the dhcpd.leases file.[3] This allows the server to maintain state over restarts of the dhcp service, which could otherwise lead to duplicate IP addresses being issued when server issued the same IP address again while another client still has the right to use it.[1]
This reference implementation of DHCP is developed by the Internet Systems Consortium [4] and is supported on Linux, Mac OS X, FreeBSD, Solaris, AIX and HP-UX.[5]
Remote access to a running instance of dhcpd is provided by the Object Management Application Programming Interface (OMAPI). [6] [7] On the server side, this interface allows for editing of registration information for managed nodes. Uses on the client include fetching configuration information, releasing and renewing leases, and changing which interfaces are managed by the DHCP client.
See also
References
- ^ a b Lemon, Ted (2012). "dhcpd - Dynamic Host Configuration Protocol Server". Canonical Systems. Retrieved June 14, 2012.
{{cite web}}: Cite has empty unknown parameter:|coauthors=(help) - ^ Droms, Ralph (March 1997). "RFC 2131 - Dynamic Host Configuration Protocol". Network Working Group. Internet Engineering Task Force.
- ^ Lemon, Ted (2012). "dhcpd.leases - DHCP Client Lease File". Canonical Systems. Retrieved June 14, 2012.
{{cite web}}: Cite has empty unknown parameter:|coauthors=(help) - ^ "DHCP - Internet Systems Consortium". Internet Systems Consortium. 2012. Retrieved June 14, 2012.
{{cite web}}: Cite has empty unknown parameter:|coauthors=(help) - ^ "README" (PDF). Internet Systems Consortium. 2012. Retrieved June 14, 2012.
{{cite web}}: Cite has empty unknown parameter:|coauthors=(help) - ^ "ISC DHCP API Interface". IPAM. Retrieved 25 January 2013.
- ^ Ralph Droms and Ted Lemon (2003). The DHCP handbook. Sams. pp. 239, 316. ISBN 9780672323270.
External links
- Configuring dhcpd on a wireless access point
- dhcpd section in the ISC website
- Official FTP repository
 | This network-related software article is a stub. You can help Wikipedia by expanding it. |