Networks -- CS 125

Check the Schedule/Calendar for the latest info on due dates, lectures, homeworks, labs, grutoring, etc.

Some important comments about Labs in general:

• Since most labs are PAIRS, please put both names on whatever you submit. Both people should have a copy of the lab report post.
• knuth vs Macs vs wilkes
  While we have tried to make the tools available on knuth and the Macs there are sometimes problems. In general wilkes has the least protection issues for network tools.
  Using Xforwarding works well, e.g., ssh -X mike@wilkes.cs.hmc.edu, for tools like Wireshark

• Tool Parameters
  Tool parameters vary by implementation. Each implementation tends to screw around with the parameters. So do a man and figure out what is required.

• Discussion questions
  Be sure to answer them!

Labs

Lab 1
Wireshark Intro

Lab 2
Wireshark At the Top

Lab 3
Investigating Networking with Unix Tools

Lab 4

• Wireshark Ethernet
• Clean up the c header file for IP that is attached. In particular, see if you can fix the address class definitions and the IP Header Stuct. IP Header Struct

Lab 5

• Arp
  
• ICMP
  
• DHCP

Lab 6
DNS & Sockets -

Lab 7
Wireshark, Sockets, DNS

Lab 8 - Last

Lab 8a:
Test Prep 1
Test Prep 1 - ANSWERS

Lab 8b:
The following is a test from a previous class that used a different book with a more low level emphasis. Rather than observing and evaluating network traffic, the labs in the previous course were low level coding. Thus the emphasis in the test was different. I do NOT expect you to answer all the questions nor do I expect you to do the Closed Book part closed book!! Test Preparation

Not updated below

Lab X
Emulab: Tutorial -

Lab X
Emulab: Networking & Routing -

Lab 6
Blast Implementation -

Lab

Lab 1

Lab Notebook

Mike Erlinger

Last Modified Monday, 03-Dec-2018 14:17:24 PST