Jozsef Kadlecsik wrote:
You can maintain one set for the network addresses, one for the IP addresses and create a setlist type of set with both "subsets" as members.
Now I have a trouble with 'setlist'. For example: [root@tomgate /]# ipset -N pool1 ipmap --network 192.168.0.0/24 [root@tomgate /]# ipset -A pool1 192.168.0.1 [root@tomgate /]# ipset -N myset setlist [root@tomgate /]# ipset -A myset pool1 [root@tomgate /]# ipset -T pool1 192.168.0.1 192.168.0.1 is in set pool1. [root@tomgate /]# ipset -T pool1 192.168.0.2 192.168.0.2 is NOT in set pool1. [root@tomgate /]# ipset -T myset 192.168.0.1 192.168.0.1 is in set myset. [root@tomgate /]# ipset -T myset 192.168.0.2 192.168.0.2 is in set myset. [root@tomgate /]# ipset -T myset stupidgarbage stupidgarbage is in set myset. When testing my setlist I always get "is in set". I suppose that is not normal. -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
