Internet Tools: Task 1
route provided by http://centralops.net/co/
Tracing route to curtin.edu.au [134.7.179.53]...
| hop | rtt | rtt | rtt |
| ip address | domain name |
| 1 | 0 | 0 | 0 |
| 70.84.211.97 | 61.d3.5446.static.theplanet.com |
| 2 | 0 | 0 | 0 |
| 70.87.254.5 | 5.fe.5746.static.theplanet.com |
| 3 | 0 | 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 | 1 |
| 157.238.225.5 | xe-4-4.r03.dllstx09.us.bb.gin.ntt.net |
| 6 | 0 | 0 | 0 |
| 129.250.2.173 | ae-2.r21.dllstx09.us.bb.gin.ntt.net |
| 7 | 44 | 44 | 61 |
| 129.250.4.25 | as-3.r21.snjsca04.us.bb.gin.ntt.net |
| 8 | 46 | 46 | 46 |
| 129.250.4.118 | ae-0.r20.plalca01.us.bb.gin.ntt.net |
| 9 | 46 | 83 | 46 |
| 129.250.3.79 | p16-0-0-0.r05.plalca01.us.bb.gin.ntt.net |
| 10 | 46 | 47 | 46 |
| 129.250.10.226 | p4-0.aarnet.plalca01.us.bb.gin.ntt.net |
| 11 | 204 | 204 | 204 |
| 202.158.194.173 | so-3-3-1.bb1.a.syd.aarnet.net.au |
| 12 | 201 | 201 | 201 |
| 202.158.194.198 | ge-0-0-0.bb1.b.syd.aarnet.net.au |
| 13 | 216 | 217 | 216 |
| 202.158.194.33 | so-2-0-0.bb1.a.mel.aarnet.net.au |
| 14 | 225 | 225 | 225 |
| 202.158.194.17 | so-2-0-0.bb1.a.adl.aarnet.net.au |
| 15 | 253 | 253 | 253 |
| 202.158.194.5 | so-0-1-0.bb1.a.per.aarnet.net.au |
| 16 | 253 | 253 | 253 |
| 202.158.198.178 | gigabitethernet0.er1.curtin.cpe.aarnet.net.au |
| 17 | 253 | 253 | 253 |
| 202.158.198.186 | gw1.er1.curtin.cpe.aarnet.net.au |
| 21 | 254 | 254 | 255 |
| 134.7.179.53 |
|
Trace complete
-- end --
How many ‘hops’ are there?20- although the first few appear to be internal. Likely to be a virtually hosted server.
what is the average time in milliseconds from the tools site to the curtin server?Im having trouble with this one. If traceroute determines the time between routers, and the final time is not massively larger (ie, a sum off) all the other times, then how can you determine the
average time in milliseconds from the tools site to the curtin server?Obviously, you could just add up all the hops, however this seems counter intuitive, and the
references given for this task imply that the number is indicated in the output of the traceroute. In fact,
this link seems to indicate that one of the primary functions for using traceroute as a diagnostic tool, is not to find the overall ping time, but to identify where problems (ie, slow packet transfer) is occuring.
Further research has revealed the answer
here. the ping time, is not measured
between hops it is measured from the originating server, to a
particular router. So, in this case, the average (assuming that the server sends a series of packets and returns an average result) time to return a result is:
or, 255ms both ways, or 125ish ms 1 way.
No comments:
Post a Comment