Well i am back and continuing on my work of the activities for Module one.
My first task for this was to look at the How Stuff Works on Traceroutes. Now i understood what it was saying, while skimming over the technical names for some of the components, but due to the title of the article the link from Mod 1 took me to, I wasn't sure that i was reading the right thing! Before continuing on to the practical side of this activity i decided to do a little more research into "Traceroutes". Using my search engine of choice (google) i entered in a search for "Traceroute explanation". As you are probably all expecting (but i'm not sure that i was!) i had a huge result. I usually choose the link to go to by skimming the little explanation paragraph under each link. Finding one that promised an explanation with diagrams (beauty!) I followed this link, but was disappointingly taken to a forum that required membership (free). So i tried again. Top of the list i followed through this link and got this fantastic description! Things could not be clearer for me now...
Traceroute is the program that shows you the route over the network between two systems, listing all the intermediate routers a connection must pass through to get to its destination. It can help you determine why your connections to a given server might be poor, and can often help you figure out where exactly the problem is. It also shows you how systems are connected to each other, letting you see how your ISP connects to the Internet as well as how the target system is connected. This quote was taken from
here.
I really wanted to see how all this works, so i decided to continue on with the activities. Firstly i used the free tools to traceroute to curtin.edu.au. I was a bit thrown by these sites to begin with - i used the first link first (
http://centralops.net/co/) but found that i didn't really know what i was doing. I had a bit more of a look around the internet at various traceroute apps - then reread the instructions for the activity. Opening the second provided link (
http://network- tools.com/ ) i decided to go on blind faith and just copy/pasted the curtin server into the box provided and recieved the following results:
134.7.179.53 is from Australia(AU) in region Oceana
TraceRoute to 134.7.179.53 [curtin.edu.au]
| Hop | (ms) | (ms) | (ms) |
| IP Address | Host name |
| 1 | 0 | 0 | 1 |
| 66.98.244.1 | gphou-66-98-244-1.ev1servers.net |
| 2 | 0 | 0 | 0 |
| 66.98.241.13 | gphou-66-98-241-13.ev1servers.net |
| 3 | 0 | 0 | 0 |
| 66.98.240.5 | gphou-66-98-240-5.ev1servers.net |
| 4 | 1 | 1 | 1 |
| 129.250.10.189 | ge-1-14.r04.hstntx01.us.bb.gin.ntt.net |
| 5 | 1 | 1 | 1 |
| 129.250.2.230 | xe-0-1-0.r21.hstntx01.us.bb.gin.ntt.net |
| 6 | 43 | 43 | 43 |
| 129.250.3.121 | as-1.r21.lsanca03.us.bb.gin.ntt.net |
| 7 | 43 | 43 | 50 |
| 129.250.3.159 | p16-1-0-0.r02.lsanca03.us.bb.gin.ntt.net |
| 8 | 203 | 202 | 203 |
| 198.172.90.102 | p4-4-1-0.r02.lsanca03.us.ce.gin.ntt.net |
| 9 | 197 | 198 | 203 |
| 202.158.194.157 | so-3-3-1.bb1.b.syd.aarnet.net.au |
| 10 | 209 | 215 | 210 |
| 202.158.194.33 | so-2-0-0.bb1.a.mel.aarnet.net.au |
| 11 | 223 | 219 | 218 |
| 202.158.194.17 | so-2-0-0.bb1.a.adl.aarnet.net.au |
| 12 | 251 | 245 | 251 |
| 202.158.194.5 | so-0-1-0.bb1.a.per.aarnet.net.au |
| 13 | 249 | 251 | 249 |
| 202.158.198.178 | gigabitethernet0.er1.curtin.cpe.aarnet.net.au |
| 14 | 246 | 249 | 252 |
| 202.158.198.186 | gw1.er1.curtin.cpe.aarnet.net.au |
| 16 | 251 | 250 | 251 |
| 134.7.248.65 | te1-1.b309-sr.net.curtin.edu.au |
| 17 | 250 | 251 | 250 |
| 134.7.179.53 | - |
Trace complete
This means that as shown - there was 17 hops to get to curtin.edu.au and it took approx 250ms to get there!
The IP address that i traced to for curtin.edu.au was 134.7.179.53 as shown in the above results.
Will be tackling the further explanation later!
Bye for now! Kellie.
No comments:
Post a Comment