From: Jozsef Kadlecsik <kadlec@netfilter.org>
To: Rob Bloemers <rob@connectedserver.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: IPSET create exists issue
Date: Wed, 26 Mar 2025 12:24:14 +0100 (CET) [thread overview]
Message-ID: <57adf6c3-4038-f1fe-2472-241a351ae837@netfilter.org> (raw)
In-Reply-To: <184E283D-2392-476C-B23A-9939FE71CA34@connectedserver.com>
[-- Attachment #1: Type: text/plain, Size: 1443 bytes --]
Hi,
On Wed, 26 Mar 2025, Rob Bloemers wrote:
> Hope this is the correct list to email, else I’m eager to hear which
> route to take.
>
> Using netfilter-persistent package on ubuntu an iptables restart gives
> error when reloading iptables and a ipset already exists. Afaics -exist
> ought to work, but it still returns error code 1 and systemctl perceives
> this as an error.
>
> /usr/share/netfilter-persistent/plugins.d/10-ipset start
>
> Which runs: ipset restore -exist < /etc/iptables/ipset
> Still returns: ipset v7.15: Error in line 1: Set cannot be created: set
> with the same name already exists
>
> ipset restore -exist < /etc/iptables/ipsets
> ipset v7.15: Error in line 1: Set cannot be created: set with the same
> name already exists
>
> ipset create -exist vxs hash:ip family inet hashsize 1024 maxelem 65536
> bucketsize 12 initval 0x9bb42fcc
> ipset v7.15: Set cannot be created: set with the same name already
> exists
What is the definition of the already existing set? If it differs from the
one above, then the command fails even with the -exist flag specified: the
set definitions must be identical.
Best regards,
Jozsef
--
E-mail : kadlec@netfilter.org, kadlec@blackhole.kfki.hu, kadlecsik.jozsef@wigner.hu
Address: Wigner Research Centre for Physics
H-1525 Budapest 114, POB. 49, Hungary
next prev parent reply other threads:[~2025-03-26 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 8:55 IPSET create exists issue Rob Bloemers
2025-03-26 11:24 ` Jozsef Kadlecsik [this message]
2025-04-02 8:37 ` Rob Bloemers
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=57adf6c3-4038-f1fe-2472-241a351ae837@netfilter.org \
--to=kadlec@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=rob@connectedserver.com \
/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;
as well as URLs for NNTP newsgroup(s).