Feature #3463
closed
Added by Junxiao Shi about 8 years ago.
Updated about 8 years ago.
Description
In ndndump, recognize Nack packets.
The output should contain at least: Nack reason, Interest name, Nonce.
Files
- Status changed from New to Code review
- % Done changed from 0 to 90
How is this tool tested beyond unit testing?
Can the assignee upload pcap files that contain Nack packets under different underlying protocols?
At least two Nack reasons plus reasonless Nack, and at least two underlying protocols should be included.
I confirm note-3 trace fulfills the requirements in note-2.
I notice that ndndump in ndn-tools:commit:589474aff39edb36b747e109d893e99187b41dc2 prints many lines of Tunnel Type: TCP, INCOMPLETE-PACKET, size: 0.
Correlating the timestamps in Wireshark, those packets are TCP ACKs without payload.
It's incorrect to label a TCP packet without payload as "INCOMPLETE" because there's no NDN packet at all; I suggest skipping them without printing anything.
Other than the above problem, Nacks are parsed correctly.
- Status changed from Code review to Feedback
ndndump manpage and tools/dump/README.md should be updated to reflect the new capability.
- Status changed from Feedback to Closed
- % Done changed from 90 to 100
Also available in: Atom
PDF
Updated by 
Updated by