From: Vladimir Oltean <olteanv@gmail.com>
To: nikolay@cumulusnetworks.com, roopa@cumulusnetworks.com,
netdev@vger.kernel.org
Subject: What is the correct way to install an L2 multicast route into a bridge?
Date: Wed, 8 Jul 2020 12:04:54 +0300 [thread overview]
Message-ID: <20200708090454.zvb6o7jr2woirw3i@skbuf> (raw)
Hi,
I am confused after reading man/man8/bridge.8. I have a bridge br0 with
4 interfaces (eth0 -> eth3), and I would like to install a rule such
that the non-IP multicast address of 09:00:70:00:00:00 is only forwarded
towards 3 of those ports, instead of being flooded.
The manual says that 'bridge mdb' is only for IP multicast, and implies
that 'bridge fdb append' (NLM_F_APPEND) is only used by vxlan. So, what
is the correct user interface for what I am trying to do?
Thank you,
-Vladimir
next reply other threads:[~2020-07-08 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 9:04 Vladimir Oltean [this message]
2020-07-08 9:16 ` What is the correct way to install an L2 multicast route into a bridge? Nikolay Aleksandrov
2020-07-08 9:42 ` Vladimir Oltean
2020-07-08 11:07 ` Nikolay Aleksandrov
2020-07-08 11:17 ` Nikolay Aleksandrov
2020-07-08 12:55 ` Nikolay Aleksandrov
2020-07-08 13:10 ` Vladimir Oltean
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=20200708090454.zvb6o7jr2woirw3i@skbuf \
--to=olteanv@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
/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).