From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Brewer To: development@lists.ipfire.org Subject: Re: ipblocklist - conflict with location update Date: Tue, 19 Apr 2022 13:13:06 +0100 Message-ID: In-Reply-To: <2dbd4aa3-36f8-ab32-7e78-b6dfa623e390@yahoo.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7770295168988291846==" List-Id: --===============7770295168988291846== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Monday 18 April 2022 14:22 Charles Brown wrote: > Upon further look, the issue is not particular to > update-location-database. Running command, firewallctrl, also results in > the same set of error indications. >=20 > -cab >=20 Charles firewallctrl runs /usr/lib/firewall/rules.pl=20 rules.pl has been changed for the new integrated ipblocklist which isn't=20 installed here as I'm still running Tim's original. update-location-database, firewallctrl and rules.pl are all running OK on my = systems. Rob=20 > On 4/18/2022 8:12 AM, Charles Brown wrote: >> >> Hi Stefan, Tim, Rob >> >> I manually updated my location database at ssh shell prompt with >> command, update-location-database. >> It appears to present some possible conflicts. Or perhaps, is this >> purely informational? See following. >> >> -Charles >> >>=20 -----------------------------------------------------------------------------= ------------------------------------------------------------ >> >> [root(a)ipfire ~]# update-location-database >> Downloaded new database from Mon, 18 Apr 2022 05:52:42 GMT >> Reloading firewall >> ipset v7.11: Error in line 3: Set cannot be created: set with the >> same name already exists >> ERROR: ipset restore -f /var/lib/ipblocklist/BLOCKLIST_DE.conf >> ipset v7.11: Error in line 3: Set cannot be created: set with the >> same name already exists >> ERROR: ipset restore -f /var/lib/ipblocklist/BOGON_FULL.conf >> ipset v7.11: Error in line 3: Set cannot be created: set with the >> same name already exists >> ERROR: ipset restore -f >> /var/lib/ipblocklist/EMERGING_COMPROMISED.conf ipset v7.11: Error in >> line 3: Set cannot be created: set with the same name already exists >> ERROR: ipset restore -f /var/lib/ipblocklist/FEODO_AGGRESIVE.conf >> ipset v7.11: Error in line 3: Set cannot be created: set with the >> same name already exists >> ERROR: ipset restore -f /var/lib/ipblocklist/SHODAN.conf >> ipset v7.11: Error in line 3: Set cannot be created: set with the >> same name already exists >> ERROR: ipset restore -f /var/lib/ipblocklist/SPAMHAUS_EDROP.conf >> ipset v7.11: Error in line 3: Set cannot be created: set with the >> same name already exists >> ERROR: ipset restore -f /var/lib/ipblocklist/TOR_ALL.conf >> [OK ] >> --===============7770295168988291846==--