Gitiles
Code Review Sign In
gerrit.named-data.net / ndn-tools / 958896e4c0aa5abec0c94b54e2619abde329017c / . / tests / dump
tree: a3cf4f3a1d3ee2caf1f27bf7066d53235e37daab [path history] [tgz]
  1. LINUXSLL-tcp4.pcap
  2. LINUXSLL-tcp6.pcap
  3. LINUXSLL-udp4.pcap
  4. LINUXSLL-udp6.pcap
  5. nack.pcap
  6. ndndump.t.cpp
  7. README.md
tests/dump/README.md

Testing Instructions

This folder contains a tcpdump trace that can be used to manually check the correctness of ndndump.

Test Cases / Trace File Description

1. NDNLPv2 NACK

Trace file: nack.pcap

Trace summary: Six IPv4 UDP packets, carrying NDN interests and NACK packets. Twelve IPv4 TCP packets, carrying NDN interests and NACK packets.

Expected result of the capture:

  • 3 NDN interests are captured with UDP tunnel type.

  • 3 NACKs are captured with UDP tunnel type and the NACK reasons:

    • Congestion
    • Duplicate
    • None

  • 3 NDN interests are captured with TCP tunnel type.

  • 4 NACKs are captured with TCP tunnel type and the NACK reasons:

    • Congestion
    • Duplicate
    • None
    • None

2. LINUX_SLL link-type

Trace file: LINUXSLL-udp4.pcap LINUXSLL-udp6.pcap LINUXSLL-tcp4.pcap LINUXSLL-tcp6.pcap

These traces are captured inside an OpenVZ container which uses LINUX_SLL (Linux cooked) link-type.

Expected result: Some Interests and Data should be displayed from udp4 and tcp4 traces. Currently nothing is displayed from udp6 and tcp6 traces because ndndump lacks IPv6 support until Feature 3861.