From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Netfilter Core Team <netfilter-devel@vger.kernel.org>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH 0/3] ipset: change 'iface' part in hash:net,iface set
Date: Fri, 06 Jul 2012 23:25:43 +0100 [thread overview]
Message-ID: <4FF765E7.6020809@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1207062319130.16055@blackhole.kfki.hu>
>> Explain the above comment please?
>>
>
> Are you deliberately deaf to the arguments?
>
My hearing is still quite sharp, thank you. As for the "arguments" bit -
as far as I understand it (well, hoping, at least anyway), this is a
discussion, and nobody's "arguing".
> You want a choice to be introduced which lead to confusion - I'm repeating
> it countless times and you just ignore it.
How am I ignoring it? I asked you before and I am asking you again to
explain what that "confusion" is? It is quite clear to me what the
meaning of "in" and "out" is (again, if it is not made clear in the
various man pages, I would certainly appreciate any suggestions you - or
anyone else following this - might have). Again, if there is something
"confusing" in that meaning, then I'd like to know.
To reiterate once again - 'in' is for matches of incoming interfaces
only and should only be used for that particular purpose (it is one
reason why I am dead against your idea for this to be used "everywhere"
- to answer your other query below). Similar with 'out', but for
outgoing interfaces.
I don't know how much more clearer that could be, to be honest, but if
you have something on your mind, I am certainly all eyes/ears!
> In order to prevent such
> confusions, I offered that let "in/out" be alias to "src/dst": accepted as
> input everywhere but printed/saved with hash:net,iface only. You point
> blank refused it.
That is correct, and I also remember asking the question to whom do you
think that solution would be "easier"? You declined to answer that
particular query. It certainly won't be for the end user, that's for sure!
As for your suggestion above, I'll repeat what I've already posted - of
course I'll refuse it, because it is completely nonsensical. Do you not
think that referring to a destination IP address, for example, as "out"
IP address isn't confusing in the slightest? I mean, really Jozsef, you
could do better than that!
> Then come up with a better solution than the submitted
> one.
>
I will, if you let me know what is wrong, in your view, with the one I
submitted yesterday.
next prev parent reply other threads:[~2012-07-06 22:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 22:34 [PATCH 0/3] ipset: change 'iface' part in hash:net,iface set Mr Dash Four
2012-07-05 22:34 ` [PATCH 1/3] iptables: " Mr Dash Four
2012-07-05 22:34 ` [PATCH 2/3] ipset: " Mr Dash Four
2012-07-05 22:34 ` [PATCH 3/3] " Mr Dash Four
2012-07-06 8:35 ` [PATCH 0/3] " Jozsef Kadlecsik
2012-07-06 19:05 ` Mr Dash Four
2012-07-06 19:11 ` Jan Engelhardt
2012-07-06 19:21 ` Mr Dash Four
2012-07-06 19:44 ` Mr Dash Four
2012-07-06 19:47 ` Jozsef Kadlecsik
2012-07-06 20:19 ` Mr Dash Four
2012-07-06 20:39 ` Jozsef Kadlecsik
2012-07-06 21:04 ` Mr Dash Four
[not found] ` <CAHo-OowHXH9f526QQc4Ln5_P_Osdm1Q_RrBkw83hSGj=oES5ww@mail.gmail.com>
2012-07-06 20:41 ` Mr Dash Four
2012-07-06 20:49 ` Jozsef Kadlecsik
2012-07-06 21:04 ` Mr Dash Four
2012-07-06 21:39 ` Jozsef Kadlecsik
2012-07-06 22:25 ` Mr Dash Four [this message]
2012-07-07 14:53 ` Jozsef Kadlecsik
2012-07-07 16:23 ` Jozsef Kadlecsik
2012-07-08 13:03 ` Mr Dash Four
2012-07-08 18:55 ` Jozsef Kadlecsik
2012-07-08 19:03 ` Mr Dash Four
2012-07-08 19:07 ` Jozsef Kadlecsik
2012-07-08 19:11 ` Mr Dash Four
2012-07-08 20:30 ` Jozsef Kadlecsik
2012-07-08 22:10 ` Mr Dash Four
2012-07-08 22:20 ` Jozsef Kadlecsik
2012-07-08 22:25 ` Mr Dash Four
2012-07-08 22:55 ` Jozsef Kadlecsik
2012-07-09 20:19 ` Mr Dash Four
2012-07-09 22:05 ` Mr Dash Four
2012-07-08 13:03 ` Mr Dash Four
[not found] ` <CAHo-Ooya+1H939TqppUcY+pwprOH34zi-jHtnsN+g522aJ3ctw@mail.gmail.com>
2012-07-08 19:43 ` Mr Dash Four
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=4FF765E7.6020809@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).