From owner-freebsd-net Tue Apr 20 11:18:30 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 211EA14E78 for ; Tue, 20 Apr 1999 11:18:19 -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 LAA10552; Tue, 20 Apr 1999 11:14:50 -0700 (PDT) Message-Id: <199904201814.LAA10552@implode.root.com> To: Paul Southworth Cc: 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 13:15:25 EDT." From: David Greenman Reply-To: dg@root.com Date: Tue, 20 Apr 1999 11:14:50 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On FreeBSD 3.0-RELEASE, when you physically break an ethernet (eg, unplug >the cable) the host still thinks the interface is up and can still >ping it. Is there any way to avoid that scenario - ie, when you break >an interface, have it be really broken, down, unpingable? 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. -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