Date: Tue, 20 Apr 1999 12:01:59 -0700 From: David Greenman <dg@root.com> To: "Matthew N. Dodd" <winter@jurai.net> Cc: Paul Southworth <pauls@ieng.com>, freebsd-net@FreeBSD.ORG Subject: Re: Interfaces don't go down when network is physically down Message-ID: <199904201901.MAA10789@implode.root.com> In-Reply-To: Your message of "Tue, 20 Apr 1999 14:42:08 EDT." <Pine.BSF.4.02.9904201439170.2158-100000@sasami.jurai.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>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 can't think of any problems off hand. I think you'd want to use if_up() and if_down(), however, since these will do routing socket notifications about the state change, although I don't know if these are safe in all interrupt contexts. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com 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?199904201901.MAA10789>