From owner-freebsd-current@FreeBSD.ORG  Thu Jan 29 23:22:48 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0B62F16A4CF; Thu, 29 Jan 2004 23:22:48 -0800 (PST)
Received: from mail.imp.ch (ns1.imp.ch [157.161.1.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 2502943D39; Thu, 29 Jan 2004 23:22:46 -0800 (PST)
	(envelope-from mb@imp.ch)
Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9])
	by mail.imp.ch (8.12.9p2/8.12.3) with ESMTP id i0U7Mg3b028570;
	Fri, 30 Jan 2004 08:22:43 +0100 (CET)
	(envelope-from Martin.Blapp@imp.ch)
Date: Fri, 30 Jan 2004 08:22:42 +0100 (CET)
From: Martin Blapp <mb@imp.ch>
To: David Syphers <dsyphers@u.washington.edu>
In-Reply-To: <200401291916.22939.dsyphers@u.washington.edu>
Message-ID: <20040130080907.O44162@cvs.imp.ch>
References: <200401291916.22939.dsyphers@u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Fri, 30 Jan 2004 05:30:02 -0800
cc: mbr@freebsd.org
cc: current@freebsd.org
Subject: Re: DHCP problems in -current?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2004 07:22:48 -0000


Hi,

> The problem started exactly when I upgraded from a Dec. 28 -current to a Jan.
> 20 -current (which is one reason I think it's on my end). I noticed that
> src/contrib/isc-dhcp/client/dhclient.c was modified in that time - with a
> commit log that sounds as if it would _solve_ problems like this, rather than
> start them. Right now I'm running -current from Jan 26, with the same
> problem.

Yes I fixed exactly this problem. Instead of a new request, we are
doing now a "renew".

Normally the lease gets renewed after 1/2 of the max lease time. If you get
a new IP all 30 minutes, this means that your ISP has the lease expiry set
to 1 hour.

Can you please use ethereal from the ports collection and record the
corresponding renew actions ?

I'd like that you first record the normal expiry, and then trigger the
it manually (you remove the cable and plug it back).

Martin