Connection closing improvements and explicit cleanup code

[dccp2tcp] / README

diff --git a/README b/README
index 02c14972b3dfd03ff3227539ea820117f7b23382..4364d412ac05d37971adac9904554ac7edcd6982 100644 (file)
--- a/README
+++ b/README
@@ -20,7 +20,7 @@ dccp2tcp dccp_file tcp_file [-d] [-y] [-g] [-s]
        -d is debug
        -y shifts the window line in tcptrace (yellow) to the highest received acknowledgment. Normally this line is just a constant amount more than the ack number(i.e. useless).
        -g shifts the ack line in tcptrace (green) to the highest received acknowledgment. Normally this line is the standard TCP ack number, which, for DCCP, translates to the highest contiguous acknowledgement in the ack vector.
-       -s converts the DCCP ack vector to TCP SACKS.
+       -s converts the DCCP ack vector to TCP SACKS. Specify -s twice to only see those Ack vectors with a loss interval in them. This is convenient way to see loss events.
 
 For typical usage, you probably just want -s.
 
@@ -32,13 +32,13 @@ xplot a2b_tsg.xpl a2b_rtt.xpl
 
 
 This program does have several important limitations:
-       1)Supports only a single DCCP contection per capture.
+       1)Supports only a single DCCP connection per capture.
        2)Source Port can't equal Destination Port. If the two are equal, this program will get very confused.
        3)DCCP MUST use 48 bit sequence numbers.
        4)Checksums are not computed (they are zeroed).
        5)Only converts those packet types used by the Linux implementation at this date
        6)DCCP Ack packets show up as TCP packets containing one byte
-       7)Very little error checking of packet headers, it's research software afterall
+       7)Very little error checking of DCCP