netdev - Re: Premature timeout for MLDv1 Host compatibility mode?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <OFA8EDA0BC.A9D42E39-ON85257A4E.004ECE32-85257A4E.004F3FC7@us.ibm.com>
Date:	Thu, 2 Aug 2012 10:25:38 -0400
From:	David Stevens <dlstevens@...ibm.com>
To:	Dragos Ilie <dragos.ilie@...il.com>
Cc:	netdev@...r.kernel.org, netdev-owner@...r.kernel.org
Subject: Re: Premature timeout for MLDv1 Host compatibility mode?

netdev-owner@...r.kernel.org wrote on 08/02/2012 10:03:24 AM:

> > The QQIC would come from v2 queries prior to the v1 query that
> > triggered us to switch to v1. But, see below.
> 
> How about the scenario where you have only MLDv1 queriers? There will
> be no prior v2 query

        Yes, this is why I suggested initializing it to the
default of 125. If we actually saw v2 queries with different
intervals, we'd adjust longer or shorter, but use the default
only when we had no queries to update it.

                                                +-DLS

--
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