netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Harald Welte <laforge@netfilter.org>
Cc: aj@dungeon.inka.de, netfilter-devel@lists.netfilter.org,
	netdev@oss.sgi.com
Subject: Re: NAT before IPsec with 2.6
Date: Wed, 28 Jan 2004 11:38:25 -0800	[thread overview]
Message-ID: <20040128113825.769fd89c.davem@redhat.com> (raw)
In-Reply-To: <20040128085831.GM11761@sunbeam.de.gnumonks.org>

On Wed, 28 Jan 2004 09:58:31 +0100
Harald Welte <laforge@netfilter.org> wrote:

> No, we don't achieve this by manipulating the routing code, but by
> placing the respective hooks in ah{4,6}.c and esp{4,6}.c
> {ah,esp}_output() function respectively. We also need to (again) reset
> the skb->nfct and drop the conntrack reference again.

Why not just do this right when we pop into the dst_output() call
in ip_output.c  This way we don't have to add all of this stuff
for every new encapsulator we ever implement.

Maybe not like this precisely, but something like it.

      parent reply	other threads:[~2004-01-28 19:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040124082252.GA19035@alpha.home.local>
     [not found] ` <Pine.LNX.4.44.0401241015470.32723-100000@filer.marasystems.com>
     [not found]   ` <20040124092721.GA19140@alpha.home.local>
     [not found]     ` <20040127103917.GC11761@sunbeam.de.gnumonks.org>
     [not found]       ` <20040127132725.GA14685@openoffice.nl>
     [not found]         ` <pan.2004.01.27.21.13.32.754125@dungeon.inka.de>
2004-01-28  8:58           ` NAT before IPsec with 2.6 Harald Welte
2004-01-28 10:21             ` Andreas Jellinghaus
2004-01-28 13:00               ` Harald Welte
2004-01-28 13:43                 ` Andreas Jellinghaus
2004-01-28 19:38             ` David S. Miller [this message]

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=20040128113825.769fd89c.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=aj@dungeon.inka.de \
    --cc=laforge@netfilter.org \
    --cc=netdev@oss.sgi.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).