Date: Wed, 21 Apr 1999 03:18:24 +0800 From: Peter Wemm <peter@netplex.com.au> To: "Matthew N. Dodd" <winter@jurai.net> Cc: David Greenman <dg@root.com>, Paul Southworth <pauls@ieng.com>, freebsd-net@FreeBSD.ORG Subject: Re: Interfaces don't go down when network is physically down Message-ID: <19990420191825.199141F68@spinner.netplex.com.au> In-Reply-To: Your message of "Tue, 20 Apr 1999 14:42:08 -0400." <Pine.BSF.4.02.9904201439170.2158-100000@sasami.jurai.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990420191825.199141F68>