ports/97074: isc-dhcpd 3.0.4 port not working

Matthew Berryman mattjb at eleceng.adelaide.edu.au
Tue May 16 03:50:21 UTC 2006


The following reply was made to PR ports/97074; it has been noted by GNATS.

From: Matthew Berryman <mattjb at eleceng.adelaide.edu.au>
To: Matthew Berryman <matthew at berrymanconsulting.com>
Cc: bug-followup at FreeBSD.org, Henric Jungheim <henric at comcast.net>,
        Joerg.Pulz at frm2.tum.de,
        "Carlos F. A. Paniago" <carlos.paniago at gmail.com>
Subject: Re: ports/97074: isc-dhcpd 3.0.4 port not working
Date: Tue, 16 May 2006 13:15:08 +0930

 This is one the same bug... the other difference between the two  
 networks I admin (apart from the XP SP2 firewall) is that one has an  
 (Intel) amd64 arch, and it's that site that's having the problem. So  
 the bug is in isc-dchp, and interestingly the changelog says:
 - 64bit pointer sizes are detected properly on FreeBSD now.
 
 but this detection doesn't seem to be working properly.
 
 Cheers,
 Matt
 
 
 
 ----- Begin forwarded message -----
 
 Date: Mon, 8 May 2006 19:07:48 -0700
 From: Henric Jungheim
 To: Joerg.Pulz at frm2.tum.de
 Subject: isc-dhcp3-server port (3.0.4) on amd64
 
 
 I have an amd64 box and I just updated to the latest ISC
 DHCP server port.  Unfortunately, amd64's time_t is 64 bits
 which is causing the server to send an 8-byte option 51
 (lease time).  This option should be 4 bytes and WinXP SP2
 isn't swallowing the 8 byte variant.
 
 Anyway, I think that's whats going on.  I can see the 8 byte
 option 51 with a sniffer, but I haven't looked too closely
 at the code generating that packet.
 
 I reinstalled it after a cvs up with -D "2 weeks ago" on the
 isc-dhcp3-server port and now clients can get leases again.
 
 
 ----- End forwarded message -----
 
 -- 
 henric at comcast.net
 http://home.comcast.net/~henric/
 
 
 On 14/05/2006, at 2:57 PM, Matthew Berryman wrote:
 
 > Tara:matthew matthew$ md5sum dhcp*
 > 1ee830c0cc720e6acd0cb03f00b5d316  dhcpdump_3.0.3_good
 > 260caa79fcca6544262de4c4fd4fa79d  dhcpdump_3.0.4_bad
 >
 > <dhcpdump_3.0.3_good>
 > <dhcpdump_3.0.4_bad>
 



More information about the freebsd-ports-bugs mailing list