Lab Assignments
Lab session Hours: (you must sign up for a session with your group)
[The lab holds about 5 groups at a time (i.e.,
15 students in groups of 3)]. Room/lab: EEB 351.
1. Lab 1 ( Start from Friday,
01/25/2002).
Useful links:
ifconfig,
route,
netstat, ping , traceroute
,tcpdump, tcptrace.
2. Lab 2 (Start from
Monday, 02/04/2002)
Useful links:
Zebra, Routed
(Please check man pages properly and create your own configuration
file).
Sample configuration files
for Zebra: (zebra.conf, ripd.conf, ospfd.conf)
3. Lab 3 (Start from Friday,
02/22/2002)
Useful links:
ping , traceroute,
Script Language
tutorial
(Every group
needs to change the sample script given in the lab3.pdf, so that it works on the
topology used for Lab1 & Lab2)
4. Lab 4 (Start from
Friday, 03/01/2002)
Useful links:
tcpdump, tcptrace, sock
options
Special
Instruction: Before coming to do this lab every group needs to find an IP
address of a machine with large RTT ( > 700ms) and
also
discard
server running there. To find this do ping to random machines from
windows machine and pick few IP addresses which have
large
RTT. Then try to telnet those IP addresses for port 9 or discard. If succeeds
then means discard server is running
there.
Command: telnet x.y.z.w
9
or
telnet x.y.z.w
discard
Useful
commands:
1. To get analysis of tcpdump output (in long
format)
tcptrace -l
filename
2. To get congestion
window
graph
tcptrace -N filename
3. To send
data using sock (sends 16 packets, each packet size
is 1024 bytes to discard server of
aludra)
/bin/sock -i -n16 aludra.usc.edu discard
5. Lab 5 (Start from Monday,
03/18/2002)
Useful
links: netperf, altq-tips.txt
As extra part, every group can do simulation and compare result with the result
obtained from testbed.
6. Lab 6 (Start from Monday, 04/01/2002)
Also, short demo on GPS and iPAQs
(with wireless support).
- Here is a good link to understand how the Global Positioning System (GPS)
works (GPS
Overview).
- Link for installation of Linux in
iPAQ.. (Handheld.org)
7. Lab 7 (Start
from Monday, 04/08/2002)
Useful links:
tcpdump, tcptrace, sock
options
Also, short demo
on motes and TinyOS.
Useful
commands:
1. To get analysis of tcpdump output (in long
format)
tcptrace -l
filename
2. To get congestion
window
graph
tcptrace -N filename
3. To get all graphs
tcptrace -G filename
4. To send
data using sock (sends 16 packets, each packet size
is 1024 bytes to discard server (port 100) of 192.168.4.1 windows
machine)
/bin/sock -i -n16 192.168.4.1 100
5. To run tcpdump only for port
100,
tcpdump -i xl1 port 100
6. To run tcpdump only for
port 100 and get binary output,
tcpdump -w filename -i xl1 port 100
Extra Exercise:
- Using ping and
traceroute. (due date April 26,
2002)
(Some minor modification may be given
later, but you can start work).
- (3/26) Updated versions (Note .pdf, Exercise .pdf).
-
(3/26) Links for more information on pathchar: