diff mbox series

[iproute2-next,7/7] bridge: mdb: Document the catchall MDB entries

Message ID 20230321130127.264822-8-idosch@nvidia.com (mailing list archive)
State Accepted
Commit be24eab05d664ff63d1216498e5f2e6986ccafc7
Delegated to: David Ahern
Headers show
Series bridge: mdb: Add VXLAN attributes support | expand

Checks

Context Check Description
netdev/tree_selection success Not a local patch

Commit Message

Ido Schimmel March 21, 2023, 1:01 p.m. UTC
Document the catchall MDB entries used to transmit IPv4 and IPv6
unregistered multicast packets.

In deployments where inter-subnet multicast forwarding is used, not all
the VTEPs in a tenant domain are members in all the broadcast domains.
It is therefore advantageous to transmit BULL (broadcast, unknown
unicast and link-local multicast) and unregistered IP multicast traffic
on different tunnels. If the same tunnel was used, a VTEP only
interested in IP multicast traffic would also pull all the BULL traffic
and drop it as it is not a member in the originating broadcast domain
[1].

[1] https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-irb-mcast#section-2.6

Signed-off-by: Ido Schimmel <idosch@nvidia.com>
---
 man/man8/bridge.8 | 6 ++++++
 1 file changed, 6 insertions(+)

Comments

Nikolay Aleksandrov March 23, 2023, 3:21 p.m. UTC | #1
On 21/03/2023 15:01, Ido Schimmel wrote:
> Document the catchall MDB entries used to transmit IPv4 and IPv6
> unregistered multicast packets.
> 
> In deployments where inter-subnet multicast forwarding is used, not all
> the VTEPs in a tenant domain are members in all the broadcast domains.
> It is therefore advantageous to transmit BULL (broadcast, unknown
> unicast and link-local multicast) and unregistered IP multicast traffic
> on different tunnels. If the same tunnel was used, a VTEP only
> interested in IP multicast traffic would also pull all the BULL traffic
> and drop it as it is not a member in the originating broadcast domain
> [1].
> 
> [1] https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-irb-mcast#section-2.6
> 
> Signed-off-by: Ido Schimmel <idosch@nvidia.com>
> ---
>  man/man8/bridge.8 | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/man/man8/bridge.8 b/man/man8/bridge.8
> index 9753ce9e92b4..4006ad23ea74 100644
> --- a/man/man8/bridge.8
> +++ b/man/man8/bridge.8
> @@ -1013,6 +1013,12 @@ device creation will be used.
>  device name of the outgoing interface for the VXLAN device to reach the remote
>  VXLAN tunnel endpoint.
>  
> +.in -8
> +The 0.0.0.0 and :: MDB entries are special catchall entries used to flood IPv4
> +and IPv6 unregistered multicast packets, respectively. Therefore, when these
> +entries are programmed, the catchall 00:00:00:00:00:00 FDB entry will only
> +flood broadcast, unknown unicast and link-local multicast.
> +
>  .in -8
>  .SS bridge mdb delete - delete a multicast group database entry
>  This command removes an existing mdb entry.

Reviewed-by: Nikolay Aleksandrov <razor@blackwall.org>
diff mbox series

Patch

diff --git a/man/man8/bridge.8 b/man/man8/bridge.8
index 9753ce9e92b4..4006ad23ea74 100644
--- a/man/man8/bridge.8
+++ b/man/man8/bridge.8
@@ -1013,6 +1013,12 @@  device creation will be used.
 device name of the outgoing interface for the VXLAN device to reach the remote
 VXLAN tunnel endpoint.
 
+.in -8
+The 0.0.0.0 and :: MDB entries are special catchall entries used to flood IPv4
+and IPv6 unregistered multicast packets, respectively. Therefore, when these
+entries are programmed, the catchall 00:00:00:00:00:00 FDB entry will only
+flood broadcast, unknown unicast and link-local multicast.
+
 .in -8
 .SS bridge mdb delete - delete a multicast group database entry
 This command removes an existing mdb entry.