From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: netdev@vger.kernel.org
Subject: Re: IGMP joins come from the wrong SA/interface
Date: Wed, 5 Feb 2014 00:34:59 +0100 [thread overview]
Message-ID: <20140204233459.GA30008@sesse.net> (raw)
In-Reply-To: <20140204233206.GA16198@order.stressinduktion.org>
On Wed, Feb 05, 2014 at 12:32:06AM +0100, Hannes Frederic Sowa wrote:
>> 2. I didn't properly understand that the multicast flag on the route did not
>> matter (although it really should!).
> Hmm, maybe that would be good but I am not sure if that could break existing
> setups if we change that now. It seems it is handled like that since Alexey
> implemented it in that way.
Thinking of it, traditionally (and by “traditionally” I mean in IOS and the
likes, not Linux) the multicast routing table has been used to look up the
rendezvous point (RP), to know where to send the PIM join. (The leads to the
confusing situation where the multicast routing table contains unicast
addresses.) In this situation, we have IGMP and not PIM, which means we do
not know anything about the RP, so maybe it's the right decision after all.
/* Steinar */
--
Homepage: http://www.sesse.net/
prev parent reply other threads:[~2014-02-04 23:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 19:11 IGMP joins come from the wrong SA/interface Steinar H. Gunderson
2014-01-18 19:17 ` Steinar H. Gunderson
2014-01-19 18:18 ` Hannes Frederic Sowa
2014-01-20 18:40 ` Steinar H. Gunderson
2014-01-30 10:47 ` Steinar H. Gunderson
2014-01-30 14:17 ` Hannes Frederic Sowa
2014-01-30 20:31 ` Steinar H. Gunderson
2014-01-30 18:08 ` Flavio Leitner
2014-01-30 18:12 ` Steinar H. Gunderson
2014-01-30 22:44 ` Hannes Frederic Sowa
2014-01-31 8:51 ` Julian Anastasov
2014-01-31 11:32 ` Hannes Frederic Sowa
2014-02-04 22:08 ` Steinar H. Gunderson
2014-02-04 23:32 ` Hannes Frederic Sowa
2014-02-04 23:34 ` Steinar H. Gunderson [this message]
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=20140204233459.GA30008@sesse.net \
--to=sgunderson@bigfoot.com \
--cc=netdev@vger.kernel.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).