commit 79be2aaf30ff4df90354719fa25f82703ed3539f
Author: Divakar D <email address hidden>
Date: Mon Oct 24 12:28:13 2016 +0530
Disable the flow processing for Neighbour Advertisements
The neighbour request packets are typically Multicast packets and there
is no flow processing for these. When a neighbour request is converted
to neighbour advertisement, we continue to use the same packet buffer
and same packet flags for this advertisement too. This ends up in not
creating a flow for neighbour advertisement too as the original packet
is marked as multicast packet. But the fix we gave https://review.opencontrail.org/#/c/24973/ for bug: #1461882 for V6
resulted in creating new packet flags for advertisement and this is
resulting in flow being created. The flow processing is dropping the
response as the neighbour advertisement should have ideally come from
different interface.
We can fix this issue either by manipulating the source interface to
match the interface on which neighbour is falling so that flow
processing succeeds or by disabling the flow processing for
advertisements.
The fix now disables the flow processing for advertisements
Reviewed: https:/ /review. opencontrail. org/25213 github. org/Juniper/ contrail- vrouter/ commit/ 79be2aaf30ff4df 90354719fa25f82 703ed3539f
Committed: http://
Submitter: Zuul
Branch: R3.0.3.x
commit 79be2aaf30ff4df 90354719fa25f82 703ed3539f
Author: Divakar D <email address hidden>
Date: Mon Oct 24 12:28:13 2016 +0530
Disable the flow processing for Neighbour Advertisements
The neighbour request packets are typically Multicast packets and there /review. opencontrail. org/#/c/ 24973/ for bug: #1461882 for V6
is no flow processing for these. When a neighbour request is converted
to neighbour advertisement, we continue to use the same packet buffer
and same packet flags for this advertisement too. This ends up in not
creating a flow for neighbour advertisement too as the original packet
is marked as multicast packet. But the fix we gave
https:/
resulted in creating new packet flags for advertisement and this is
resulting in flow being created. The flow processing is dropping the
response as the neighbour advertisement should have ideally come from
different interface.
We can fix this issue either by manipulating the source interface to
match the interface on which neighbour is falling so that flow
processing succeeds or by disabling the flow processing for
advertisements.
The fix now disables the flow processing for advertisements
Change-Id: Ic91f0fb794c139 12e43d8c96c726b d80e559b7fb
closes-bug: #1635931