All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aleksandar Milivojevic <amilivojevic@pbl.ca>
To: netfilter@lists.netfilter.org
Subject: Re: IPSec - IPTables issues
Date: Wed, 05 May 2004 14:07:03 -0500	[thread overview]
Message-ID: <40993B57.6070309@pbl.ca> (raw)
In-Reply-To: <200405051829.14783.Antony@Soft-Solutions.co.uk>

Antony Stone wrote:
> On Wednesday 05 May 2004 5:12 pm, Aleksandar Milivojevic wrote:
>>Actually, I like better Linux 2.6 implementation that doesn't use virtual
>>devices.
> 
> Yes, it seems like a better design; now if only we could work out how to 
> filter the unencrypted traffic before it all just disappears down the tunnel, 
> it might turn out to be a good idea.

You let IPSec kernel module take care that anything unencrypted comming 
from the wire or into the wire is dropped.  This should be easily 
acomplished by setting IPSec policy for the connection to required.  So 
you do not need Netfilter to filter out unencrypted traffic from the 
wire.  IPSec is going to do that for you.

Than in Netfilter, you accept packets if they are:

1. IPSec packets (AH, ESP, UDP/500)
2. unencrypted packets for the services (HTTP, FTP, telnet, etc) you are 
allowing

This way, Netfilter will take care of packets before they are encrypted, 
and after they are decrypted.  Therefore protecting the local services 
and allowing you to filter "before it all just dissapears down the 
tunnel".  IPSec will take care that there is no unecrypted traffic going 
onto the wire (or accepted from the wire).

So you don't need virtual interface to differentiate first and second 
pass through Netfilter's chains.

-- 
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 19:07 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
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 [this message]
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=40993B57.6070309@pbl.ca \
    --to=amilivojevic@pbl.ca \
    --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.