| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
svn path=/trunk/; revision=4619
|
|
|
|
|
|
|
|
|
|
|
|
| |
formats we can read; include vendor names.
We should be able to read TokenPeek captures, as well as captures from
the Windows versions of EtherPeek.
Don't list the version numbers for EtherPeek and TokenPeek - those are
file format version numbers, not program version numbers.
svn path=/trunk/; revision=4599
|
|
|
|
| |
svn path=/trunk/; revision=4562
|
|
|
|
|
|
| |
read is Visual UpTime.
svn path=/trunk/; revision=4339
|
|
|
|
|
|
|
|
|
|
|
|
| |
libpcap format, and say that it's also used by "other tools" (tcpdump
and Ethereal/Tethereal aren't the only tools that write captures in that
format).
Weaken the claim that we read Etherpeek files to say only that we read
Etherpeek versions 5, 6, and 7 for Macintosh, so people don't conclude
that we read Etherpeek-for-Windows captures (we don't).
svn path=/trunk/; revision=4337
|
|
|
|
|
|
| |
and writing Visual Networks traffic capture files.
svn path=/trunk/; revision=4329
|
|
|
|
| |
svn path=/trunk/; revision=4042
|
|
|
|
|
|
|
|
| |
Update the lists of known capture file formats in the Tethereal,
editcap, and mergecap man pages to match the current list (as found in
the Ethereal man page).
svn path=/trunk/; revision=4039
|
|
|
|
| |
svn path=/trunk/; revision=3701
|
|
|
|
|
|
| |
Renfro.
svn path=/trunk/; revision=3696
|
|
|
|
|
|
|
|
|
| |
- at least some versions of makewhatis (e.g., the Solaris version)
uses that name in a case-sensitive fashion, so you can't do "man
ethereal", say, you have to do "man Ethereal", and that doesn't work as
the man page file is "ethereal.1", not "Ethereal.1".
svn path=/trunk/; revision=3656
|
|
|
|
| |
svn path=/trunk/; revision=2578
|
|
|
|
| |
svn path=/trunk/; revision=2234
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
is finally dead, and you're walking away, it springs up again and
attacks.
It appears that the ss990915 version of Alexey Kuznetzov's libpcap patch
has some extra stuff in the per-packet header for some sort of SMP
debugging, and that SuSE Linux 6.3 picked it up.
Thus, even if a libpcap file has the modified magic number, we *still*
have to go through the usual heuristic hell to figure out what type of
file it is.
svn path=/trunk/; revision=2164
|
|
|
|
|
|
| |
Mayer, and yours truly.
svn path=/trunk/; revision=2002
|
|
|
|
|
|
|
|
|
|
|
| |
snapshot length before writing them to the output file; this may come in
handy if you are translating the file to a different format so that it
can be read by a program that can't handle packets above a certain size
(e.g., the snoop in Solaris 2.5.1 or 2.6, which reject Ethernet packets
larger than the Ethernet MTU, and thus can't handle gigabit Ethernet
captures using jumbo frames).
svn path=/trunk/; revision=1891
|
|
|
|
|
|
|
| |
headers, it just causes it to force the encapsulation type of the output
file to the specified type.
svn path=/trunk/; revision=1702
|
|
svn path=/trunk/; revision=1446
|