From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 16 18:00:28 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C3841065670 for ; Wed, 16 Apr 2008 18:00:28 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id E6EEC8FC13 for ; Wed, 16 Apr 2008 18:00:27 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id m3GHchG1023927; Wed, 16 Apr 2008 10:38:43 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 16 Apr 2008 10:38:37 -0700 Message-ID: In-Reply-To: <1dd0a33d0804160337o3090ac08g4a2cbc3be0d58b19@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Multipath routing - failover version Thread-Index: Acifsbqwo5QwhbG3SPqfAyPlWFKhSAANC0Ug References: <1dd0a33d0804160337o3090ac08g4a2cbc3be0d58b19@mail.gmail.com> From: "Li, Qing" To: "M.S. Motanu" , Cc: Subject: RE: Multipath routing - failover version X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Apr 2008 18:00:28 -0000 Hi, I recently incorporated multipath support into -CURRENT, for the upcoming 8.0. This patch originated from the KAME project and builds on the existing routing data structures and infrastructure. As a result I did not have to modify the userland programs, however, I think netstat can use some tweaking in its output.=20 I am in the process of incorporating additional functionalities such as allowing for preference setting, and performing active=20 health-check on the gateways and updating the routes accordingly. >=20 > Switching between different paths is done by the kernel based=20 > on the link state of the interface associated with the=20 > gateway. This way when can achieve a level of redundancy at=20 > the link level (this is not a routing protocol!). >=20 Hmm... in the current code if_unroute() would remove the interface route when the interface is down. -- Qing