From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>
Subject: Re: arptables and the generic xtables issues
Date: Thu, 16 Oct 2008 15:23:38 +0200 [thread overview]
Message-ID: <48F7405A.2050302@trash.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0810152151070.28060@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Wednesday 2008-10-15 21:43, Pablo Neira Ayuso wrote:
>> Currently, we have tagged quite a lot of targets and matches with
>> AF_UNSPEC as they are generic for the netfilter supported protocols.
>> This is fine if we only think of ebtables, iptables and ip6tables but
>> not for arptables, I doubt that all those target and matches can work
>> with arptables - even if we still need the userspace support, of course.
>>
>> I think that we should fix those, right?
>
> That would be a tremendous amount of work, given that arptables (and
> ebtables too) is not quite the same codebase as iptables anymore.
> Most of the iptables development just went by arp and ebtables due
> to the nature of all these semiforks.
>
> I think we should rather focus on a truly family-independent table
> in the very near future. In fact I have ideas floating around that,
> but am stuck with how I'd exactly funnel it into reviewable patch
> chunks.
I think we should finish the unification/resyncing efforts before
adding new features in this area. There's still *a lot* of old
cruft that could probably be removed.
next prev parent reply other threads:[~2008-10-16 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 1:43 arptables and the generic xtables issues Pablo Neira Ayuso
2008-10-16 2:00 ` Jan Engelhardt
2008-10-16 13:23 ` Patrick McHardy [this message]
2008-10-16 17:19 ` Jan Engelhardt
2008-10-16 11:55 ` Patrick McHardy
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=48F7405A.2050302@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.