All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Emiel Mols <emiel@fulgor-hosting.nl>
Cc: netfilter-devel@lists.netfilter.org
Subject: RE: IPSEC and NAT
Date: Sat, 16 Oct 2004 10:59:34 -0400	[thread overview]
Message-ID: <1097938773.2833.87.camel@localhost> (raw)
In-Reply-To: <200410160653.i9G6rmMc025506@nmibwkms1.nexusmgmt.com>

On Sat, 2004-10-16 at 02:53, Emiel Mols wrote:
<snip>
> Indeed, the problem is that the packets get encrypted before reaching
> POSTROUTING. I've managed the patch you're referring to:
> 
> router linux # cat ../patch-o-matic-ng-20040621/ipsec-01-output-hooks/help
> [NETFILTER+IPSEC 1/4]
> 
> This patch adds new output hooks for IPsec. Packets traverse the hooks like
> this:
> 
> 1. -> (plain) FORWARD   -> POST_ROUTING -> (encrypted) LOCAL_OUT ->
> POST_ROUTING
> 2. -> (plain) LOCAL_OUT -> POST_ROUTING -> (encrypted) LOCAL_OUT ->
> POST_ROUTING
> 
> However, I can't get it patched on 2.6.8.1 (about 5 rejects) and 2.6.7 (1
> reject). This patch is just what I need, but further downgrading isn't an
> option. Has anyone succeeded with this patch in a recent 2.6 kernel?
I'd imagine you have but, just in case, have you applied any dependent
patches? For example, when I first applied the tcp window patch, I had
the same problem until I realized I had to apply all the pending patches
first.
> 
<snip>
-- 
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com

       reply	other threads:[~2004-10-16 14:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200410160653.i9G6rmMc025506@nmibwkms1.nexusmgmt.com>
2004-10-16 14:59 ` John A. Sullivan III [this message]
     [not found] <200410152203.i9FM3kMc029703@nmibwkms1.nexusmgmt.com>
2004-10-16  2:09 ` IPSEC and NAT John A. Sullivan III
2004-10-16  6:53   ` Emiel Mols
     [not found] <200410151800.i9FI09Mc018462@nmibwkms1.nexusmgmt.com>
2004-10-15 22:02 ` John A. Sullivan III
2004-10-15 22:03   ` Emiel Mols
2004-10-16  1:18   ` Alexander Samad
2004-10-15 18:00 Emiel Mols

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=1097938773.2833.87.camel@localhost \
    --to=john.sullivan@nexusmgmt.com \
    --cc=emiel@fulgor-hosting.nl \
    --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.