From owner-freebsd-bugs  Wed Aug  2 12: 0: 7 2000
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id D64A637BDF2
	for <freebsd-bugs@FreeBSD.org>; Wed,  2 Aug 2000 12:00:01 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id MAA23640;
	Wed, 2 Aug 2000 12:00:01 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by hub.freebsd.org (Postfix) with ESMTP id 4FAD937BF25
	for <FreeBSD-gnats-submit@freebsd.org>; Wed,  2 Aug 2000 11:57:46 -0700 (PDT)
	(envelope-from robert@fledge.watson.org)
Received: (from robert@localhost)
	by fledge.watson.org (8.9.3/8.9.3) id OAA94888;
	Wed, 2 Aug 2000 14:57:41 -0400 (EDT)
	(envelope-from robert)
Message-Id: <200008021857.OAA94888@fledge.watson.org>
Date: Wed, 2 Aug 2000 14:57:41 -0400 (EDT)
From: rwatson@freebsd.org
Reply-To: rwatson@freebsd.org
To: FreeBSD-gnats-submit@freebsd.org
X-Send-Pr-Version: 3.2
Subject: bin/20363: dhclient doesn't know what to do when an interface disappears
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         20363
>Category:       bin
>Synopsis:       dhclient doesn't know what to do when an interface disappears
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Aug 02 12:00:01 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     Robert Watson
>Release:        FreeBSD 4.1-STABLE i386
>Organization:
>Environment:

pccard environment, DHCP in use to configure IP on card

>Description:

Leaving the ethernet card in the slot, suspend, then wake up the notebook.
if_detach() will free th struct ifnet, and BPF will return an appropriate
error to dhclient (I believe, haven't tracked it down quite), but dhclient
apparently doesn't know how to deal with that.

Aug  1 12:53:35 numocking dhclient: receive_packet failed on wi0: Device not con
figured
Aug  1 12:53:58 numocking last message repeated 167598 times

>How-To-Repeat:

suspend notebook, wake it up, watch syslog

>Fix:

errno checking in the receive packet event loop probably needs to check
for ENXIO, which indicates that the device is no longer valid.  Not
sure what it should do next -- probably exit.


>Release-Note:
>Audit-Trail:
>Unformatted:
 >


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message