From owner-freebsd-net@FreeBSD.ORG Wed Dec 12 23:21:09 2007 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 9C7E116A421 for ; Wed, 12 Dec 2007 23:21:09 +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 5FD8D13C45A for ; Wed, 12 Dec 2007 23:21:09 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from bcs-mail2.internal.cacheflow.com (bcs-mail2.internal.cacheflow.com [10.2.2.59]) by whisker.bluecoat.com (8.13.8/8.13.8) with ESMTP id lBCNL7jg016959; Wed, 12 Dec 2007 15:21:07 -0800 (PST) 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, 12 Dec 2007 15:21:00 -0800 Message-ID: <305C539CA2F86249BF51CDCE8996AFF409091A7F@bcs-mail2.internal.cacheflow.com> In-Reply-To: <476061FD.8050500@elischer.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: bikeshed for all! Thread-Index: Acg9D0By7FMr+felSyedi/6tThNMCwABgS3g References: <476061FD.8050500@elischer.org> From: "Li, Qing" To: "Julian Elischer" , "FreeBSD Net" Cc: Subject: RE: bikeshed for all! 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: Wed, 12 Dec 2007 23:21:09 -0000 =20 > -----Original Message----- > From: owner-freebsd-net@freebsd.org=20 > [mailto:owner-freebsd-net@freebsd.org] On Behalf Of Julian Elischer > Sent: Wednesday, December 12, 2007 2:35 PM > To: FreeBSD Net > Subject: bikeshed for all! >=20 > So, I'm playing with some multiple routing table support.. > the first version is a minimal impact version with very=20 > limited functionality. > It's done that way so I can put it in RELENG_6/7 without=20 > breaking ABIs (I hope). > Later there will be a more flexible version for-current. >=20 > Here's the question.. >=20 > I need a word to use to describe the network view one is=20 > currently on.. > e.g. if you are usinghe second routing table, you could say=20 > I've set xxx to 1 (0 based).. >=20 >=20 > current;y in my code I'm using 'universe' but I don't like that.. >=20 > one could think of it as a routing plane.. > each routing plane has he same interfaces on it but they are=20 > logically treated differently becasue each plane has a=20 > different routing table. >=20 Are you saying an interface can belong to multiple routing domains ? So how is that going to work with overlapping prefixes, which routing domain does the interface feed the packets to ? >=20 > so here's an axample of it in use now... > the names should change... >=20 > setuniverse 1 netstat -rn > [shows table 1] > setuniverse 2 route add 10.0.0.0/24 192.168.2.1 > setuinverse 1 route add 10.0.0.0/24 192.168.3.1 > setuniverse 2 route -n get 10.0.0.3 > [shows 192.168.2.1] > setuniverse 1 route -n get 10.0.0.3 > [shows 192.168.3.1] > setuniverse 2 start_apache > [appache starts, always using 192.168.2.1 to reach the 10.0.0 net. >=20 >=20 > also the syscall is setuniverse() >=20 > so, you see I really need a better name.... > setrtab? >=20 > rtab? rtbl? >=20 > and the command should be called "????" >=20 >=20 > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >=20