Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
To: kossentini_3@voila.fr
Cc: netfilter@lists.netfilter.org
Subject: RE: documentation netfilter
Date: Wed, 14 Sep 2005 08:22:11 -0400	[thread overview]
Message-ID: <1126700531.2651.8.camel@localhost> (raw)
In-Reply-To: <24026302.1126689606287.JavaMail.www@wwinf4002>

On Wed, 2005-09-14 at 11:20 +0200, kossentini_3@voila.fr wrote:
> hello,
>  Within the framework of my project of end of study, I must choose best the firewall open source and then I must develop new functionalities so that it is same level as check point or another owner firewall (for example cisco Centri Firewall...). 
>  
> can you help me in this subject? which is the best  firewall open source (if there is one of the bonds towards site, a study)...? 
> thank you in advance 
<snip>
From everything I have seen, iptables combined with other open source
projects such as iproute2 and {open,strong}swan is far superior to
CheckPoint and most other commercial firewalls.  In fact, it amazes me
that no one has commercially exploited this yet with significant
success.  Even some of the more successful linux based solutions are
using fairly old technology.

iptables not only excels in functionality but in flexibility.

The main disadvantage I have found is the dearth of enterprise/carrier
grade management tools.  One can do more with iptables than one can do
with Checkpoint if one administers one firewall at a time (or several).
For smaller environments, it is better than learning a complex user
interface.  But there is nothing akin to Provider1, Solsoft or
SmartPipes for very large deployments of hundreds and thousands of
firewalls with thousands to hundreds of thousands of users with highly
complex security.

Although one can make iptables do far more than Checkpoint in such
scenarios, the manpower cost of managing such an installation with open
source tools is prohibitive.

That is why we have been working on the ISCS project
(http://iscs.sourceforge.net). This project exceeds the capabilities of
tools like Provider1, Solsoft and SmartPipes yet is entirely open source
and works with open source products like iptables, iproute2 and *swan.
Unfortunately, I've been mostly pulled off the project for the last year
+.  If anyone would like to jump in and help so we can fill this missing
gap and make open source firewalls a superior choice to commercial
products on all fronts - not just functionality and flexibility but
management, too, please let me know - John
-- 
John A. Sullivan III
Open Source Development Corporation
+1 207-985-7880
jsullivan@opensourcedevel.com

Financially sustainable open source development
http://www.opensourcedevel.com



  reply	other threads:[~2005-09-14 12:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14  9:20 documentation netfilter kossentini_3
2005-09-14 12:22 ` John A. Sullivan III [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-14  7:05 kossentini_3
2005-09-14  7:08 ` Ruben Cardenal

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=1126700531.2651.8.camel@localhost \
    --to=jsullivan@opensourcedevel.com \
    --cc=kossentini_3@voila.fr \
    --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