From: Rick Kennell <kennell@ecn.purdue.edu>
To: Chris Wilson <chris@netservers.co.uk>
Cc: netfilter-devel@lists.netfilter.org, netfilter@lists.netfilter.org
Subject: Re: port-based filtering of ESP packets with in-kernel IPsec?
Date: 30 Jul 2003 10:42:36 -0500 [thread overview]
Message-ID: <1059579755.22690.6.camel@k7.localnet> (raw)
In-Reply-To: <Pine.LNX.4.44.0307301124150.22684-100000@localhost>
On Wed, 2003-07-30 at 05:34, Chris Wilson wrote:
> Hi Rick,
>
> > Since ESP packets that reach the mangle INPUT chain are destined for a
> > local process, why not unencapsulate them just before that point? It
> > might still be nice to have an indication that this was once an ESP
> > packet for filtering, but that could be done by setting a mark in the
> > mangle PREROUTING chain.
>
> The ESP itself will presumably be for a security association (SA) which
> terminates on the machine, but it could easily be for some tunnel, in
> which case the unencrypted packet should be sent through FORWARD instead
> of INPUT.
Mmm, sure. But if it is directed to INPUT, it should still be
decapsulated.
> Logically, it makes sense to me that the packet should pass through the
> whole of Netfilter _again_ after it's been decapsulated, similarly to what
> now happens with FreeS/WAN (but presumably without an ipsec0 interface
> being involved).
I thought about this for a while trying to figure out how to do so
without an extra interface. Maybe a netfilter rule to decapsulate and
requeue to PREROUTING?
> Or, maybe it should be decapsulated before routing (and
> hence visible unencrypted in FORWARD, INPUT and OUTPUT).
If the packet were being routed by the local host (i.e. from one subnet
to another) we'd want to preserve the encapsulation. Actually, we
probably wouldn't be able to decapsulate it.
--
Rick Kennell <kennell@ecn.purdue.edu>
Purdue University School of Electrical and Computer Engineering
next prev parent reply other threads:[~2003-07-30 15:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 4:44 port-based filtering of ESP packets with in-kernel IPsec? Rick Kennell
2003-07-30 10:34 ` Chris Wilson
2003-07-30 15:42 ` Rick Kennell
2003-07-30 15:42 ` Rick Kennell [this message]
2003-07-30 19:10 ` Henrik Nordstrom
2003-07-30 19:10 ` Henrik Nordstrom
2003-07-30 14:24 ` Harald Welte
2003-07-30 14:51 ` Andreas Jellinghaus
2003-07-30 14:51 ` Andreas Jellinghaus
2003-07-30 15:16 ` Harald Welte
2003-07-30 15:16 ` Harald Welte
2003-07-30 15:16 ` Harald Welte
2003-07-30 20:37 ` Dax Kelson
2003-07-30 22:51 ` Dax Kelson
2003-07-30 14:51 ` Andreas Jellinghaus
2003-07-30 15:45 ` Jeremy Davis
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=1059579755.22690.6.camel@k7.localnet \
--to=kennell@ecn.purdue.edu \
--cc=chris@netservers.co.uk \
--cc=netfilter-devel@lists.netfilter.org \
--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.