From: Bent Mathiesen <bent@oriad.net>
To: Matt Hellman <netfilter@taxandfinance.com>, ads nat <adsnat@yahoo.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Is Linux IPTABLES firewall comparable with license Firewall
Date: Mon, 20 Oct 2003 03:00:12 +0200 [thread overview]
Message-ID: <200310200300.12689.bent@oriad.net> (raw)
In-Reply-To: <3F932E05.6040307@taxandfinance.com>
I would say that only one thing come in mind for commercial solutions:
I work in an enterprise business, there we use sunscreens, checkpoint version
4-NG(FP3)+prover-1, Pix, ipchains, etc.
For checkpoint, it is the resent gui version, that enable to look into details
of a larger rulesbase (N*100 customer base). However, I would say, that the
quality/stability of the gui software itself is --- at the same level at it
always have been....
The second, and most important, is options for HA (high awailabillity).
However, I do not think the quality of the software and hardware from
top-vendors is that good. I can give plenty of examples of checkpoint
software/fw problems and hardware failure of Cisco.
And we have used ipchains for years to protect Checkpoint boxes!!
(the hardware is old pc stuff and have been the most stable of it all).
(I would use iptables and PF more if possible - however, as an enterprise, you
have to have the right names on the official papers).
The above is my personal observation and oppinions and not those of the
company I work for.
Best regards
Bent Mathiesen
On Monday 20 October 2003 02:36, Matt Hellman wrote:
> ads nat wrote:
> > Hi,
> > I don't know whether this is right list for my
> > question.
> >
> > I am facing basic problem while convincing to users. I
> > have implemented IPTABLES firewall on my Linux 8.0
> > server. I am frequently asked by users which
> > firewall/security measures are taken for my network.
> > My competitors use Checkpoint Firewall.
> > Can somebody guide me how to convince my users that
> > Linux IPTABLES Firewall is technically at par with
> > commercial Firewall such as checkpoint.
> >
> > Also if same security policies are adopted for
> > IPTABLES and checkpoint, Is IPTABLES technically at
> > par with commercial FIREWALLs?
> >
> > Thanks
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > The New Yahoo! Shopping - with improved product search
> > http://shopping.yahoo.com
>
> netfilter is best suited for configurations in small to medium
> enteriprises IMHO (it is also an excellent host based firewall).
> Commerial firewalls have significant advantages...they come out of the
> box with top-notch gui management capabilities, fail-over, vpn and
> application-level services which support multiple authentication
> sources. Some of this can be accomplished on a netfilter box, but not
> without significant effort to configure and maintain.
>
> The greatest advantage netfilter has is that it runs on a Linux box
> which gives it a tremendous amount of flexibility. You can do some
> things on a Linux box that you wouldn't dream of on a commercial
> firewall. Of course, some see this as a distinct disadvantage compared
> to an appliance;-)
>
> Anymore, I'm having a tough time recommending a PC running Linux versus
> some of the entry level commercial firewalls, like a Pix, that can be
> had for under $1000, if for no other reason that it will be FAR less
> likely to have a hardware failure. If you're customers aren't
> satifisfied with your using netfilter on Linux, buy an inexpensive cisco
> Pix...I'm sure the name "Cisco" will impress them;-)
>
> Goodluck,
> Matt
--
Bent Mathiesen
bent@oriad.net
next prev parent reply other threads:[~2003-10-20 1:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-18 9:18 Is Linux IPTABLES firewall comparable with license Firewall ads nat
2003-10-18 9:53 ` Joel
2003-10-18 18:36 ` Mark E. Donaldson
2003-10-18 21:40 ` Josh Berry
2003-10-19 15:13 ` Stephen Satchell
2003-10-20 0:36 ` Matt Hellman
2003-10-20 1:00 ` Bent Mathiesen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-19 22:22 Daniel Chemko
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=200310200300.12689.bent@oriad.net \
--to=bent@oriad.net \
--cc=adsnat@yahoo.com \
--cc=netfilter@lists.netfilter.org \
--cc=netfilter@taxandfinance.com \
/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