netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft] src: Support netdev egress hook
Date: Wed, 27 Oct 2021 15:29:06 +0200	[thread overview]
Message-ID: <YXlUIuoRaI8WmbZT@salvia> (raw)
In-Reply-To: <20211027121442.GA20375@wunner.de>

On Wed, Oct 27, 2021 at 02:14:42PM +0200, Lukas Wunner wrote:
> On Wed, Oct 27, 2021 at 12:17:15PM +0200, Pablo Neira Ayuso wrote:
> > Hi Lukas,
> > 
> > This is the rebase I'm using here locally for testing, let me know if
> > you have more pending updates on your side.
> 
> I'm using the attached two patches.  The first one moves Python tests
> dup.t and fwd.t to the netdev directory, the second one adds nft egress
> support.
> 
> Phil and Florian noted back in January that the payload dumps should
> contain "oiftype" instead of "iiftype".  That's the only remaining
> issue not yet addressed in the attached patches:
> 
> https://lore.kernel.org/all/20210125133405.GR19605@breakpoint.cc/

See:
https://patchwork.ozlabs.org/project/netfilter-devel/patch/20211025134329.1030333-1-pablo@netfilter.org/

to generalize the iftype.

I still have to post a patch to update libnftnl, then update all
dumps to refer to iftype instead of iiftype.

> The difference between the patch you've posted here and the attached ones
> are primarily more extensive docs.  Also, the following two issues are
> not present in my version:
> 
> 
> > +All packets leaving the system are processed by this hook. It is invoked after
> > +layer 3 protocol handlers and after *tc* egress. It can be used for late
>                                  ^^^^^
> 				 before
> 
> > --- a/tests/py/inet/ah.t
> > +++ b/tests/py/inet/ah.t
> > @@ -1,10 +1,12 @@
> >  :input;type filter hook input priority 0
> >  :ingress;type filter hook ingress device lo priority 0
> > +:egress;type filter hook ingress device lo priority 0
>                             ^^^^^^^
> 			    egress

I'll apply these two patches if you are fine with their state.

I'd just would like to have this in the tree for easier testing,
I have to switch over several local branches here, one less makes it
slightly easier for me. And to include this in the next release.

Thanks.

  reply	other threads:[~2021-10-27 13:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27 10:17 [PATCH nft] src: Support netdev egress hook Pablo Neira Ayuso
2021-10-27 12:14 ` Lukas Wunner
2021-10-27 13:29   ` Pablo Neira Ayuso [this message]
2021-10-27 22:13     ` Lukas Wunner
2021-10-27 22:52       ` Pablo Neira Ayuso
2021-10-28  7:10         ` Lukas Wunner
2021-10-28  0:04   ` Pablo Neira Ayuso
  -- strict thread matches above, loose matches on Subject: below --
2020-03-11 12:20 Lukas Wunner

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=YXlUIuoRaI8WmbZT@salvia \
    --to=pablo@netfilter.org \
    --cc=lukas@wunner.de \
    --cc=netfilter-devel@vger.kernel.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).