From owner-freebsd-net Tue Apr 20 12:20:55 1999 Delivered-To: freebsd-net@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id C5CFE153CA for ; Tue, 20 Apr 1999 12:20:52 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 199141F68; Wed, 21 Apr 1999 03:18:25 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: "Matthew N. Dodd" Cc: David Greenman , Paul Southworth , freebsd-net@FreeBSD.ORG Subject: Re: Interfaces don't go down when network is physically down In-reply-to: Your message of "Tue, 20 Apr 1999 14:42:08 -0400." Date: Wed, 21 Apr 1999 03:18:24 +0800 From: Peter Wemm Message-Id: <19990420191825.199141F68@spinner.netplex.com.au> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Matthew N. Dodd" wrote: > On Tue, 20 Apr 1999, David Greenman wrote: > > For many of the ethernet interfaces, there isn't any indication that the > > link is down. On the other hand, for the 100Mbps interfaces, it is possible > > in some cases to get an interrupt from the PHY of the link status change. > > We don't currently do anything with that, however. > > Should we? > > Is it acceptable for the driver to frob the IFF_UP flag when it gets an > event that should be reflected by a state change of IFF_UP? I've always thought IFF_RUNNING was for this... IFF_UP was meant to be reserved for the administrator, while IFF_RUNNING indicates the driver and hardware state. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message