From: Born Without <blackhole@airpost.net>
To: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Deleting set/SET rules by exact match fails
Date: Thu, 29 Nov 2012 12:31:10 +0100 [thread overview]
Message-ID: <50B7477E.8050603@airpost.net> (raw)
Hello list,
the problem I ran into is, that I'm unable to delete any iptables rule,
which uses either the set match or the SET target, by the exact matching
rule options. Deleting by rule number works though.
See below output.
System is Debian squeeze with debian kernel 2.6.32.
I downloaded the debian kernel source package.
Applied the netlink.patch and compiled/run it successfully.
Installed latest ipset successfully:
# ipset version
ipset v6.16.1, protocol version: 6
I tried to apt-src iptables and compile that, but made no difference.
# iptables -V
iptables v1.4.8
Any ideas on that?
Thank you very much!
-----------------------------------------------------------------
iptables -vnL FOO
Chain FOO (1 references)
pkts bytes target prot opt in out source
destination
# iptables -A FOO -s 192.168.13.0/24 -p icmp -j SET --add-set foo src
# iptables -A FOO -m set --match-set foo src -j ACCEPT
- generate some traffic...
iptables -vnL FOO
Chain FOO (1 references)
pkts bytes target prot opt in out source
destination
4 240 SET icmp -- * * 192.168.13.0/24
0.0.0.0/0 add-set foo src
18 1148 ACCEPT all -- * * 0.0.0.0/0
0.0.0.0/0 match-set foo src
iptables -D FOO -s 192.168.13.0/24 -p icmp -j SET --add-set foo src
iptables: No chain/target/match by that name.
# iptables -D FOO -m set --match-set foo src -j ACCEPT
iptables: Bad rule (does a matching rule exist in that chain?).
# ipset list foo
Name: foo
Type: hash:ip
Revision: 0
Header: family inet hashsize 1024 maxelem 65536
Size in memory: 8288
References: 2
Members:
192.168.13.254
next reply other threads:[~2012-11-29 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 11:31 Born Without [this message]
2012-12-04 14:25 ` Deleting set/SET rules by exact match fails Jozsef Kadlecsik
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=50B7477E.8050603@airpost.net \
--to=blackhole@airpost.net \
--cc=netfilter@vger.kernel.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