interface FIB
Igor Sysoev
is at rambler-co.ru
Sat Nov 28 08:03:55 UTC 2009
On Fri, Nov 27, 2009 at 09:12:37PM -0800, Julian Elischer wrote:
> Igor Sysoev wrote:
> > Currently only packets generated during encapsulation can use
> > interface's FIB stored during interface creation:
> >
> > setfib 1 ifconfig gif0 ...
> > setfib 1 ifconfig tun0 ...
>
> not sure if tun actually does this (in fac tit shouldn't)
>
> but for gre and gif (and stf) these are tunnelling other things into
> IP and thus it makes sense to be able to connect a routing table with
> the generated envelopes.
I've got this from 8.0 release notes:
A packet generated on tunnel interfaces such as gif(4) and tun(4) will
be encapsulated using the FIB of the process which set up the tunnel.
However, sys/net/if_tun.c is really has no FIB related changes.
> > is it possible to implement this feature for any interface:
> >
> > setfib 1 ifconfig vlan0 ...
> >
> > or
> >
> > ifconfig vlan0 setfib 1 ...
>
> these two things would mean differnt things.
> and one of them wouldn't mean anything.
>
> setfig 1 ifconfig vlan0 woudl mean "what" exactly?
> VLAN tagging is an L2/L1 operation and FIBS have no effect on this.
>
> as for ifconfig vlan0 setfib 1, or ifconfig em0 setfib 1
>
> this will (shortly) mean that incoming packets through this interface
> will be default be connected with fib 1 so the any return packets
> (resets, icmp etc.) will use FIB1 to go back to the sender.
This is exactly what I meant.
> That patch is in the works.
I'm ready to test the patch in production on 7/8-STABLE if the patch
can be applied to it.
--
Igor Sysoev
http://sysoev.ru/en/
More information about the freebsd-net
mailing list