[Bug 744] set:list behavior

bugzilla-daemon at bugzilla.netfilter.org bugzilla-daemon at bugzilla.netfilter.org
Mon Sep 5 15:35:34 CEST 2011


http://bugzilla.netfilter.org/show_bug.cgi?id=744





--- Comment #2 from martin barrowcliff <martinbarrowcliff at gmail.com>  2011-09-05 15:35:34 ---
I installed ipset-6.8 from xtables-addons which lists the ipset version
(v6.8-genl-xta) and protocol version (96?!). Jan can clarify any confusion on
that.

In V4 a setlist could be tested/matched. I used this heavily for both single
IP sets and Network sets. It worked nice and I liked it. Now I switched to V6. 

Forgive my naive question.
If, in ipset-V6 a set:list cannot be tested, it would seem it cannot be
matched.
Both functions do essentially the same thing, regardless of set types.
And without test/match functionality, how can set:list be used with iptables
????
Seems to me set:list doesn't do anything useful.

As a solution I will add iptables rules to test/match each individual set and
delete the useless set:lists I was using. Solves my problem.

Marty B.


-- 
Configure bugmail: http://bugzilla.netfilter.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.



More information about the netfilter-buglog mailing list