From owner-freebsd-net Tue May 5 13:02:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25518 for freebsd-net-outgoing; Tue, 5 May 1998 13:02:10 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25316 for ; Tue, 5 May 1998 13:01:59 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.7] (user10.dataplex.net [208.2.87.10]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id PAA09176 for ; Tue, 5 May 1998 15:01:25 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 5 May 1998 15:00:21 -0500 To: freebsd-net@FreeBSD.ORG From: Richard Wackerbarth Subject: Have I left something out? Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I set up a test network and it did not behave as I had hoped/expected. I wanted to have redundant connections so that if one goes down, another can be used. Consider the simple case of a loop. For discussion, we will have 6 nets. 10.0.1.0/24, 10.0.2.0/24, ..., 10.0.6.0/24. We will join them with routers 10.0.1.1 == 10.0.2.1 10.0.2.2 == 10.0.3.2 ... 10.0.5.5 == 10.0.6.5 and to close the loop 10.0.6.6 == 10.0.1.6 Now we bring them all up and let them exchange routing info. All is well. A packet from net 1 ==> net 3 goes via net 2. A packet from net 1 ==> net 5 goes via net 6. Now we break the loop by declaring net 6 (or one of the router interfaces thereon) down. The routes reconfigure and the packet to net 5 now takes the longer (but still available) route via nets 2,3,4. However, and this is my problem, if I declared the 10.0.1.6 interface down, I cannot reach the machine. Host 10.0.1.1 INSISTS that the packet go out the net 1 interface and cannot reach 10.0.1.6. It never finds the "backdoor", 10.0.6.6. Any suggestions? Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message