From: "Maciej Soltysiak" <solt@dns.toxicfilms.tv>
To: netfilter@lists.netfilter.org
Subject: Re: advantage and disadvantage between iptables and ISAServer?
Date: Wed, 25 Feb 2004 17:17:35 +0100 [thread overview]
Message-ID: <001b01c3fbba$e14cc720$0e25fe96@pysiak> (raw)
In-Reply-To: 20040225084959.471bb675@mgalepc.utilitran.com
> I am not to familure with ISA because the M$ admins here tell me it is not
worth
> the enough to test it out. I would assume it is like any other M$ product
though
> ... you need double or triple the hardware to run it as compared to
iptables.
Agree, oh, this is true. Currently w2k3 runs very bad on:
p4 1,5ghz, 384MB
with a few of the services setup: AD, WMS, IIS (HTTP+FTP), SUS, SMS.
> You are stuck with the options the M$ provides instead of the endless
> possibilities the a Unix or Linux could offer.
Well, sort of. iptables is very powerfull, but I think that upcomming isa
2004
is going to be modular and pluggable too, plus it will certainly address
popular
security issues like: p2p (yes, it is a security issue), worms, network
attacks
that have signatures: slammer, floods, land, dos, etc...
Like checkpoint's SmartDefense.
I have not been using isa, but only read and seen a presentation of isa
2004,
It is possible that is going to be a powerfull tool. No information about
stability,
propably it'd depend on which version of windows you are running and how
stable it is. Performance? No idea.
Regards,
Maciej
next prev parent reply other threads:[~2004-02-25 16:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 9:00 advantage and disadvantage between iptables and ISAServer? Monty Ree
2004-02-25 15:49 ` Michael Gale
2004-02-25 16:07 ` [OT] " Antony Stone
2004-02-25 16:18 ` Tim Evans
2004-02-25 16:24 ` Antony Stone
2004-02-27 1:35 ` Arnt Karlsen
2004-02-25 16:17 ` Maciej Soltysiak [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-25 21:29 bmcdowell
2004-02-28 11:33 Lasse Pettersson
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='001b01c3fbba$e14cc720$0e25fe96@pysiak' \
--to=solt@dns.toxicfilms.tv \
--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