From: Joachim Wiberg <troglobit@gmail.com>
To: netdev@vger.kernel.org
Cc: David Ahern <dsahern@kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>,
Nikolay Aleksandrov <razor@blackwall.org>,
Joachim Wiberg <troglobit@gmail.com>
Subject: [PATCH iproute2-next v3 6/7] man: ip-link: mention bridge port's default mcast_flood state
Date: Wed, 9 Mar 2022 20:23:15 +0100 [thread overview]
Message-ID: <20220309192316.2918792-7-troglobit@gmail.com> (raw)
In-Reply-To: <20220309192316.2918792-1-troglobit@gmail.com>
Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
---
man/man8/ip-link.8.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man/man8/ip-link.8.in b/man/man8/ip-link.8.in
index c0e7f122..1237ff4c 100644
--- a/man/man8/ip-link.8.in
+++ b/man/man8/ip-link.8.in
@@ -2458,7 +2458,7 @@ this flag is on.
.BR mcast_flood " { " on " | " off " }"
- controls whether a given port will flood multicast traffic for which
- there is no MDB entry.
+ there is no MDB entry. By default this flag is on.
.BR mcast_to_unicast " { " on " | " off " }"
- controls whether a given port will replicate packets using unicast
--
2.25.1
next prev parent reply other threads:[~2022-03-09 19:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 19:23 [PATCH iproute2-next v3 0/7] bridge: support for controlling broadcast flooding per port Joachim Wiberg
2022-03-09 19:23 ` [PATCH iproute2-next v3 1/7] bridge: support for controlling flooding of broadcast " Joachim Wiberg
2022-03-09 19:23 ` [PATCH iproute2-next v3 2/7] man: bridge: document new bcast_flood flag for bridge ports Joachim Wiberg
2022-03-09 19:23 ` [PATCH iproute2-next v3 3/7] man: bridge: add missing closing " in bridge show mdb Joachim Wiberg
2022-03-09 19:23 ` [PATCH iproute2-next v3 4/7] ip: iplink_bridge_slave: support for broadcast flooding Joachim Wiberg
2022-03-09 19:23 ` [PATCH iproute2-next v3 5/7] man: ip-link: document new bcast_flood flag on bridge ports Joachim Wiberg
2022-03-09 19:23 ` Joachim Wiberg [this message]
2022-03-09 19:23 ` [PATCH iproute2-next v3 7/7] man: ip-link: whitespace fixes to odd line breaks mid sentence Joachim Wiberg
2022-03-10 9:01 ` [PATCH iproute2-next v3 0/7] bridge: support for controlling broadcast flooding per port Nikolay Aleksandrov
2022-03-12 16:10 ` patchwork-bot+netdevbpf
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=20220309192316.2918792-7-troglobit@gmail.com \
--to=troglobit@gmail.com \
--cc=dsahern@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.