public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: ipblocklist - Call for testers (disable attribute in sources)
Date: Sun, 10 Apr 2022 20:47:57 +0200	[thread overview]
Message-ID: <961884a7cc18d074b7b74ab4c597ac97072d0205.camel@ipfire.org> (raw)
In-Reply-To: <7ddd588a-e82f-814f-b8cc-8a80c823a2f0@yahoo.com>

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

Hello Charles,

thanks for a first look and your feedback.

Now after you have put my attention to those "disable" value in the
sources file, I have to admit I totally have overseen this.

When interpreting this field and the values, it seems has been designed
to automatically disable conflicting/obsolete sets in case such a set
is enabled.

So for this feature I have go back to the drawing board and put some
attention to it.

In the meantime please go on with testing and report any other issues.

Best regards,

-Stefan 
>  Tim, Stefan,
> I have installed the ipblocklist feature. It looks great.
> I’m curious about the disable attribute in the sources file. 
>  I have all the lists enabled, I would have thought enabling
> EMERGING_FWRULE would have the DSHIELD list automatically disabled.
> However, I am showing several hits on DSHIELD and I see 20 entries in
> ipset for DSHIELD. Is the disable attribute in sources there for
> informational purposes only? 
> Thanks for your excellent work on this feature,
>  Charles Brown
> 
>  



       reply	other threads:[~2022-04-10 18:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7ddd588a-e82f-814f-b8cc-8a80c823a2f0@yahoo.com>
2022-04-10 18:47 ` Stefan Schantl [this message]
2022-04-10 18:53 ` Matthias Fischer
2022-04-10 22:39 ` Rob Brewer
2022-04-11 21:51 Tim FitzGeorge
2022-04-12  4:12 ` Stefan Schantl
2022-04-12 16:46   ` 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=961884a7cc18d074b7b74ab4c597ac97072d0205.camel@ipfire.org \
    --to=stefan.schantl@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