Gitiles
Code Review Sign In
gerrit.named-data.net / ndn-tools / b6b176c7b991d88ab7f86e2f437e61c879bdd762 / . / tests / dump
tree: 7007046ee71bed7f341a95ffc41de3f72be62482 [path history] [tgz]
  1. invalid-tlv-length.pcap
  2. linux-sll-tcp4.pcap
  3. linux-sll-tcp6.pcap
  4. linux-sll-udp4.pcap
  5. linux-sll-udp6.pcap
  6. nack.pcap
  7. ndndump.t.cpp
  8. README.md
  9. unrecognized-lp-field.pcap
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.