[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTingTdmhyJhENb9AYDjUT7m_-yQflw5-gJqIA9iw@mail.gmail.com>
Date: Mon, 3 May 2010 23:19:22 -0700
From: enh <enh@...gle.com>
To: David Miller <davem@...emloft.net>
Cc: brian.haley@...com, netdev@...r.kernel.org
Subject: Re: linux kernel's IPV6_MULTICAST_HOPS default is 64; should be 1?
On Mon, May 3, 2010 at 23:05, David Miller <davem@...emloft.net> wrote:
> From: Brian Haley <brian.haley@...com>
> Date: Mon, 03 May 2010 22:16:39 -0400
>
>> It looks like a bug to me, feel free to send along a patch :)
>
> Is it? The quoted text is only about setting the value and what
> effect setting -1 or whatever has.
>
> For getting the value, the behavior described sounds just fine.
>
> The default for a socket is whatever the kernel-wide default is.
for the *unicast* hops, a part of the RFC i didn't quote says:
If the [IPV6_UNICAST_HOPS] option is not set, the
system selects a default value.
but for the *multicast* hops, which is what i'm talking about, this
part of the quoted text seems pretty definitive:
If IPV6_MULTICAST_HOPS is not set, the default is 1
(same as IPv4 today)
this is what my test shows isn't true of linux; linux reuses its
unicast default instead.
--
Elliott Hughes - http://who/enh - http://jessies.org/~enh/
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists