On 5/19/23 20:24, Vladislav Odintsov wrote:
> Finally, I’ve managed to find the correct place for this change.
> I’ve submitted a patch series here: [1]
>
> Thanks Dumitru, your help was very valuable!
> I’d be glad if you can find some time to review this series. :)
>
Hi Vladislav,
I'll try
Finally, I’ve managed to find the correct place for this change.
I’ve submitted a patch series here: [1]
Thanks Dumitru, your help was very valuable!
I’d be glad if you can find some time to review this series. :)
1:
Thanks Dumitru for the response.
I’ve looked through this code and even tried to implement similar logic for
vtep lport, but realized, that vtep mcast traffic is a bit different from
localnet port.
mcast traffic originated in normal vif port in localnet-attached lswitch has
two cases:
- if
On 5/16/23 21:48, Vladislav Odintsov wrote:
> Hi Numan, Dumitru, Ilya, Mark,
>
Hi Vladislav,
> if someone can help, I’ll be very grateful.
>
> Thanks in advance.
>
>> On 15 May 2023, at 15:06, Vladislav Odintsov wrote:
>>
>> Hi, I’m implementing neighbour learning on the chassis-redirect
Hi Numan, Dumitru, Ilya, Mark,
if someone can help, I’ll be very grateful.
Thanks in advance.
> On 15 May 2023, at 15:06, Vladislav Odintsov wrote:
>
> Hi,
>
> I’m implementing neighbour learning on the chassis-redirect ports for
> traffic coming from lport of vtep type and have some
Hi,
I’m implementing neighbour learning on the chassis-redirect ports for
traffic coming from lport of vtep type and have some misunderstanding of
how MC_FLOOD action works with traffic coming from localnet lports.
Imagine, we’ve got lswitch with 4 LSPs:
- vtep lport (type vtep)
- lrp
