There seems to be 21 hops to the Curtin server. Amongst the class on the Curtin discussion forum and on the Internet there is some uncertainty in regards to hops with the * * * value. Some sources define it a s a time out or a "packet-filtering" technique.
The hops are pasted below.
Tracing route to curtin.edu.au [134.7.177.136]...
| hop | rtt | rtt | rtt | | ip address | domain name |
| 1 | 5 | 2 | 2 | | 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 | 0 | | 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 | 65 | 44 | 45 | | 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 | 46 | 46 | | 129.250.4.242 | xe-4-4.r04.plalca01.us.bb.gin.ntt.net |
| 10 | 46 | 46 | 46 | | 140.174.28.138 |
|
| 11 | 204 | 204 | 204 | | 202.158.194.173 | so-3-3-1.bb1.a.syd.aarnet.net.au |
| 12 | 205 | 201 | 201 | | 202.158.194.198 | ge-0-0-0.bb1.b.syd.aarnet.net.au |
| 13 | 216 | 216 | 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 | 252 | 252 | 252 | | 202.158.194.5 | so-0-1-0.bb1.a.per.aarnet.net.au |
| 16 | 252 | 252 | 252 | | 202.158.198.178 | gigabitethernet0.er1.curtin.cpe.aarnet.net.au |
| 17 | 252 | 252 | 253 | | 202.158.198.186 | gw1.er1.curtin.cpe.aarnet.net.au |
Trace aborted
-- end --
IP address of Curtin.edu.au =
134.7.177.136Pinging the address curtin.edu.au returns a value of 254ms as the average time take to reach the address.
Found it somewhat
interesting to run these tests from a networking administrator angle. As a web developer
I'm often analysing the size of web pages and how long they take to load. If pages are too "heavy" I reduce them to load quicker. Never really analyse the network and hops though, which is something I should probably be looking at from time to time.
No comments:
Post a Comment