All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Clark <sclark46@earthlink.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: SNAT before IPSEC - why?
Date: Sat, 08 Oct 2011 21:01:30 -0400	[thread overview]
Message-ID: <4E90F26A.3030800@earthlink.net> (raw)
In-Reply-To: <alpine.LNX.2.01.1110090025040.3981@frira.zrqbmnf.qr>

On 10/08/2011 06:27 PM, Jan Engelhardt wrote:
> On Saturday 2011-10-08 23:09, Stephen Clark wrote:
>
>    
>> On 10/08/2011 05:26 AM, Jan Engelhardt wrote:
>>      
>>> On Saturday 2011-10-08 04:08, Stephen Clark wrote:
>>>
>>>
>>>        
>>>> Hi,
>>>>
>>>> What is the reasoning for having SNAT happen before ipsec encryption?
>>>>
>>>>          
>>> It can happen before and/or after - see the nf flow graph.
>>>
>>>        
>> Do you have a link to the graph?
>>      
> http://jengelh.medozas.de/images/nf-packet-flow.png or .svg
>    
Beautiful! Thanks,

-- 

"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety."  (Ben Franklin)

"The course of history shows that as a government grows, liberty
decreases."  (Thomas Jefferson)




  reply	other threads:[~2011-10-09  1:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-08  2:08 SNAT before IPSEC - why? Stephen Clark
2011-10-08  8:06 ` Chris Wilson
2011-10-08 21:15   ` Stephen Clark
2011-10-08  9:13 ` Michal Kubecek
2011-10-08  9:26 ` Jan Engelhardt
2011-10-08 21:09   ` Stephen Clark
2011-10-08 22:27     ` Jan Engelhardt
2011-10-09  1:01       ` Stephen Clark [this message]
2011-10-09  1:12         ` Stephen Clark
2011-10-09  1:35           ` Jan Engelhardt

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=4E90F26A.3030800@earthlink.net \
    --to=sclark46@earthlink.net \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@vger.kernel.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.