From: Rob Brewer <ipfire-devel@grantura.co.uk>
To: development@lists.ipfire.org
Subject: Re: ipblocklist - conflict with location update
Date: Tue, 19 Apr 2022 13:13:06 +0100 [thread overview]
Message-ID: <t3m90i$fn6$1@tuscan3.grantura.co.uk> (raw)
In-Reply-To: <2dbd4aa3-36f8-ab32-7e78-b6dfa623e390@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 2420 bytes --]
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 ]
>>
next parent reply other threads:[~2022-04-19 12:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2dbd4aa3-36f8-ab32-7e78-b6dfa623e390@yahoo.com>
2022-04-19 12:13 ` Rob Brewer [this message]
2022-05-02 18:34 ` Stefan Schantl
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='t3m90i$fn6$1@tuscan3.grantura.co.uk' \
--to=ipfire-devel@grantura.co.uk \
--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