#
285830 |
|
23-Jul-2015 |
gjb |
- Copy stable/10@285827 to releng/10.2 in preparation for 10.2-RC1 builds. - Update newvers.sh to reflect RC1. - Update __FreeBSD_version to reflect 10.2. - Update default pkg(8) configuration to use the quarterly branch.[1]
Discussed with: re, portmgr [1] Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
256281 |
|
10-Oct-2013 |
gjb |
Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
228259 |
|
04-Dec-2011 |
dumbbell |
Support domain-search in dhclient(8)
The "domain-search" option (option 119) allows a DHCP server to publish a list of implicit domain suffixes used during name lookup. This option is described in RFC 3397.
For instance, if the domain-search option says: ".example.org .example.com" and one wants to resolve "foobar", the resolver will try: 1. "foobar.example.org" 2. "foobar.example.com"
The file /etc/resolv.conf is updated with a "search" directive if the DHCP server provides "domain-search".
A regression test suite is included in this patch under tools/regression/sbin/dhclient.
PR: bin/151940 Sponsored by Yakaz (http://www.yakaz.com)
|
#
183974 |
|
17-Oct-2008 |
brooks |
Support the remaining options listed in dhcp-options(5) and RFC 2132.
PR: bin/127076 Submitted by: jkim MFC after: 1 week
|
#
166602 |
|
09-Feb-2007 |
emaste |
Implement RFC3442, the Classless Static Route option.
The original DHCP specification includes a route option but it supports only class-based routes. RFC3442 adds support for specifying the netmask width for each static route. A variable length encoding is used to minimize the size of this option.
PR: bin/99534 Submitted by: Andrey V. Elsukov <bu7cher@yandex.ru> Reviewed by: brooks
|
#
149399 |
|
23-Aug-2005 |
brooks |
Add __FBSDID to all .c files in dhclient to aid in determining file versions when dealing with user problems.
|
#
148411 |
|
25-Jul-2005 |
brooks |
Change host-name from type "X" to type "t". This allows the client to accept NUL-terminated strings as required by RFC 2132.
This solution is not perfect as it removes the ability to send NUL-terminated host-name options which may be required by some broken servers. Given the current lack of an existance proof of such servers and the fact that servers that send NUL-terminated domain names do exist, this seems like an acceptable compromise. A discussion of these issues can be found at:
http://marc.theaimsgroup.com/?l=dhcp-client&m=96837107208382&w=2
PR: bin/83468 Reported by: Sean Winn <sean at gothic dot net dot au> MFC-after: 3 days
|
#
147073 |
|
07-Jun-2005 |
brooks |
This commit was generated by cvs2svn to compensate for changes in r147072, which included commits to RCS files with non-trunk default branches.
|
#
147072 |
|
07-Jun-2005 |
brooks |
Import the OpenBSD dhclient as shipped with OpenBSD-3.7 (the tag OPENBSD_3_7).
|