From owner-freebsd-current@FreeBSD.ORG Thu Mar 25 07:42:03 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 36B0716A4CE for ; Thu, 25 Mar 2004 07:42:03 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3F7E43D31 for ; Thu, 25 Mar 2004 07:42:02 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i2PFg2vK028797 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Mar 2004 10:42:02 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i2PFfvxa022747; Thu, 25 Mar 2004 10:41:57 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16482.64965.82974.270044@grasshopper.cs.duke.edu> Date: Thu, 25 Mar 2004 10:41:57 -0500 (EST) To: Mike Silbersack In-Reply-To: <20040324202737.D672@odysseus.silby.com> References: <20040324202737.D672@odysseus.silby.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: current@freebsd.org Subject: Re: Ok, who broke interface autoconfiguration? 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: Thu, 25 Mar 2004 15:42:03 -0000 Mike Silbersack writes: > > For the last week or two (perhaps longer, I didn't cvsup for a while), > I haven't been able to autoconfigure wi0 when it's inserted. I haven't I've also noticed problems getting a dhcp address from dhclient over fxp (x86) and sk (amd64). On the amd64, I'm certain that the problem happened sometime between 5.2.1 and last week's -current. My current workaround is to manually edit the lease file and extend it so that it falls back to using the lease when the dhcp server does not answer. My dhcp server is an embedded linux Snapgear box. So debugging from that side is pretty hard. I've done almost nothing to debug this, but its nice to hear I'm not alone. Drew