# mac addresses only when coming / going to a PHY, as tun interfaces are 元-only Tos 0x00, ttl 64, length 688, checksum 0x1bc5 dscp CS0 ecn NON_ECN # we read TCP header, addresses and ports Hdr: flags 0x00 gso_type 0x00 hdr_len 0 gso_size 0 csum_start 0 csum_offset 0 num_buffers 1 Virtio: hw_if_index 2 next-index 1 vring 0 len 688 # This packet has been received on the interface number #2 (column Idx in `show int`)

The following snippet will allow you to capture all traffic coming from containers on a particular node, grep from a specific packet, Then inside your pods (usually with tcpdump) Traffic capture inside VPP Traffic from a pod We cover the three cases, first inside VPP (depending on where your traffic is coming from : a pod or outside your host)

as it is received in the second pod (in Linux again).

as it exits the pod (in Linux inside the first pod).

You might want to inspect the traffic at 3 different locations :

Let’s take the case of two pods talking to each other in your cluster (see the schema above). Tap0 is the interface providing connectivity to the host, using the original interface name on the Linux side (use show tap tap0 and show ip punt redirect). # If you want more info about this interface (name in Linux, queues, descriptors. Path-list: locks:3 flags:shared, uPRF-list:24 len:1 itfs: Ipv4-VRF:0, fib_index:0, flow hash: epoch:0 flags:none locks:Ĭnat refs:1 entry-flags:uRPF-exempt,interpose, src-flags:added,contributing,active, cover:-1 cnat-client: tr:0 sess:1 # Show the route for address 11.0.166.132 Name Idx State MTU (元/IP4/IP6/MPLS) Counter Count

Wireshark mac crashes stack guard