Class Schedule
21 Aug | intro
23 Aug | clients
28 Aug | servers
30 Aug | networks |
inter-networks |
paths |
IP v. URL addressing |
next session
04 Sep | basics lab
06 Sep | structural layer
11 Sep | presentational layer
18 Sep | working with layers
20 Sep | behavior layer
25 Sep | images & design
27 Sep | website lab
02 Oct | object layers
04 Oct | tools that read markup
09 Oct | document markup lab
11 Oct | spreadsheets, formulas & functions
16 Oct | data display
18 Oct | Fall Break
23 Oct | database tools
25 Oct | spreadsheets lab
30 Oct | relational databases
01 Nov | tables
06 Nov | relationships
08 Nov | input & output
13 Nov | SQL
15 Nov | complex queries
20 Nov | databases lab
22 Nov | Thanksgiving
27 Nov | presentation design
29 Nov | presentation delivery
04 Dec | presentation lab
13 Dec | 0800-1100 | final in class presentation
This work
is licensed under a
Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.
home & schedule | class blog | syllabus | contact | grades
Use a traceroute tool and explain the difference between IP addresses and URLs
Remember our convention.
commandsargumentvalue
Using a traceroute tool, trace the route the packets take from your computer (whether you start with your client or with a server) to any domain name you are interested in.
Please run a traceroute on its domain name (in this case, you will need to include the full www.name.top_level_domain), then copy and paste a screenshot of your results into a file. We are interested in how many hops it takes to get from your location to this site. If the trace can tell exactly where this site is, I will see it in your screenshot. If the trace times out prior to reaching the site, I will see how many hops it took prior to timing out.
If you don't have any domain names you are interested in, here are a few you can use.
Use your ALT+PrtSc tool to capture a screenshot of the data you want, then save the captured image into a file of some sort. It could be a .docx file, a .rtf file, a .pptx file; it just needs to be a file that can hold the image. If you can save the image as a .jpg, .png, or any other image format, that would suffice as well. It just needs to be able to be downloaded.
After you have saved the file on your client, FTP it into your password-protected directory, from where it can be retrieved.
The structure takes advantage of how operating systems want to index things.
LastName.FirstName(s).YYYYMMDD.TaskNN.descriptor.file extension
An example might be
johnson.pat.20180830.task01.06.traceroute.pdf
Send me the file name.
Whether or not the traceroute times out prior to arriving at this site, I would like you to do answer one question as well.
You can add this to your email note.
Can you describe the difference between the IP address and the URL? Why does the trace go to an IP address and not to a URL?
You are to do the traceroute, but you can also see a web based traceroute tool do the same thing.