Usage is pretty simple:
-dccp2tcp dccp_file tcp_file [-d] [-y] [-g] [-s]
- -d is debug
+dccp2tcp dccp_file tcp_file [-v] [-V] [h] [-y] [-g] [-s]
+ -v is verbose. Repeat for additional verbosity.
+ -V is Version information
+ -h is help
-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. Specify -s twice to only see those Ack vectors with a loss interval in them. This is convenient way to see loss events.
You can then use xplot to view the resulting graphs, like this:
xplot a2b_tsg.xpl a2b_rtt.xpl
+One important note on interpreting the graphs is that DCCP Ack packets show up
+as TCP packets containing one byte.
-This program does have several important limitations:
- 1)CCID2 ONLY
- 2)DCCP MUST use 48 bit sequence numbers.
- 3)Checksums are not computed (they are zeroed).
- 4)DCCP DATA packets are not implemented (Linux doesn't use them)
- 5)DCCP Ack packets show up as TCP packets containing one byte
-
+Finally, an important limitation of this program is that DCCP MUST use 48 bit
+sequence numbers. dccp2tcp will complain at you if you try to process a connection
+with short sequence numbers.
dccp2tcp is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
along with dccp2tcp. If not, see <http://www.gnu.org/licenses/>.
-Copyright 2011
+Copyright 2013
Samuel Jero
-Computer Science student, Ohio University
+Masters Student
+Internetworking Research Group
+Ohio University
sj323707@ohio.edu