Thursday, December 6, 2007

Module One Internet Tools Task

Trace route

Tracing route to curtin.edu.au [134.7.179.53]...
hop
rtt
rtt
rtt

ip address
domain name

1
0
1
1

70.84.211.97
61.d3.5446.static.theplanet.com

2
0
0
0

70.84.160.162
vl2.dsr02.dllstx5.theplanet.com

3
126
0
0

70.85.127.109
po52.dsr02.dllstx3.theplanet.com

4
0
0
0

70.87.253.21
et3-1.ibr03.dllstx3.theplanet.com

5
0
0
0

157.238.225.5
xe-4-4.r03.dllstx09.us.bb.gin.ntt.net

6
37
0
0

129.250.2.153
ae-2.r20.dllstx09.us.bb.gin.ntt.net

7
7
10
8

129.250.3.130
as-0.r20.hstntx01.us.bb.gin.ntt.net

8
8
8
7

129.250.3.25
ae-0.r21.hstntx01.us.bb.gin.ntt.net

9
52
61
52

129.250.3.121
as-1.r21.lsanca03.us.bb.gin.ntt.net

10
52
52
52

129.250.3.159
p16-1-0-0.r02.lsanca03.us.bb.gin.ntt.net

11
49
49
49

198.172.90.102
p4-4-1-0.r02.lsanca03.us.ce.gin.ntt.net

12
205
201
201

202.158.194.153
so-3-2-0.bb1.b.syd.aarnet.net.au

13
217
216
213

202.158.194.33
so-2-0-0.bb1.a.mel.aarnet.net.au

14
224
236
226

202.158.194.17
so-2-0-0.bb1.a.adl.aarnet.net.au

15
252
248
253

202.158.194.5
so-0-1-0.bb1.a.per.aarnet.net.au

16
252
252
249

202.158.198.178
gigabitethernet0.er1.curtin.cpe.aarnet.net.au

17
252
249
254

202.158.198.186
gw1.er1.curtin.cpe.aarnet.net.au

18
254
254
254

134.7.16.46


19
254
254
252

134.7.248.65
te1-1.b309-sr.net.curtin.edu.au

20
254
254
254

134.7.179.53

Trace complete
-- end --

Ping

Pinging curtin.edu.au [134.7.179.53] with 32 bytes of data...
Results
count
ttl (hops)
rtt (ms)

from



1
112
247

134.7.179.53



2
112
249

134.7.179.53



3
112
249

134.7.179.53



4
112
247

134.7.179.53



5
112
252

134.7.179.53


Statistics
packets
sent
5


received
5
100%

lost
0
0%




times (ms)
min
247


avg
249


max
252

-- end --




Task Questions

IP # of the Hostname; Curtin.edu.au - 134.7.179.53
Number of hops- ???????? 20 or 112
Average time in m/s from tool site to Curtin server- 249ms

Description

I found the text on routers (http://www.howstuffworks.com/) quite fascinating..... Maybe it was the late hour. I suspect it’s because I actually understood it. I carried out the trace route task with some problems interpreting data not with the actual program download or usage.


Concerns

I have at least 2 answers to the question about hops at the end of the task.
Problem: I had trouble interpreting the data. I found the hostnames IP addy ok but the average in m/s wasn't clear at first and I still have two answers for the number of hops; i.e; 20 or 112.....


Analysis

I have use http://mirc.com/ a lot over the last 10 years and I’m familiar with the term 'ping' from there but understanding trace routes and finding MS-Prompt brings a whole new level of ping-knowledge. It's very useful to know how to do it for any site.

Via http://howstuffworks.com/, I tried out the MS DOS-Prompt command. I used it on howstuffworks.com. I believe it shows me the route my computer goes through to get to a site; i.e; the servers it travels through and the time it takes to do that. I think the term "my computer" in that last sentence needs some fleshing out. I also want to find the trace route for when I send email via outlook express. When I do, I'll post it.

Conclusion

My understanding of the applications for my new knowledge of trace routes and 'ping-ing' is;
a) if there was a problem with receiving/sending mail or files, the user can check the route the 'packets' of data have taken and the time it's taking these 'packets' to go through servers.
b) in a live real time chat relay program (like mirc), the user can check the time it's taking for their message to reach the host site. I often use the trivia channels on mirc and timing is essential to winning!!

In the context of concept #23; Human-Computer Interface, I think humans are used to a certain 'flow' and timing in conversations.Because we are not face to face with the other user/s we rely on their responses and (to a lesser degree) the time it takes them to respond to make our judgement on and form our opinions about the other user/s. Delayed responses can hinder our progress in creating meaningful contact with other users.

No comments: