home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
tcpcsd2.zip
/
BASECSD2.EXE
/
DOC
/
IPTRACE.DOC
< prev
next >
Wrap
Text File
|
1993-01-28
|
2KB
|
47 lines
****************************************************************
I P T R A C E B E T A C O D E
****************************************************************
IP tracing allows to trace all the packets, IP and ARP ones,
incoming and outgoing.
Three executables: IPTRACE.EXE, IPPARSE.EXE and TR2SNIF.EXE
Requirements:
INET and IFNDIS versions 1.2.2.24 or later. (CSD UN29511 or higher)
Start:
Run IPTRACE.EXE
While iptrace.exe is running it collects packets in
a file called iptrace.dmp in current dir.
Tracing is active only when this process is running.
Stop:
In the IPTRACE window press Ctrl-C or Ctrl-Break to stop the trace
Format:
IPPARSE is used to generate a somewhat format listing of the trace.
IPPARSE writes to standard output, so it can be redirected to a file.
TR2SNIF can be used for conversion of IPTRACE.DMP to IPTRACE.TRC
which can be loaded by the sniffer. IPTRACE.TRC is in internal
format of the "Sniffer" software. IPTRACE.TRC does not preserve timing
of frames, so sniffer timing information is not accurate and can't
be used for analysis (in fact, all of times in the current version
of tr2snif are zeros).
****************************************************************
N O T E!!!!!!!
****************************************************************
ip tracing slows the tcp/ip stack significantly
and SHOULD NOT be run for a stressful applications which
tend to fan through a lot of data. IP tracing dumps all
the packets contents including LAN headers. The way you
determine whether the packet is incoming our outgoing is
be looking at source address (in a LAN header or IP header).
Unlike socket level tracing, ip tracing may store in its
trace a lot of data.