From: Andrew Lunn <andrew@lunn.ch>
To: Julian Labus <julian@freifunk-rtk.de>
Cc: netdev@vger.kernel.org, mschiffer@universe-factory.net
Subject: Re: stmmac: zero udp checksum
Date: Mon, 5 Apr 2021 15:27:29 +0200 [thread overview]
Message-ID: <YGsQQUHPpuEGIRoh@lunn.ch> (raw)
In-Reply-To: <cfc1ede9-4a1c-1a62-bdeb-d1e54c27f2e7@freifunk-rtk.de>
On Mon, Apr 05, 2021 at 02:53:15PM +0200, Julian Labus wrote:
> Hi all,
>
> in our community mesh network we recently discovered that a TP-Link Archer
> C2600 device is unable to receive IPv6 UDP packets with a zero checksum when
> RX checksum offloading is enabled. The device uses ipq806x-gmac-dwmac for
> its ethernet ports.
>
> According to https://tools.ietf.org/html/rfc2460#section-8.1 this sounds
> like correct behavior as it says a UDP checksum must not be zero for IPv6
> packets. But this definition was relaxed in
> https://tools.ietf.org/html/rfc6935#section-5 to allow zero checksums in
> tunneling protocols like VXLAN where we discovered the problem.
>
> Can the behavior of the stmmac driver be changed to meet RFC6935 or would it
> be possible to make the (RX) Checksum Offloading Engine configurable via a
> device tree property to disable it in environments were it causes problems?
Hi Julian
I don't know the stmmac driver at all...
Have you played around with ethtool -k/-K? Can use this to turn off
hardware checksums?
I doubt a DT property would be accepted. What you probably want to do
is react on the NETDEV notifiers for when an upper interface is
changed. If a VXLAN interface is added, turn off hardware checksums.
Andrew
next prev parent reply other threads:[~2021-04-05 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 12:53 stmmac: zero udp checksum Julian Labus
2021-04-05 13:27 ` Andrew Lunn [this message]
2021-04-05 16:11 ` Julian Labus
2021-04-05 16:42 ` Andrew Lunn
2021-04-05 19:30 ` Julian Labus
2021-04-05 23:03 ` Jakub Kicinski
2021-05-20 12:18 ` Julian Labus
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=YGsQQUHPpuEGIRoh@lunn.ch \
--to=andrew@lunn.ch \
--cc=julian@freifunk-rtk.de \
--cc=mschiffer@universe-factory.net \
--cc=netdev@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.