From: David Miller <davem@davemloft.net>
To: dlstevens@us.ibm.com
Cc: shemminger@linux-foundation.org, herbert@gondor.hengli.com.au,
netdev@vger.kernel.org, netdev-owner@vger.kernel.org
Subject: Re: [Bug 18212] New: force_igmp_version ignored when a IGMPv3 query received (+1 line patch)
Date: Tue, 14 Sep 2010 14:24:18 -0700 (PDT) [thread overview]
Message-ID: <20100914.142418.149835514.davem@davemloft.net> (raw)
In-Reply-To: <OF1A09F28B.15E7E7BC-ON8825779E.00741A65-8825779E.007540E3@us.ibm.com>
From: David Stevens <dlstevens@us.ibm.com>
Date: Tue, 14 Sep 2010 14:20:40 -0700
> netdev-owner@vger.kernel.org wrote on 09/10/2010 09:19:36 AM:
>
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=18212
>>
>> Summary: force_igmp_version ignored when a IGMPv3 query
>> received (+1 line patch)
>
>>
>> Created an attachment (id=29512)
>> --> (https://bugzilla.kernel.org/attachment.cgi?id=29512)
>> fix force_igmp_version v3 query problem
>>
>> After all these years, it turns out that the
>> /proc/sys/net/ipv4/conf/*/force_igmp_version
>> parameter isn't fully implemented.
>
> I don't think it's correct to send a v2 response to a v3
> query in any case. The question for answering v3 queries was
> whether to answer them with a v3 report, or to drop them and
> ignore them when force_igmp_version==2. I chose to respond,
> but I can see the case for dropping it too. I don't agree that
> a v3 query should be answered with a v2 resport (a real v2
> host would drop it).
Do you have an alternative patch to suggest?
next prev parent reply other threads:[~2010-09-14 21:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 16:19 Fw: [Bug 18212] New: force_igmp_version ignored when a IGMPv3 query received (+1 line patch) Stephen Hemminger
2010-09-13 19:51 ` David Miller
2010-09-14 21:20 ` Fw: " David Stevens
2010-09-14 21:24 ` David Miller [this message]
2010-09-15 2:02 ` Herbert Xu
2010-09-15 9:33 ` David Stevens
2010-09-15 9:05 ` David Stevens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100914.142418.149835514.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dlstevens@us.ibm.com \
--cc=herbert@gondor.hengli.com.au \
--cc=netdev-owner@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).