{"id":13641496,"url":"https://github.com/isc-projects/dhcp","last_synced_at":"2025-04-09T08:10:16.455Z","repository":{"id":41102751,"uuid":"234092917","full_name":"isc-projects/dhcp","owner":"isc-projects","description":"ISC DHCP is enterprise grade, open source solution for DHCP servers, relay agents, and clients, supports both IPv4 and IPv6, and is suitable for use in high-volume and high-reliability applications.","archived":false,"fork":false,"pushed_at":"2023-03-29T15:56:32.000Z","size":42378,"stargazers_count":176,"open_issues_count":0,"forks_count":80,"subscribers_count":11,"default_branch":"master","last_synced_at":"2025-04-02T05:08:53.955Z","etag":null,"topics":["c","console","dhcp","dhcp-client","dhcp-relay","dhcp-server","dhcpv6","eol","failover","freebsd","linux","macos","netbsd","openbsd"],"latest_commit_sha":null,"homepage":"https://gitlab.isc.org/isc-projects/dhcp","language":"C","has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/isc-projects.png","metadata":{"files":{"readme":"README","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null}},"created_at":"2020-01-15T14:01:24.000Z","updated_at":"2025-03-30T11:39:18.000Z","dependencies_parsed_at":"2024-01-14T09:11:00.062Z","dependency_job_id":"5cf64077-63b2-4d41-b1c1-94432a2e5254","html_url":"https://github.com/isc-projects/dhcp","commit_stats":null,"previous_names":[],"tags_count":392,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/isc-projects%2Fdhcp","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/isc-projects%2Fdhcp/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/isc-projects%2Fdhcp/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/isc-projects%2Fdhcp/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/isc-projects","download_url":"https://codeload.github.com/isc-projects/dhcp/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":247999861,"owners_count":21031046,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["c","console","dhcp","dhcp-client","dhcp-relay","dhcp-server","dhcpv6","eol","failover","freebsd","linux","macos","netbsd","openbsd"],"created_at":"2024-08-02T01:01:21.235Z","updated_at":"2025-04-09T08:10:16.432Z","avatar_url":"https://github.com/isc-projects.png","language":"C","readme":"\t      Internet Systems Consortium DHCP Distribution\n\t\t\t     Version 4.4.3-P1\n\t\t\t      5 October 2022\n\n\t\t\t      README FILE\n\nNOTE: This software is now End-Of-Life. 4.4.3 is the final release planned. \nWe will continue to keep the public issue tracker and user mailing list open.\n\nYou should read this file carefully before trying to install or use\nthe ISC DHCP Distribution.\n\n\t\t\t  TABLE OF CONTENTS\n\n\t1\tWHERE TO FIND DOCUMENTATION\n\t2\tRELEASE STATUS\n\t3\tBUILDING THE DHCP DISTRIBUTION\n\t 3.1\t UNPACKING IT\n\t 3.2\t CONFIGURING IT\n\t  3.2.1\t  DYNAMIC DNS UPDATES\n\t  3.2.2   LOCALLY DEFINED OPTIONS\n\t 3.3\t BUILDING IT\n\t4\tINSTALLING THE DHCP DISTRIBUTION\n\t5\tUSING THE DHCP DISTRIBUTION\n\t 5.1\t  FIREWALL RULES\n\t 5.2\t LINUX\n\t  5.2.1\t  IF_TR.H NOT FOUND\n\t  5.2.2\t  SO_ATTACH_FILTER UNDECLARED\n\t  5.2.3\t  PROTOCOL NOT CONFIGURED\n\t  5.2.4\t  BROADCAST\n\t  5.2.6\t  IP BOOTP AGENT\n\t  5.2.7\t  MULTIPLE INTERFACES\n     5.3    ATF\n\t6\tSUPPORT\n\t 6.1\t HOW TO REPORT BUGS\n\t7\tHISTORY\n\n\t\t      WHERE TO FIND DOCUMENTATION\n\nDocumentation for this software includes this README file, the\nRELNOTES file, and the manual pages, which are in the server, common,\nclient and relay subdirectories.  The README file (this file) includes\nlate-breaking operational and system-specific information that you\nshould read even if you don't want to read the manual pages, and that\nyou should *certainly* read if you run into trouble.  Internet\nstandards relating to the DHCP protocol are listed in the References\ndocument that is available in html, txt and xml formats in doc/\nsubdirectory.  You will have the best luck reading the manual pages if\nyou build this software and then install it, although you can read\nthem directly out of the distribution if you need to.\n\nDHCP server documentation is in the dhcpd man page.  Information about\nthe DHCP server lease database is in the dhcpd.leases man page.\nServer configuration documentation is in the dhcpd.conf man page as\nwell as the dhcp-options man page.   A sample DHCP server\nconfiguration is in the file server/dhcpd.conf.example.   The source for\nthe dhcpd, dhcpd.leases and dhcpd.conf man pages is in the server/ sub-\ndirectory in the distribution.   The source for the dhcp-options.5\nman page is in the common/ subdirectory. The server component is End-of-Life. \n\nDHCP Client documentation is in the dhclient man page.  DHCP client\nconfiguration documentation is in the dhclient.conf man page and the\ndhcp-options man page.  The DHCP client configuration script is\ndocumented in the dhclient-script man page.   The format of the DHCP\nclient lease database is documented in the dhclient.leases man page.\nThe source for all these man pages is in the client/ subdirectory in\nthe distribution.   In addition, the dhcp-options man page should be\nreferred to for information about DHCP options. The client component\nis End-of-Life.\n\nDHCP relay agent documentation is in the dhcrelay man page, the source\nfor which is distributed in the relay/ subdirectory. The relay component\nis End-of-Life.\n\nKEA Migration Assistant documentation, including how to build, install\nand use it, is included in the keama/ directory.\n\nTo read installed manual pages, use the man command.  Type \"man page\"\nwhere page is the name of the manual page.   This will only work if\nyou have installed the ISC DHCP distribution using the ``make install''\ncommand (described later).\n\nIf you want to read manual pages that aren't installed, you can type\n``nroff -man page |more'' where page is the filename of the\nunformatted manual page.  The filename of an unformatted manual page\nis the name of the manual page, followed by '.', followed by some\nnumber - 5 for documentation about files, and 8 for documentation\nabout programs.   For example, to read the dhcp-options man page,\nyou would type ``nroff -man common/dhcp-options.5 |more'', assuming\nyour current working directory is the top level directory of the ISC\nDHCP Distribution.\n\nPlease note that the pathnames of files to which our manpages refer\nwill not be correct for your operating system until after you iterate\n'make install' (so if you're reading a manpage out of the source\ndirectory, it may not have up-to-date information).\n\n\t\t\t\tRELEASE STATUS\n\nVersion 4.4.3-P1 is a maintenance release of the DHCP client, relay and\nserver. It is the final release for the client and relay components,\nwhich have reached end-of-life and will no longer be maintained.\n\n\t\t    BUILDING THE DHCP DISTRIBUTION\n\n\t\t\t     UNPACKING IT\n\nTo build the DHCP Distribution, unpack the compressed tar file using\nthe tar utility and the gzip command - type something like:\n\n\tgunzip dhcp-4.4.3-P1.tar.gz\n\ttar xvf dhcp-4.4.3-P1.tar\n\n\t\t\t    CONFIGURING IT\n\nNow, cd to the dhcp-4.4.3-P1 subdirectory that you've just created and\nconfigure the source tree by typing:\n\n\t./configure\n\nIf the configure utility can figure out what sort of system you're\nrunning on, it will create a custom Makefile for you for that\nsystem; otherwise, it will complain.  If it can't figure out what\nsystem you are using, that system is not supported - you are on\nyour own.\n\nSeveral options may be enabled or disabled via the configure command.\nYou can get a list of these by typing:\n\n\t./configure --help\n\nIf you want to use dynamic shared libraries automake, autoconf\n(aka GNU autotools) and libtool must be available. The DHCP\ndistribution provides 3 configure.ac* files: the -lt version\nhas no libtool support and was copied to the configure.ac\nstandard file in the distribution. To enable libtool support\nyou should perform these steps:\n\n\tcp configure.ac+lt configure.ac\n\tautoreconf -i\n\nafter you can use the regenerated configure as usual\n(with libtool support (--enable-libtool) on by default):\n\n\t./configure\n\nFor compatibility (and people who don't read this documentation)\nthe --enable-libtool configuration file is supported even by\nthe distributed configure (and off by default). The previous\nsteps are performed and the regenerated configure called with\nalmost the same parameters (this \"almost\" makes the use of\nthis feature not recommended).\n\nNote you can't go back from with libtool support to without libtool\nsupport by restoring configure.ac and rerun autoreconf. If you\nwant or need to restore the without libtool support state the\nrequired way is to simply restore the whole distribution.\n\n\t\t\t DYNAMIC DNS UPDATES\n\nA fully-featured implementation of dynamic DNS updates is included in\nthis release.  It uses libraries from BIND and, to avoid issues with\ndifferent versions, includes the necessary BIND version.  The appropriate\nBIND libraries will be compiled and installed in the bind subdirectory\nas part of the make step.  In order to build the necessary libraries you\nwill need to have \"gmake\" available on your build system.\n\n\nThere is documentation for the DDNS support in the dhcpd.conf manual\npage - see the beginning of this document for information on finding\nmanual pages.\n\n\t\t       LOCALLY DEFINED OPTIONS\n\nIn previous versions of the DHCP server there was a mechanism whereby\noptions that were not known by the server could be configured using\na name made up of the option code number and an identifier:\n\"option-nnn\"   This is no longer supported, because it is not future-\nproof.   Instead, if you want to use an option that the server doesn't\nknow about, you must explicitly define it using the method described\nin the dhcp-options man page under the DEFINING NEW OPTIONS heading.\n\n\t\t\t     BUILDING IT\n\nOnce you've run configure, just type ``make'', and after a while\nyou should have a dhcp server.  If you get compile errors on one\nof the supported systems mentioned earlier, please let us know.\nIf you get warnings, it's not likely to be a problem - the DHCP\nserver compiles completely warning-free on as many architectures\nas we can manage, but there are a few for which this is difficult.\nIf you get errors on a system not mentioned above, you will need\nto do some programming or debugging on your own to get the DHCP\nDistribution working.\n\nIf you cross compile you have to follow the instructions from\nthe BIND README, in particular you must set the BUILD_CC\nenvironment variable.\n\n\t\t   INSTALLING THE DHCP DISTRIBUTION\n\nOnce you have successfully gotten the DHCP Distribution to build, you\ncan install it by typing ``make install''.   If you already have an old\nversion of the DHCP Distribution installed, you may want to save it\nbefore typing ``make install''.\n\n\t\t     USING THE DHCP DISTRIBUTION\n\n\t\t\t    FIREWALL RULES\n\nIf you are running the DHCP server or client on a computer that's also\nacting as a firewall, you must be sure to allow DHCP packets through\nthe firewall.  In particular, your firewall rules _must_ allow packets\nfrom IP address 0.0.0.0 to IP address 255.255.255.255 from UDP port 68\nto UDP port 67 through.  They must also allow packets from your local\nfirewall's IP address and UDP port 67 through to any address your DHCP\nserver might serve on UDP port 68.  Finally, packets from relay agents\non port 67 to the DHCP server on port 67, and vice versa, must be\npermitted.\n\nWe have noticed that on some systems where we are using a packet\nfilter, if you set up a firewall that blocks UDP port 67 and 68\nentirely, packets sent through the packet filter will not be blocked.\nHowever, unicast packets will be blocked.   This can result in strange\nbehaviour, particularly on DHCP clients, where the initial packet\nexchange is broadcast, but renewals are unicast - the client will\nappear to be unable to renew until it starts broadcasting its\nrenewals, and then suddenly it'll work.   The fix is to fix the\nfirewall rules as described above.\n\n\t\t\t   PARTIAL SERVERS\n\nIf you have a server that is connected to two networks, and you only\nwant to provide DHCP service on one of those networks (e.g., you are\nusing a cable modem and have set up a NAT router), if you don't write\nany subnet declaration for the network you aren't supporting, the DHCP\nserver will ignore input on that network interface if it can.  If it\ncan't, it will refuse to run - some operating systems do not have the\ncapability of supporting DHCP on machines with more than one\ninterface, and ironically this is the case even if you don't want to\nprovide DHCP service on one of those interfaces.\n\n\t\t\t\tLINUX\n\nThere are three big LINUX issues: the all-ones broadcast address,\nLinux 2.1 ip_bootp_agent enabling, and operations with more than one\nnetwork interface.   There are also two potential compilation/runtime\nproblems for Linux 2.1/2.2: the \"SO_ATTACH_FILTER undeclared\" problem\nand the \"protocol not configured\" problem.\n\n\t\t    LINUX: PROTOCOL NOT CONFIGURED\n\nIf you get the following message, it's because your kernel doesn't\nhave the Linux packetfilter or raw packet socket configured:\n\n Make sure CONFIG_PACKET (Packet socket) and CONFIG_FILTER (Socket\n Filtering) are enabled in your kernel configuration\n\nIf this happens, you need to configure your Linux kernel to support\nSocket Filtering and the Packet socket, or to select a kernel provided\nby your Linux distribution that has these enabled (virtually all modern\nones do by default).\n\n\t\t\t   LINUX: BROADCAST\n\nIf you are running a recent version of Linux, this won't be a problem,\nbut on older versions of Linux (kernel versions prior to 2.2), there\nis a potential problem with the broadcast address being sent\nincorrectly.\n\nIn order for dhcpd to work correctly with picky DHCP clients (e.g.,\nWindows 95), it must be able to send packets with an IP destination\naddress of 255.255.255.255.  Unfortunately, Linux changes an IP\ndestination of 255.255.255.255 into the local subnet broadcast address\n(here, that's 192.5.5.223).\n\nThis isn't generally a problem on Linux 2.2 and later kernels, since\nwe completely bypass the Linux IP stack, but on old versions of Linux\n2.1 and all versions of Linux prior to 2.1, it is a problem - pickier\nDHCP clients connected to the same network as the ISC DHCP server or\nISC relay agent will not see messages from the DHCP server.   It *is*\npossible to run into trouble with this on Linux 2.2 and later if you\nare running a version of the DHCP server that was compiled on a Linux\n2.0 system, though.\n\nIt is possible to work around this problem on some versions of Linux\nby creating a host route from your network interface address to\n255.255.255.255.   The command you need to use to do this on Linux\nvaries from version to version.   The easiest version is:\n\n\troute add -host 255.255.255.255 dev eth0\n\nOn some older Linux systems, you will get an error if you try to do\nthis.   On those systems, try adding the following entry to your\n/etc/hosts file:\n\n255.255.255.255\tall-ones\n\nThen, try:\n\n\troute add -host all-ones dev eth0\n\nAnother route that has worked for some users is:\n\n\troute add -net 255.255.255.0 dev eth0\n\nIf you are not using eth0 as your network interface, you should\nspecify the network interface you *are* using in your route command.\n\n\t\t\tLINUX: IP BOOTP AGENT\n\nSome versions of the Linux 2.1 kernel apparently prevent dhcpd from\nworking unless you enable it by doing the following:\n\n\t      echo 1 \u003e/proc/sys/net/ipv4/ip_bootp_agent\n\n\n\t\t      LINUX: MULTIPLE INTERFACES\n\nVery old versions of the Linux kernel do not provide a networking API\nthat allows dhcpd to operate correctly if the system has more than one\nbroadcast network interface.  However, Linux 2.0 kernels with version\nnumbers greater than or equal to 2.0.31 add an API feature: the\nSO_BINDTODEVICE socket option.  If SO_BINDTODEVICE is present, it is\npossible for dhcpd to operate on Linux with more than one network\ninterface.  In order to take advantage of this, you must be running a\n2.0.31 or greater kernel, and you must have 2.0.31 or later system\nheaders installed *before* you build the DHCP Distribution.\n\nWe have heard reports that you must still add routes to 255.255.255.255\nin order for the all-ones broadcast to work, even on 2.0.31 kernels.\nIn fact, you now need to add a route for each interface.   Hopefully\nthe Linux kernel gurus will get this straight eventually.\n\nLinux 2.1 and later kernels do not use SO_BINDTODEVICE or require the\nbroadcast address hack, but do support multiple interfaces, using the\nLinux Packet Filter.\n\n\t\t\t     LINUX: OpenWrt\n\nDHCP 4.1 has been tested on OpenWrt 7.09 and 8.09.  In keeping with\nstandard practice, client/scripts now includes a dhclient-script file\nfor OpenWrt.  However, this is not sufficient by itself to run dhcp on\nOpenWrt; a full OpenWrt package for DHCP is available at\nftp://ftp.isc.org/isc/dhcp/dhcp-4.1.0-openwrt.tar.gz\n\n\t\t    LINUX: 802.1q VLAN INTERFACES\n\nIf you're using 802.1q vlan interfaces on Linux, it is necessary to\nvconfig the subinterface(s) to rewrite the 802.1q information out of\npackets received by the dhcpd daemon via LPF:\n\n\tvconfig set_flag eth1.523 1 1\n\nNote that this may affect the performance of your system, since the\nLinux kernel must rewrite packets received via this interface.  For\nmore information, consult the vconfig man pages.\n\n\n\t\t\t       ATF\n\nPlease see the file DHCP/doc/devel/atf.dox for a description of building\nand using these tools.\n\nThe optional unit tests use ATF (Automated Testing Framework) including\nthe atf-run and atf-report tools. ATF deprecated these tools in\nversion 0.19 and removed these tools from its sources in version 0.20,\nrequiring you to get an older version, use Kyua with an ATF compatibility\npackage or use the version included in the Bind sources.\n\n\t\t\t       SUPPORT\n\nThe Internet Systems Consortium DHCP server is developed and distributed\nby ISC in the public trust, thanks to the generous donations of its\nsponsors.  ISC now also offers commercial quality support contracts for\nISC DHCP, more information about ISC Support Contracts can be found at\nthe following URL:\n\n\thttps://www.isc.org/support/\n\nPlease understand that we may not respond to support inquiries unless\nyou have a support contract.  ISC will continue its practice of always\nresponding to critical items that effect the entire community, and\nresponding to all other requests for support upon ISC's mailing lists\non a best-effort basis.\n\nHowever, ISC DHCP has attracted a fairly sizable following on the\nInternet, which means that there are a lot of knowledgeable users who\nmay be able to help you if you get stuck.  These people generally\nread the dhcp-users@isc.org mailing list.  Be sure to provide as much\ndetail in your query as possible.\n\nIf you are going to use ISC DHCP, you should probably subscribe to\nthe dhcp-users or dhcp-announce mailing lists.\n\nWHERE TO SEND FEATURE REQUESTS: We like to hear your feedback.  We may\nnot respond to it all the time, but we do read it.  If ISC DHCP doesn't\nwork well for you, or you have an idea that would improve it for your\nuse, please create an issue at https://gitlab.isc.org/isc-projects/dhcp/issues.\nThis is also an excellent place to send patches that add new features.\n\nWHERE TO REPORT BUGS: If you want the act of sending in a bug report\nto result in you getting help in the form of a fixed piece of\nsoftware, you are asking for help.  Your bug report is helpful to us,\nbut fundamentally you are making a support request, so please use the\naddresses described in the previous paragraphs.  If you are _sure_ that\nyour problem is a bug, and not user error, or if your bug report\nincludes a patch, you can submit it to our ticketing system at\nhttps://gitlab.isc.org/isc-projects/dhcp/issues.  If you have not received\na notice that the ticket has been resolved, then we're still working on it.\nNotice that this is the final release that features client and relay\ncomponents. Reporting bugs in them makes limited sense. The ISC team\nwill not be fixing any issues related to client or relay. They may be\nuseful for other users to document some problems or perhaps discuss\nand share workarounds.\n\nPLEASE DO NOT REPORT BUGS IN OLD SOFTWARE RELEASES!  Fetch the latest\nrelease and see if the bug is still in that version of the software,\nand if it is still present, _then_ report it.  ISC release versions\nalways have three numbers, for example: 1.2.3.  The 'major release' is\n1 here, the 'minor release' is 2, and the 'maintenance release' is 3.\n\nPLEASE take a moment to determine where the ISC DHCP distribution\nthat you're using came from.  ISC DHCP is sometimes heavily modified\nby integrators in various operating systems - it's not that we\nfeel that our software is perfect and incapable of having bugs, but\nrather that it is very frustrating to find out after many days trying\nto help someone that the sources you're looking at aren't what they're\nrunning.  When in doubt, please retrieve the source distribution from\nISC's web page and install it.\n\n\t\tHOW TO REPORT BUGS OR REQUEST HELP\n\nWhen you report bugs or ask for help, please provide us complete\ninformation.  A list of information we need follows.  Please read it\ncarefully, and put all the information you can into your initial bug\nreport.  This will save us a great deal of time and more informative\nbug reports are more likely to get handled more quickly overall.\n\n      1.  The specific operating system name and version of the\n\t  machine on which the DHCP server or client is running.\n      2.  The specific operating system name and version of the\n\t  machine on which the client is running, if you are having\n\t  trouble getting a client working with the server.\n      3.  If you're running Linux, the version number we care about is\n\t  the kernel version and maybe the library version, not the\n\t  distribution version - e.g., while we don't mind knowing\n\t  that you're running Redhat version mumble.foo, we must know\n\t  what kernel version you're running, and it helps if you can\n\t  tell us what version of the C library you're running,\n\t  although if you don't know that off the top of your head it\n\t  may be hard for you to figure it out, so don't go crazy\n\t  trying.\n      4.  The specific version of the DHCP distribution you're\n\t  running, as reported by dhcpd -t.\n      5.  Please explain the problem carefully, thinking through what\n\t  you're saying to ensure that you don't assume we know\n\t  something about your situation that we don't know.\n      6.  Include your dhcpd.conf and dhcpd.leases file as MIME attachments\n\t  if they're not over 100 kilobytes in size each.  If they are\n\t  this large, please make them available to us, e.g., via a hidden\n\t  http:// URL or FTP site.  If you're not comfortable releasing\n\t  this information due to sensitive contents, you may encrypt\n\t  the file to our release signing key, available on our website.\n      7.  Include a log of your server or client running until it\n\t  encounters the problem - for example, if you are having\n\t  trouble getting some client to get an address, restart the\n\t  server with the -d flag and then restart the client, and\n\t  send us what the server prints.   Likewise, with the client,\n\t  include the output of the client as it fails to get an\n\t  address or otherwise does the wrong thing.   Do not leave\n\t  out parts of the output that you think aren't interesting.\n      8.  If the client or server is dumping core, please run the\n\t  debugger and get a stack trace, and include that in your\n\t  bug report.   For example, if your debugger is gdb, do the\n\t  following:\n\n\t\tgdb dhcpd dhcpd.core\n\t\t(gdb) where\n\t\t      [...]\n\t\t(gdb) quit\n\n\t  This assumes that it's the dhcp server you're debugging, and\n\t  that the core file is in dhcpd.core.\n\nPlease see https://www.isc.org/dhcp/ for details on how to subscribe\nto the ISC DHCP mailing lists.\n\n\t\t\t       HISTORY\n\nISC DHCP was originally written by Ted Lemon under a contract with\nVixie Labs with the goal of being a complete reference implementation\nof the DHCP protocol.  Funding for this project was provided by\nInternet Systems Consortium. The first release of the ISC DHCP\ndistribution in December 1997 included just the DHCP server.\nRelease 2 in June 1999 added a DHCP client and a BOOTP/DHCP relay\nagent. DHCP 3 was released in October 2001 and included DHCP failover\nsupport, OMAPI, Dynamic DNS, conditional behaviour, client classing,\nand more. Version 3 of the DHCP server was funded by Nominum, Inc.\nThe 4.0 release in December 2007 introduced DHCPv6 protocol support\nfor the server and client. The client and relay components reached\ntheir End-of-Life in January 2022.\n\nThis product includes cryptographic software written\nby Eric Young (eay@cryptsoft.com).\n","funding_links":[],"categories":["C"],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fisc-projects%2Fdhcp","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fisc-projects%2Fdhcp","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fisc-projects%2Fdhcp/lists"}