* Re: ipblocklist - conflict with location update
2022-04-19 12:13 ` ipblocklist - conflict with location update Rob Brewer
@ 2022-05-02 18:34 ` Stefan Schantl
0 siblings, 0 replies; 2+ messages in thread
From: Stefan Schantl @ 2022-05-02 18:34 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 2957 bytes --]
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 ]
> > >
>
^ permalink raw reply [flat|nested] 2+ messages in thread