From owner-freebsd-current@FreeBSD.ORG Sat May 10 04:23:56 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A00BE106564A for ; Sat, 10 May 2008 04:23:56 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by mx1.freebsd.org (Postfix) with ESMTP id 56E2F8FC18 for ; Sat, 10 May 2008 04:23:55 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so899157ywe.13 for ; Fri, 09 May 2008 21:23:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=/bjgatrZl90p9HnsMmV58KLN4joGgx/z2KOwouckmnU=; b=Nks34Mmv8AGn0VzWpf/0rAA6U01x+Q14uP64xI8ZiJm/vu7YJCSU5aKq1QHL1vc8VnwjHPimyyVPeezq0Pswpmi0tk1Y6wVp9w6nwjzxBGs2XMBdvneqDQsX/9FAbA2Slus5Cw9putLj560ANHRpDAkhPRVt9VOB8tIB+5z02Yo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Fx194d4EUTowiTDs8E0c+8vlGxbpRsyb6v9DqxGvRsR3N+R16JsZvtQXCSGcKdEJqnLKMhcycbRx14d5kra37XrrqpIvqMG+YI09XcF2unp7XcRgKj3MHDKRK0vl4b6lPxEh+WVVH4qhxEEz6KJ9t5eaGq+Ubv5hOH/WU5eTSzw= Received: by 10.150.82.41 with SMTP id f41mr5668477ybb.171.1210391839139; Fri, 09 May 2008 20:57:19 -0700 (PDT) Received: by 10.150.53.13 with HTTP; Fri, 9 May 2008 20:57:19 -0700 (PDT) Message-ID: <5f67a8c40805092057y166d549x2dc2fe397f016c79@mail.gmail.com> Date: Fri, 9 May 2008 23:57:19 -0400 From: "Zaphod Beeblebrox" To: "Julian Elischer" In-Reply-To: <4824F1B4.6010302@elischer.org> MIME-Version: 1.0 References: <4824F1B4.6010302@elischer.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Current Subject: Re: Multiple routing table support commited X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 May 2008 04:23:56 -0000 On Fri, May 9, 2008 at 8:52 PM, Julian Elischer wrote: > I have committed the base of teh Multi-routing-table support. > I am current;y waiting for it to loop back to me before a final > make universe test, but I think it should be ok. > if you do nothing you should not see any difference. > > for a description of what and how, look at: > > > http://perforce.freebsd.org/fileViewer.cgi?FSPC=//depot/user/julian/routing/plan.txt >From my read of your file, this doesn't address FreeBSD's utter lack of what they often call an RIB --- where routes are chosen to be put into the FIB. Zebra does this to some extent, but there is one glaring case where zebra cannot fix the problem and FreeBSD's actions need be improved. Consider a colocation facility where customer equipment is on a vlan and every one of these vlan's has two routers (each advertising RIP default routes to the customer equipment). All of these routers synchronize with OSPF. Now ... if vlan 10 on router-a and router-b both service a particular customer, you would (on router-a) ifconfig vlan10 192.168.10.1/24 ... and on router-b ifconfig vlan10 192.168.10.2/24 ... and then the customer would take the other addresses on that network and listen to RIP for his default route. But there's a problem. When you type this command on router-a, it will dutifully advertise 192.168.10.0/24 to OSPF ... including to router-b... at which point the ifconfig command on router-b will fail unless you offline OSPF on router-b (which is an unattractive solution). Now... some would argue that for all other uses of multiple routes, zebra forms an adequate solution. However, it does not address this particular problem and there are far more uses of multiple identical routes (including multipath, etc) s.t. FreeBSD really does need a multiple route plan.