From: Stephen Hemminger <stephen@networkplumber.org>
To: roucaries.bastien@gmail.com
Cc: netdev@vger.kernel.org, sergei.shtylyov@cogentembedded.com,
"Bastien Roucariès" <rouca@debian.org>
Subject: Re: [PATCH 1/6] Better documentation of mcast_to_unicast option
Date: Mon, 20 Apr 2020 09:43:51 -0700 [thread overview]
Message-ID: <20200420094351.0fadab71@hermes.lan> (raw)
In-Reply-To: <20200412235038.377692-2-rouca@debian.org>
On Mon, 13 Apr 2020 01:50:33 +0200
roucaries.bastien@gmail.com wrote:
> +.BR mcast_to_unicast
> +works on top of the multicast snooping feature of
> +the bridge. Which means unicast copies are only delivered to hosts which
> +are interested in it and signalized this via IGMP/MLD reports
> +previously.
> +
> +This feature is intended for interface types which have a more reliable
> +and/or efficient way to deliver unicast packets than broadcast ones
> +(e.g. WiFi).
> +
> +However, it should only be enabled on interfaces where no IGMPv2/MLDv1
> +report suppression takes place. IGMP/MLD report suppression issue is usually
> +overcome by the network daemon (supplicant) enabling AP isolation and
> +by that separating all STAs.
> +
> +Delivery of STA-to-STA IP mulitcast is made possible again by
> +enabling and utilizing the bridge hairpin mode, which considers the
> +incoming port as a potential outgoing port, too (see
> +.B hairpin
> +option).
It probably doesn't make difference but seems like inconsistent usage
of Bold and BoldRoman macros
.B mcast_to_unicast
works on top of the multicast snooping feature of
.BR hairpin "option)."
next prev parent reply other threads:[~2020-04-20 16:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 13:48 Improve documentation of bridge Bastien Roucariès
2020-04-05 13:48 ` [PATCH iproute2 1/6] Better documentation of mcast_to_unicast option Bastien Roucariès
2020-04-05 13:48 ` [PATCH iproute2 2/6] Improve hairpin mode description Bastien Roucariès
2020-04-05 13:48 ` [PATCH iproute2 3/6] Document BPDU filter option Bastien Roucariès
2020-04-05 13:48 ` [PATCH iproute2 4/6] Better documentation of BDPU guard Bastien Roucariès
2020-04-05 13:48 ` [PATCH iproute2 5/6] Document root_block option Bastien Roucariès
2020-04-06 9:54 ` Sergei Shtylyov
2020-04-05 13:48 ` [PATCH iproute2 6/6] State of bridge STP port are now case insensitive Bastien Roucariès
2020-04-12 23:50 ` [V2][PATH 0/6] iproute improve documentation of bridge roucaries.bastien
2020-04-12 23:50 ` [PATCH 1/6] Better documentation of mcast_to_unicast option roucaries.bastien
2020-04-20 16:43 ` Stephen Hemminger [this message]
2020-04-12 23:50 ` [PATCH 2/6] Improve hairpin mode description roucaries.bastien
2020-04-12 23:50 ` [PATCH 3/6] Document BPDU filter option roucaries.bastien
2020-04-12 23:50 ` [PATCH 4/6] Better documentation of BDPU guard roucaries.bastien
2020-04-13 9:28 ` Sergei Shtylyov
2020-04-12 23:50 ` [PATCH 5/6] Document root_block option roucaries.bastien
2020-04-12 23:50 ` [PATCH 6/6] State of bridge STP port are now case insensitive roucaries.bastien
2020-04-20 16:51 ` [V2][PATH 0/6] iproute improve documentation of bridge Stephen Hemminger
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=20200420094351.0fadab71@hermes.lan \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=rouca@debian.org \
--cc=roucaries.bastien@gmail.com \
--cc=sergei.shtylyov@cogentembedded.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).