public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Rob Brewer <ipfire-devel@grantura.co.uk>
To: development@lists.ipfire.org
Subject: Re: ipblacklist V2
Date: Sat, 05 Mar 2022 21:46:22 +0000	[thread overview]
Message-ID: <t00lne$1i0$1@tuscan3.grantura.co.uk> (raw)
In-Reply-To: <e14a83280a4f0ba003c6f4a285c4deba012c35f7.camel@ipfire.org>

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

Hi Stefan

On Saturday 05 March 2022 18:52 Stefan Schantl wrote:

> Hello *,
> 
> I've made some development progress, which I want to share here:
> 
> Most parts of the main backend script ("ipblacklist") from Tim and Rob
> are ported into a new functions library (ipblocklist-functions.pl) and
> into the main firewall script (rules.pl).
> 
Good
> This process is almost finished and currently allows to create the
> firewall rules, download the blocklists and to convert them into an
> ipset compatible format.
> 
> Next step will be to import the frontend code (WUI) and adjust it to
> use the backend code (functions) from the "ipblocklist-functions.pl".
> 
> At this time the blocklist feature should be in a use-able state again
> and I'll go to create an automatic update script and to import all the
> logging pages stuff etc.
> 
> The development progress and single commits can be found here:
> 
> 
https://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=shortlog;h=refs/heads/ipblocklist
> 
> As usual please feel free to ask any questions or to share your opinion
> here.
> 
> I wish you a nice day,
> 
> -Stefan
Great progress. I did find a bug I introduced when I modified the ipblacklist V2 
perl script to add a space after the log-prefix BLKLST entry to make the logs 
compatible with other log-prefixes. 
This affected showrequestfromblacklist.dat and the modified version 
'modified regex for V3 log-prefix added space' should be used.

https://git.ipfire.org/?p=people/helix/ipfire-2.x.git;a=commit;h=2ccc47f1944fcf1f8eec8ad132fa606081b21578

Rob

  reply	other threads:[~2022-03-05 21:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ef8ac1dcde46b22207dde653d6717a95d2a737e7.camel@ipfire.org>
2022-03-01 13:13 ` Michael Tremer
2022-03-01 16:08 ` Rob Brewer
2022-03-05 18:52 ` Stefan Schantl
2022-03-05 21:46   ` Rob Brewer [this message]
2022-03-07 20:39     ` Michael Tremer
2022-03-07 22:54       ` Rob Brewer
2022-03-08 10:59         ` Rob Brewer
2022-03-08 15:45           ` Michael Tremer
2022-04-03  9:16           ` Stefan Schantl
2022-04-03 21:09             ` Rob Brewer
2022-02-04 18:17 Rob Brewer
2022-02-07 10:31 ` Michael Tremer
2022-02-07 12:58   ` Rob Brewer
2022-02-09 14:38     ` Adolf Belka
2022-02-09 21:43       ` Rob Brewer
2022-02-09 22:14         ` Adolf Belka
2022-02-10  9:45           ` Michael Tremer
2022-02-09 13:23   ` Rob Brewer
2022-02-09 14:29     ` Adolf Belka
2022-02-10  9:41     ` Michael Tremer
2022-02-10 15:12       ` Rob Brewer
2022-02-10 16:48         ` Michael Tremer
2022-02-12 21:29           ` Tim FitzGeorge
2022-02-13 12:44             ` Rob Brewer
2022-02-15 12:58               ` Michael Tremer
2022-02-15 12:54             ` Michael Tremer

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='t00lne$1i0$1@tuscan3.grantura.co.uk' \
    --to=ipfire-devel@grantura.co.uk \
    --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