From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 19:16:14 2004 Return-Path: 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 7304716A4CE; Thu, 29 Jan 2004 19:16:14 -0800 (PST) Received: from yggdrasil.seektruth.org (D-128-208-61-153.dhcp4.washington.edu [128.208.61.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D03E43D2F; Thu, 29 Jan 2004 19:16:13 -0800 (PST) (envelope-from dsyphers@seektruth.org) Received: from yggdrasil.seektruth.org (localhost [127.0.0.1]) i0U3GNlo015873; Thu, 29 Jan 2004 19:16:23 -0800 (PST) (envelope-from dsyphers@seektruth.org) Received: by yggdrasil.seektruth.org (8.12.10/8.12.10/Submit) id i0U3GNg1015872; Thu, 29 Jan 2004 19:16:23 -0800 (PST) (envelope-from dsyphers) From: David Syphers To: current@freebsd.org Date: Thu, 29 Jan 2004 19:16:22 -0800 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401291916.22939.dsyphers@u.washington.edu> cc: mbr@freebsd.org Subject: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2004 03:16:14 -0000 I'm trying to figure out if the problems I'm having with DHCP are on my end (I'm a client) or on the DHCP server's end. Every 15-30 minutes I'm assigned a new IP. When I looked through my logs for four months before the problem started, I noticed I was only assigned a new IP once in all that time before this started. I contacted my ISP, who verified that was an abnormal frequency of IP change, and they did fix something which made my computer stop complaining that someone else was using my IP (that was due to a security issue with another computer). But I'm still getting a new IP every 15 minutes. 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. I don't see a pr on this subject. Is it a known problem, or likely a configuration problem with my ISP? Thanks, -David -- Department of Physics The University of Washington, Seattle