In link local case, handle the fragmented packets that does not have L4 headers

[Divakar Dharanalakota]

To handle the link local packets, all link local ports are maintained as database in Vrouter. When a data packet arrives in fabric VRF we look up this lonk local port db to identify whether it needs to be subjected to flow processing. If not found, packet is given to Vhost.
Above logic is valid only if L4 packet is not fragmented and L4 header is present in packet. For fragmented packets, the above logic does not work.
-Divakar

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/6890
Committed: http://github.org/Juniper/contrail-vrouter/commit/16d8ec043724f980972fe8677cc162a0ba9fc2e0
Submitter: Zuul
Branch: master

commit 16d8ec043724f980972fe8677cc162a0ba9fc2e0
Author: Divakar <email address hidden>
Date: Mon Feb 2 02:00:34 2015 -0800

closes-bug:#1416268. If packet on fabric is fragmented packet, identify the transport header from fragment db, whether it belongs to Link local ports and subject it to flow 2)If packet needs to be transported without tunnels and higher than MTU , packets needs to be handed over to linux for segmenting/fragmenting 3)Add tunnel type for vxlan packets

Change-Id: Ibb9297144b72bc5530c9abeda3df884ab5a4efad

[Divakar Dharanalakota (ddivakar)]

The fix for this is committed into R2.1 by commit id aeac8a693ac8e0010aa70292b217271504c6e901