CS 555 ns-2 Projects

Students	Test to Write	Tests to Validate (2)
Samy and Martin	tcpOptions: timeouts_newreno_full	tcp-init-win: Reno4, Tahoe4
Georges and Mragendra	tcpOptions: timeouts_reno2_full	tcp-init-win: Reno2, Tahoe2
Hadi and Gyanesh	tcpOptions: timeouts_tahoe2_full	tcp-init-win: NewReno1, NewReno2
Sheetal and Raghavendra	tcpOptions: timeouts_tahoe1_full	tcp-init-win: Reno1/Reno3, Tahoe1/Tahoe3
Snow and Shripad	tcpOptions: timeouts_tahoe3_full	tcp-init-win: NewReno3, NewReno4
Aditya and Arjun	tcpOptions: timeouts_reno1_full

Validation Suites

test-suite-tcp-init-win-full - validate

test-suite-tcpOptions - some to write and some commented out (to validate)

test-suite-tcpReset - write

test-suite-newreno - write

test-suite-tcp - write

test-suite-tcpVariants - write

test-suite-testReno-full - some commented out (to validate)

Note: Double-check test/tcl/FullTCP.notes to see which tests need to be validated or written in these suites.

I've put a couple of helpful shell scripts in /home/mweigle/555/ns/ for looking at what tests are needed. (Both of these are modifications of tools written by Sally Floyd.)

compare-suites - given the names of two test suites (minus "test-suite" and ".tcl"), indicate which are in one suite and not in the other
list-tests - given the name of a test suite (again minus "test-suite" and ".tcl"), print all of the tests in that suite

Setting Up a Local Copy of the Tests

Save a copy of setup-ns-test in your home directory in Unix.
Change permissions so that you can execute the script
chmod 755 setup-ns-test
Run the script
./setup-ns-test
This will create the directory ns in your home directory. The validation scripts will then be in ~/ns/tcl/test/ (~/ is your home directory).

Setting PATH Environment Variable

Add /home/mweigle/555/ns-allinone-2.30/bin to your PATH environment variable.
setenv PATH ${PATH}:/home/mweigle/555/ns-allinone-2.30/bin

In order to avoid having to do this each time you login, add this line to your ~/.cshrc or ~/.login.

Running a Test

Change directory to tcl/test
cd ~/ns/tcl/test
See what tests are available
../../ns test-suite-tcp-init-win-full.tcl (for example)
Run a test
../../ns test-suite-tcp-init-win-full.tcl tahoe1 (for example)
Typically, the files all.tr and temp.rands will be created after the script is finished. all.tr is a trace-queue file (similar to the +-rd format we discussed in class) and temp.rands will often be a filtered version of all.tr

Setting Up a Local Copy of the ns Source

Set appropriate environment variables:

setenv TCL_LIBRARY /home/mweigle/src/ns-allinone-2.30/tcl8.4.13/library
setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:/home/mweigle/src/ns-allinone-2.30/otcl-1.12:/home/mweigle/src/ns-allinone-2.30/lib
setenv PATH ${PATH}:~/ns-allinone-2.30/bin

(In order to avoid having to do this each time you login, add these lines to your ~/.cshrc or ~/.login.)

From your home directory, make a new directory to hold the ns source:
mkdir ns-allinone-2.30
cd ns-allinone-2.30
Run this script to generate links to the supporting libraries for ns (otcl, nam, etc):
/home/mweigle/555/ns/link-ns
Unpack the ns source:
tar xvzf /home/mweigle/555/ns/ns-2.30.tgz
cd ns-2.30
./configure
make
This last step may take a little while, but at the end you should see several "Nothing to be done" messages.

Note: Once you have initially compiled the ns source, you can just run make in the ns-allinone-2.30/ns-2.30 directory to compile just those changes.

References