> Do you have a test case that demonstrates this? It appears to
> me that an MLDv2 general query doesn't execute that code (short circuited
> above) and an MLDv1 general query (what that code is handling) will
> have a timer expiring before switching back to MLDv2 mode (so it'll send
> a v1
Yan Zheng <[EMAIL PROTECTED]> wrote on 11/07/2005 06:46:20 AM:
> If the first query message receive after expiration is MLDv2 general
> query and MAF_GSQUERY flag is set. The report message only contains
> sources marked by last MLDv2 Multicast Address and Source Specific
> Queries . Although this
> Could you be more specific about what problem it will cause?
>
> Thanks,
>
> John
> --
> John W. Linville
> [EMAIL PROTECTED]
If the first query message receive after expiration is MLDv2 general
query and MAF_GSQUERY flag is set. The report message only contains
sources marked by last MLDv2 Mul
On Mon, Nov 07, 2005 at 10:13:34PM +0800, Yan Zheng wrote:
> MAF_GSQUERY flag may cause problem when MLDv1 compatibility mode expires.
Could you be more specific about what problem it will cause?
Thanks,
John
--
John W. Linville
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the lin
Hi.
MAF_GSQUERY flag may cause problem when MLDv1 compatibility mode expires.
Signed-off-by: Yan Zheng <[EMAIL PROTECTED]>
Index: net/ipv6/mcast.c
--- linux-2.6.14/net/ipv6/mcast.c 2005-11-05 09:09:47.0
