Ron Bandes wrote:
ACP -
"Analyzer CaPture", probably. I think captures from Analyzer:
http://analyzer.polito.it/
use that suffix. (Analyzer's native format is libpcap format.)
> APC -
"AiroPeek Capture"? TokenPeek, from WildPackets, according to
http://www.wildpackets.com/products/proconvert/files
ATC -
"ATm Capture". ATM captures from the old DOS-based Sniffer.
BFR -
"BuFfeR"? Network Instruments Observer, according to the ProConvert page.
CAP - Libpcap (common file extension)
An annoyingly large number of network analyzers chose the "obvious" name
for CAPture files - ones we support include Microsoft Network Monitor,
NetXRay/Windows Sniffer, and Shomiti/Finisar Surveyor. The P page whose
URL is given above lists some others.... (That's *another* good reason
to rely on the file contents, not the suffix.)
ENC -
"EtherNet Capture". Ethernet captures from the old DOS-based Sniffer.
FDC -
"FDdi Capture". FDDI captures from the old DOS-based Sniffer.
PKT -
"PacKeT". {Ether,Giga}Peek, from WildPackets, according to the
ProConvert page.
SYC -
"SYnchronous Capture". Synchronous line - and asynchronous line - WAN
captures from the old DOS-based Sniffer.
TPC -
"TokenPeek Capture"? TokenPeek, from WildPackets, according to the
ProConvert page.
TR1 -
Novell LANAlyzer - I think that if they write to multiple files in a
capture, subsequent files might be called ".tr2", ".tr3", etc. (but we
don't support reading multiple LANAlyzer files in one read).
TRC -
"Token Ring Capture". Token Ring captures from the old DOS-based Sniffer.
WPC -
WPZ -
"WanPeek Capture", and possibly "WanPeek capture, gZipped" - WanPeek,
from WildPackets, according to the ProConvert page.
Ron Bandes, CCNP, CTT+, etc.
_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users