From: David Ahern <dsahern@gmail.com>
To: Stefano Brivio <sbrivio@redhat.com>,
"David S . Miller" <davem@davemloft.net>
Cc: "Wei Wang" <weiwan@google.com>,
"Hideaki YOSHIFUJI" <yoshfuji@linux-ipv6.org>,
"Maciej Żenczykowski" <maze@google.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net] ipv6: Reflect MTU changes on PMTU of exceptions for MTU-less routes
Date: Fri, 2 Mar 2018 15:39:03 -0700 [thread overview]
Message-ID: <84593e49-357b-818c-79c5-d265d8c32b03@gmail.com> (raw)
In-Reply-To: <81bfe26bed31319d765a4ebfe86705a49c0a39d5.1520003901.git.sbrivio@redhat.com>
On 3/2/18 8:36 AM, Stefano Brivio wrote:
> Currently, administrative MTU changes on a given netdevice are
> not reflected on route exceptions for MTU-less routes, with a
> set PMTU value, for that device:
>
> # ip -6 route get 3000::b
> 3000::b from :: dev vti_a proto kernel src 3000::a metric 256 pref medium
> # ping6 -c 1 -q -s10000 3000::b > /dev/null
> # ip netns exec a ip -6 route get 3000::b
> 3000::b from :: dev vti_a src 3000::a metric 0
> cache expires 571sec mtu 4926 pref medium
> # ip link set dev vti_a mtu 3000
> # ip -6 route get 3000::b
> 3000::b from :: dev vti_a src 3000::a metric 0
> cache expires 571sec mtu 4926 pref medium
> # ip link set dev vti_a mtu 9000
> # ip -6 route get 3000::b
> 3000::b from :: dev vti_a src 3000::a metric 0
> cache expires 571sec mtu 4926 pref medium
Addresses in the 2001:db8: range should be used for commit messages.
And please codify the above expectation as a test under
tools/testing/selftests/net
next prev parent reply other threads:[~2018-03-02 22:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 22:47 [PATCH net v2] ipv6: Reflect MTU changes on PMTU of exceptions for MTU-less routes Stefano Brivio
2018-03-02 18:54 ` [PATCH net] " Maciej Żenczykowski
2018-03-03 11:21 ` Stefano Brivio
2018-03-02 22:39 ` David Ahern [this message]
2018-03-03 11:22 ` Stefano Brivio
2018-03-04 23:12 ` Stefano Brivio
2018-03-05 1:11 ` David Ahern
2018-03-05 12:29 ` Stefano Brivio
2018-03-05 14:14 ` David Miller
2018-03-05 15:27 ` David Ahern
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=84593e49-357b-818c-79c5-d265d8c32b03@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=sbrivio@redhat.com \
--cc=weiwan@google.com \
--cc=yoshfuji@linux-ipv6.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).