Hi All,
I am working on VPP 17.07 and using ubuntu 14.04. I have two VMs say VM1
and VM2. I am running VPP on VM1 and interface between VM1 and VM2 is DPDK
type.
*Configuration*
vpp# set int state GigabitEthernet0/a/0 up
vpp#
vpp# create sub-interface GigabitEthernet0/a/0 500 dot1q 500 exact-match
GigabitEthernet0/a/0.500
vpp#
vpp# set int ip address GigabitEthernet0/a/0.500 5.5.5.1/24
vpp# set interface state GigabitEthernet0/a/0.500 up
vpp# show int addr
GigabitEthernet0/10/0 (up):
GigabitEthernet0/9/0 (up):
GigabitEthernet0/a/0 (up):
GigabitEthernet0/a/0.500 (up):
5.5.5.1/24
local0 (dn):
Tagged packets received on VPP are dropped as l3 mac mismatch. Enabling
trace is showing all packets received with incorrect hardware address.
*Trace*
00:13:14:020654: dpdk-input
GigabitEthernet0/a/0 rx queue 0
buffer 0xe487: current data 0, length 64, free-list 0, clone-count 0,
totlen-nifb 0, trace 0x4
PKT MBUF: port 1, nb_segs 1, pkt_len 64
buf_len 2176, data_len 64, ol_flags 0x0, data_off 128, phys_addr
0x7514ac40
packet_type 0x0
0x0000: 00:00:00:00:00:00 -> 00:00:00:00:00:00
00:13:14:020708: ethernet-input
0x0000: 00:00:00:00:00:00 -> 00:00:00:00:00:00
00:13:14:020730: error-drop
ethernet-input: l3 mac mismatch
If i ping from VPP, VM2 is responding with ARP reply. Is there any known
issue with tagged packets for DPDK interfaces across VMs? Any pointers
would be appreciated.
However there are no issues with base interface on same setup. I am not
sure whether tagged packets are corrupted or not on dpdk-input.
Regards,
Balaji
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
