Comment 18 for bug 1570180

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/19515
Committed: http://github.org/Juniper/contrail-vrouter/commit/67cdf45909b8415dd58a797e24719794f602b2ec
Submitter: Zuul
Branch: R2.22.x

commit 67cdf45909b8415dd58a797e24719794f602b2ec
Author: Divakar <email address hidden>
Date: Thu Apr 14 14:34:33 2016 +0530

Treat ARP requestsas VM's requests if VRF is different when compared to VIF's VRF

This issue is valid only for unicast ARP request packets. As multicast ARP
request packets are always handled in Multicast Composite nexthop and as
they are never subjected to GRO, this issue is not observed for
multicast ARP packets.
When an unicast ARP request is received on Fabric interface it is treated as ARP
reqest for VM if there is a label attached to it. Due to the changes in
GRO, post GRO, the label is not going to be present in fmd. So ARP
packets are treated as if they are meant for fabric network. This is
resulting in unicast ARP requests never being answered.

As a fix, if the VRF of fmd is different from VIF's VRF, these packets
are treated as VM's ARP packets.

Change-Id: I013b83c38642697c81e32460be936154e42a067e
closes-bug: #1570180