Re: Moving from IPTABLES to SonicWall

The true reason is that the Linux machine with IPTABLES is growing old, and
will sooner or later fail. We need to find a stand-by replacement for it,
without necessarily shutting it down right away. Mirroring the existing
environment on another box, as well as making changes to the existing rules
from time to time, requires some understanding of what one is doing, and at
the present time there is no-one in the office with skills to do so.

I used to do this myself, but I am on an assignment far away from the
office, and cannot provide any maintenance and support to the firewall. So,
we thought that the firmware-based solution is less prone to failures, and
might require less maintenance.

Features provided by IPTABLES are sufficient for our needs. But maintaining
it is beyond the skill level of people left behind in the office.

Thank you for looking into this.

Alex.

"Leythos" <void@nowhere.lan> wrote in message
news:BIvXf.70993$9I5.67137@tornado.ohiordc.rr.com...
> In article <442e2dc3@news.uni-ulm.de>, bumens@dingens.org says...
> > Alex Molochnikov <NOBODY@nospam.com> wrote:
> > > We are contemplating a move from the IPTABLES firewall to a
firmware-based
> > > one.
> >
> > Just for being interested: why?
>
> Maybe, because like many, they want a certified solution, they want
> something that they are sure is doing what they want with the protection
> they need, with a support contract, with features not found in IPTables.
>
> --
>
> spam999free@rrohio.com
> remove 999 in order to email me
Received on Mon May 1 01:03:58 2006