From: Chris Wilson <chris@netservers.co.uk>
To: netfilter-devel@lists.netfilter.org
Cc: netfilter@lists.netfilter.org
Subject: Re: port-based filtering of ESP packets with in-kernel IPsec?
Date: Wed, 30 Jul 2003 11:34:43 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0307301124150.22684-100000@localhost> (raw)
In-Reply-To: <1059540296.16545.305.camel@k7.localnet>
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.
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). Or, maybe it should be decapsulated before routing (and
hence visible unencrypted in FORWARD, INPUT and OUTPUT).
Cheers, Chris.
--
___ __ _
/ __// / ,__(_)_ | Chris Wilson -- UNIX Firewall Lead Developer |
/ (_ / ,\/ _/ /_ \ | NetServers.co.uk http://www.netservers.co.uk |
\ _//_/_/_//_/___/ | 21 Signet Court, Cambridge, UK. 01223 576516 |
next prev parent reply other threads:[~2003-07-30 10:34 UTC|newest]
Thread overview: 10+ 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 [this message]
2003-07-30 15:42 ` Rick Kennell
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
[not found] ` <1059576701.4586.20.camel@simulacron>
2003-07-30 15:16 ` Harald Welte
2003-07-30 20:37 ` Dax Kelson
2003-07-30 22:51 ` Dax Kelson
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=Pine.LNX.4.44.0307301124150.22684-100000@localhost \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox