[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53973D42.4010209@enst-bretagne.fr>
Date: Tue, 10 Jun 2014 19:15:46 +0200
From: Florent Fourcot <florent.fourcot@...t-bretagne.fr>
To: Milos Vyletel <milos.vyletel@...il.com>, davem@...emloft.net,
amwang@...hat.com, netdev@...r.kernel.org
CC: Oliver Neukum <oliver@...kum.org>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
James Morris <jmorris@...ei.org>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Patrick McHardy <kaber@...sh.net>,
stephen hemminger <stephen@...workplumber.org>,
Pravin B Shelar <pshelar@...ira.com>,
Nicolas Dichtel <nicolas.dichtel@...nd.com>,
Mike Rapoport <mike.rapoport@...ellosystems.com>,
Daniel Borkmann <dborkman@...hat.com>,
Or Gerlitz <ogerlitz@...lanox.com>,
Tom Herbert <therbert@...gle.com>,
Hannes Frederic Sowa <hannes@...essinduktion.org>,
Eric Dumazet <edumazet@...gle.com>,
Paul Durrant <Paul.Durrant@...rix.com>,
"open list:USB CDC ETHERNET..." <linux-usb@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [patch net-next 3/5] ipv6: consider net.ipv6.conf.all sysctls
when making decisions
Hello,
>
> IN6_DEV_MAXCONF
> IN6_DEV_HOPLIMIT
> IN6_DEV_MTU
I'm a little bit surprise to set the MTU as the maximum of all/dev
value. Since the default for "all" is IPV6_MIN_MTU, it is probably
harmless, but it could be a little bit surprising for administrators.
> IN6_DEV_USE_TEMPADDR
For this one, the default is zero, except for point-to-point and
loopback, with -1. I didn't see any difference between 0 and -1 in the
current kernel code, but if I missed something, it could be a little
problem.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists