From: "Dj Statik" <djstatik@djstatik.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Any FERM Users
Date: Wed, 5 Nov 2003 20:26:05 +1100 [thread overview]
Message-ID: <002701c3a37e$d6ab6770$c001a8c0@NUKLEUZ> (raw)
In-Reply-To: <Pine.BSF.4.58.0311050158060.45757@server1.shellworld.net>
I've been using it locally for a little while, it's fairly complex, but not
half as painful as tring to script the firewall rules yourself.
If you want something really simple though you might want to check out
freshmeat for phptables or similar, i.e. a nice little web GUI where you can
tick a couple of boxes and have it spit out a iptables script for you, but
it can't do anything overly complicated.
If you want to script a nice secure and functional firewall though FERM is a
great way to go about it.
It's docs are pretty useful too.
>From Mitchell
----- Original Message -----
From: "Luke Davis" <ldavis@shellworld.net>
To: <Speakup@braille.uwo.ca>
Sent: Wednesday, November 05, 2003 6:58 PM
Subject: Any FERM Users
> I am looking for a firewall scripting language, or structure system, for
> iptables configurations.
>
> I have found some X solutions, but I'm looking for something textmode.
>
> The most promising of these I have found, are no longer supported, or have
> not been recently updated.
>
> I did, however, come across FERM (Debian: apt-get install ferm).
>
> Has anyone used this, and/or what are the thoughts of anyone who has any,
> respecting this system?
>
> Thanks,
>
> Regards,
>
> Luke
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Luke Davis
` Dj Statik [this message]
` Luke Davis
` Alex Snow
` Thomas Stivers
` Scott Howell
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='002701c3a37e$d6ab6770$c001a8c0@NUKLEUZ' \
--to=djstatik@djstatik.net \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).