From owner-freebsd-net@FreeBSD.ORG Thu Jul 24 18:01:25 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 820ED1065674 for ; Thu, 24 Jul 2008 18:01:25 +0000 (UTC) (envelope-from is@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.freebsd.org (Postfix) with ESMTP id 45F088FC19 for ; Thu, 24 Jul 2008 18:01:25 +0000 (UTC) (envelope-from is@rambler-co.ru) Received: from localhost (is1.park.rambler.ru [81.19.64.121]) by relay0.rambler.ru (Postfix) with ESMTP id DFCB85F04; Thu, 24 Jul 2008 22:01:23 +0400 (MSD) Date: Thu, 24 Jul 2008 21:59:46 +0400 From: Igor Sysoev To: Julian Elischer Message-ID: <20080724175946.GA60773@rambler-co.ru> References: <20080724145610.GA57814@rambler-co.ru> <4888A0B5.4060302@elischer.org> <20080724163128.GE57814@rambler-co.ru> <4888B15F.7060704@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4888B15F.7060704@elischer.org> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-net@freebsd.org Subject: Re: FIB MFC X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2008 18:01:25 -0000 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/