Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Martin Gröger" <mgroeger1@web.de>
To: Florian Westphal <fw@strlen.de>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
	netfilter@vger.kernel.org, bernhard.thaler@wvnet.at
Subject: Re: nftables: bridge filter with queue to userspace
Date: Fri, 30 Oct 2015 08:16:21 +0100	[thread overview]
Message-ID: <56331945.1080804@web.de> (raw)
In-Reply-To: <20151029222303.GF18062@breakpoint.cc>


Am 29.10.2015 23:23, schrieb Florian Westphal:
> Pablo Neira Ayuso <pablo@netfilter.org> wrote:
>
> [ CC Bernhard ]
>
>> On Thu, Oct 29, 2015 at 10:23:44PM +0100, Martin Gröger wrote:
>>> I'm trying to build a transparent filter with application level filtering.
>>> First experiment with ip and output hook and queue to userspace was
>>> successful. Then I changed to bridge filtering with forward hook. With
>>> counter action I see that the packets match the rule, but the queue to the
>>> usersapce doesn't work.
>>>
>>> Am I right, that this fuction should work?
> nfqueue backend only works with NFPROTO_IPV4 and _IPV6 at the moment,
> i.e. nft ip and nft ip6, or via bridge_netfilter hack (which 'pushes'
> packets though ipv4/ipv6 netfilter hooks).
Ok, this explains why my experiment with ip work, but not the one with 
bridge family.

>
>> Florian told me he will come up sooner or later with native queue
>> support for nft (ie. no bridge_netfilter required anymore).
> Argh.  I'm a moron and forgot about this.
How does a native (indepent on bridge) queue support should work ?
>
> I still have the q&d hack that makes it work but no reroute (re-bridge,
> cough) support, just dump-to-userspace.
As far as I understand this would be sufficient for my usecase, since I 
want simply to inspect the packets and then decide to accept or drop them.

>
> Bernhard, did you have time to work on this?
>
> If not, I think I can make time available soon since the other work
> (nft bridge conntrack, nf netns hook stuff) is delayed at the moment
> anyways.
>
Would be great, if you can help me!


  reply	other threads:[~2015-10-30  7:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29 21:23 nftables: bridge filter with queue to userspace Martin Gröger
2015-10-29 22:11 ` Pablo Neira Ayuso
2015-10-29 22:23   ` Florian Westphal
2015-10-30  7:16     ` Martin Gröger [this message]
2015-10-30 13:38       ` Florian Westphal
2015-10-30 20:21         ` Martin Gröger
2015-10-30 21:27           ` Florian Westphal
2015-10-31  9:02             ` Martin Gröger

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=56331945.1080804@web.de \
    --to=mgroeger1@web.de \
    --cc=bernhard.thaler@wvnet.at \
    --cc=fw@strlen.de \
    --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