From owner-freebsd-net Tue Apr 20 12:27:12 1999 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (Postfix) with ESMTP id 45C9314BCD for ; Tue, 20 Apr 1999 12:27:05 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id PAA01563; Tue, 20 Apr 1999 15:24:18 -0400 (EDT) Date: Tue, 20 Apr 1999 15:24:18 -0400 (EDT) From: "Matthew N. Dodd" To: Peter Wemm Cc: David Greenman , Paul Southworth , freebsd-net@FreeBSD.ORG Subject: Re: Interfaces don't go down when network is physically down In-Reply-To: <19990420191825.199141F68@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 21 Apr 1999, Peter Wemm wrote: > 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. Bill seems to be thinking the same thing. (At least I think he is; he's off on a rant now.) The original poster wanted to know why wasn't able to detect link status events (cable unpluged etc). While OSPF will eventually detect that the link is dead, stuff like RIP may not. If IFF_RUNNING is for the driver to use how can we give routing daemons hints about link status changes? I am under the impression that they are looking for IFF_UP, not IFF_RUNNING. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message