From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753116AbbDAJ65 (ORCPT ); Wed, 1 Apr 2015 05:58:57 -0400 Received: from forward-corp1f.mail.yandex.net ([95.108.130.40]:46357 "EHLO forward-corp1f.mail.yandex.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752880AbbDAJ6y (ORCPT ); Wed, 1 Apr 2015 05:58:54 -0400 From: Roman Gushchin To: David Miller , "hannes@stressinduktion.org" Cc: "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" In-Reply-To: <20150331.164923.229749666073516444.davem@davemloft.net> References: <1427718657-21674-1-git-send-email-klamm@yandex-team.ru> <20150331.160538.1808487957641759931.davem@davemloft.net> <1427834148.979686.247747037.29964C1B@webmail.messagingengine.com> <20150331.164923.229749666073516444.davem@davemloft.net> Subject: Re: [PATCH v3] net: sysctl for RA default route MTU MIME-Version: 1.0 Message-Id: <68621427882330@webcorp01g.yandex-team.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Wed, 01 Apr 2015 12:58:50 +0300 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 31.03.2015, 23:49, "David Miller" : > From: Hannes Frederic Sowa > 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