Date: Tue, 20 Apr 1999 15:24:18 -0400 (EDT) From: "Matthew N. Dodd" <winter@jurai.net> To: Peter Wemm <peter@netplex.com.au> 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: <Pine.BSF.4.02.9904201521240.2158-100000@sasami.jurai.net> In-Reply-To: <19990420191825.199141F68@spinner.netplex.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <random routing daemon> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.02.9904201521240.2158-100000>