Fix next-protocol issue configured from Honeycomb 11/1511/2
authorHongjun Ni <hongjun.ni@intel.com>
Sun, 12 Jun 2016 10:45:25 +0000 (18:45 +0800)
committerHongjun Ni <hongjun.ni@intel.com>
Sun, 12 Jun 2016 03:02:32 +0000 (03:02 +0000)
PatchSet 2: rebuild.

Change-Id: I18ee050629129871b44271f92a1e63b661d55c05
Signed-off-by: Hongjun Ni <hongjun.ni@intel.com>
vpp/api/api.c

index 75e98fb..95301f4 100644 (file)
@@ -4557,7 +4557,7 @@ vl_api_vxlan_gpe_add_del_tunnel_t_handler
     }
     encap_fib_index = p[0];
 
-    protocol = ntohl(mp->protocol);
+    protocol = mp->protocol;
 
     /* Interpret decap_vrf_id as an opaque if sending to other-than-ip4-input */
     if (protocol == VXLAN_GPE_INPUT_NEXT_IP4_INPUT) {