Monday, March 9, 2009

TraceRoute

TraceRoute task I tried the built in software Network Utility that came with the Mac which for some reason I could not get to work. It kept returning time out signals. Then I when to the Mac web site and downloaded Visual TraceRoute which worked first go.

There were 23 hops from my base to curtin.edu.au with hops 1, 20, 21 and 23 failing.
Now I know you have asked for the average time taken to hop but hope you won't be too upset when I say work it out for yourself, the information is below. I don't have the inclination.

The interesting point is that I went through this process three or four times and received the same results when it came to failed hops, it was always hop 1, 20, 21 and 23.

Ideas anyone?

Don't worry about answering I have read some more. According to Wikipedia the act of Traceroute opens up doors for hackers, "Traceroute information has been frequently used by hackers as a way to acquire sensitive information about a company's network architecture." http://en.wikipedia.org/wiki/Traceroute, 13 March 10:15pm
So the hops that consistently lose packets are in all probability being blocked at the server for traceroute requests. I guess the server may be down but I did try traceroute over a few days so I think that's unlikely.

Not being an expert I guess there may be other reason to.

------------------------------------------------
Trace to curtin.edu.au

Hop 1: Reply 1: PACKET LOST
Reply 2: PACKET LOST

Hop 2: core-32-25.grapevine.net.au (203.129.32.25)
Reply 1: 15.664 ms
Reply 2: 12.879 ms

Hop 3: gigabitethernet1-4.core01.eqnx.transact.net.au (202.55.149.209)
Reply 1: 15.160 ms
Reply 2: 11.501 ms

Hop 4: gigabitethernet14-17.core01.gate.transact.net.au (202.55.144.193)
Reply 1: 12.071 ms
Reply 2: 22.742 ms

Hop 5: gigabitethernet1-1.core01.eqnx.transact.net.au (202.55.144.82)
Reply 1: 17.030 ms
Reply 2: 19.115 ms

Hop 6: ge-0-1-0-46.a02.sydnau01.au.ra.gin.ntt.net (202.68.66.57)
Reply 1: 16.912 ms
Reply 2: 20.666 ms

Hop 7: ge-0-0-0.r01.sydnau01.au.bb.gin.ntt.net (202.68.64.225)
Reply 1: 18.272 ms
Reply 2: 16.330 ms

Hop 8: as-0.r01.snjsca04.us.bb.gin.ntt.net (129.250.3.93)
Reply 1: 177.392 ms
Reply 2: 176.178 ms

Hop 9: p16-0-1-1.r21.snjsca04.us.bb.gin.ntt.net (129.250.2.182)
Reply 1: 179.008 ms
Reply 2: 175.100 ms

Hop 10: ae-1.r21.plalca01.us.bb.gin.ntt.net (129.250.5.32)
Reply 1: 178.053 ms
Reply 2: 180.007 ms

Hop 11: po-3.r04.plalca01.us.bb.gin.ntt.net (129.250.2.218)
Reply 1: 179.055 ms
Reply 2: 176.563 ms

Hop 12: 140.174.28.138 (140.174.28.138)
Reply 1: 176.975 ms
Reply 2: 179.716 ms

Hop 13: so-3-3-1.bb1.a.syd.aarnet.net.au (202.158.194.173)
Reply 1: 175.731 ms
Reply 2: 178.296 ms

Hop 14: ge-0-0-0.bb1.b.syd.aarnet.net.au (202.158.194.198)
Reply 1: 180.335 ms
Reply 2: 174.478 ms

Hop 15: so-2-0-0.bb1.a.mel.aarnet.net.au (202.158.194.33)
Reply 1: 185.321 ms
Reply 2: 187.045 ms

Hop 16: so-2-0-0.bb1.a.adl.aarnet.net.au (202.158.194.17)
Reply 1: 193.864 ms
Reply 2: 194.194 ms

Hop 17: so-0-1-0.bb1.a.per.aarnet.net.au (202.158.194.5)
Reply 1: 223.796 ms
Reply 2: 220.002 ms

Hop 18: gigabitethernet0.er1.curtin.cpe.aarnet.net.au (202.158.198.178)
Reply 1: 219.910 ms
Reply 2: 221.319 ms

Hop 19: gw1.er1.curtin.cpe.aarnet.net.au (202.158.198.186)
Reply 1: 226.028 ms
Reply 2: 218.888 ms

Hop 20: Reply 1: PACKET LOST
Reply 2: PACKET LOST

Hop 21: Reply 1: PACKET LOST
Reply 2: PACKET LOST

Hop 22: Reply 1: PACKET LOST
Reply 2: PACKET LOST

Hop 23: systems.curtin.edu.au (134.7.179.56)
Reply 1: 219.450 ms
Reply 2: 223.142 ms



Screen shots and data listed below.

No comments:

Post a Comment