All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@vger.kernel.org, netfilter-devel@lists.netfilter.org
Subject: Re: [NF+IPsec 4/6]: Make IPsec input processing symetrical to output
Date: Sat, 05 Nov 2005 10:19:51 +0100	[thread overview]
Message-ID: <436C7937.9070901@trash.net> (raw)
In-Reply-To: <20051105090904.GA30733@gondor.apana.org.au>

Herbert Xu wrote:
> On Sat, Nov 05, 2005 at 09:58:24AM +0100, Patrick McHardy wrote:
> 
>>IMO the view for netfilter should be as if we called netif_rx,
>>so on the input path decapsulated packets from the innermost
>>transport mode SA should go through PRE_ROUTING->LOCAL_IN
>>or possibly FORWARD in case of NAT.
> 
> You mean we simply skip the pre-decapsulation LOCAL_IN step
> and the post-encapsulation LOCAL_OUT step? That sounds great
> to me.

No, that won't be possible if we have more than one SA and
would also make DNAT in LOCAL_OUT on the encapsulated packet
impossible.

What I propose is to keep tunnel mode handling as it is, so
for each tunnel mode SA we hit PRE_ROUTING and LOCAL_IN in
the normal packet path. If the final SA is a transport mode
SA, we don't call netif_rx as in my first patchset, but pass
the packet through a new PRE_ROUTING hook in xfrm{4,6}_input
and LOCAL_IN afterwards. The packet won't be processed a second
time by the stack, just the netfilter hooks will be called.
NAT be will be handled manually for IPv4 by doing a new route
lookup and calling dst_input if NAT took place.

  reply	other threads:[~2005-11-05  9:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-17  0:22 [NF+IPsec 4/6]: Make IPsec input processing symetrical to output Patrick McHardy
2005-10-17  0:49 ` YOSHIFUJI Hideaki / 吉藤英明
2005-10-17  1:24   ` Patrick McHardy
2005-10-17  1:46     ` Herbert Xu
2005-10-25 23:09       ` Patrick McHardy
2005-10-25 23:10         ` Herbert Xu
2005-10-25 23:14           ` Patrick McHardy
2005-10-26  0:39             ` Herbert Xu
2005-10-27 14:42               ` Patrick McHardy
2005-10-30 23:15                 ` Patrick McHardy
2005-10-31  3:19                   ` Yasuyuki KOZAKAI
2005-11-01 18:39                     ` Stephen Frost
     [not found]                   ` <200510310319.j9V3JHNl019752@toshiba.co.jp>
2005-11-01 18:23                     ` Patrick McHardy
2005-10-26  4:39             ` James Morris
2005-10-26  7:37             ` Ingo Oeser
2005-10-26 13:37             ` Stephen Frost
2005-10-27 12:15   ` Herbert Xu
2005-10-27 14:57     ` YOSHIFUJI Hideaki / 吉藤英明
2005-10-27 16:58       ` Patrick McHardy
2005-11-05  6:30       ` Herbert Xu
2005-11-05  7:55         ` Patrick McHardy
2005-11-05  8:39           ` Herbert Xu
2005-11-05  8:58             ` Patrick McHardy
2005-11-05  9:09               ` Herbert Xu
2005-11-05  9:19                 ` Patrick McHardy [this message]
2005-11-05  9:38                   ` Herbert Xu
2005-11-05  9:55                     ` Patrick McHardy
2005-11-05 10:01                       ` Herbert Xu
2005-11-05 10:05                         ` Patrick McHardy
2005-11-05 10:32                       ` Yasuyuki KOZAKAI
     [not found]                       ` <200511051032.jA5AWl2l000619@toshiba.co.jp>
2005-11-08 14:01                         ` Patrick McHardy
2005-11-05  8:23         ` YOSHIFUJI Hideaki / 吉藤英明

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=436C7937.9070901@trash.net \
    --to=kaber@trash.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.