David,
my words may have been poorly chosen. Last thing I want is to break things...
What I meant to say is that this changes the behavior of conf.all.*
sysctls from no-op to be part of decision along with interface
specific ones. Default settings still work the same way unless
conf.all.* was man
From: Milos Vyletel
Date: Tue, 10 Jun 2014 13:49:35 -0400
> On Tue, Jun 10, 2014 at 1:13 PM, Stephen Hemminger
> wrote:
>> On Tue, 10 Jun 2014 12:19:11 -0400
>> Milos Vyletel wrote:
>>
>>> As it is right now net.ipv6.conf.all.* are mostly ignored and instead
>>> we're only making decisions base
On Tue, Jun 10, 2014 at 1:13 PM, Stephen Hemminger
wrote:
> On Tue, 10 Jun 2014 12:19:11 -0400
> Milos Vyletel wrote:
>
>> As it is right now net.ipv6.conf.all.* are mostly ignored and instead
>> we're only making decisions based on interface specific settings. These
>> settings are coppied from
> 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.
>
>> I
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_TEMP
On Tue, 10 Jun 2014 12:19:11 -0400
Milos Vyletel wrote:
> As it is right now net.ipv6.conf.all.* are mostly ignored and instead
> we're only making decisions based on interface specific settings. These
> settings are coppied from net.ipv6.conf.default and changing either all
> or default settings
