From owner-freebsd-net Sat May 9 09:02:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25465 for freebsd-net-outgoing; Sat, 9 May 1998 09:02:34 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25420 for ; Sat, 9 May 1998 09:02:20 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (localhost.softweyr.com [127.0.0.1]) by softweyr.com (8.8.8/8.8.7) with ESMTP id KAA07999; Sat, 9 May 1998 10:02:07 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <35547DFB.950E6F33@softweyr.com> Date: Sat, 09 May 1998 10:02:03 -0600 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: randal@comtest.com CC: freebsd-net@FreeBSD.ORG, Richard Wackerbarth Subject: Re: Have I left something out? References: <199805071926.JAA03049@oldyeller.comtest.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Randal S. Masutani wrote: > Well is supposed to work that way. If you down the interface 10.0.1.6 then by > definition that host is down. Host 10.0.1.1 cannot get to 10.0.1.6 by > any other route, other than by its own interface 10.0.1.1 for network 10.0.1.0. > What you are asking is that Host 10.0.1.1 redirect its interface for net > 10.0.1.0 to route thru 10.0.2.1. This is not possible. Not only is it possible, it's perfectly reasonable. TCP/IP was designed to route around network failures of this sort. It works marvelously on Xylan switches, if you have XOS 3.1.7.G or 3.2.3.>=10. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message