This folder contains several crafted tcpdump traces that can be used to manually check correctness of NDN Packet Dissector for Wireshark in several scenarios.
To use the dissector, follow the instructions in dissector's README.md.
-r <trace-file>
command-line flag can be used to directly open a specific trace file in WireShark. For example:
wireshark -X lua_script:../../tools/dissect-wireshark/ndn.lua -r ipv4-udp-fragmented.pcap
Trace file: ipv4-udp-fragmented.pcap
Trace summary: several IPv4 UDP packets, carrying NDN interests and data packets. One datagram is fragmented into several IPv4 packets.
Expected result of the dissection:
Trace file: ipv6-udp-fragmented.pcap
Trace summary: several IPv6 UDP packets, carrying NDN interests and data packets. One datagram is fragmented into several IPv6 packets.
Expected result of the dissection:
Trace file: ipv4-tcp-segmented.pcap
Trace summary: several IPv4 TCP packets, carrying NDN interest and a data packets. The data packet spans several TCP segments.
Expected result of the dissection:
Trace file: ipv4-tcp-multi-ndn-packets-in-segment.pcap
Trace summary: Several IPv4 TCP packets, payload of one containing several NDN interests.
Expected result of the dissection:
Trace file: ipv6-tcp-segmented.pcap
Trace summary: several IPv6 TCP packets, carrying an NDN data packet that spans several TCP segments.
Expected result of the dissection:
Trace file: ipv4-websocket-segmented.pcap
Trace summary: Partial capture of a live IPv4 WebSocket session with a single NDN interest retrieving large (~5k) NDN data packet.
Expected result of the dissection:
Trace file: ipv6-websocket-segmented.pcap
Trace summary: Partial capture of a live IPv6 WebSocket session with a single NDN interest retrieving large (~5k) NDN data packet.
Expected result of the dissection:
Trace file: ethernet.pcap
Trace summary: Short capture, containing an NDN interest multicasted directly in Ethernet frame.
Expected result of the dissection:
Trace file: bug3603.pcap
Trace summary: A Data whose payload could be read as incomplete TLV and may cause tvb overflow if parser does not check packet length.
Expected result of the dissection: