public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: ipblocklist - Call for testers
Date: Fri, 15 Jul 2022 12:57:19 +0200	[thread overview]
Message-ID: <b9f46a9a-be5b-b946-484c-b64a02f10f6f@ipfire.org> (raw)
In-Reply-To: <t975fp$lb8$1@tuscan3.grantura.co.uk>

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

Hi,

On 25.06.2022 16:18, Rob Brewer wrote:
> Hi Stefan
> 
> On Tuesday 21 June 2022 18:21 Stefan Schantl wrote:
> 
>> Hello list followers,
>> 
>> today I've uploaded a new ipblocklist test version (ipblocklist-002).
>> 
>> It has been rebased to work with core update 168 and also contains some
>> bugfixes and new features:
>> 
>> * The update interval now is set to 15 minutes
>> * The WUI now displays the "Firewall reload hint" as notice instead of
>> an error.
>> * The logging of the ipblocklist-update script has been improved.
>> * Support for logwatch has been added.
>> * A bug which sometimes prevents from reloading a blocklist after an
>> update has been performed has been fixed.
>> 
>> HINT: The update instructions are the same than for installing.
>> 
>> WARNING: Any taken settings from previous test versions will be lost,
>> when updating! (Please backup your "/var/ipfire/ipblocklist/settings"
>> file in that case.)
>> 
>> I'm planing to submit this addon to be merged and released with core
>> update 170 so, please heavily test and report any kind of remaining
>> issues.
>> 
>> A big thanks in advance,
>> 
>> -Stefan
>>  
> 
> There seems to be a problem with the 'disable' function in the sources list. 
> For instance if I enable the BOGON list and the attempt to enable the 
> BOGON_FULL list in IPBlacklist I see the error message "Disabling BOGON 
> because it is included in BOGON_FULL" after selecting 'save' and the 'enable 
> box' would be un-ticked. This isn't happening in -002 and I can select both 
> BOGON lists.

I can confirm with -002.

Matthias

> 
> Rob
>  
> 
>>> Hello mailing list followers,
>>> 
>>> it has been done - the port of the well known (ipblacklist) feature
>>> from Tim FitzGeorge has been finished.
>>> 
>>> Now it's time for the final steps. For this I need your help, in
>>> testing and giving feedback and/or bug reports.
>>> 
>>> I've backed and uploaded a test version, which contains all necessary
>>> files and modifications. There is also a README file available which
>>> gives further details and how to install the test version on your
>>> sytems.
>>> 
>>> This all can be found here:
>>> 
>>> https://people.ipfire.org/~stevee/ipblocklist/
>>> 
>>> For those of you which are interested in the source code:
>>> 
>>> 
> https://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=shortlog;h=refs/heads/ipblocklist-rbsed
>>> 
>>> 
>>> Best regards and a happy testing,
>>> 
>>> -Stefan
>>>
> 


  reply	other threads:[~2022-07-15 10:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-10 11:09 Stefan Schantl
2022-04-11  8:25 ` Rob Brewer
2022-04-11 12:42   ` Rob Brewer
2022-06-21 17:21 ` Stefan Schantl
2022-06-24  7:53   ` Rob Brewer
2022-06-25 14:18   ` Rob Brewer
2022-07-15 10:57     ` Matthias Fischer [this message]
2022-07-21 15:43 ` Matthias Fischer
     [not found] <181fd0ece98.2777.cac9d3ffac9e24d09d20af05166fd73b@ipfire.org>
2022-07-14 15:40 ` Matthias Fischer

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=b9f46a9a-be5b-b946-484c-b64a02f10f6f@ipfire.org \
    --to=matthias.fischer@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