Date: Thu, 24 Jul 2008 09:44:15 -0700 From: Julian Elischer <julian@elischer.org> To: Igor Sysoev <is@rambler-co.ru> Cc: freebsd-net@freebsd.org Subject: Re: FIB MFC Message-ID: <4888B15F.7060704@elischer.org> In-Reply-To: <20080724163128.GE57814@rambler-co.ru> References: <20080724145610.GA57814@rambler-co.ru> <4888A0B5.4060302@elischer.org> <20080724163128.GE57814@rambler-co.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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). 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). 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. > >> It is an excellent idea however, and I don't know why I didn't >> do it already.. >> >>> tcp4 0 0 192.168.1.100.80 XXXXXXXXXX SYN_RCVD >>> tcp4 0 0 192.168.1.100.80 XXXXXXXXXX SYN_RCVD >>> tcp4 0 0 192.168.1.100.80 XXXXXXXXXX SYN_RCVD >>> >>> Can TCP connection inherit FIB from first SYN packet or not ? >> no but it is a good idea. > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4888B15F.7060704>