commit 54ae2596f1149ef4ace527cf2f39d19897c3628b
Author: Divakar <email address hidden>
Date: Sat Feb 27 09:27:06 2016 +0530
Keeping ingres vif id in L2 header for post GRO processing
Currently the L2 header used for both L2 and L3 GRO processing is only
next hop id. Post GRO, the nexthop is retrieved from this id and packet
is subjected to this nexthop for further processing. The ingress
interface filled in the packet is nh_dev of this nexthop. This is
resulting in ingress interface as Tap interface though packet acttually ingressed
on Fabric interface. This can potentially lead to issues in the packet's
further processing as Tap interface is not the real ingress
interface.
As a fix, the ingress interface id is also pushed as L2 header.
Reviewed: https:/ /review. opencontrail. org/18614 github. org/Juniper/ contrail- vrouter/ commit/ 54ae2596f1149ef 4ace527cf2f39d1 9897c3628b
Committed: http://
Submitter: Zuul
Branch: R2.22.x
commit 54ae2596f1149ef 4ace527cf2f39d1 9897c3628b
Author: Divakar <email address hidden>
Date: Sat Feb 27 09:27:06 2016 +0530
Keeping ingres vif id in L2 header for post GRO processing
Currently the L2 header used for both L2 and L3 GRO processing is only
next hop id. Post GRO, the nexthop is retrieved from this id and packet
is subjected to this nexthop for further processing. The ingress
interface filled in the packet is nh_dev of this nexthop. This is
resulting in ingress interface as Tap interface though packet acttually ingressed
on Fabric interface. This can potentially lead to issues in the packet's
further processing as Tap interface is not the real ingress
interface.
As a fix, the ingress interface id is also pushed as L2 header.
Change-Id: I6fbe055fff7da4 c957fde29d132b5 6ea19bd2f3f
closes-bug: #1550632