From: Jiri Pirko <jpirko@redhat.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Patrick McHardy <kaber@trash.net>,
netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org
Subject: Re: [question] ipt_CLUSTERIP and address length
Date: Thu, 25 Feb 2010 13:56:32 +0100 [thread overview]
Message-ID: <20100225125631.GF2667@psychotron.lab.eng.brq.redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.01.1002251347580.11377@obet.zrqbmnf.qr>
Thu, Feb 25, 2010 at 01:54:50PM CET, jengelh@medozas.de wrote:
>On Thursday 2010-02-25 13:18, Pablo Neira Ayuso wrote:
>>>>
>>>> I want to ask if there is any particular reason for ipt_CLUSTERIP to support
>>>> only address length of 6 (ETH_ALEN)? It seems to me reasonable for this to work
>>>> even with another types of network hw with different addr_len.
>>>
>>> None that I'm aware of, but the length is also used in the ABI,
>>> so you presently can't supply larger addresses.
>>
>>Not directly related to this but I wanted to discuss this time ago. Now
>>that we have xt_CLUSTER I think that we can deprecate ipt_CLUSTERIP.
>
>xt_CLUSTER - where in the tree would that be?
I was trying to find it too. I guess it stands out of it (at least net-next).
next prev parent reply other threads:[~2010-02-25 12:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 10:12 [question] ipt_CLUSTERIP and address length Jiri Pirko
2010-02-25 10:23 ` Patrick McHardy
2010-02-25 11:04 ` Jan Engelhardt
2010-02-25 11:37 ` Jiri Pirko
2010-02-25 12:05 ` Jan Engelhardt
2010-02-25 12:13 ` Jiri Pirko
2010-02-25 12:18 ` Pablo Neira Ayuso
2010-02-25 12:23 ` Patrick McHardy
2010-02-25 12:38 ` Pablo Neira Ayuso
2010-02-25 12:54 ` Jan Engelhardt
2010-02-25 12:56 ` Jiri Pirko [this message]
2010-02-25 13:03 ` Pablo Neira Ayuso
2010-02-25 12:57 ` Jan Engelhardt
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=20100225125631.GF2667@psychotron.lab.eng.brq.redhat.com \
--to=jpirko@redhat.com \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@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).