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 07:39:10 +0000	[thread overview]
Message-ID: <20190107073910.Horde.qkAR68ETx7xfl65l2Z93pdY@whytea.ipfire-zuhause.de> (raw)
In-Reply-To: <q0tge9$bhj$1@tuscan3.grantura.co.uk>

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

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.

-
Daniel


Bob Brewer – Sun, 6. January 2019 19:12
> Hi,
> 
> I have ported a version of the old IPCop addon 'Banish' to IPFire and use it 
> to maintain my local blacklist. Banish was one of my favorite IPCop addons 
> but it ceased to be maintained about 10 years ago and for later versions of 
> IPCop I installed a locally written text version of Banish to maintain the 
> Blacklist.
> 
> This new IPFire version restores all the original GUI functionality and is 
> currently running on an PC Engines ‐ apu2 with IPFire 2.21 (i586) - Core 
> Update 125.
> 
> If you would like to try this addon, I have uploaded it to 
> github.com/Grantura/Banish-IPFire
> grab the self installing file banish-ipfire.tar-1.0.1.gz
> and extract it to /tmp.
> 
> The install also contains an uninstall script should you want to back out at 
> any time.
> 
> Regards
> 
> Rob Brewer

  reply	other threads:[~2019-01-07  7:39 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 [this message]
2019-01-07 10:07   ` Bob Brewer
2019-01-07 12:17     ` Daniel Weismüller
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=20190107073910.Horde.qkAR68ETx7xfl65l2Z93pdY@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