From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter@vger.kernel.org
Subject: Re: ipporthash, ipportiphash, ipportnethash problems
Date: Wed, 06 Oct 2010 15:23:41 +0100 [thread overview]
Message-ID: <4CAC866D.7060101@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1010041134130.28881@blackhole.kfki.hu>
>> So I should not use IP_NF_SET_HASHSIZE for the time being until it is fixed,
>> right?
>>
>
> Yes, because currently it's ignored. In this week I'm going to fix it in
> the git repository but won't release a new version just for this.
>
There is another issue I found when using ipmap sets: when I execute,
for example, "ipset -N port-map ipmap --from 10 --to 30000" and then add
an element "ipset -A port-map 20" the two statements are accepted
without any error given (they shouldn't be as the map defined is an IP
map, not a port map and the values submitted are numbers, not IP
addresses)!
When I issue "ipset -L port-map" I get:
Header: from: 0.0.0.10 to: 0.0.117.48
members:
0.0.0.20
Is this deliberate or a bug?
next prev parent reply other threads:[~2010-10-06 14:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 22:03 ipporthash, ipportiphash, ipportnethash problems Mr Dash Four
2010-10-01 7:18 ` Jozsef Kadlecsik
2010-10-01 11:22 ` Mr Dash Four
2010-10-01 21:05 ` Jozsef Kadlecsik
2010-10-02 10:36 ` Mr Dash Four
2010-10-02 19:21 ` Jozsef Kadlecsik
2010-10-02 20:08 ` Mr Dash Four
2010-10-02 20:40 ` Jan Engelhardt
2010-10-02 20:54 ` Mr Dash Four
2010-10-02 21:06 ` Jan Engelhardt
2010-10-03 18:57 ` Jozsef Kadlecsik
2010-10-03 22:02 ` Mr Dash Four
2010-10-02 20:35 ` Mr Dash Four
2010-10-03 19:13 ` Jozsef Kadlecsik
2010-10-03 22:04 ` Mr Dash Four
2010-10-04 9:36 ` Jozsef Kadlecsik
2010-10-06 14:23 ` Mr Dash Four [this message]
2010-10-06 14:37 ` Mike Wright
2010-10-06 15:26 ` Mr Dash Four
2010-10-06 19:57 ` 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=4CAC866D.7060101@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=kadlec@blackhole.kfki.hu \
--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