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: Mon, 07 Feb 2022 12:58:21 +0000	[thread overview]
Message-ID: <str51d$emq$1@tuscan3.grantura.co.uk> (raw)
In-Reply-To: <1DC94D84-CE41-4A42-8195-27E14E542AAA@ipfire.org>

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

Hi Michael,


Michael Tremer wrote:

> Hello Rob,
> 
> Thank you for your interest in working on this.
> 
> Yes, I always thought that there was great interest in moving this over
> the line. However, I could not find where we left off here.
> 
> There were a couple of outstanding issues that had to be resolved. I just
> couldn’t find my last emails. Are you aware of these?
> 

You expect have seen the topic :

https://community.ipfire.org/t/can-i-help-progress-version2-of-ipblacklist-addon/6998/18

 where Adolf has been encouraging me to look at this feature and I now have 
a working copy on my firewall.

I believe the patches on patchwork are mostly complete and with a few 
additions/corrections can be incorporated into the latest build.

Here is my understanding of where we are:

https://patchwork.ipfire.org/project/ipfire/patch/20200427143123.6378-9-ipfr(a)tfitzgeorge.me.uk/

[v2,0/8] ipblacklist: IP Address Blacklists

This patch was applied to convert V1 into V2 and used to make the the 
remaining patches
It can safely be ignored.

[v2,1/8] ipblacklist: Main script
This is the ipblacklist main perl program. It can be incorporated without 
problems.


[v2,2/8] ipblacklist: WUI Settings page
ipblacklist.cgi Patch can be applied without any changes.


[v2,3/8] ipblacklist: WUI Log page
ipblacklists.dat  - Needs to be modified with an additional patch to:

1)    remove - require “${General::swroot}/geoip-functions.pl”; - This isn’t 
included in core 161 and not used in this program.

2)  change
        &General::readhash( “/srv/web/ipfire/html/themes/”.
$mainsettings{‘THEME’}."/include/colors.txt", %color );
    to
        &General::readhash( 
“/srv/web/ipfire/html/themes/ipfire/include/colors.txt”, %color );


[v2,4/8] ipblacklist: WUI Log details page

showrequestfromblacklist.dat - Patch can be applied without any changes


[v2,5/8] ipblacklist: WUI menus, language file etc

50-firewall.menu
70-log.menu
log.dat
en.pl

Requires additional lang files for de, es, fr, it, nl, pl, ru, tr.
All others are OK

[v2,6/8] ipblacklist: Ancillary files

sources
getipsetstat.c 
ipblacklistctrl.c

 Can be applied without any changes
 

[v2,8/8] ipblacklist: Build infrastructure

aarch64/stage2
configroot
ipblacklist-sources
logwatch
misc-progs
common/stage2
web-user-interface
x86_64/stage2
lfs/configroot
lfs/ipblacklist-sources
lfs/logwatch
make.sh
misc-progs/Makefile

Missing Files and links:

ipblacklist.conf (for logwatch)
ipblacklist (for logwatch)
/etc/rc.d/init.d/ipblacklist (Start -up)
/etc/rc.d/rcsysinit.d/S87ipblacklist -> ../init.d/ipblacklist

I have written code for the missing files which are working on my firewall 
and I could submit as patches if required. 

 /usr/share/logwatch/default.conf/services/ipblacklist.conf
 /usr/share/logwatch/scripts/services/ipblacklist
 /etc/rc.d/init.d/ipblacklist 

I haven't tried incorporating the patches as I extracted the files from 
Patchwork and manually inserted them into my firewall for testing. I would 
be very surprised if there were any problems  with Tim's code however.

Hope this will help to progress this very useful addition to IPFire.


Rob


  reply	other threads:[~2022-02-07 12:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04 18:17 Rob Brewer
2022-02-07 10:31 ` Michael Tremer
2022-02-07 12:58   ` Rob Brewer [this message]
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
     [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
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

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='str51d$emq$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