src/contrib/isc-dhcp, branch main

Remove isc-dhcp files from HEAD now that we're using the OpenBSD

2005-06-29T01:46:40Z

dhclient. Reminded by: ru Approved by: re (blanket dhclient)

Make 'client DNS forward update' working again which got broken in rev.

2004-08-16T22:35:56Z

RC9 of dhclient 3.0.1. This fix will be part of dhclient 3.0.2. It is also part of the official redhat package. Submitted by: Jason Vas Dias Discussed on: dhcp-hackers@isc.org

Document local changes r1.41 and r1.42 of dhclient.c

2004-08-16T21:31:34Z

Recommit removed Rev. 1.40. This fix does solve a FPE with negative lease

2004-08-16T21:26:04Z

time as described in the PR below. It seems that this patch should have been part of the vendor tree but got accidently missed in the 3.0.1 final version. It will definitly be part of 3.0.2 but until then it's a long way to go. Submitted by: ISC (Vendor) PR: bin/54517

It could happen that the renew/rebind times in the leasefile were

2004-08-16T16:09:50Z

expired but the expire time itself was still valid and in the future. If this happened we ended up using the state S_RENEW with an INADDR_BROADCAST address set in the request and dhclient never got any answer back. The only workaround was to delete the lease file. Fix this case with a check for the S_RENEW and a fallback to the S_INIT state. PR: bin/69361 Submitted by: Andrew Gallatin

Sync a reverted part of dhclient.c with the vendor source. It seems

2004-08-16T15:48:02Z

that a buxfix from rc14 got backed out again. We do the same.

Resolve conflicts from dhclient 3.0.1 final import.

2004-08-15T23:37:10Z

No functional changes in this import.

This commit was generated by cvs2svn to compensate for changes in r133783,

2004-08-15T23:33:13Z

which included commits to RCS files with non-trunk default branches.

Import ISC DHCP 3.0.1 client.

2004-08-15T23:33:13Z

Fix a number of incorrect assumptions regarding the size of time_t.

2004-07-06T15:15:14Z

The code has its own TIME type, which is actually defined to time_t, but it still used u_int32_t in some places. In addition, dhclient not only had two separate global cur_time variables, one of which was defined as u_int32_t and the other as TIME, but cur_time was sometimes shadowed by local variables, leading to widespread confusion as to which of these variable was being referenced. There is a lesson in here somewhere: a decent compiler with warnings enabled should have caught all of this long before it became a problem. This patch has been submitted to the vendor, but it will likely be some time before they release a version that includes it. Approved by: mbr