CSCI 184: Networks II

Class Information

CRN: 35550
News and Notices
Current Exercises:
Type Assign Date Due Date Information
Homework 1 Jan. 13, 2004 Jan. 16, 2004 Assignment (txt).
Exercise 1 Jan. 22, 2004 Jan. 29, 2004 Assignment (pdf).
Homework 2 Feb. 5, 2004 Feb. 10, 17, 2004 Assignment (pdf). The paper to read is A Design Framework for Highly Concurrent Systems. The epoll documentation I handed out consists of the following man pages: epoll.txt, epoll_create.txt, epoll_ctl.txt, epoll_wait.txt.
Note, In class I extended the deadline for Part 2 until tuesday Feb 17th, instead of Feb 12th as stated in the assignment.
Homework 3 Feb. 24, 2004 Mar. 02, 2004 Assignment (txt).
Exercise 2 Emulab and iperf Mar. 9, 2004 Mar. 12/22, 2004 Assignment (pdf).
Final Project Mar. 23, 2004 Mar. 30,April 22, May 4 2004 Assignment (pdf).
For each lecture we will have a link to the slides or lecture notes.

  1. Introduction.
  2. Protocol Security.
  3. Network Security.
  4. Denial of Service.
  5. Wireless Link Security.
  6. IPSEC.
  7. Concurrency.
  8. Network Programming Models.
  9. Operating System Networking.
  10. High Bandwidth Networking Protocols.
  11. Encoding and Modulation.
  12. Ethernet.
  13. Emulab.
  14. Optical Networks.
  15. Myrinet.
  16. Half Pipe.
  17. Flow Control.
  18. Peer to Peer: Chord.
  19. Network Topology.

General course information

For more information about the course please contact the instructor. Their email and phone number can be found on this web page.

Class Schedule
Office Hours
Academic Integrity

Academic Honesty and Ethical behavior are required in this course, as it is in all courses at George Washington University. This course will strictly enforce the University and Computer Science Department's Academic Integrity policies. These policies can be found at:
GW Policy and CS Policy.

The application of the policy to this course is that you must work on your own on all assignments, unless told otherwise in writing. This includes discussing how to work on it and sharing code or solutions. You are also prohibited from altering or falsifying the output of programs. We run all code submissions ourselves and grade based on how they work when we run them. If it appears that you have falsified the reported results it will be treated as severely as if you had cheated or plagerized someone elses work.

You are encouraged to talk with the professor about any questions you have about what is permitted on any particular assignment.

Department of Computer Science The George Washington University