From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Jiri Pirko <jpirko@redhat.com>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netfilter@vger.kernel.org
Subject: Re: [question] ipt_CLUSTERIP and address length
Date: Thu, 25 Feb 2010 13:23:33 +0100 [thread overview]
Message-ID: <4B866BC5.7030800@trash.net> (raw)
In-Reply-To: <4B866A7F.7070205@netfilter.org>
Pablo Neira Ayuso wrote:
> Patrick McHardy wrote:
>> Jiri Pirko wrote:
>>> Hi all.
>>>
>>> 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.
If xt_cluster supports everything ipt_CLUSTERIP does, thats fine
with me.
> With regards to this issue, it seems arptables only support EUI-48 (6
> bytes) for ethernet addresses, so xt_CLUSTER would inherit the same
> problem but the point would be to fix arptables (not sure if possible
> now without breaking ABI or adding some versioning like iptables).
arptables currently supports up to 16 byte long addresses. Increasing
this is difficult since the addresses are embedded in struct arpt_arp.
next prev parent reply other threads:[~2010-02-25 12:23 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 [this message]
2010-02-25 12:38 ` Pablo Neira Ayuso
2010-02-25 12:54 ` Jan Engelhardt
2010-02-25 12:56 ` Jiri Pirko
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=4B866BC5.7030800@trash.net \
--to=kaber@trash.net \
--cc=coreteam@netfilter.org \
--cc=jpirko@redhat.com \
--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).