Difference between revisions of "COMP 3000 Lab 7 2011"

From Soma-notes
Jump to navigation Jump to search
Line 12: Line 12:


==Part B==
==Part B==
# Why does <tt>tracepath</tt> return "no reply" sometimes?

Revision as of 16:22, 20 November 2011

A few guidelines:

  • Submit your solutions for both Part A and Part B via WebCT by Sunday, November 27th at 11:30 PM.
  • Please answer using a single text file (with a .txt extension). Do not submit doc, docx, pdf, or other formats. Also, please do not submit an archive (zip, tarball, rar) of multiple text files, just upload one. (Please don't just cut and paste your work into a text box on webct.) Anything other than a single text file will receive -1 points
  • Show all your work. If you find an answer by browsing code, explain your search path (e.g., I searched for X, which led me to source file Y, where I found function Z.) Also, list any websites or individuals you consult.
  • Do all of the following on a UNIX-like system. Ubuntu Linux is guaranteed to work, but other systems, including MacOS X, should work.

Part A

  1. Run ifconfig. For all configured interfaces except loopback, there should be an "inet" address, a "HWaddr" (hardware) address, and perhaps even an "inet6" address. Each of these addresses identifies the computer within a certain context. In what context are each of these addresses used? Specifically, for what protocol is the address used, and what other computers can access this one using this address? (Ignore NAT issues.)
  2. How could you use netcat (nc) to listen on port 9200 and write received data to the file /tmp/foo?
  3. What does tracepath slashdot.org return?

Part B

  1. Why does tracepath return "no reply" sometimes?