From: Grant Taylor <gtaylor@riverviewtech.net>
To: Aaron Smith <aaron@pandora-net.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Filtering Transport Mode IPSec
Date: Mon, 03 Oct 2005 20:29:11 -0500 [thread overview]
Message-ID: <4341DAE7.9000208@riverviewtech.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0509291103090.12174@cerberus.private.pandora-net.com>
Take a look at the NetFilter IPSec patches (4 of them I think). These patches are designed to have the traffic that is passing through the IPSec VPN pass through the NetFilter table twice, once encrypted and once decrypted. This will allow you to filter the traffic on the 2nd (decrypted) pass the way that you are wanting to do.
Grant. . . .
Aaron Smith wrote:
> I have a Windows 2003 server connecting as a client, in Transport mode,
> via IPSec to a RHEL4 server running a 2.6.9 kernel and StrongSwan.
> I would like to use netfilter to filter the protocols and ports that the
> windows server can access on the RHEL4 server, but from what I've read,
> transport mode IPSec packets are decrypted AFTER they have traversed the
> netfilter chains. I have a rule in my INPUT chain that says to allow
> ESP (protocol 50) packets and this appears to be enough for the windows
> client to bypass the rest of the rules. I also have a linux client
> connecting to this same server in Tunnel mode and it's packets appear to
> be accepted, decrypted, an then sent back into the interface to be
> subjected to netfilter so everything works fine there. Is there anyway
> to use netfilter to filter Transport Mode IPSec?
>
> ------
> "The pain of war cannot exceed the woe of aftermath
> The drums will shake the castle walls, the Ringwraiths ride in black..."
> Led Zeppelin, "The Battle of Evermore"
>
next prev parent reply other threads:[~2005-10-04 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 15:09 Filtering Transport Mode IPSec Aaron Smith
2005-10-04 1:29 ` Grant Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-03 20:57 Aaron Smith
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=4341DAE7.9000208@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=aaron@pandora-net.com \
--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.