SYMC: Packets with size 1473-1479, 2953-2959 getting dropped by vrouter

[Varun Lodaya]

With vrouter 2.01-44, packets with sizes 1473-1479, 2953-2959 are getting dropped.

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/11230
Submitter: Anand H. Krishnan (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/11231
Submitter: Anand H. Krishnan (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/11231
Committed: http://github.org/Juniper/contrail-vrouter/commit/6f2edd76d32348cf02a9f1c4b4bc0927532358f2
Submitter: Zuul
Branch: R2.0

commit 6f2edd76d32348cf02a9f1c4b4bc0927532358f2
Author: Anand H. Krishnan <email address hidden>
Date: Wed Jun 3 16:41:39 2015 +0530

Pull a transport header only if one is present

When packets arrive from a vm/fabric, we try to pull all data till
the first 8 bytes of a transport header into the first buffer so
that linear access to data is possible (keys to flow is what we
look for in the transport header). We do this operation
without checking whether the packet is a fragment or not and such
an unconditional attempt at pull can result in pull failures for
fragments whose data length is less that 8.

Hence, pull only for packets that have a valid transport header and
that has a trapsort protocol we recognize.

Change-Id: Iaf8ec480bef045c774630a7c0cc9afbc867a6062
Closes-BUG: #1460218

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/11254
Submitter: Anand H. Krishnan (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/11255
Submitter: Anand H. Krishnan (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/11255
Committed: http://github.org/Juniper/contrail-vrouter/commit/00169d499d575e8c750d2c9d7f8182cdd11f85d1
Submitter: Zuul
Branch: R2.20

commit 00169d499d575e8c750d2c9d7f8182cdd11f85d1
Author: Anand H. Krishnan <email address hidden>
Date: Wed Jun 3 16:41:39 2015 +0530

Pull a transport header only if one is present

When packets arrive from a vm/fabric, we try to pull all data till
the first 8 bytes of a transport header into the first buffer so
that linear access to data is possible (keys to flow is what we
look for in the transport header). We do this operation
without checking whether the packet is a fragment or not and such
an unconditional attempt at pull can result in pull failures for
fragments whose data length is less that 8.

Hence, pull only for packets that have a valid transport header and
that has a trapsort protocol we recognize.

Change-Id: Iaf8ec480bef045c774630a7c0cc9afbc867a6062
Closes-BUG: #1460218

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/11230
Committed: http://github.org/Juniper/contrail-vrouter/commit/3b719332ca0210bc28ea5337c43ca46fc5efa5c2
Submitter: Zuul
Branch: master

commit 3b719332ca0210bc28ea5337c43ca46fc5efa5c2
Author: Anand H. Krishnan <email address hidden>
Date: Wed Jun 3 16:41:39 2015 +0530

Pull a transport header only if one is present

When packets arrive from a vm/fabric, we try to pull all data till
the first 8 bytes of a transport header into the first buffer so
that linear access to data is possible (keys to flow is what we
look for in the transport header). We do this operation
without checking whether the packet is a fragment or not and such
an unconditional attempt at pull can result in pull failures for
fragments whose data length is less that 8.

Hence, pull only for packets that have a valid transport header and
that has a trapsort protocol we recognize.

Change-Id: Iaf8ec480bef045c774630a7c0cc9afbc867a6062
Closes-BUG: #1460218

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/11254
Committed: http://github.org/Juniper/contrail-vrouter/commit/672beadc047c88d769951c5a4a73bb17488bed92
Submitter: Zuul
Branch: R2.1

commit 672beadc047c88d769951c5a4a73bb17488bed92
Author: Anand H. Krishnan <email address hidden>
Date: Wed Jun 3 16:41:39 2015 +0530

Pull a transport header only if one is present

When packets arrive from a vm/fabric, we try to pull all data till
the first 8 bytes of a transport header into the first buffer so
that linear access to data is possible (keys to flow is what we
look for in the transport header). We do this operation
without checking whether the packet is a fragment or not and such
an unconditional attempt at pull can result in pull failures for
fragments whose data length is less that 8.

Hence, pull only for packets that have a valid transport header and
that has a trapsort protocol we recognize.

Change-Id: Iaf8ec480bef045c774630a7c0cc9afbc867a6062
Closes-BUG: #1460218