Maybe we're splitting hairs here or we're agreeing violently :-). Is to read the magic number in the Open and ReadAndVerifyFileHeader You *can* change the way ns-3 is reading PCAPs. However, I don't understand the other concern about documentation: So I will update the patch to fix these concerns. I understand Thomasso's comment about the documentation needing clarification, and I understand the comment about needing to document the m_nanosecMode variable in cap-file.h. "magic number" read from the file header. Interpretation of these timestamps is determined by the Timestamps when *reading* pcap trace files because the correct Note: This attribute does not change the way that ns3 interprets The format of the pcap capture files is more fully Programs that read the files that the timestamp format isĭifferent. The pcap packet trace files have "magic number" at the to notify Value of ns3::Simulator::Now() and converting to either Timestamps for saving pcap trace files are created by taking the The following example C++ code shows how to do this:Ĭonfig::SetDefault ("ns3::PcapFileWrapper::NanosecMode", The boolean attribute ns3::PcapFileWrapper::NanosecMode mayīe set to true to change the resolution of timestamp written Support reading and writing pcap packet trace files that have Of tcpdump, Wireshark and other libpcap based applications ![]() ![]() Packet timestamps with microsecond resolution. By default, when saving pcap packet trace files, ns3 records
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |