public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Daniel Weismüller" <daniel.weismueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPCop Banish Addon for IPFire
Date: Mon, 07 Jan 2019 12:17:12 +0000	[thread overview]
Message-ID: <20190107121712.Horde.wVwXr-9M3pA7ehIqSmcjQCb@whytea.ipfire-zuhause.de> (raw)
In-Reply-To: <q0v8dp$6uu$1@tuscan3.grantura.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]

Hi Rob,

did you see Guardian? 
In my opinion it does nearly the same.

-
Daniel


Bob Brewer – Mon, 7. January 2019 11:07
> Daniel Weismüller wrote:
> 
> > Hi Rob,
> > 
> > thanks for your work.
> > I don't know the banish addon for IPCop so I've read the readme.md on your
> > github link.
> > 
> > But I don't see the advantage against the way to make firewall rules over
> > the firewall.cgi
> > 
> > Please share your view of things with me.
> > 
> 
> Hi Daniel
> 
> Thank you for your interest.
> 
> I have uploaded a couple of screenshots to github showing the Banish 
> configuration page and the Banish Log page which I hope will help to show 
> the difference with firewall.cgi.
> 
> I have a blocklist of about 150 IP Addresses, CIDR, or fully qualified 
> domain names which have shown themselves to be long term abusers and Banish 
> is a very good way of managing this list.
> 
> I use Banish as part of an overall blocklist to protect my mail server from 
> abuse. I also have an in house IPFire front end addon to Fail2ban running 
> on the mail server which uses a dynamic blocklist for short and medium term 
> abuse with Banish used for blocking long term abuse.
> 
> I have been using various flavors of Banish with IPCop for a number of years 
> and find it very easy to manage my blocked resources which I think would be 
> quite difficult if I used just firewall rules.
> 
> Rob

  reply	other threads:[~2019-01-07 12:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-06 18:12 Bob Brewer
2019-01-07  7:39 ` Daniel Weismüller
2019-01-07 10:07   ` Bob Brewer
2019-01-07 12:17     ` Daniel Weismüller [this message]
2019-01-07 14:36       ` Bob Brewer
2019-01-07 12:13 ` Matthias Fischer
2019-01-07 12:26   ` Bob Brewer
2019-01-07 12:38     ` Bob Brewer
2019-01-07 14:48       ` Matthias Fischer
2019-01-07 19:28         ` Bob Brewer
2019-01-07 21:13           ` Matthias Fischer
2019-01-08 16:42             ` Bob Brewer

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=20190107121712.Horde.wVwXr-9M3pA7ehIqSmcjQCb@whytea.ipfire-zuhause.de \
    --to=daniel.weismueller@ipfire.org \
    --cc=development@lists.ipfire.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