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: Sat, 02 Oct 2010 21:35:23 +0100 [thread overview]
Message-ID: <4CA7978B.9020900@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1010022104571.23216@blackhole.kfki.hu>
OK, I quickly tested the new version with my previous test on the ssh
port and it all works now, though I found some other (minor) issues:
When I do 'make IP_NF_SET_MAX=xx IP_NF_SET_HASHSIZE=xx' and then do
'make install' (as root) both values I have given during my first 'make'
were completely disregarded.
If I do 'make IP_NF_SET_MAX=xx IP_NF_SET_HASHSIZE=xx' and 'make
IP_NF_SET_MAX=xx IP_NF_SET_HASHSIZE=xx install' I can see that at least
the default hash size has also been disregarded (built a set without
specifying --hashsize and when I executed 'ipset -L' the hashsize was
1024 and not the number I have given during make). I cannot check
whether IP_NF_SET_MAX has also been disregarded (don't know how to do it!).
Is this a known issue or have I done something wrong?
next prev parent reply other threads:[~2010-10-02 20:35 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 [this message]
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
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=4CA7978B.9020900@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