Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Aleksandar Milivojevic <amilivojevic@pbl.ca>
To: Aleksandar Milivojevic <amilivojevic@pbl.ca>
Cc: Nico Schottelius <nico-linux-net@schottelius.org>,
	Pablo Neira <pablo@eurodev.net>,
	netfilter@lists.netfilter.org, gregor-net@paasch.name,
	linux-net@vger.kernel.org
Subject: Re: IPSec - IPTables issues
Date: Wed, 05 May 2004 10:01:17 -0500	[thread overview]
Message-ID: <409901BD.10603@pbl.ca> (raw)
In-Reply-To: <4098FE7A.8070707@pbl.ca>

Aleksandar Milivojevic wrote:
> Nico Schottelius wrote:
>> - allow AH, ESP, UDP/500, deny rest on eth0
>> - allow IPs/networks, etc. on ipsec0
> 
>   - allow hosts/networks on eth0 (in Netfilter part of kernel)
>   - setup IPSec policies so that traffic from allowed hosts/networks is 
> required to be encrypted (in IPSec part of kernel)

One thing that just came to my mind.  The unencrypted packet is 
obviously related to the encrypted packet.  I don't know if IPSec part 
of kernel is aware of Netfilter part of kernel, and I have no idea how 
Netfilter (or kernel) is internally tracking packtes, but a thing to try 
(might work, or might fail misserably) in exactly this order:

- allow hosts/networks if state is RELATED
- allow AH, ESP, UDP/500 if state is NEW or ESTABLISHED

Once again, I have no idea if your assumption that encrypted packtes are 
traversing Netfilter tables twice is correct, so above might just be me 
blabing about something I have no idea how it works.  Consider this to 
well intended brainstorming (just some ideas from back of my head, that 
might not have any support in reality).

-- 
Aleksandar Milivojevic <amilivojevic@pbl.ca>    Pollard Banknote Limited
Systems Administrator                           1499 Buffalo Place
Tel: (204) 474-2323 ext 276                     Winnipeg, MB  R3T 1L7

  reply	other threads:[~2004-05-05 15:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040502155538.GD515@schottelius.org>
     [not found] ` <4096317F.8020609@eurodev.net>
2004-05-04 21:15   ` IPSec - IPTables issues Nico Schottelius
2004-05-05  5:28     ` Aidas Kasparas
2004-05-05 10:27     ` Patrick McHardy
2004-05-05 10:48     ` Alexander Samad
2004-05-05 14:47     ` Aleksandar Milivojevic
2004-05-05 15:01       ` Aleksandar Milivojevic [this message]
2004-05-05 15:22       ` Antony Stone
2004-05-05 16:08         ` John A. Sullivan III
2004-05-05 17:32           ` Antony Stone
2004-05-06 15:59             ` Aleksandar Milivojevic
2004-05-06 16:31               ` John A. Sullivan III
2004-05-05 16:12         ` Aleksandar Milivojevic
2004-05-05 17:29           ` Antony Stone
2004-05-05 19:07             ` Aleksandar Milivojevic
2004-05-06  0:21       ` Patrick Turley
2004-05-06  9:10     ` Wolfgang Walter

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=409901BD.10603@pbl.ca \
    --to=amilivojevic@pbl.ca \
    --cc=gregor-net@paasch.name \
    --cc=linux-net@vger.kernel.org \
    --cc=netfilter@lists.netfilter.org \
    --cc=nico-linux-net@schottelius.org \
    --cc=pablo@eurodev.net \
    /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