From owner-freebsd-current@FreeBSD.ORG  Thu Mar 25 13:20:57 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 9827316A4CE
	for <current@freebsd.org>; Thu, 25 Mar 2004 13:20:57 -0800 (PST)
Received: from relay.pair.com (relay.pair.com [209.68.1.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id 09E5243D2F
	for <current@freebsd.org>; Thu, 25 Mar 2004 13:20:57 -0800 (PST)
	(envelope-from silby@silby.com)
Received: (qmail 89899 invoked from network); 25 Mar 2004 21:20:55 -0000
Received: from niwun.pair.com (HELO localhost) (209.68.2.70)
  by relay.pair.com with SMTP; 25 Mar 2004 21:20:55 -0000
X-pair-Authenticated: 209.68.2.70
Date: Thu, 25 Mar 2004 15:20:54 -0600 (CST)
From: Mike Silbersack <silby@silby.com>
To: Andrew Gallatin <gallatin@cs.duke.edu>
In-Reply-To: <16482.64965.82974.270044@grasshopper.cs.duke.edu>
Message-ID: <20040325151940.O9792@odysseus.silby.com>
References: <20040324202737.D672@odysseus.silby.com>
 <16482.64965.82974.270044@grasshopper.cs.duke.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Fri, 26 Mar 2004 05:05:54 -0800
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
	<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: Thu, 25 Mar 2004 21:20:57 -0000


On Thu, 25 Mar 2004, Andrew Gallatin wrote:

> 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

I should probably be more specific.  The problem I'm seeing is that the
interface does not get configured whatsoever; no ssid, no IP, no wepkey,
etc.  If I manually run ifconfig <etc>, all is well, so it's just
something in the scripts that is no longer working properly when a pccard
is inserted.

Mike "Silby" Silbersack