From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "stéphane bryant" <stephane.ml.bryant@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: queuing to userspace for the bridge family, using nftables
Date: Thu, 16 Oct 2014 10:54:49 +0200 [thread overview]
Message-ID: <20141016085449.GA8884@salvia> (raw)
In-Reply-To: <5432D0D2.5050905@gmail.com>
On Mon, Oct 06, 2014 at 07:26:42PM +0200, stéphane bryant wrote:
> Hello,
>
> We are currently working on a project which may need the use of nftables
> to queue AF_BRIDGE packets to the userspace and back. Apparently this
> is already supported in the nftables code itself, but not in the
> bridge netfilter code (the corresponding nf_afinfo is missing, at least).
>
> I would like to know if there are plans to support this? If yes, in what
> timeframe? If no, would you be interested if we were to submit a patch
> to that effect?
Please, submit patches.
> Also, what should be included in the payload send to userspace?
> (starting from the 802.3 LLC/protocol header, or also including up to
> the MAC addresses ?)
I think you have to include everything relevant from layer 2 upward. I
think it would be good if we indicate userspace that NFQA_PAYLOAD
starts from the mac header some way. So the same process can handle
packets coming from bridge and the ip layer.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-10-16 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 17:26 queuing to userspace for the bridge family, using nftables stéphane bryant
2014-10-16 8:54 ` Pablo Neira Ayuso [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-11 7:00 stéphane bryant
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=20141016085449.GA8884@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=stephane.ml.bryant@gmail.com \
/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).