Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: ѽ҉ᶬḳ℠ <vtol@gmx.net>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: [nftables] packet (filtering) flow NIC vs. PPPoE?
Date: Tue, 29 Sep 2020 17:06:22 +0200	[thread overview]
Message-ID: <20200929150622.GA30270@salvia> (raw)
In-Reply-To: <dd201d62-d014-e9e3-254b-f7644bc759d7@gmx.net>

On Mon, Sep 28, 2020 at 09:35:00PM +0000, ѽ҉ᶬḳ℠ wrote:
> Whilst testing NFTables's flow offload on a node with a PPPoE subscriber
> line it turned out that the flow offload happens with the NIC netdev and not
> (as I expected) the virtual PPPoE netdev.
> 
> Just for reference this being the NFT config (eth2 being the NIC)
> 
> flowtable fte    {
>   hook ingress priority -100
>   devices = { eth2 }
>   counter
> }

Could you describe your testbed?

> ip protocol { 6, 17 } flow add @fte;
> ip6 nexthdr { 6, 17 } flow add @fte;

You can consolidate this rule with:

  meta l4proto { tcp, udp } flow add @fte;

You might also want to use the existing protocol definitions, instead
of numeric protocols to make your ruleset more readable.

> Why would the packet filtering have to take place on the PPPoE netdev but
> the flowatable happens with the NIC instead?

What would you like to achieve with the flowtable?

  parent reply	other threads:[~2020-09-29 15:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28 21:35 [nftables] packet (filtering) flow NIC vs. PPPoE? ѽ҉ᶬḳ℠
2020-09-29 11:23 ` ѽ҉ᶬḳ℠
2020-09-29 15:06 ` Pablo Neira Ayuso [this message]
2020-09-29 16:08   ` ѽ҉ᶬḳ℠

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=20200929150622.GA30270@salvia \
    --to=pablo@netfilter.org \
    --cc=netfilter@vger.kernel.org \
    --cc=vtol@gmx.net \
    /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