From: Daniel Bidwell <bidwell@andrews.edu>
To: "Masiero Giorgio, PD" <gmasiero@cerved.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Checkpoint fw-1 Iptables translation
Date: 09 Jun 2003 11:17:49 -0400 [thread overview]
Message-ID: <1055171871.731.2.camel@samwise> (raw)
In-Reply-To: <E9C5F057A783F94E9868010ACFDB3AA42D8CE2@srvpadovaad.cerved.com>
On Mon, 2003-06-09 at 08:44, Masiero Giorgio, PD wrote:
> Hy, my name is Giorgio and I have this problem.
>
> We have Checkpoint FW-1 firewalls, and we are trying to build a program
> that translate all the Checkpoint FW-1 configuration files (Objects, Rules,
> NATs)
> into an understandable set of files for Iptables.
> We wanto to do this because we are tryng to build a "disaster recovery" site
> on which we want to use a linux machine with Iptables as firewall.
>
> I'm trying to write this program, but It isn't easy.
> Is there anybody that could help me doing this job?
> Maybe someone has already had my problem and has already writed the program
> I'm looking for.
>
There is a contributed program with the fwbuilder package that converts
checkpoint-1 configurations into fwbuilder configurations. fwbuilder
has a graphical interface that is very similar to that of checkpoint
also.
You can convert checkpoint firewall configurations into fwbuilder
configurations in about 30 seconds. fwbuilder can be found at
fwbuilder.sourceforge.net
> Thanks for your help Giorgio
--
Daniel R. Bidwell | bidwell@andrews.edu
Andrews University | Information Technology Services
If two always agree, one of them is unnecessary
"Friends don't let friends do DOS"
"In theory, theory and practice are the same.
In practice, however, they are not."
prev parent reply other threads:[~2003-06-09 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 12:44 Checkpoint fw-1 Iptables translation Masiero Giorgio, PD
2003-06-09 15:17 ` Daniel Bidwell [this message]
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=1055171871.731.2.camel@samwise \
--to=bidwell@andrews.edu \
--cc=gmasiero@cerved.com \
--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