From owner-freebsd-net@FreeBSD.ORG Wed Dec 12 22:34:39 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 CF31416A46B for ; Wed, 12 Dec 2007 22:34:39 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outS.internet-mail-service.net (outS.internet-mail-service.net [216.240.47.242]) by mx1.freebsd.org (Postfix) with ESMTP id C78EF13C4EE for ; Wed, 12 Dec 2007 22:34:39 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Wed, 12 Dec 2007 14:34:39 -0800 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id B46ED126CA1 for ; Wed, 12 Dec 2007 14:34:38 -0800 (PST) Message-ID: <476061FD.8050500@elischer.org> Date: Wed, 12 Dec 2007 14:34:37 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: FreeBSD Net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: 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 22:34:39 -0000 So, I'm playing with some multiple routing table support.. the first version is a minimal impact version with very limited functionality. It's done that way so I can put it in RELENG_6/7 without breaking ABIs (I hope). Later there will be a more flexible version for-current. Here's the question.. I need a word to use to describe the network view one is currently on.. e.g. if you are usinghe second routing table, you could say I've set xxx to 1 (0 based).. current;y in my code I'm using 'universe' but I don't like that.. one could think of it as a routing plane.. each routing plane has he same interfaces on it but they are logically treated differently becasue each plane has a different routing table. so here's an axample of it in use now... the names should change... 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. also the syscall is setuniverse() so, you see I really need a better name.... setrtab? rtab? rtbl? and the command should be called "????"