From: Tom Eastep <teastep@shorewall.net>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Husnu Demir <hdemir@metu.edu.tr>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: ipset problem.
Date: Fri, 22 Jan 2010 10:05:44 -0800 [thread overview]
Message-ID: <4B59E8F8.1060401@shorewall.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1001221419550.13886@blackhole.kfki.hu>
[-- Attachment #1: Type: text/plain, Size: 2092 bytes --]
Jozsef Kadlecsik wrote:
>> nl# ipset -v
>> ipset v4.1, protocol version 4.
>> Kernel module protocol version 4.
>
> I'll try to reproduce and find the reason for the difference in the
> listing.
>
I can add another data point.
A similar issue can be seen when xtables-addons 1.21 is installed on
Debian Lenny, kernel 2.6.26-openvz-am64. In that case, extra /31
networks show up whether a set name is supplied or not; they are
different in the two cases, however.
gateway:~# ipset -L dshield -n
Name: dshield
Type: nethash
References: 1
Header: hashsize: 1024 probes: 4 resize: 50
Members:
74.63.225.0/24
218.206.128.0/24
210.212.152.0/24
77.254.150.0/24
116.55.199.0/24
118.160.213.0/24
70.38.64.0/24
91.144.92.0/24
58.221.42.0/24
174.129.75.0/24
88.163.67.0/24
219.139.40.0/24
88.79.127.0/24
194.165.153.0/24
75.101.178.0/24
222.45.112.0/24
202.155.202.0/24
89.149.204.0/24
118.161.234.0/24
122.200.121.0/24
116.114.111.222/31
0.112.97.216/31
0.1.0.0/31
97.109.111.218/31
0.0.108.208/31
97.104.112.208/31
0.0.104.228/31
gateway:~# ipset -L -n
...
Name: dshield
Type: nethash
References: 1
Header: hashsize: 1024 probes: 4 resize: 50
Members:
74.63.225.0/24
218.206.128.0/24
210.212.152.0/24
77.254.150.0/24
116.55.199.0/24
118.160.213.0/24
70.38.64.0/24
91.144.92.0/24
58.221.42.0/24
174.129.75.0/24
88.163.67.0/24
219.139.40.0/24
88.79.127.0/24
194.165.153.0/24
75.101.178.0/24
222.45.112.0/24
202.155.202.0/24
89.149.204.0/24
118.161.234.0/24
122.200.121.0/24
48.116.105.228/31
97.104.112.208/31
0.0.104.228/31
0.5.0.8/31
95.116.101.218/31
101.114.105.198/31
0.0.116.196/31
...
All of the /31 nets are bogus.
When installed on a Lenny system running kernel 2.6.26-686, things seem
to work as expected.
-Tom
--
Tom Eastep \ When I die, I want to go like my Grandfather who
Shoreline, \ died peacefully in his sleep. Not screaming like
Washington, USA \ all of the passengers in his car
http://shorewall.net \________________________________________________
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2010-01-22 18:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 11:54 ipset problem Husnu Demir
2010-01-22 13:22 ` Jozsef Kadlecsik
2010-01-22 18:05 ` Tom Eastep [this message]
2010-01-23 21:00 ` Jozsef Kadlecsik
2010-01-23 21:44 ` Jozsef Kadlecsik
[not found] ` <alpine.DEB.2.00.1001242243560.20757@blackhole.kfki.hu>
2010-01-25 7:17 ` Husnu Demir
2010-01-25 10:24 ` Jozsef Kadlecsik
2010-01-25 11:33 ` Jan Engelhardt
2010-01-25 11:47 ` Husnu Demir
2010-01-25 11:34 ` Husnu Demir
2010-01-25 11:39 ` Jan Engelhardt
2010-01-25 11:49 ` Jozsef Kadlecsik
2010-01-25 11:57 ` Husnu Demir
2010-01-25 12:01 ` Husnu Demir
-- strict thread matches above, loose matches on Subject: below --
2012-09-13 14:19 Ipset Problem Lutfi ODUNCUOGLU
2012-09-13 14:53 ` Jozsef Kadlecsik
2012-09-13 20:12 ` hdemir
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=4B59E8F8.1060401@shorewall.net \
--to=teastep@shorewall.net \
--cc=hdemir@metu.edu.tr \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).