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 posted to their twiki account.
• knuth vs Macs
  While we have tried to make the tools available on knuth and the Macs there are sometimes problems. In general knuth has the least protection issues for network tools, while individual Macs may have limitations..
  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.

• Annotate: What do we mean by <>annotate? If you hand in a paper copy, please highlight where in the printout you have found the answer and add some text (preferably with a colored pen) noting what you found in what you have highlighted. If you hand in an electronic copy, it would be great if you could also highlight and annotate

• Discussion questions
  Be sure to answer them!

Labs

Lab 1
Wireshark Intro

Lab 2


• Be sure to clean up your twiki page!! In particular upload a picture of you and organize your abstracts, labs, and homework directories.

• Wireshark Ethernet

Lab 3
Investigating Networking with Unix Tools

Lab 4
DNS & Sockets -

• My 'reasonably commented' solution for dnsaccess with getaddr, use to work.
  dnsaccess.c
• My 'reasonably commented' solution for echo, use to work.
  echoclient.c
  echoserver.c
• One Team's Solutions, slightly commented
  • DNS Header
  • DNS Routines
  • DNS Main
• Some old code, should work fine.
• UDPEchoServer
• UDPEchoClient
• Some Code from Last year, that worked, some liberaties taken...
• UDP Echo Server
• UDP Echo Client DNS Access

Lab 5
Wireshark, Sockets, DNS

Lab 6

• Arp
  
• ICMP
  
• DHCP



Labs, 7, 8, and 9 are to be done alone. You are free to seek help, but the lab is yours alone. You can also run anywhere you would like: your own machine, Birch lab, Ballon lab, Rock lab, etc.



Lab 7
Wireshark TCP

Lab 8
Wireshark SSL

Lab 9 - Last - Blast
Blast Implementation -

Lab 10:


• Test Prep 1
• Test Prep 1 - ANSWERS



Not updated below



• Lab
  Wireshark At the Top

  Lab

  • 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

  

  

  Not updated below

Lab 6
Blast Implementation -

Lab Notebook

Mike Erlinger

Last Modified Monday, 11-Nov-2019 09:45:50 PST