From owner-freebsd-net@FreeBSD.ORG Tue Sep 16 00:10:26 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54945106566B; Tue, 16 Sep 2008 00:10:26 +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 38AC18FC21; Tue, 16 Sep 2008 00:10:26 +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 m8G0APa8014989; Mon, 15 Sep 2008 17:10:25 -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: Mon, 15 Sep 2008 17:10:19 -0700 Message-ID: In-Reply-To: <8e10486b0809151302l5a1c9433j5e44b54198409cd8@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ECMP Support Thread-Index: AckXbgWtwhY7QdlUQN6IRzYpoKtPbAAINjpA References: <8e10486b0809140950h6200dfdco5950f59d23718866@mail.gmail.com> <48CD4C11.6020104@FreeBSD.org> <8e10486b0809141053i69f9c4b5raffdad187ecd16eb@mail.gmail.com> <48CD506F.8090401@FreeBSD.org> <8e10486b0809141456t48e799a0tcd74b605f2ad473f@mail.gmail.com> <48CDE229.905@elischer.org> <8e10486b0809151302l5a1c9433j5e44b54198409cd8@mail.gmail.com> From: "Li, Qing" To: "Alexandre Biancalana" Cc: freebsd-net@freebsd.org, Julian Elischer , Qing Li Subject: RE: ECMP Support X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2008 00:10:26 -0000 >=20 > My idea is use ECMP on 7.x branch to balance 100Mbit=20 > Lan-2-Lan links between our enterprise network and IDC network. >=20 I can merge those changes into 7.x. Frankly I have lost track of the release schedule so I do need to talk to the FreeBSD release team to figure out where and when I should integrate the code. >=20 > In this case the route table only change when a link goes=20 > down, so I will remove this from routing table until this=20 > goes up again. This is a problem with current ECMP implementation ? >=20 The route selection uses a hash and because the number of route=20 entries changes when you remove that route from the routing table, and depending on the hash key, you may get a different route=20 entry. In earlier 5.x releases when "inp_route" is present (route is sticky), tcp_output() provides that value and route lookup is bypassed. =09 This is something we are working on for a fix in -current. > > > > The "route" and "netstat" commands work with ECMP.=20 > > There isn't much documentation but I do intend to update the=20 > > manpages soon. > > Please indicate if there is any other command that you need. >=20 > I think this is enough for me. >=20 Okay. -- Qing