Hello all.

I am using VPP 19.04 with DPDK 19.02.
When I start a pcap trace on physical or tap interfaces, pcap trace status 
reports it as 'local0'.

vpp# pcap rx trace on max 500 intfc tap0 file subif-rx.pcap
pcap rx capture on...
vpp# pcap rx trace status
max is 500 for interface local0 to file /tmp/subif-rx.pcap
pcap rx capture is on: 0 of 500 pkts...

vpp# pcap tx trace on max 500 intfc tap0 file subif-tx.pcap
pcap tx capture on...
vpp# pcap tx trace status
max is 500 for interface local0 to file /tmp/subif-tx.pcap
pcap tx capture is on: 0 of 500 pkts...

vpp# pcap rx trace status
max is 500 for interface local0 to file /tmp/subif-rx.pcap
pcap rx capture is on: 1 of 500 pkts...
vpp# pcap tx trace status
max is 500 for interface local0 to file /tmp/subif-tx.pcap
pcap tx capture is on: 2 of 500 pkts...

Additionally, a single ICMP ping which resulted in a single packet in each 
direction through that tap interface had two identical frames in the tx 
direction.
# tshark -nn -r /tmp/subif-rx.pcap
    1   0.000000 192.168.1.249 → 192.168.1.142 ICMP 98 Echo (ping) request  
id=0x088e, seq=1/256, ttl=64
# tshark -nn -r /tmp/subif-tx.pcap
    1   0.000000 192.168.1.142 → 192.168.1.249 ICMP 98 Echo (ping) reply    
id=0x088e, seq=1/256, ttl=255
    2   0.000001 192.168.1.142 → 192.168.1.249 ICMP 98 Echo (ping) reply    
id=0x088e, seq=1/256, ttl=255
 
tap0 is in a l2 xconnect with a VLAN sub-interface, does that explain the 
duplication?

vpp# sh mode
l3 local0
l3 TenGigabitEthernet3/0/0
l3 TenGigabitEthernet3/0/1
l3 GigabitEthernet81/0/1
l3 GigabitEthernet81/0/2
l3 GigabitEthernet81/0/3
l2 xconnect tap0 GigabitEthernet81/0/1.3010270
l2 xconnect GigabitEthernet81/0/1.3010270 tap0

Charles
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12787): https://lists.fd.io/g/vpp-dev/message/12787
Mute This Topic: https://lists.fd.io/mt/31188853/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to