From owner-freebsd-net Tue Apr 20 10:18: 8 1999 Delivered-To: freebsd-net@freebsd.org Received: from home.ieng.com (home.ieng.com [207.24.215.20]) by hub.freebsd.org (Postfix) with ESMTP id 29CA715774 for ; Tue, 20 Apr 1999 10:18:00 -0700 (PDT) (envelope-from pauls@ieng.com) Received: from localhost (pauls@localhost) by home.ieng.com (8.9.1a/8.9.1) with SMTP id NAA15123 for ; Tue, 20 Apr 1999 13:15:25 -0400 (EDT) Date: Tue, 20 Apr 1999 13:15:25 -0400 (EDT) From: Paul Southworth To: freebsd-net@freebsd.org Subject: Interfaces don't go down when network is physically down 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 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? The reason I ask is that a physically down ethernet network interface does not appear to be visible FreeBSD (or to gated) which means that OSPF really doesn't work properly. For example, two machines, three networks: +------+ +------+ ----net1----| box1 |----net2----| box2 |----net3---- +------+ +------+ If box1 is announcing net1 to box2 via OSPF, and I physically take down the net1 interface on box1, box1's gated never knows it, keeps announcing the route to box2. box2 can still reach the net1 interface on box1, even though net1 should really be unreachable via box1. Any work-around for this? [FYI, this is not really a FreeBSD-specific problem - Linux and Solaris also appear to fail this test.] --Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message