From: Roman Gushchin <klamm@yandex-team.ru>
To: David Miller <davem@davemloft.net>,
"hannes@stressinduktion.org" <hannes@stressinduktion.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] net: sysctl for RA default route MTU
Date: Wed, 01 Apr 2015 12:58:50 +0300 [thread overview]
Message-ID: <68621427882330@webcorp01g.yandex-team.ru> (raw)
In-Reply-To: <20150331.164923.229749666073516444.davem@davemloft.net>
31.03.2015, 23:49, "David Miller" <davem@davemloft.net>:
> From: Hannes Frederic Sowa <hannes@stressinduktion.org>
> Date: Tue, 31 Mar 2015 22:35:48 +0200
>> Could you quickly comment on what you had in mind? I guess it is about
>> handling RA in user space on the end hosts and overwriting MTU during
>> insertion of the routes?
>
> Even after reading your email I have no idea why you can't just have
> RA provide a 1500 byte MTU, everything else uses the device's 9000
> MTU, problem solved?
Because the MTU (provided by RA) is assigned to the device.
Thanks,
Roman
next prev parent reply other threads:[~2015-04-01 9:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 18:03 [PATCH] " Roman Gushchin
2015-03-24 19:27 ` David Miller
2015-03-25 9:49 ` Roman Gushchin
2015-03-25 11:07 ` [PATCH v2] " Roman Gushchin
2015-03-25 12:34 ` Denis Kirjanov
2015-03-25 15:52 ` Hannes Frederic Sowa
[not found] ` <39171427301187@webcorp02f.yandex-team.ru>
2015-03-25 18:14 ` Hannes Frederic Sowa
2015-03-26 11:49 ` [PATCH v3] " Roman Gushchin
2015-03-26 14:49 ` Hannes Frederic Sowa
2015-03-29 19:42 ` David Miller
2015-03-30 12:30 ` Roman Gushchin
2015-03-31 20:05 ` David Miller
2015-03-31 20:35 ` Hannes Frederic Sowa
2015-03-31 20:49 ` David Miller
2015-04-01 9:58 ` Roman Gushchin [this message]
2015-04-01 17:55 ` David Miller
2015-04-01 19:27 ` Hannes Frederic Sowa
2015-04-02 18:08 ` Roman Gushchin
2015-04-07 15:58 ` Hannes Frederic Sowa
2015-04-08 19:03 ` Roman Gushchin
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=68621427882330@webcorp01g.yandex-team.ru \
--to=klamm@yandex-team.ru \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®