From: <marcmicalizzi@gmail.com>
To: <netfilter-devel@vger.kernel.org>
Subject: nftables flow offload possible mtu handling issue
Date: Fri, 17 May 2019 12:27:48 -0400 [thread overview]
Message-ID: <013801d50ccd$77ef0600$67cd1200$@gmail.com> (raw)
With flow offload between devices of differing mtus, there seems to be an
issue sending from through higher mtu to the lower mtu device.
Im currently on 4.20 from the linux-arm mcbin branch, as its all I can get
running on my specific embedded platform.
In my case I have
table ip nat {
chain POSTROUTING {
type nat hook postrouting priority 100; policy accept;
oifname "ppp0" ip saddr 192.168.10.0/24 snat to
xx.xxx.xx.xxx
}
}
table ip filter {
flowtable f1 {
hook ingress priority 0
devices = { eth0.1, ppp0 }
}
chain FORWARD {
type filter hook forward priority 0; policy accept;
ip protocol tcp flow offload @f1
counter
tcp flags syn tcp option maxseg size set rt mtu
}
}
ppp0 has an mtu of 1500.
Running a speedtest from a device connected to eth0.1, download seems to
always be fine, but if eth0.1 has an mtu higher than 1492, upload fails
completely most of the time. (Prior to flow offloading, eth0/eth0.1 has an
mtu of 9000, and this is the mtu I would prefer to have it running at.
An interesting observation, as well, is that with eth0.1 mtu at 9000, if
during the upload portion of a speed test I issue `ip link set ppp0 mtu
(1492/1500, whichever it currently is not)`, the upload will start working
for the remainder of the upload test.
This also manifests outside speedtest, but less predictably, with dropped
connections due to outgoing packet failures.
next reply other threads:[~2019-05-17 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 16:27 marcmicalizzi [this message]
2019-05-18 21:45 ` nftables flow offload possible mtu handling issue Florian Westphal
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='013801d50ccd$77ef0600$67cd1200$@gmail.com' \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.