netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>,
	Bart De Schuymer <bdschuym@pandora.be>
Cc: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>,
	Netfilter Development Mailing list
	<netfilter-devel@vger.kernel.org>
Subject: Re: Merging iptables-nftables into iptables
Date: Thu, 12 Dec 2013 11:15:58 +0200	[thread overview]
Message-ID: <52A97ECE.8020000@linux.intel.com> (raw)
In-Reply-To: <20131205215447.GA4367@localhost>

Hi Pablo and Bart,

> Regarding arptables, there's still one limitation that we have to
> resolve as it only allows EUI-64 addresses (which should be the most
> common case), the arptables kernel code seems to support variable
> length hardware addresses up to 128 bytes long IIRC. Tomasz has been
> working on that for a while.

Actually I have a question about that.
On INPUT or OUTPUT I guess we need to handle input device and output 
device, respectively.

What about FORWARD? Still input device? Afaik the output device is not 
know yet at that point, is it?

Thanks,

Tomasz

  reply	other threads:[~2013-12-12  9:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04 11:48 Merging iptables-nftables into iptables Pablo Neira Ayuso
2013-12-04 15:11 ` Arturo Borrero Gonzalez
2013-12-05  8:24   ` Pablo Neira Ayuso
2013-12-05 21:15     ` Bart De Schuymer
2013-12-05 21:54       ` Pablo Neira Ayuso
2013-12-12  9:15         ` Tomasz Bursztyka [this message]
2013-12-30 23:07 ` Pablo Neira Ayuso
2013-12-31  9:40   ` 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=52A97ECE.8020000@linux.intel.com \
    --to=tomasz.bursztyka@linux.intel.com \
    --cc=arturo.borrero.glez@gmail.com \
    --cc=bdschuym@pandora.be \
    --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).