From: Ivan Mitev <imitev@obs.bg>
To: netfilter-devel@lists.netfilter.org
Subject: netfilter/ipsec packet flow
Date: Wed, 14 Apr 2004 20:37:49 +0300 [thread overview]
Message-ID: <20040414173749.GA6170@obs.bg> (raw)
hi
sorry if that sounds like a stupid question; but let's ask, as more people
should be concerned by that when they'll migrate their freeswan/2.4 to 2.6's
ipsec...
1- is this 2.6 ipsec packet flow "freezed" ?
[incoming packet]
|<-----------------.
v |
PREROUTING |
dest!=local? / \ dest==local? |
/ \ |
FORWARD LOCAL_IN |
| | |
| (ipsec?decrypt:nop)|
| | \ / dest!=local ?
| | `------'
v v dest==local ?
(excellent ascii-art stolen from willy tarreau in
http://lists.netfilter.org/pipermail/netfilter-devel/2004-March/014464.html
in a discussion about patrick's new netfilter/ipsec patches)
because for those of us that need to begin to migrate to 2.6 and that have
very complex traffic control done with mangle/fwmark, it's important to know
where ipsec packets will be seen twice (encrypted/de-encrypted). (and where
they won't be seen, eg. encrypted ESP/AH pkts in OUTPUT/filter ?)
2- does the ipsec policy match by patrick McHardy is considered as the
"standard" way of matching de-encrypted packets ? (eg. compared to the earlier
fwmark hack), or are there other ways ?
...or do some netfilter core developers have other design ideas ? (i'm talking
only of the packet flow here; not the internals/implementation)
question for patrick: does the last patch in pom-ng change the design above ?
("The input patch is replaced with a new version which...")
(http://lists.netfilter.org/pipermail/netfilter-devel/2004-April/014977.html)
another thing (sorry for the lengthy post), can someone put patrick's xfig pic
somewhere (or send it to me); i don't manage to "unbase64" it.
(http://lists.netfilter.org/pipermail/netfilter-devel/2004-March/014469.html)
oh, and btw let me know if i can help with testing - i have a full 2.6 network
testbed here ...
thanks !
ivan
next reply other threads:[~2004-04-14 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 17:37 Ivan Mitev [this message]
2004-04-15 3:58 ` netfilter/ipsec packet flow Patrick McHardy
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=20040414173749.GA6170@obs.bg \
--to=imitev@obs.bg \
--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.