Re: [ovs-dev] [PATCH ovn 0/2] Further restrict ARP/ND broadcast domain for E-W and S-N traffic.

On 11/4/20 8:54 AM, Numan Siddique wrote: > On Wed, Nov 4, 2020 at 3:44 AM Mark Michelson wrote: >> >> Aside from spelling "update" properly in the title of patch 1, this Oops, thanks for spotting this! >> looks good to me. >> >> Acked-by: Mark Michelson Thanks! > > Thanks Dumitru for fixing

Re: [ovs-dev] [PATCH ovn 0/2] Further restrict ARP/ND broadcast domain for E-W and S-N traffic.

On Wed, Nov 4, 2020 at 3:44 AM Mark Michelson wrote: > > Aside from spelling "update" properly in the title of patch 1, this > looks good to me. > > Acked-by: Mark Michelson Thanks Dumitru for fixing this issue and thanks Mark for the reviews. I applied this patch series to master by updating

Re: [ovs-dev] [PATCH ovn 0/2] Further restrict ARP/ND broadcast domain for E-W and S-N traffic.

Aside from spelling "update" properly in the title of patch 1, this looks good to me. Acked-by: Mark Michelson On 11/3/20 10:50 AM, Dumitru Ceara wrote: This series aims at further restricting ARP/ND broadcast domain for self originated packets. Until now those packets were always flooded on

[ovs-dev] [PATCH ovn 0/2] Further restrict ARP/ND broadcast domain for E-W and S-N traffic.

This series aims at further restricting ARP/ND broadcast domain for self originated packets. Until now those packets were always flooded on all ports of the switch. The first patch of the series is needed in order to remove dependency on self-originated GARPs to be sent through the network (OVS)