Monday, December 8, 2008

Module One - Internet tools

Here's a traceroute to the curtin.edu.au server, from network-tools.com

TraceRoute to 134.7.179.53 [curtin.edu.au]

Hop(ms)(ms)(ms)
IP AddressHost name
111117
72.249.0.65 -
2131818
209.249.122.73209.249.122.73.available.above.net
3621117
64.125.26.205xe-0-0-0.er1.dfw2.us.above.net
4876
64.125.12.5464.125.12.54.available.above.net
5779
129.250.2.173ae-2.r21.dllstx09.us.bb.gin.ntt.net
6647873
129.250.4.25as-3.r21.snjsca04.us.bb.gin.ntt.net
7585352
129.250.4.118ae-0.r20.plalca01.us.bb.gin.ntt.net
85452Timed out
129.250.3.79p16-0-0-0.r05.plalca01.us.bb.gin.ntt.net
9545255
129.250.10.226p4-0.aarnet.plalca01.us.bb.gin.ntt.net
10212210210
202.158.194.173so-3-3-1.bb1.a.syd.aarnet.net.au
11211209209
202.158.194.198ge-0-0-0.bb1.b.syd.aarnet.net.au
12226226222
202.158.194.33so-2-0-0.bb1.a.mel.aarnet.net.au
13233233233
202.158.194.17so-2-0-0.bb1.a.adl.aarnet.net.au
14260264265
202.158.194.5so-0-1-0.bb1.a.per.aarnet.net.au
15264293259
202.158.198.178gigabitethernet0.er1.curtin.cpe.aarnet.net.au
16261259259
202.158.198.186gw1.er1.curtin.cpe.aarnet.net.au
17Timed outTimed outTimed out

-
18Timed outTimed outTimed out

-
19Timed outTimed outTimed out

-
20262264268
134.7.179.53 -

Trace complete

Looking at that, it tells me that there's 20 hops from there to curtin.edu.au (134.7.179.53) and the average time looks to be about 265 milliseconds, which isn't too bad for a source address in the US. The jump from nnt to aarnet is the main culprit (at hop 9 to 10), with 150 milliseconds being tacked on there. Well, you can't beat the speed of light and that's pretty much what it takes to for light to get from one side of the globe to the other via the fibre-optic cable that's in that hop.

Pinging curtin.edu.au from the nettools site returns an average of 261 milliseconds - pinging from my computer however returns a much more wheezy 1100 milliseconds on average. This is mainly due to the satellite link adding on average about 800-900 milliseconds to everything I access.

Looking then at a traceroute from my computer, it never completes fully to curtin.edu.au, getting lost somewhere in the last few hops of curtin's computer network.

traceroute to 137.4.139.53 (137.4.139.53), 30 hops max, 40 byte packets
1 192.168.5.100 0.517 ms 0.556 ms 0.661 ms
2 192.168.1.25 978.378 ms 1030.286 ms 1299.785 ms
3 203.169.16.37 838.609 ms 926.173 ms 1014.289 ms
4 203.169.16.33 901.807 ms 878.245 ms 1169.051 ms
5 202.142.142.150 690.752 ms 942.883 ms 1346.864 ms
6 202.142.142.145 813.088 ms 1445.575 ms 721.957 ms
7 202.142.143.97 668.695 ms 1432.124 ms 706.238 ms
8 210.80.189.77 1541.364 ms 864.133 ms 690.344 ms
9 210.80.34.221 967.395 ms 1121.390 ms 707.247 ms
10 210.80.33.9 1263.788 ms 917.024 ms 1471.170 ms
11 210.80.50.58 2331.318 ms 1171.324 ms 861.684 ms
12 210.80.4.46 788.692 ms 1401.905 ms 1220.459 ms
13 202.249.2.110 1009.805 ms 1244.279 ms *
14 59.128.7.129 887.954 ms 59.128.7.130 881.134 ms 59.128.7.66 957.427 ms
15 59.128.4.166 1129.960 ms 59.128.4.174 1289.874 ms 59.128.4.70 1041.359 ms
16 203.181.100.158 1007.284 ms 1411.495 ms 203.181.100.174 1087.519 ms
17 59.128.2.74 1781.460 ms 1225.797 ms 892.894 ms
18 63.146.26.69 1534.297 ms 1288.753 ms 1112.930 ms
19 67.14.7.70 1329.015 ms 1215.824 ms 1248.874 ms
20 67.128.87.186 1525.588 ms 1268.134 ms 1104.466 ms
21 198.26.99.25 1725.893 ms 1207.306 ms 1079.079 ms
22 140.52.117.53 1421.106 ms 1084.493 ms 1229.883 ms
23 214.20.22.133 1180.716 ms 1220.947 ms 1087.384 ms
24 214.40.22.178 1348.568 ms 1107.809 ms 1156.763 ms
25 132.3.32.193 1249.906 ms 1061.992 ms 1114.932 ms
26 10.100.32.6 1118.107 ms 1151.573 ms 1338.672 ms
27 137.4.120.11 1110.450 ms 1322.924 ms 1382.136 ms
28 * * *
29 * * *
30 * * *

The first hop from my computer to 192.168.1.25 is the jump across the satellite link and shows the typical delays that I encounter. Every single request performed by my computer has to suffer this delay, so my patience with complex websites that use many tiny images to assemble the page is pretty short.

And speaking of short, it appears that battery life here on my laptop is becoming an issue, so I'll wind it up for today.



No comments: