|
Dave,
As it is, it doesn't hurt anything if you set it to "47"-- it'll use IGMPv1 if it's
set to "1", IGMPv2 if it's set to "2" and IGMPv3 (default) for all other values. It may
look odd in "sysctl -a" output, but it'll behave reasonably.
I can add new handler functions used only by this that restrict the values
(unless there's an easier way using some existing method I don't know about),
if you think it's worth it, but it won't actually cause any problem if it's set to any
value out of range.
+-DLS
Sent by: netdev-bounce@xxxxxxxxxxx
To: David Stevens/Beaverton/IBM@IBMUS
cc: netdev@xxxxxxxxxxx
Subject: Re: sysctl variable to force IGMP version [PATCH]
On Tue, 27 Jan 2004 14:13:41 -0700
David Stevens <dlstevens@xxxxxxxxxx> wrote:
> Below is a patch that allows forcing of the IGMP version. The primary
> use would be with an IGMP-snooping switch that doesn't grok IGMPv3
> packet formats and when there are no IGMPv2 or IGMPv1 multicast
> routers on the network. By forcing the IGMP reports to version 2 (or
> version 1, for really old switches), Linux would send reports that the
> switch can understand for multicast forwarding to the port.
Perhaps some sanity to prevent values other than 1 or 2 from being
set?
|