Due Wednesday, 1/9/02. Questions on RFCs 1436, 2026, and 2028.
Due Wednesday, 1/16/02 and Thursday, 1/17/02. Implementing gopher.
Due 9:00PM Monday, 1/28/02. You may work with one partner or alone.
Modify the cnet code stopandwait.c to use piggybacking and a 4-node fully connected network. See sections 8.2 and 8.3 of Getting started with cnet for more details.
Write your code in such a way that you can easily regulate the size of the network (either 2 or 4 nodes) and whether piggybacking is or is not being used. Probably the easiest way to do this is to use #ifdef statements, but you can use something more elegant if you wish.
When your code is working, run the network for an hour of simulation time and save the summary of statistics. Do this four times--once each for 2-node and 4-node networks with piggybacking on or off. Report the statistics in each case, and write an analysis of the statistics. Put your code in piggyback.c and piggyback.h, your analysis in analysis.txt. Put them all in a directory called piggyback, and use HSP to submit the directory.
Due 8:30AM Wednesday, 2/6/02. Do problems 1, 4, 6, 10, 15, 20, 23, and 26 from Chapter 2 of Peterson and Davie. Also, do problems 1, 3, 15 from Chapter 3, and problems 12, 13, and 15 from Chapter 4. Hand them in on paper.
Due 5:00 PM Friday, 2/22/02. Distance vector routing.
Due 5:00 PM Saturday, 3/16/02. Final project
1/4/02. Sign up for the Internet Engineering Task Force (IETF) general discussion mailing list. Instructions are at http://www.ietf.org/maillist.html. This will generate kind of a lot of e-mail for you, but I want you to see what kinds of technical issues are being worked on at the moment.
1/4/02. If you have never installed a network card into a computer, you ought to do so. Find a time when Mike Tie or Jeff Ondich can let you into CMC 318 to do a brief (less than half an hour) card installation exercise. If you have done this sort of thing before, don't bother to do this.