diff options
| author | Gilbert Ramirez <gram@alumni.rice.edu> | 1999-10-31 17:46:11 +0000 |
|---|---|---|
| committer | Gilbert Ramirez <gram@alumni.rice.edu> | 1999-10-31 17:46:11 +0000 |
| commit | 558e714449ea30104c2bb7f35421328125a2a24a (patch) | |
| tree | a8d7d038636feee1bb1addd3488aedc7df8716a9 /README | |
| parent | 10fdc90bb0784b067d4e77c73907c6adfa5f5d08 (diff) | |
Add a module to wiretap to be able to read trace files from Toshiba's
line of ISDN routers. Much like the ascend reader, this module reads an
ASCII hex dump of trace data.
Rearranged the order in which wiretap tries trace files, to keep the
ASCII-readers (ascend and toshiba) at the end, and put the binary-readers
(everything else) at the front of the list. If a telnet session of
and ascend trace or toshiba trace were captured near the beginning of
another trace, wiretap might think the trace was ascend or toshiba if it
tried that module first.
Fixed the way wtap_seek_read() selects functions to call. It was using
the encap type instead of the file type. We got lucky because
WTAP_ENCAP_ASCEND == WTAP_FILE_ASCEND
svn path=/trunk/; revision=952
Diffstat (limited to 'README')
| -rw-r--r-- | README | 29 |
1 files changed, 23 insertions, 6 deletions
@@ -73,9 +73,10 @@ its infancy. However, wiretap is used in ethereal for its ability to read multiple file types. You can read the following file formats, and create display filters for them as well: -libpcap, Sniffer (uncompresed), NetXray, Sniffer Pro, snoop, -Shomiti, LANalyzer, Network Monitor, iptrace 2.0 (AIX), RADCOM's -WAN/LAN Analyzer, Lucent/Ascend access products, and HP-UX's nettl. +libpcap (tcpdump -w), Sniffer (uncompressed), NetXray, Sniffer Pro, +snoop, Shomiti, LANalyzer, Network Monitor, AIX's iptrace 2.0, +RADCOM's WAN/LAN Analyzer, Lucent/Ascend access products, HP-UX's nettl, +and Toshiba's ISDN routers. Although Ethereal can read AIX iptrace files, the documentation on AIX's iptrace packet-trace command is sparse. The 'iptrace' command @@ -103,9 +104,25 @@ the following pages: "wdd" on the Pipeline series: http://aos.ascend.com/aos:/gennavviewer.html?doc_id=0900253d80006877 -To use these commands in conjunction with Ethereal, you must capture the -trace output to a file on disk. An easy way of doing this under Unix is -to run "telnet <ascend> | tee <outfile>". +Ethereal can also read dump trace output from the Toshiba "Compact Router" +line of ISDN routers (TR-600 and TR-650). You can telnet to the router +and start a dump session with "snoop dump". + +To use the Lucent/Ascend and Toshiba traces with Ethereal, you must capture +the trace output to a file on disk. The trace is happening inside the router +and the router has no way of saving the trace to a file for you. +An easy way of doing this under Unix is to run "telnet <ascend> | tee <outfile>". +Or, if your system has the "script" command installed, you can save +a shell session, including telnet to a file. For example, to a file named +tracefile.out: + +$ script tracefile.out +Script started on <date/time> +$ telnet router +..... do your trace, then exit from the router's telnet session. +$ exit +Script done on <date/time> + IPv6 |