From owner-freebsd-net@FreeBSD.ORG Fri Jan 20 13:34:31 2012 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 77250106564A for ; Fri, 20 Jan 2012 13:34:31 +0000 (UTC) (envelope-from sem@semmy.ru) Received: from sunner.semmy.ru (sunner.semmy.ru [IPv6:2a00:14d0:0:20::3]) by mx1.freebsd.org (Postfix) with ESMTP id BDA108FC1B for ; Fri, 20 Jan 2012 13:34:30 +0000 (UTC) Received: from dhcp170-160-red.yandex.net ([95.108.170.160]) by sunner.semmy.ru with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1RoEbH-000LVQ-5u for freebsd-net@freebsd.org; Fri, 20 Jan 2012 17:33:51 +0400 Message-ID: <4F196D64.6020508@semmy.ru> Date: Fri, 20 Jan 2012 17:34:28 +0400 From: Sergey Matveychuk User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <4F190F3F.7050302@fsn.hu> In-Reply-To: <4F190F3F.7050302@fsn.hu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Adding setfib support to rc.d/routing 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: Fri, 20 Jan 2012 13:34:31 -0000 20.01.2012 10:52, Attila Nagy wrote: > Hi, > > Having multiple routing tables is a very nice and (was a) long awaited > capability in FreeBSD. Having it since years is even more cool, because > we can assume it's stable now. > But not having infrastructure support for it sucks, this makes people > hacking with rc.local or various scripts in various places. > > There is a(t least one) PR about it: conf/145440, which proposes a > standard method for setting up different FIBs in a seems to be logical > way, which is compatible with the current single routing table method of > static_routes. > > Are there any objections about this PR? Is there something we can do to > get it committed? > JFYI conf/132476