From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: ipblocklist - conflict with location update
Date: Mon, 02 May 2022 20:34:57 +0200
Message-ID: <0b4df367aad25ff9c55f6c89567f6b9600a15ad4.camel@ipfire.org>
In-Reply-To: <t3m90i$fn6$1@tuscan3.grantura.co.uk>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4665619665614022948=="
List-Id: <development.lists.ipfire.org>

--===============4665619665614022948==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Hello Rob, Hello Charles,

sorry for the long delay.

Thanks for reporting this issue, I figured out the problem and already
fixed it.

At the moment I'm working on some more fixes and to create a second
test release for ipblocklist.

Please stay tuned,

-Stefan
> 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.
> > 
> > -cab
> > 
> 
> Charles
> 
> firewallctrl runs  /usr/lib/firewall/rules.pl 
> 
> rules.pl has been changed for the new integrated ipblocklist which
> isn't 
> 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 
> 
> 
> 
> 
> 
> > 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
> > > 
> > > 
> ---------------------------------------------------------------------
> --------------------------------------------------------------------
> > > 
> > >     [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  ]
> > > 
> 



--===============4665619665614022948==--