From: Daniel Borkmann <dborkman@redhat.com>
To: Simon Schneider <simon-schneider@gmx.net>
Cc: netdev@vger.kernel.org,
Hannes Frederic Sowa <hannes@stressinduktion.org>
Subject: Re: MLD maturity in kernel version 2.6.32.60
Date: Mon, 18 Nov 2013 13:23:54 +0100 [thread overview]
Message-ID: <528A06DA.6040302@redhat.com> (raw)
In-Reply-To: <trinity-825e48d2-0bab-4020-84f0-77800e55f25a-1384777048114@3capp-gmx-bs16>
On 11/18/2013 01:17 PM, Simon Schneider wrote:
>
> 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?
(cc'ing Hannes)
You might want to try 3.12 kernel, and if needed backport some of these:
http://www.spinics.net/lists/netdev/msg249262.html
> 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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-11-18 12:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 12:17 MLD maturity in kernel version 2.6.32.60 Simon Schneider
2013-11-18 12:23 ` Daniel Borkmann [this message]
2013-11-18 22:18 ` Hannes Frederic Sowa
2013-11-19 0:12 ` Daniel Borkmann
2013-11-19 6:11 ` Simon Schneider
2013-11-19 7:29 ` Daniel Borkmann
2013-12-06 7:40 ` Aw: " Simon Schneider
2013-12-06 13:53 ` Hannes Frederic Sowa
2013-11-21 4:04 ` Hannes Frederic Sowa
2013-11-21 10:16 ` Daniel Borkmann
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=528A06DA.6040302@redhat.com \
--to=dborkman@redhat.com \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
--cc=simon-schneider@gmx.net \
/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).