From: Andreas Jellinghaus <aj@dungeon.inka.de>
To: netfilter@lists.netfilter.org
Subject: iptables and 2.5.* ipsec
Date: 14 May 2003 11:53:59 +0200 [thread overview]
Message-ID: <1052906039.6883.24.camel@simulacron> (raw)
Hi,
How does 2.5.* ipsec and netfilter interact?
I guess this way, but I'm not sure:
(encrypted) network card -> routing -> INPUT -> decrypt
(decrypted) ipsec -> routing -> INPUT/FORWARD
A normal packet is processed this way:
ipsec -> routing -> INPUT/FORWARD
The first is easy to see: proto 50 or 51 (or udp port 500 for ike).
But how can I see whether an unencrypted packet came in unencrypted
or came in encrypted via ipsec?
with freeswan I could match -i ipsec0, but with kernel 2.5.* there
is no ipsec0 device. What shall I use instead? fwmark?
Thanks for your help.
Regards, Andreas
reply other threads:[~2003-05-14 9:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1052906039.6883.24.camel@simulacron \
--to=aj@dungeon.inka.de \
--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