From owner-freebsd-net Tue Apr 20 13:23:58 1999 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id D712B15818 for ; Tue, 20 Apr 1999 13:23:23 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id QAA29630; Tue, 20 Apr 1999 16:20:49 -0400 (EDT) (envelope-from wollman) Date: Tue, 20 Apr 1999 16:20:49 -0400 (EDT) From: Garrett Wollman Message-Id: <199904202020.QAA29630@khavrinen.lcs.mit.edu> To: "Matthew N. Dodd" Cc: David Greenman , Paul Southworth , freebsd-net@FreeBSD.ORG Subject: Re: Interfaces don't go down when network is physically down In-Reply-To: References: <199904201814.LAA10552@implode.root.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > 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? The trouble is that, once an interface goes down, there might not be any traffic traversing it which will cause it to come back up again. (Some NICs don't notice the state of the wire unless they are transmitting.) That's why Cisco implemented `keepalive'. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message