From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Schantl To: development@lists.ipfire.org Subject: Re: ipblocklist - Call for testers (disable attribute in sources) Date: Sun, 10 Apr 2022 20:47:57 +0200 Message-ID: <961884a7cc18d074b7b74ab4c597ac97072d0205.camel@ipfire.org> In-Reply-To: <7ddd588a-e82f-814f-b8cc-8a80c823a2f0@yahoo.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8840100049924474727==" List-Id: --===============8840100049924474727== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit 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 > >   --===============8840100049924474727==--