netdev - MLD maturity in kernel version 2.6.32.60

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-next>] [day] [month] [year] [list]

Message-ID: <trinity-825e48d2-0bab-4020-84f0-77800e55f25a-1384777048114@3capp-gmx-bs16>
Date:	Mon, 18 Nov 2013 13:17:28 +0100 (CET)
From:	"Simon Schneider" <simon-schneider@....net>
To:	netdev@...r.kernel.org
Subject: MLD maturity in kernel version 2.6.32.60

Hi,
in a development project, we started evaluating MLD functionality.

Our development is based on kernel version 2.6.32.60.

We noticed some pretty basic issues:

- With force_mld_version set to 0 (we expect "MLDv2 with MLDv1 fallback"), we saw only MLDv2 messages, the fallback to MLDv1 didn't seem to work, when we sent MLDv1 messages to the unit.
- With force_mld_version set to 1 (we expect "MLDv1 only mode"), we also saw MLDv2 messages being generated.

Can someone give a general statement about the MLD implementation maturity in kernel 2.6.32.60? Are there known bugs that would explain the above observations?

We need to see whether it makes sense to put further effort in investigating/fixing any MLD related issue we see.

If this is the wrong list to ask this kind of question, please point me to the correct one.

Thanks in advance,
best regards, Simon Schneider

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