From: Captain Wiggum <captwiggum@gmail.com>
To: netdev@vger.kernel.org
Subject: IPv6 unexpectedly changes MTU on wrong interface
Date: Mon, 1 Apr 2019 15:48:37 -0600 [thread overview]
Message-ID: <CAB=W+o=Ar4sScW3tkn+bscMTC-XzWSqY7D5mm=XF=no-XXsb_A@mail.gmail.com> (raw)
This bug exists in the LTS kernels, but has been fixed in mainline.
My problem is I have no idea what to search for in git find the commit(s).
Hopefully someone recognizes this issue and can give some tips to find it.
Summary:
Three TAHI IPv6 test cases fail on this:
Two interface test: first interface used only for IPv4, and the second
only for IPv6.
The problem is with the IPv6 PMTU (RFC 1981).
When the kernel receives an ICMPv6 "packet to big" message,
it must update the source to destination path MTU with the new value
provided in the "packet to big" message.
The kernel always uses the first interface as the local end of the path,
instead of the interface where the issue occured.
Therefore when IPv6 goes to check the Path MTU on the second interface
when transmitting a packet, it is not getting the reduced MTU value.
--John Masinter
reply other threads:[~2019-04-01 21:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAB=W+o=Ar4sScW3tkn+bscMTC-XzWSqY7D5mm=XF=no-XXsb_A@mail.gmail.com' \
--to=captwiggum@gmail.com \
--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 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).