From owner-freebsd-ports@FreeBSD.ORG Sat May 13 19:11:13 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A26D16A408 for ; Sat, 13 May 2006 19:11:13 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx1.parodius.com (mx1.parodius.com [64.62.145.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 753E543DA8 for ; Sat, 13 May 2006 19:10:54 +0000 (GMT) (envelope-from jdc@parodius.com) Received: by mx1.parodius.com (Postfix, from userid 500) id 651CB5D4E; Sat, 13 May 2006 12:10:54 -0700 (PDT) Date: Sat, 13 May 2006 12:10:54 -0700 From: Jeremy Chadwick To: freebsd-ports@freebsd.org Message-ID: <20060513191054.GA10409@pentarou.parodius.com> Mail-Followup-To: freebsd-ports@freebsd.org References: <200605131326.38566.jimmyjohnsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200605131326.38566.jimmyjohnsf@yahoo.com> X-PGP-Key: http://jdc.parodius.com/pubkey.asc User-Agent: Mutt/1.5.11 Subject: Re: isc-dhcp3-server-3.0.4 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 May 2006 19:11:13 -0000 On Sat, May 13, 2006 at 01:26:34PM -0500, Jimmy F. Johns wrote: > My Windows clients no longer can get dhcp leases from my FreeBSD box, running > isc-dhcp3-server-3.0.4 -- since the port upgrade May 7. Windows box sends > DHCP DISCOVER, FreeBSD issues DHCP OFFER, then another DISCOVER, another > OFFER, etc. > > Ethereal on the Windows side shows only one issue: the lease-time (Option > 51) "isn't 4 bytes." > > The TEN bytes Ethereal highlights are: > > 33 08 00 00 ea 60 00 00 00 00 > > "ea60" is my 60,000-second default lease time. Some obvious screw-up on my > part? Or would anyone need dmesg, ifconfig, dhcpd.conf, dhcpd.leases, etc., > to tell? You're not the first person to report this. There's been numerous reports of it here on freebsd-ports, and it's always between ISC dhcpd 3.0.4 and Windows machines. This time around, however, I really don't think Windows is to blame (especially since 3.0.3 works). I've yet to see anything about what the actual cause is (is it a FreeBSD port problem, or is it something in ISC's dhcpd which got changed?). I haven't upgraded to 3.0.4 on my LAN, and to be quite honest, I doubt I'm going to until this can be tracked down and solved. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. |