[Codel] CoDel on ns2.35 simulator

Joey Padden J.Padden at cablelabs.com
Fri Jun 7 08:31:35 EDT 2013 

Safa,

I'm not sure what you mean by output, so I'll lightly cover all bases.

The output to standard out that you are showing below is for warnings and errors. The code is now running with CoDel patched and working I am assuming based on what you've said. Exactly what the illegal sack block means, I don't know off hand, I'd look through the TCP code for that message and backtrack from there. I'd start looking in ns/tcp/tcp-full.{cc,h}.

The nam output is commented out in the CoDel.tcl file from the Pollere website, so it won't be active. See lines 380-384 in CoDel.tcl. I have never used nam much and honestly have yet to see the real value.

The true output files in ns are trace files. Trace files can be attached to links and possibly other ns objects, memory is a bit foggy here. CoDel.tcl creates it's trace files in lines 388-394 on a link between nodes $n0 and $n1. The main output of this script is the file /tmp/f.tr<http://f.tr>  the format of which is explained here http://nsnam.isi.edu/nsnam/index.php/NS-2_Trace_Formats

OK for now,
Jp

On Jun 7, 2013, at 12:39 AM, safa khan <safakhan413 at gmail.com<mailto:safakhan413 at gmail.com>>
 wrote:

Joey
your help will be greatly appreciated. I have tried to triangulate the problem. With more packmime connections I get more illegal SACK bllock warnings. Can you or anyone on the CoDel list tell me what output is expected after runniing the TCL script?

Safa


On Mon, Jun 3, 2013 at 6:10 PM, safa khan <safakhan413 at gmail.com<mailto:safakhan413 at gmail.com>> wrote:
Thanks Joey! You are awesome man.

Since I did not know what to copy and what not to, I followed everything here

http://pollere.net/CoDel.html

I ran codel after PATCHING it into the ns2 simulator. Then I ran the following command

./ns codel.tcl 4 5 0 100Mb -1 5

However there was no nam output and I get the following result. Would you please tell if Codel.tcl even has nam output or not? And what are these warnings for? Also how the result is to be interpreted?

ftps 4 webrate 5 cbrs 0 bw 100000000.0 filesize -1 reverse 0
accessdly 20 bneckdly 10 realrtt 100 bneckbw 100000000.0
bottleneck starts at 100000000bps
change at 50 to 10.0Mbps
change at 100 to 1.0Mbps
change at 150 to 50.0Mbps
change at 200 to 1.0Mbps
change at 250 to 100.0Mbps
f.tr<http://f.tr/>
cmd select_ca cubic
cmd select_ca cubic
cmd select_ca cubic
cmd select_ca cubic
1.603260: FullTcpAgent(_o211) warning: received illegal SACK block [107,107]
10000000.0
55.098906: FullTcpAgent(_o217) warning: received illegal SACK block [264,264]
55.695007: FullTcpAgent(_o241) warning: received illegal SACK block [72,72]
60.292143: FullTcpAgent(_o217) warning: received illegal SACK block [124,124]
60.540666: FullTcpAgent(_o301) warning: received illegal SACK block [582,582]
61.275364: FullTcpAgent(_o249) warning: received illegal SACK block [3206,3206]
1000000.0
103.964724: FullTcpAgent(_o357) warning: received illegal SACK block [152,152]
104.982964: FullTcpAgent(_o289) warning: received illegal SACK block [411,411]
105.313196: FullTcpAgent(_o217) warning: received illegal SACK block [646,646]
107.602393: FullTcpAgent(_o289) warning: received illegal SACK block [179,179]
108.347540: FullTcpAgent(_o221) warning: received illegal SACK block [211,211]
110.080323: FullTcpAgent(_o329) warning: received illegal SACK block [437,437]
111.459607: FullTcpAgent(_o417) warning: received illegal SACK block [696,696]
112.831121: FullTcpAgent(_o261) warning: received illegal SACK block [199,199]
118.597599: FullTcpAgent(_o329) warning: received illegal SACK block [670,670]
119.580768: FullTcpAgent(_o365) warning: received illegal SACK block [1435,1435]
119.655479: FullTcpAgent(_o305) warning: received illegal SACK block [485,485]
123.072111: FullTcpAgent(_o349) warning: received illegal SACK block [728,728]
131.987632: FullTcpAgent(_o349) warning: received illegal SACK block [929,929]
132.357178: FullTcpAgent(_o293) warning: received illegal SACK block [320,320]
133.444730: FullTcpAgent(_o401) warning: received illegal SACK block [357,357]
141.070035: FullTcpAgent(_o233) warning: received illegal SACK block [172,172]
141.368133: FullTcpAgent(_o293) warning: received illegal SACK block [908,908]
145.503133: FullTcpAgent(_o325) warning: received illegal SACK block [132,132]
145.828200: FullTcpAgent(_o353) warning: received illegal SACK block [258,258]
147.140807: FullTcpAgent(_o417) warning: received illegal SACK block [798,798]
50000000.0
1000000.0
212.234133: FullTcpAgent(_o585) warning: received illegal SACK block [331,331]
214.253093: FullTcpAgent(_o657) warning: received illegal SACK block [1424,1424]
215.172477: FullTcpAgent(_o421) warning: received illegal SACK block [280,280]
217.604597: FullTcpAgent(_o725) warning: received illegal SACK block [138,138]
224.780413: FullTcpAgent(_o625) warning: received illegal SACK block [311,311]
225.913829: FullTcpAgent(_o1069) warning: received illegal SACK block [1142,1142]
228.437312: FullTcpAgent(_o1233) warning: received illegal SACK block [97,97]
229.008533: FullTcpAgent(_o829) warning: received illegal SACK block [130,130]
230.466246: FullTcpAgent(_o413) warning: received illegal SACK block [757,757]
230.576166: FullTcpAgent(_o1245) warning: received illegal SACK block [391,391]
230.584466: FullTcpAgent(_o233) warning: received illegal SACK block [678,678]
230.789350: FullTcpAgent(_o633) warning: received illegal SACK block [431,431]
231.104630: FullTcpAgent(_o369) warning: received illegal SACK block [130,130]
232.006687: FullTcpAgent(_o1333) warning: received illegal SACK block [217,217]
232.454507: FullTcpAgent(_o1349) warning: received illegal SACK block [639,639]
234.957352: FullTcpAgent(_o313) warning: received illegal SACK block [935,935]
235.201241: FullTcpAgent(_o1185) warning: received illegal SACK block [137,137]
237.336677: FullTcpAgent(_o541) warning: received illegal SACK block [185,185]
237.383566: FullTcpAgent(_o1157) warning: received illegal SACK block [126,126]
237.692238: FullTcpAgent(_o1069) warning: received illegal SACK block [960,960]
238.369279: FullTcpAgent(_o1253) warning: received illegal SACK block [687,687]
238.811276: FullTcpAgent(_o513) warning: received illegal SACK block [1323,1323]
238.871383: FullTcpAgent(_o1213) warning: received illegal SACK block [112,112]
239.108312: FullTcpAgent(_o309) warning: received illegal SACK block [824,824]
239.895494: FullTcpAgent(_o1193) warning: received illegal SACK block [132,132]
241.157944: FullTcpAgent(_o1069) warning: received illegal SACK block [303,303]
241.183073: FullTcpAgent(_o597) warning: received illegal SACK block [130,130]
241.339148: FullTcpAgent(_o533) warning: received illegal SACK block [379,379]
241.708525: FullTcpAgent(_o211) warning: received illegal SACK block [338,338]
242.306111: FullTcpAgent(_o445) warning: received illegal SACK block [83,83]
242.406312: FullTcpAgent(_o361) warning: received illegal SACK block [297,297]
242.540972: FullTcpAgent(_o685) warning: received illegal SACK block [750,750]
243.316109: FullTcpAgent(_o553) warning: received illegal SACK block [122,122]
244.446153: FullTcpAgent(_o393) warning: received illegal SACK block [433,433]
244.997886: FullTcpAgent(_o477) warning: received illegal SACK block [552,552]
244.998366: FullTcpAgent(_o833) warning: received illegal SACK block [158,158]
244.999086: FullTcpAgent(_o825) warning: received illegal SACK block [221,221]
246.901650: FullTcpAgent(_o533) warning: received illegal SACK block [168,168]
249.093984: FullTcpAgent(_o1025) warning: received illegal SACK block [118,118]
249.919780: FullTcpAgent(_o365) warning: received illegal SACK block [151,151]
249.934924: FullTcpAgent(_o597) warning: received illegal SACK block [67,67]
100000000.0
256.844373: FullTcpAgent(_o973) warning: received illegal SACK block [281,281]


Regards
Safa


On Sun, Jun 2, 2013 at 1:12 AM, safa khan <safakhan413 at gmail.com<mailto:safakhan413 at gmail.com>> wrote:

Thanks Joey! You are awesome man.

Since I did not know what to copy and what not to, I followed everything here

http://pollere.net/CoDel.html

I ran codel after PATCHING it into the ns2 simulator. Then I ran the following command

./ns codel.tcl 4 5 0 100Mb -1 5

However there was no nam output and I get the following result. Would you please tell if Codel.tcl even has nam output or not? And what are these warnings for? Also how the result is to be interpreted?

ftps 4 webrate 5 cbrs 0 bw 100000000.0 filesize -1 reverse 0
accessdly 20 bneckdly 10 realrtt 100 bneckbw 100000000.0
bottleneck starts at 100000000bps
change at 50 to 10.0Mbps
change at 100 to 1.0Mbps
change at 150 to 50.0Mbps
change at 200 to 1.0Mbps
change at 250 to 100.0Mbps
f.tr<http://f.tr/>
cmd select_ca cubic
cmd select_ca cubic
cmd select_ca cubic
cmd select_ca cubic
1.603260: FullTcpAgent(_o211) warning: received illegal SACK block [107,107]
10000000.0
55.098906: FullTcpAgent(_o217) warning: received illegal SACK block [264,264]
55.695007: FullTcpAgent(_o241) warning: received illegal SACK block [72,72]
60.292143: FullTcpAgent(_o217) warning: received illegal SACK block [124,124]
60.540666: FullTcpAgent(_o301) warning: received illegal SACK block [582,582]
61.275364: FullTcpAgent(_o249) warning: received illegal SACK block [3206,3206]
1000000.0
103.964724: FullTcpAgent(_o357) warning: received illegal SACK block [152,152]
104.982964: FullTcpAgent(_o289) warning: received illegal SACK block [411,411]
105.313196: FullTcpAgent(_o217) warning: received illegal SACK block [646,646]
107.602393: FullTcpAgent(_o289) warning: received illegal SACK block [179,179]
108.347540: FullTcpAgent(_o221) warning: received illegal SACK block [211,211]
110.080323: FullTcpAgent(_o329) warning: received illegal SACK block [437,437]
111.459607: FullTcpAgent(_o417) warning: received illegal SACK block [696,696]
112.831121: FullTcpAgent(_o261) warning: received illegal SACK block [199,199]
118.597599: FullTcpAgent(_o329) warning: received illegal SACK block [670,670]
119.580768: FullTcpAgent(_o365) warning: received illegal SACK block [1435,1435]
119.655479: FullTcpAgent(_o305) warning: received illegal SACK block [485,485]
123.072111: FullTcpAgent(_o349) warning: received illegal SACK block [728,728]
131.987632: FullTcpAgent(_o349) warning: received illegal SACK block [929,929]
132.357178: FullTcpAgent(_o293) warning: received illegal SACK block [320,320]
133.444730: FullTcpAgent(_o401) warning: received illegal SACK block [357,357]
141.070035: FullTcpAgent(_o233) warning: received illegal SACK block [172,172]
141.368133: FullTcpAgent(_o293) warning: received illegal SACK block [908,908]
145.503133: FullTcpAgent(_o325) warning: received illegal SACK block [132,132]
145.828200: FullTcpAgent(_o353) warning: received illegal SACK block [258,258]
147.140807: FullTcpAgent(_o417) warning: received illegal SACK block [798,798]
50000000.0
1000000.0
212.234133: FullTcpAgent(_o585) warning: received illegal SACK block [331,331]
214.253093: FullTcpAgent(_o657) warning: received illegal SACK block [1424,1424]
215.172477: FullTcpAgent(_o421) warning: received illegal SACK block [280,280]
217.604597: FullTcpAgent(_o725) warning: received illegal SACK block [138,138]
224.780413: FullTcpAgent(_o625) warning: received illegal SACK block [311,311]
225.913829: FullTcpAgent(_o1069) warning: received illegal SACK block [1142,1142]
228.437312: FullTcpAgent(_o1233) warning: received illegal SACK block [97,97]
229.008533: FullTcpAgent(_o829) warning: received illegal SACK block [130,130]
230.466246: FullTcpAgent(_o413) warning: received illegal SACK block [757,757]
230.576166: FullTcpAgent(_o1245) warning: received illegal SACK block [391,391]
230.584466: FullTcpAgent(_o233) warning: received illegal SACK block [678,678]
230.789350: FullTcpAgent(_o633) warning: received illegal SACK block [431,431]
231.104630: FullTcpAgent(_o369) warning: received illegal SACK block [130,130]
232.006687: FullTcpAgent(_o1333) warning: received illegal SACK block [217,217]
232.454507: FullTcpAgent(_o1349) warning: received illegal SACK block [639,639]
234.957352: FullTcpAgent(_o313) warning: received illegal SACK block [935,935]
235.201241: FullTcpAgent(_o1185) warning: received illegal SACK block [137,137]
237.336677: FullTcpAgent(_o541) warning: received illegal SACK block [185,185]
237.383566: FullTcpAgent(_o1157) warning: received illegal SACK block [126,126]
237.692238: FullTcpAgent(_o1069) warning: received illegal SACK block [960,960]
238.369279: FullTcpAgent(_o1253) warning: received illegal SACK block [687,687]
238.811276: FullTcpAgent(_o513) warning: received illegal SACK block [1323,1323]
238.871383: FullTcpAgent(_o1213) warning: received illegal SACK block [112,112]
239.108312: FullTcpAgent(_o309) warning: received illegal SACK block [824,824]
239.895494: FullTcpAgent(_o1193) warning: received illegal SACK block [132,132]
241.157944: FullTcpAgent(_o1069) warning: received illegal SACK block [303,303]
241.183073: FullTcpAgent(_o597) warning: received illegal SACK block [130,130]
241.339148: FullTcpAgent(_o533) warning: received illegal SACK block [379,379]
241.708525: FullTcpAgent(_o211) warning: received illegal SACK block [338,338]
242.306111: FullTcpAgent(_o445) warning: received illegal SACK block [83,83]
242.406312: FullTcpAgent(_o361) warning: received illegal SACK block [297,297]
242.540972: FullTcpAgent(_o685) warning: received illegal SACK block [750,750]
243.316109: FullTcpAgent(_o553) warning: received illegal SACK block [122,122]
244.446153: FullTcpAgent(_o393) warning: received illegal SACK block [433,433]
244.997886: FullTcpAgent(_o477) warning: received illegal SACK block [552,552]
244.998366: FullTcpAgent(_o833) warning: received illegal SACK block [158,158]
244.999086: FullTcpAgent(_o825) warning: received illegal SACK block [221,221]
246.901650: FullTcpAgent(_o533) warning: received illegal SACK block [168,168]
249.093984: FullTcpAgent(_o1025) warning: received illegal SACK block [118,118]
249.919780: FullTcpAgent(_o365) warning: received illegal SACK block [151,151]
249.934924: FullTcpAgent(_o597) warning: received illegal SACK block [67,67]
100000000.0
256.844373: FullTcpAgent(_o973) warning: received illegal SACK block [281,281]


Regards
Safa


On Sat, Jun 1, 2013 at 1:42 AM, Joey Padden <J.Padden at cablelabs.com<mailto:J.Padden at cablelabs.com>> wrote:
The all-in-one install creates may sub-directories for tcl,tk, otcl, tctcl, and most importantly ns-2.35.

the contents of the  git /ns directory can replace the contents of the ns-2.35 directory.

after copying the contents cd into the directory and do a

./configure; make;

then try the command

ns codel.tcl

OK for now,
Jp

On May 31, 2013, at 12:42 PM, safa khan <safakhan413 at gmail.com<mailto:safakhan413 at gmail.com>>
 wrote:

Dear Joey

I have followed the instructions to build ns2. Let me give you a stepwise description of what I have done.

I have downloaded and installed ns2 from the following source
http://sourceforge.net/projects/nsnam/files/allinone/ns-allinone-2.35/ns-allinone-2.35.tar.gz/download

After that I downloaded the whole master repository as a zip and unzipped it
 https://github.com/dtaht/ns2

Now could you please give me a stepwise description as to how I should proceed from here. I have been trying to run the codel.tcl directly by
ns codel.tcl
after going to ns2-master directory without success. I keep getting the error:


ftps 1 webrate 0 cbrs 0 bw 3000000.0 filesize 10000000 reverse 0
accessdly 20 bneckdly 10 realrtt 100 bneckbw 3000000.0
invalid command name "Queue/CoDel"
    while executing
"Queue/CoDel set target_ $target"
    (file "codel.tcl" line 143)

How am I supposed to build ns2.35 with the CoDel. And where do the codel.h and codel.cc files come in? I would really appreciate a more detailed response.


On Fri, May 31, 2013 at 5:35 PM, Joey Padden <J.Padden at cablelabs.com<mailto:J.Padden at cablelabs.com>> wrote:
Safa,

In the CoDel.tcl from Dave's git repo, the line your code is choking on is 210 not 143, did you modify CoDel.tcl?

Also, did you rebuild ns after downloading the CoDel updates? It sounds like ns doesn't know about the queue type CoDel but it is in the makefile.in<http://makefile.in/> so it should if you did

cd /ns2/
./configure; make;

after downloading and unpacking the zip.

-Joey


Sent from my iPhone

On May 31, 2013, at 5:17 AM, "safa khan" <safakhan413 at gmail.com<mailto:safakhan413 at gmail.com>> wrote:

Dear Members

First of all thank you for the amazing idea that CoDel is :)

I have downloaded CoDel from https://github.com/dtaht/ns2
In fact I downloaded everything as a zip so that if CoDel needs some other files in the directory I wouldn't miss them out.

However, I have been trying to run ns codel.tcl on the my shell. My linux kernel version is 3.6. It gives the following error

ftps 1 webrate 0 cbrs 0 bw 3000000.0 filesize 10000000 reverse 0
accessdly 20 bneckdly 10 realrtt 100 bneckbw 3000000.0
invalid command name "Queue/CoDel"
    while executing
"Queue/CoDel set target_ $target"
    (file "codel.tcl" line 143)

A little help will be highly appreciated.

--
Regards
Safa Nasir

_______________________________________________
Codel mailing list
Codel at lists.bufferbloat.net<mailto:Codel at lists.bufferbloat.net>
https://lists.bufferbloat.net/listinfo/codel



--
Regards
Safa Nasir





--
Regards
Safa Nasir




--
Regards
Safa Nasir




--
Regards
Safa Nasir


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/codel/attachments/20130607/147684c7/attachment-0002.html>

More information about the Codel mailing list