All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@lists.netfilter.org>
Subject: Re: SNAT before IPSec
Date: Tue, 05 Jun 2007 09:36:59 -0500	[thread overview]
Message-ID: <4665750B.9020805@riverviewtech.net> (raw)
In-Reply-To: <8bd3dfad0706050529s484d42b6t9ef4ae0fd1730367@mail.gmail.com>

On 06/05/07 07:29, noa levy wrote:
> SNAT takes place in POST_ROUTING. Can IPSec be applied after that? I
> have read that after IPSec the packet gets injected to LOCAL_OUT
> again, but when does the actual IPSec policy decision take place?
> Won't it happen *before* SNAT? Can I control it?

Last I looked (it's been a while) the basic methodology at the time was 
that (unencrypted) traffic would pass through the kernel like regular 
traffic.  Then after everything else was done it would be encrypted and 
looped back through the system in its encrypted form.  So what you would 
do is selectively do what ever you wanted to do to the traffic before it 
was encrypted by matching that traffic with filters.  In short, do what 
ever you want to with the clear text traffic, then do what ever you want 
with cypher text traffic.

There use to be a series of patches that needed to be applied to the 
kernel to make this packet flow possible.  I do not know if these 
patches are still required or not, though I would expect it to be main 
line by now.

Can / will any one confirm / refute this please?



Grant. . . .


  parent reply	other threads:[~2007-06-05 14:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 12:29 SNAT before IPSec noa levy
2007-06-05 12:56 ` Yasuyuki KOZAKAI
2007-06-05 14:36 ` Grant Taylor [this message]
2007-06-05 20:15 ` Jorge Davila
2007-06-05 20:28   ` Grant Taylor
2007-06-05 20:45     ` Jorge Davila
2007-06-05 23:53       ` Grant Taylor
2007-06-06 15:39         ` Jorge Davila
2007-06-06 18:48           ` Grant Taylor
2007-06-05 21:29   ` noa levy
2007-06-05 22:40     ` Jorge Davila
2007-06-05 22:40       ` noa levy
2007-06-05 22:59         ` Jorge Davila
2007-06-05 23:05           ` noa levy
2007-06-06 15:47             ` Jorge Davila
2007-06-07 15:40               ` noa levy
2007-06-07 16:36                 ` Jorge Davila
2007-06-07 17:07                 ` Grant Taylor
2007-06-07 18:03                   ` Grant Taylor
2007-06-07 20:57                     ` Jorge Davila
2007-06-08 17:57                       ` Grant Taylor
2007-06-05 22:43     ` Jorge Davila
  -- strict thread matches above, loose matches on Subject: below --
2007-06-04 22:43 noa levy

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=4665750B.9020805@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --cc=gtaylor+reply@riverviewtech.net \
    --cc=netfilter@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.