From: Stephen Hemminger <shemminger@vyatta.com>
To: Nick Carter <ncarter100@gmail.com>
Cc: Ed Swierk <eswierk@bigswitch.com>,
netdev@vger.kernel.org, David Lamparter <equinox@diac24.net>,
bridge@linux-foundation.org
Subject: Re: [RFC] bridge: allow passing link-local multicast
Date: Thu, 18 Aug 2011 08:10:19 -0700 [thread overview]
Message-ID: <20110818081019.4b9bb79e@nehalam.ftrdhcpuser.net> (raw)
In-Reply-To: <CAEJpZP0fOydMMbgquAud7dfwcO28BXAMzAwnMjSZO6TvEjxgpQ@mail.gmail.com>
On Thu, 18 Aug 2011 16:06:19 +0100
Nick Carter <ncarter100@gmail.com> wrote:
> Why can't we use the 802.1D specified STP group address to identify ?
> The existing code uses that address.
> I know you said on another thread that there are people using other addresses.
> Who are these people ?
> Are they following any standard ?
> What address / address range are they using ?
The group address can be reprogrammed, and it is settable on other
routing equipment. People do it to create spanning tree domains.
next prev parent reply other threads:[~2011-08-18 15:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAF5U64C+WgQhfJL3zfVnvzE7p=G61humQCObHGUxAvY2-MGAFQ@mail.gmail.com>
2011-08-12 22:37 ` [PATCH] bridge: mask forwarding of IEEE 802 local multicast groups Ed Swierk
2011-08-12 22:45 ` Stephen Hemminger
2011-08-13 5:43 ` Ed Swierk
2011-08-15 22:05 ` [RFC] bridge: allow passing link-local multicast Stephen Hemminger
2011-08-18 15:06 ` Nick Carter
2011-08-18 15:10 ` Stephen Hemminger [this message]
2011-08-18 15:52 ` Nick Carter
2011-08-18 16:39 ` Stephen Hemminger
2011-08-19 2:27 ` David Lamparter
2011-08-19 20:58 ` [RFC] bridge: add netfilter hook for forwarding 802.1D group addresses Stephen Hemminger
2011-08-19 22:18 ` Christian Benvenuti (benve)
2011-08-19 22:24 ` Stephen Hemminger
2011-08-20 15:31 ` Bart De Schuymer
2011-08-22 13:59 ` David Lamparter
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=20110818081019.4b9bb79e@nehalam.ftrdhcpuser.net \
--to=shemminger@vyatta.com \
--cc=bridge@linux-foundation.org \
--cc=equinox@diac24.net \
--cc=eswierk@bigswitch.com \
--cc=ncarter100@gmail.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).