vxlan-gpe: packet drop due to incorrect lisp local eid

[Onong Tayeng]

Instead of the local VM's mac, the vhostuser interface's mac is programmed as lisp local eid in VPP. This causes VPP to drop outgoing packets effectively ensuring that no communication can happen between VMs.

Packet 2

00:10:00:620004: vhost-user-input
     VirtualEthernet0/0/0 queue 0
   virtio flags:
    SINGLE_DESC Single descriptor packet
   virtio_net_hdr first_desc_len 110
     flags 0x00 gso_type 0
     num_buff 0
00:10:00:620013: ethernet-input
  frame: flags 0x1, hw-if-index 4, sw-if-index 4
  IP4: fa:16:3e:f5:c3:e3 -> fa:16:3e:23:06:7a
00:10:00:620021: l2-input
  l2-input: sw_if_index 4 dst fa:16:3e:23:06:7a src fa:16:3e:f5:c3:e3
00:10:00:620027: l2-input-feat-arc
  IN-FEAT-ARC: head 1 feature_bitmap 500525 ethertype 800 sw_if_index 4, next_index 22
00:10:00:620041: acl-plugin-in-ip4-l2
  acl-plugin: lc_index: 1, sw_if_index 4, next index 1, action: 2, match: acl 3 rule 0 trace_bits 00000000
  pkt info 0000000000000000 0000000000000000 0000000000000000 d000000afc00000a 0004030100000008 0200ffff00000001
   lc_index 1 l3 ip4 10.0.0.252 -> 10.0.0.208 l4 lsb_of_sw_if_index 4 proto 1 l4_is_input 1 l4_slow_path 1 l4_flags 0x03 port 8 -> 0 tcp flags (invalid) 00 rsvd 0
00:10:00:620105: l2-input-feat-arc-end
  IN-FEAT-ARC: head 0 feature_bitmap 100525 ethertype 0 sw_if_index -1, next_index 17
00:10:00:620109: l2-input-acl
  INACL: sw_if_index 4, next_index 9, table 11, offset 1200
00:10:00:620117: l2-learn
  l2-learn: sw_if_index 4 dst fa:16:3e:23:06:7a src fa:16:3e:f5:c3:e3 bd_index 1
00:10:00:620126: l2-fwd
  l2-fwd: sw_if_index 4 dst fa:16:3e:23:06:7a src fa:16:3e:f5:c3:e3 bd_index 1 result [0xffffffffffffffff, -1] static age-not bvi filter learn-event learn-move
00:10:00:620134: l2-flood
  l2-flood: sw_if_index 4 dst fa:16:3e:23:06:7a src fa:16:3e:f5:c3:e3 bd_index 1
00:10:00:620137: l2-output
  l2-output: sw_if_index 3 dst fa:16:3e:23:06:7a src fa:16:3e:f5:c3:e3 data 08 00 45 00 00 54 5a 1c 40 00 40 01
00:10:00:620141: l2_lisp_gpe999-output
  l2_lisp_gpe999
  flags: N L E V I
  ver_res 22 res 62 next_protocol 35 iid 424698(67afa)
00:10:00:620149: l2_lisp_gpe999-tx
  L2-LISP-GPE-TX: load-balance 8
00:10:00:620152: l2-load-balance
  L2-load-balance: index 8
00:10:00:620157: lisp-cp-lookup-l2
  LISP-CP-LOOKUP: map-resolver: 0.0.0.0 destination eid [999] fa:16:3e:23:06:7a
00:10:00:620175: error-drop
  rx:VirtualEthernet0/0/0
00:10:00:620188: drop
  lisp-cp-lookup-l2: drop

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/747908

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/747908
Committed: https://git.openstack.org/cgit/x/networking-vpp/commit/?id=74c100a73c1c092a2888d83b012a9fbf872202f0
Submitter: Zuul
Branch: master

commit 74c100a73c1c092a2888d83b012a9fbf872202f0
Author: Onong Tayeng <email address hidden>
Date: Tue Aug 25 16:50:28 2020 +0530

    vxlan-gpe: packet drop due to incorrect lisp local eid

    Instead of the local VM's mac, the vhostuser interface's mac is
    programmed as lisp local eid in VPP. This causes VPP to drop outgoing
    packets effectively ensuring that no communication can happen between
    VMs across compute nodes.

    Change-Id: I786888793bb474802b0294f5b3fd73c2507ad147
    Closes-Bug: #1892766