Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Post GRO, label in fmd can't be used to check whether the packet
was tunneled or not Once the packet is submitted for GRO, all datapath information is lost. Post GRO, only values that are saved in the packet are the vif and the nexthop. vif is a recent addition to the saved information that helped us to identify which interface the packet came from originally. Once the vif value was set properly, the logic that checked whether the packet should be trapped to agent or not based on the presence of label (basically fabric arp responses should be trapped or not), misbehaved since label information is not saved pre-GRO and hence not available in the metadata post GRO. For now, fix the specific logic by checking whether the egress vrf is different from the ingress vrf, which will be the case since physical interface vrf will not be the same as vm's vrf. Change-Id: Iba000889039bc8a5020fc11a462ba1b1a68ce1c8 Closes-BUG: #1551382 Do not reuse forwarding metadata post mirroring A mirror action needs its own forwarding metadata since the forwarding parameeters that are used for mirroring will be different from those that are used for packet forwarding. In this particular case, the vrf to which the packets are mirrored are different from the vrf to which packets need to be classified, and hence the packets were dropped in the flow module with no source route as the drop reason. Change-Id: I21930818a5cdec560818acb79f671ce29ac8bc85 Closes-BUG: #1552101
- Loading branch information