From owner-freebsd-questions@FreeBSD.ORG Thu Jul 16 17:23:26 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 410621065676 for ; Thu, 16 Jul 2009 17:23:26 +0000 (UTC) (envelope-from nvass9573@gmx.com) Received: from mail.gmx.com (unknown [213.165.64.42]) by mx1.freebsd.org (Postfix) with SMTP id 8A3C28FC21 for ; Thu, 16 Jul 2009 17:23:25 +0000 (UTC) (envelope-from nvass9573@gmx.com) Received: (qmail invoked by alias); 16 Jul 2009 17:23:24 -0000 Received: from ipa160.22.107.79.tellas.gr (EHLO [169.254.0.10]) [79.107.22.160] by mail.gmx.com (mp-eu004) with SMTP; 16 Jul 2009 19:23:24 +0200 X-Authenticated: #46156728 X-Provags-ID: V01U2FsdGVkX19ROEY8W0pRKOjbbGFqCW8zKB4G7H9WvQtaCbTUjO nZmBQNAE/hRbI3 Message-ID: <4A5F61F6.8040906@gmx.com> Date: Thu, 16 Jul 2009 20:23:02 +0300 From: Nikos Vassiliadis User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: Brent Bloxam References: <4A5F3D48.608@beanfield.com> In-Reply-To: <4A5F3D48.608@beanfield.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.71 Cc: "freebsd-questions@freebsd.org" Subject: Re: FreeBSD & FIBs (setfib) - How to modify? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jul 2009 17:23:26 -0000 Brent Bloxam wrote: > The documentation on FIBs is pretty slim unless I've been looking in the > wrong places, all I've seen are a few mentions in errata and release > notes. setfib(1) doesn't offer much in the way of associated commands, > and definitely doesn't explain how to actually work with a FIB. I'm > curious if there's a command to specifically modify a FIB beyond 0, > besides something like > > setfib 1 route add ... setfib selects the routing table for locally originated outgoing packets. Besides locally originated packets, there are packets arriving from the network and need to be forwarded. These packets can be classified in a specific routing table with the aid of ipfw. That's all there is. I can't think of something else that needs to be thought with regard to multiple routing tables. HTH, Nikos