From: Mr Dash Four <mr.dash.four@googlemail.com>
To: netfilter@vger.kernel.org
Subject: ipporthash, ipportiphash, ipportnethash problems
Date: Thu, 30 Sep 2010 23:03:07 +0100 [thread overview]
Message-ID: <4CA5091B.1090200@googlemail.com> (raw)
I am not able to get *any* matches when I have the following combinations:
1. ipporthash: x.x.x.x,y [src,dst] or [dst,src] (i.e. source IP address
and destination port and vice versa);
2. ipportiphash: x.x.x.x,y,z.z.z.z [src,dst,dst] or [dst,src,src] (i.e.
source IP address, destination port and destination IP address and vice
versa);
3. ipportnethash x.x.x.x,y,z.z.z.z/c [src,dst,dst] or [dst,src,src]
(i.e. source IP address, destination port and destination subnet and
vice versa);
When I split up the above sets like:
For case 1: match-set single-set src match-set single-port dst (and vice
versa with src and dst reversed) - all in one line - i.e. creating two
separate sets containing the appropriate src IP address and and dst
ports respectively;
For case 2: match-set single-set src match-set double-set dst,dst (and
vice versa with src and dst reversed) - all in one line - i.e. creating
two separate sets containing the appropriate src IP address and another
set containing the destination IP addresses *and* ports respectively;
For case 3: match-set single-set src match-set double-net-set dst,dst
(and vice versa with src and dst reversed) - all in one line - i.e.
creating two separate sets containing the appropriate src IP address and
another set containing the destination IP subnet addresses *and* ports
respectively;
I was able to get a match! This leads me to believe that either xtables
has a bug and can't handle mixed src,dst designations in the same set,
or, I am doing something wrong. Which is it?
next reply other threads:[~2010-09-30 22:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 22:03 Mr Dash Four [this message]
2010-10-01 7:18 ` ipporthash, ipportiphash, ipportnethash problems 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
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=4CA5091B.1090200@googlemail.com \
--to=mr.dash.four@googlemail.com \
--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