From owner-freebsd-net Tue Apr 20 12: 6: 2 1999 Delivered-To: freebsd-net@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 829E81583F for ; Tue, 20 Apr 1999 12:06:00 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id MAA10789; Tue, 20 Apr 1999 12:01:59 -0700 (PDT) Message-Id: <199904201901.MAA10789@implode.root.com> To: "Matthew N. Dodd" Cc: 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 EDT." From: David Greenman Reply-To: dg@root.com Date: Tue, 20 Apr 1999 12:01:59 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >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