/usr/share/doc/wireshark-doc/wsug_html_chunked/AppFiles.html is in wireshark-doc 1.10.6-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 | <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Appendix A. Files and Folders</title><link rel="stylesheet" type="text/css" href="ws.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="Wireshark User's Guide"><link rel="up" href="index.html" title="Wireshark User's Guide"><link rel="prev" href="lua_module_Utility.html" title="11.13. Utility Functions"><link rel="next" href="ChAppFilesConfigurationSection.html" title="A.2. Configuration Files and Folders"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix A. Files and Folders</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="lua_module_Utility.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ChAppFilesConfigurationSection.html">Next</a></td></tr></table><hr></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="AppFiles"></a>Appendix A. Files and Folders</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="AppFiles.html#ChAppFilesCaptureFilesSection">A.1. Capture Files</a></span></dt><dd><dl><dt><span class="section"><a href="AppFiles.html#ChIOFileContentSection">A.1.1. Libpcap File Contents</a></span></dt><dt><span class="section"><a href="AppFiles.html#ChIOFileNotContentSection">A.1.2. Not Saved in the Capture File</a></span></dt></dl></dd><dt><span class="section"><a href="ChAppFilesConfigurationSection.html">A.2. Configuration Files and Folders</a></span></dt><dd><dl><dt><span class="section"><a href="ChAppFilesConfigurationSection.html#ChProtocolHelp">A.2.1. Protocol help configuration</a></span></dt></dl></dd><dt><span class="section"><a href="ChWindowsFolder.html">A.3. Windows folders</a></span></dt><dd><dl><dt><span class="section"><a href="ChWindowsFolder.html#ChWindowsProfiles">A.3.1. Windows profiles</a></span></dt><dt><span class="section"><a href="ChWindowsFolder.html#ChWindowsRoamingProfiles">A.3.2. Windows 7, Vista, XP, 2000, and NT roaming profiles</a></span></dt><dt><span class="section"><a href="ChWindowsFolder.html#ChWindowsTempFolder">A.3.3. Windows temporary folder</a></span></dt></dl></dd></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ChAppFilesCaptureFilesSection"></a>A.1. Capture Files</h2></div></div></div><p>
To understand which information will remain available after
the captured packets are saved to a capture file,
it's helpful to know a bit about the capture file contents.
</p><p>
Wireshark uses the libpcap file format as the default format to save
captured packets; this format has existed for a long time and it's pretty simple.
However, it has some drawbacks: it's not extensible and lacks some
information that would be really helpful (e.g. being able to add a comment
to a packet such as "the problems start here" would be really nice).
</p><p>
In addition to the libpcap format, Wireshark supports several different
capture file formats. However, the problems described above also applies
for these formats.
</p><p>
A new capture file format "PCAP Next Generation Dump File Format"
is currently under development, which will fix these drawbacks.
However, it still might take a while until the new file format is ready
and Wireshark can use it.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="ChIOFileContentSection"></a>A.1.1. Libpcap File Contents</h3></div></div></div><p>
At the start of each libpcap capture file some basic information is stored
like a magic number to identify the libpcap file format.
The most interesting information of this file start is the link layer type
(Ethernet, Token Ring, ...).
</p><p>
The following data is saved for each packet:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
the timestamp with millisecond resolution
</p></li><li class="listitem"><p>
the packet length as it was "on the wire"
</p></li><li class="listitem"><p>
the packet length as it's saved in the file
</p></li><li class="listitem"><p>
the packet's raw bytes
</p></li></ul></div><p>
A detailed description of the libpcap file format can be found at:
<a class="ulink" href="http://wiki.wireshark.org/Development/LibpcapFileFormat" target="_top">http://wiki.wireshark.org/Development/LibpcapFileFormat</a>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="ChIOFileNotContentSection"></a>A.1.2. Not Saved in the Capture File</h3></div></div></div><p>
Probably even more interesting for everyday Wireshark usage is to know
the things that are <span class="command"><strong>not saved</strong></span> in the capture file:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
current selections (selected packet, ...)
</p></li><li class="listitem"><p>
name resolution information, see <a class="xref" href="ChAdvNameResolutionSection.html" title="7.7. Name Resolution">Section 7.7, “Name Resolution”</a> for details
</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Warning: Warning!"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="wsug_graphics/warning.png"></td><th align="left">Warning!</th></tr><tr><td align="left" valign="top"><p>
The name resolution information is rebuilt each time Wireshark is
restarted so this information might even change when the capture file
is reopened on the same machine later!
</p></td></tr></table></div><p>
</p></li><li class="listitem"><p>
the number of packets dropped while capturing
</p></li><li class="listitem"><p>
packet marks set with "Edit/Mark Packet"
</p></li><li class="listitem"><p>
time references set with "Edit/Time Reference"
</p></li><li class="listitem"><p>
the current display filter
</p></li><li class="listitem"><p>
...
</p></li></ul></div><p>
</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="lua_module_Utility.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="ChAppFilesConfigurationSection.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">11.13. Utility Functions </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> A.2. Configuration Files and Folders</td></tr></table></div></body></html>
|