netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: marcmicalizzi@gmail.com
Cc: netfilter-devel@vger.kernel.org
Subject: Re: nftables flow offload possible mtu handling issue
Date: Sat, 18 May 2019 23:45:00 +0200	[thread overview]
Message-ID: <20190518214500.u6mf3oelw47i6nbi@breakpoint.cc> (raw)
In-Reply-To: <013801d50ccd$77ef0600$67cd1200$@gmail.com>

marcmicalizzi@gmail.com <marcmicalizzi@gmail.com> wrote:
> With flow offload between devices of differing mtus, there seems to be an
> issue sending from through higher mtu to the lower mtu device.
> I’m currently on 4.20 from the linux-arm mcbin branch, as it’s all I can get
> running on my specific embedded platform.

Current assumptions:
1. Flow offload can't deal with GRO skbs when MTU of oif is smaller,
   as it bypasses the code in ip output that deals with this

2. flow offload expr should never offload connections that have
   active helper and/or seqadj extension.


  reply	other threads:[~2019-05-18 21:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-17 16:27 nftables flow offload possible mtu handling issue marcmicalizzi
2019-05-18 21:45 ` Florian Westphal [this message]
2019-05-21  1:44 ` Florian Westphal

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=20190518214500.u6mf3oelw47i6nbi@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=marcmicalizzi@gmail.com \
    --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).