Date: Thu, 24 Jul 2008 21:59:46 +0400 From: Igor Sysoev <is@rambler-co.ru> To: Julian Elischer <julian@elischer.org> Cc: freebsd-net@freebsd.org Subject: Re: FIB MFC Message-ID: <20080724175946.GA60773@rambler-co.ru> In-Reply-To: <4888B15F.7060704@elischer.org> References: <20080724145610.GA57814@rambler-co.ru> <4888A0B5.4060302@elischer.org> <20080724163128.GE57814@rambler-co.ru> <4888B15F.7060704@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 24, 2008 at 09:44:15AM -0700, Julian Elischer wrote: > Igor Sysoev wrote: > >On Thu, Jul 24, 2008 at 08:33:09AM -0700, Julian Elischer wrote: > > > > > >>I was thinking that it might be possible to tag a socket to accept the > >>fib of the packet coming in, but if we do this, we should decide > >>API to label a socket in this way.. > > > >I think it should be sysctl to globaly enable TCP FIB inheritance. > >API is already exists: sockopt(SO_SETFIB) for listening socket. > > But a socket ALWAYS has a fib, even if you do nothing > because every process has a fib (usually 0) > so you need a new bit of state somewhere that means "inherit". > (I guess in the socket flags). I see. > Possibly the FIB value of -1 when applied on a socket option might > signify that behaviour. (thus save us a new sockopt). > But such a value would revert to that of the process if the socket was > not used as a listen socket. (or clear itself). -1 is good variant. > I have some MRT unhansements in hte pipeline and will include this if > I can. > > BTW could you send me the diff for ipfw(8)? > I'll compare it with the one I'm about to commit. This is exactly your already commited 1.108.2.9 -- Igor Sysoev http://sysoev.ru/en/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080724175946.GA60773>