Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 11 May 2008 02:42:12 -0700
From:      Julian Elischer <julian@elischer.org>
To:        Igor Sysoev <is@rambler-co.ru>
Cc:        FreeBSD Net <freebsd-net@freebsd.org>
Subject:   Re: Multiple routing tables in action...
Message-ID:  <4826BF74.3030204@elischer.org>
In-Reply-To: <20080511092046.GC79358@rambler-co.ru>
References:  <48134DDE.9010306@elischer.org>	<20080429084032.GW71371@stlux503.dsto.defence.gov.au>	<48175793.30606@elischer.org> <48175B91.1010202@gtcomm.net>	<481766A2.7040809@elischer.org> <48176C65.4080600@gtcomm.net>	<481772C7.8090300@elischer.org> <20080511092046.GC79358@rambler-co.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
Igor Sysoev wrote:
> On Tue, Apr 29, 2008 at 12:11:03PM -0700, Julian Elischer wrote:
> 
>>> Then you can export RIB entries , say 
>>> you have 5 BGP peers and you want to export 2 or 3 or all of them into 
>>> the 'main' routing instance you can set up a policy to add those learned 
>>> routes into the main instance and v-v.
>>> Linux behaves a little bit differently as you have to make an 'ip rule' 
>>> entry for it but it doesn't use the firewall.
>> for now this code asks you to use a firewall to classify incoming 
>> packets..
>>
>> e.g.
>> 100 setfib 2 ip from any to any in recv em0
> 
> Is is possible to extend ifconfig to classify incoming packets ?
> 
> 

You could assign a default fib for all packets received by an
interface and that is on my list of things to look at doing later.


In the meantime you can use ipfw and pf to assign fibs to incoming 
packets depending on the receive interface.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4826BF74.3030204>