commit a06f19d60761287728dba554fe57e91da205861a
Author: Anand H. Krishnan <email address hidden>
Date: Wed Mar 4 19:19:00 2015 +0530
vrf for packets sent to agent via encap nexthop should come from metadata
and not from ingress interface
Till now, packets that were sent to agent via an encap nexthop, had the vrf
in the agent header set to the ingress interface vrf. The vrf value in all
cases have to be the vrf to which the packet has been classified to.
Bug fix for arp behavior: If an arp request ingressed from fabric interface
and if the proxy bit was set in the route, but the stitching information was
not present, vrouter used to proxy with the vhost mac. This behavior is wrong.
vrouter should proxy only if the destination is hosted by it or if the
destination is not hosted and it is a TSN or if the request was meant for a
host in the cp port.
Reviewed: https:/ /review. opencontrail. org/8055 github. org/Juniper/ contrail- vrouter/ commit/ a06f19d60761287 728dba554fe57e9 1da205861a
Committed: http://
Submitter: Zuul
Branch: R2.1
commit a06f19d60761287 728dba554fe57e9 1da205861a
Author: Anand H. Krishnan <email address hidden>
Date: Wed Mar 4 19:19:00 2015 +0530
vrf for packets sent to agent via encap nexthop should come from metadata
and not from ingress interface
Till now, packets that were sent to agent via an encap nexthop, had the vrf
in the agent header set to the ingress interface vrf. The vrf value in all
cases have to be the vrf to which the packet has been classified to.
Bug fix for arp behavior: If an arp request ingressed from fabric interface
and if the proxy bit was set in the route, but the stitching information was
not present, vrouter used to proxy with the vhost mac. This behavior is wrong.
vrouter should proxy only if the destination is hosted by it or if the
destination is not hosted and it is a TSN or if the request was meant for a
host in the cp port.
Closes BUG: #1428135
Change-Id: Ibe543c743a0783 4a87e1512ac305f 1e0f32d5d30