Fix the compile issue for 3.13 kernels

Change-Id: I6101a469343c202b976c9e31ed7a1f5c8acb80fb
If DHCP is disabled in config, flood DHCP requests in the VN

Change-Id: I81f27a921b1e88ba55dbf0b5ae2f6de0ce501dbe
* Add a flag in route to trap GARP packets hitting that route

Change-Id: Ifd77b2456b91104fe8c2eed5e5e45397fb76453a
- Changes to support cross connect without scripts
  - agent alive/dead detected based on addition of pkt0 vif and removal of
    pkt0 interface from the system (OS)
  - on agent's death, all vhost interface and their corresponding physical
    interfaces are put on cross connect mode where the traffic will still
    pass through vrouter
  - from the time of reset till vhost gets added back again, traffic moves
    directly from physical interface to vhost
  - once vhost interface is added, traffic flows normally through vrouter

Change-Id: I7cacebc5432347e11fc15213edd22f372cf6c9ef
- Vlan tagged packets are handled different between 2.6 (Centos) kernel
and later kernels. To make handling uniform in all platforms, push the
vlan header in the packet for the later kernels

Change-Id: I06fe6bb06cd5ab483f88606a402f826510815cb5
- BUG:1337295- NULL terminate getopt_long option list

Change-Id: I50463864ef515d5706b0b27206d2583b83bbfca9
Merge "- BUG:1337295- NULL terminate getopt_long option list"
- Ensure that inner header checksums are correct on the wire when the outer
header is UDP (MPLSoUDP or VXLAN).

- Outer UDP header source port is now a hash of inner header 5-tuple.

Bug 1338326

Change-Id: I8e1519b562faef30523a297e42c2a4a64759e6f4
- interface notifier argument changed in 3.11 kernel. Add #ifdefs
to accommodate that change

Change-Id: Ieb1b0512c9531fe0e67a562c92f3c91d93c8d540
Merge "- Ensure that inner header checksums are correct on the wire when the outer header is UDP (MPLSoUDP or VXLAN)."
Make vrouter coexist with Linux bridge (and not coexist with OVS).

Bug 1338900

Change-Id: Ie2455a070acd03f55d0a920a4495fe2fded1ab74
BUG:1336717
Do trap + forward the packet when the packet arrives from an ECMP source
that was different from the destination of the forward flow

[ forward port into mainline ]

Change-Id: If9283fde17f4353cd483b0f5b87100e82a4c8fca
BUG 1340528

- For ICMP error packets, the flow key has to be the same as that of the
original payload. This is because, in a floating IP case, default security
group rules allow only outgoing packets originated by the VM and incoming
packets to VM that belong to the same security group. Packets originated
from the destination floating ip network does not belong to the same security
group and hence will be dropped if we use the outer IP header for forming the
flow key.

Another issue is with the NAT-ing. The ip header source ip and destination ip
+ transport header ports in the icmp error payload have to be NAT-ed back.

Change-Id: If5082cc5fb9d20175a71abac42d09ac27100bf55
Merge remote-tracking branch 'upstream/master'

Conflicts:
	dp-core/vr_interface.c