public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Blizbor <kernel@globalintech.pl>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6 native IPsec implementation question
Date: Mon, 15 Nov 2004 17:47:36 +0100	[thread overview]
Message-ID: <4198DDA8.3000100@globalintech.pl> (raw)
In-Reply-To: <Pine.LNX.4.53.0411151557550.17812@yvahk01.tjqt.qr>

Jan Engelhardt wrote:

>You "sit" on the network card chip and then think of input and output.
>Btw, -j DROP will only drop what has not been matched up to now. So if you get
>to -j ACCEPT IPsec traffic beforehand (I think -m ah / -m esp, did not
>it?), they will never reach -j DROP.
>  
>
No, it's not like you think.

Situation is NOT EASY IF you have ONE VPN.
Just "close" eth0 for anything, allow AH,ESP,DNS from "any" IP addres,
then how you detect if tcp/389 is from VPN or form world ? You cant.
To make things harder - there are eth0, eth1, eth2 and eth3, two of them
has public IP addresses, two has private IP addresses, there is IPsec VPN
server running on both public addresses and a lot (32) of roadwarrior VPN
clients.

So, in this not easy situation firewalling is not possible.
Believe me.

But, how to implement firewall using iptables command is not my issue.
Lets assume that I just want to do "mrtg" traffic accounting....

So, my questions are still actual.

Regards,
Blizbor


  reply	other threads:[~2004-11-15 16:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-15 13:44 2.6 native IPsec implementation question Blizbor
2004-11-15 14:02 ` Jan Engelhardt
2004-11-15 14:48   ` Blizbor
2004-11-15 15:05     ` Jan Engelhardt
2004-11-15 16:47       ` Blizbor [this message]
2004-11-16 17:47 ` Andreas Unterkircher

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=4198DDA8.3000100@globalintech.pl \
    --to=kernel@globalintech.pl \
    --cc=linux-kernel@vger.kernel.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