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: Thu, 21 Jul 2022 17:43:30 +0200	[thread overview]
Message-ID: <4f322bd2-b36c-f463-567c-06d2c276baba@ipfire.org> (raw)
In-Reply-To: <c0dd9b99727a7b7b88a5f14649870f8cee36c235.camel@ipfire.org>

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

On 10.04.2022 13:09, Stefan Schantl wrote:
> Hello mailing list followers,

Hi Stefan,

> 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 took a closer look at 'ipblocklist' in the last week and I noticed a
few things. Everything seems to work, I'm just curious:

E.g., 'ipblocklist.dat' (IP Address Blocklist Logs) shows a total number
of "168 hits" for today (July 21). These are "150 hits" for BLOCKLIST_DE
and "18 hits" for SHODAN.

When I look at the IPTables "BLOCKLISTIN" chain I find "614 pkts" for
BLOCKLIST_DE_DROP (match-set BLOCKLIST_DE src) and "95 pkts" for
SHODAN_DROP (match-set SHODAN src).

Why do these numbers differ? Different time slots?

Best,
Matthias


  parent reply	other threads:[~2022-07-21 15:43 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
2022-07-21 15:43 ` Matthias Fischer [this message]
     [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=4f322bd2-b36c-f463-567c-06d2c276baba@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