From owner-freebsd-net@FreeBSD.ORG Tue Apr 29 18:19:13 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 E67811065686 for ; Tue, 29 Apr 2008 18:19:13 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outC.internet-mail-service.net (outc.internet-mail-service.net [216.240.47.226]) by mx1.freebsd.org (Postfix) with ESMTP id CC03F8FC2D for ; Tue, 29 Apr 2008 18:19:13 +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; Tue, 29 Apr 2008 16:35:01 -0700 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 3CA812D6011; Tue, 29 Apr 2008 11:19:13 -0700 (PDT) Message-ID: <481766A2.7040809@elischer.org> Date: Tue, 29 Apr 2008 11:19:14 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: Paul References: <48134DDE.9010306@elischer.org> <20080429084032.GW71371@stlux503.dsto.defence.gov.au> <48175793.30606@elischer.org> <48175B91.1010202@gtcomm.net> In-Reply-To: <48175B91.1010202@gtcomm.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Net , "Wilkinson, Alex" Subject: Re: Multiple routing tables in action... 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, 29 Apr 2008 18:19:14 -0000 Paul wrote: > I've been waiting for something like this. Linux has done policy > routing for many many years and is very good at it. I prefer to use > FreeBSD for routing though and this is a feature I have been waiting for :) > Mainly to use with BGP , having multiple BGP routing tables. I would > like it to be similar to Cisco's VRF or Juniper's routing instance, but > maybe that's asking too much. We use it on our hardware routers for > implementations such as having multiple bgp route tables and having > customer bandwidth pricing change based on which routing table their > traffic gets , say.. value customers, premium customers, customers who > want only certain carriers in their bandwidth mix, etc. Would be fun > to have support for FBSD with quagga/openbgpd etc.. and be able to use > dscp for marking or any other policy based rule (source ip for instance). > > Thanks Julian.. This is a step forward in the right direction :) The interaction with routing daemons is something I don't know enough about. I need someone who knows routing daemons to tell how to correctly tweek code that sends routing events. I think it is possible that events from a particular FIB should only be reported to routing sockets that are associated with that FIB. but I'm not sure about this. This would mean running a separate instance of the routing daemon for each FIB (VRF?). Does this sound right to people? > > > Julian Elischer wrote: >> Wilkinson, Alex wrote: >>> 0n Sat, Apr 26, 2008 at 08:44:30AM -0700, Julian Elischer wrote: >>> >A little progress report >>> >From a recently installed (6.3) machine.... (plus patches) >>> >>> Ok, being ignorant to this, possibly a silly question: >>> >>> Why would i want or need multiple routing tables ? >> >> any time you wnat to base a route upon something other than just >> the destination address. It's basically called "Policy based >> routing". >> >> >> Trivial examples: >> You have two ISPs and you want to send all SMTP via one link and >> all other traffic via the other. >> >> You have 3 ISPs and want all traffic from the accounting department >> to go via a particular path (that is encrypted) but regular office >> chatter to go via another. >> >> I have other more complex examples in my work. >> >> I'm sure others have more solid examples as well. >> >> google for policy routing. >> _______________________________________________ >> 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" >>