Bug 2175 – Cannot read PCAP files in src/test/ns3tcp/response-vectors

Bug 2175 - Cannot read PCAP files in src/test/ns3tcp/response-vectors


Summary:	Cannot read PCAP files in src/test/ns3tcp/response-vectors

Status:	RESOLVED WONTFIX

Product:	ns-3
Classification:	Unclassified
Component:	tcp
Version:	pre-release
Hardware:	PC Linux

Importance:	P5 normal
Assigned To:	ns-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-09-03 05:02 UTC by natale.patriciello
Modified:	2015-10-29 08:53 UTC (History)
CC List:	2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description natale.patriciello 2015-09-03 05:02:11 UTC

Trying to open these files under wireshark or TCPdump fails. In this state, they are completely useless.. Sincerely, I don't know if the problem is inside TCP module or the point to point one, which is used to write the PCAP.

As a side note: PCAP generated with point to point in other code works.

Comment 1 Tom Henderson 2015-09-04 01:40:53 UTC

I think that we should ignore this issue or else replace the tests with new tests from the new test framework.

This was by design that the pcap files (response vectors) only contain TCP information, so that they are not perturbed by non-TCP changes to the packet traces, and to save space.  That is, the pcaps only store TCP layer info and not the lower layers.  Hence, they cannot be used for wireshark, but they are just serving as binary files for comparison.

There is an argument m_writeResults (default false) that will write Wireshark-compatible pcap traces if the variable is set to true.

So, I don't advocate spending time to rework these response vectors.  I would be OK with replacing the tests with functionally equivalent tests in the new test framework.