[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <18810a42-b9cb-ce27-431d-310c903af3d3@blackwall.org>
Date: Thu, 23 Mar 2023 17:19:28 +0200
From: Nikolay Aleksandrov <razor@...ckwall.org>
To: Ido Schimmel <idosch@...dia.com>, netdev@...r.kernel.org
Cc: dsahern@...il.com, stephen@...workplumber.org, petrm@...dia.com,
mlxsw@...dia.com
Subject: Re: [PATCH iproute2-next 4/7] bridge: mdb: Add destination VNI
support
On 21/03/2023 15:01, Ido Schimmel wrote:
> In a similar fashion to VXLAN FDB entries, allow user space to program
> and view the destination VNI of VXLAN MDB entries. Specifically, add
> support for the 'MDBE_ATTR_VNI' and 'MDBA_MDB_EATTR_VNI' attributes in
> request and response messages, respectively.
>
> This is useful when ingress replication (IR) is used and the destination
> VXLAN tunnel endpoint (VTEP) is not a member of the source broadcast
> domain (BD). In this case, the ingress VTEP should transmit the packet
> using the VNI of the Supplementary Broadcast Domain (SBD) in which all
> the VTEPs are member of [1].
>
> Example:
>
> # bridge mdb add dev vxlan0 port vxlan0 grp 239.1.1.1 permanent dst 198.51.100.1 vni 1111
>
> $ bridge -d -s mdb show
> dev vxlan0 port vxlan0 grp 239.1.1.1 permanent filter_mode exclude proto static dst 198.51.100.1 vni 1111 0.00
>
> $ bridge -d -s -j -p mdb show
> [ {
> "mdb": [ {
> "index": 15,
> "dev": "vxlan0",
> "port": "vxlan0",
> "grp": "239.1.1.1",
> "state": "permanent",
> "filter_mode": "exclude",
> "protocol": "static",
> "flags": [ ],
> "dst": "198.51.100.1",
> "vni": 1111,
> "timer": " 0.00"
> } ],
> "router": {}
> } ]
>
> [1] https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-irb-mcast#section-3.2.2
>
> Signed-off-by: Ido Schimmel <idosch@...dia.com>
> ---
> bridge/mdb.c | 34 ++++++++++++++++++++++++++++++++--
> man/man8/bridge.8 | 10 +++++++++-
> 2 files changed, 41 insertions(+), 3 deletions(-)
>
Reviewed-by: Nikolay Aleksandrov <razor@...ckwall.org>
Powered by blists - more mailing lists