From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Subject: Re: [NF+IPsec 4/6]: Make IPsec input processing symetrical to output Date: Wed, 26 Oct 2005 01:14:31 +0200 Message-ID: <435EBC57.7090000@trash.net> References: <4352EEC8.9000602@trash.net> <20051017.094919.56989341.yoshfuji@linux-ipv6.org> <4352FD49.4090201@trash.net> <20051017014629.GB32661@gondor.apana.org.au> <435EBB18.50701@trash.net> <20051025231049.GA13679@gondor.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, netfilter-devel@lists.netfilter.org Return-path: To: Herbert Xu In-Reply-To: <20051025231049.GA13679@gondor.apana.org.au> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-devel-bounces@lists.netfilter.org Errors-To: netfilter-devel-bounces@lists.netfilter.org List-Id: netdev.vger.kernel.org Herbert Xu wrote: > On Wed, Oct 26, 2005 at 01:09:12AM +0200, Patrick McHardy wrote: > >>>So how about this? We let the SA tell us whether they want to go through >>>netfilter again. So each SA will carry a flag which determines whether >>>packets through it should go through netfilter. >>> >>>This flag would only affect transport mode SAs of course. >> >>That would be one possibility. But I'm not a big fan of per-state flags >>that affect packet flow, so I think I'd prefer to just ignore this >>case. I don't think not handling inner transport mode SAs would be a >>big loss, so how about we just skip inner transport mode SAs completely >>on output and keep the input code as it is? > > > Actually I was thinking of transport mode SAs with no accompanying > tunnel mode SAs. Did you have another way of dealing with them? No. I thought of this as a special case of inner transport mode SAs (without any further SAs) which would be unhandled. I've never used pure transport mode SAs except for testing, and I've never seen any other users of this. Do you think it is important to handle?