Reference: http://communication.howstuffworks.com/convergence/router10.htm
The first number shows how many routers are between your computer and the router shown. In this instance, there were a total of 14 routers involved in the process (number 15 is the Howstuffworks.com Web server). The next three numbers show how long it takes a packet of information to move from your computer to the router shown and back again. Next, in this example, starting with step six, comes the "name" of the router or server. This is something that helps people looking at the list but is of no importance to the routers and computers as they move traffic along the Internet. Finally, you see the Internet Protocol (IP) address of each computer or router. The final picture of this trace route shows that there were 14 routers between the Web server and me and that it took, on average, a little more than 2.5 seconds for information to get from my computer to the server and back again.
You can see that it took only one more step to reach a Web server on the other side of the Atlantic Ocean than it did to reach a server two states away!
Tracing a Message
If you're using a Microsoft Windows-based system, you can see just how many routers are involved in your Internet traffic by using a program you have on your computer. The program is called Traceroute, and that describes what it does -- it traces the route that a packet of information takes to get from your computer to another computer connected to the Internet. To run this program, click on the "MS-DOS Prompt" icon on the "Start" menu. Then, at the"C:\WINDOWS>" prompt, type "tracert www.howstuffworks.com". When I did this from my office in Florida, the results looked like this:
The first number shows how many routers are between your computer and the router shown. In this instance, there were a total of 14 routers involved in the process (number 15 is the Howstuffworks.com Web server). The next three numbers show how long it takes a packet of information to move from your computer to the router shown and back again. Next, in this example, starting with step six, comes the "name" of the router or server. This is something that helps people looking at the list but is of no importance to the routers and computers as they move traffic along the Internet. Finally, you see the Internet Protocol (IP) address of each computer or router. The final picture of this trace route shows that there were 14 routers between the Web server and me and that it took, on average, a little more than 2.5 seconds for information to get from my computer to the server and back again.
You can use Traceroute to see how many routers are between you and any other computer you can name or know the IP address for. It can be interesting to see how many steps are required to get to computers outside your nation. Since I live in the United States, I decided to see how many routers were between my computer and the Web server for the British Broadcasting Corporation. At the C:\WINDOWS> prompt, I typed tracert www.bbc.com. The result was this:
You can see that it took only one more step to reach a Web server on the other side of the Atlantic Ocean than it did to reach a server two states away!
It surely works, when tried from a place in North India;
C:\>cd windows
C:\WINDOWS>tracert www.howstuffworks.com
Tracing route to a462.g.akamai.net [96.17.182.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 30 ms 31 ms 33 ms ABTS-North-Static-157.130.160.122.airtelbroadband.in [122.160.130.157]
3 29 ms 31 ms 29 ms ABTS-North-Static-153.130.160.122.airtelbroadband.in [122.160.130.153]
4 30 ms 31 ms 29 ms 125.19.22.145
5 30 ms 30 ms 31 ms 59.145.7.230
6 30 ms 34 ms 34 ms a96-17-182-8.deploy.akamaitechnologies.com [96.17.182.8]
Trace complete.
C:\WINDOWS>
C:\WINDOWS>tracert www.yahoo.com
Tracing route to any-fp.wa1.b.yahoo.com [69.147.125.65]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 35 ms 47 ms 31 ms ABTS-North-Static-157.130.160.122.airtelbroadband.in [122.160.130.157]
3 31 ms 29 ms 29 ms ABTS-North-Static-149.130.160.122.airtelbroadband.in [122.160.130.149]
4 29 ms 29 ms 29 ms 203.101.83.197
5 50 ms 50 ms 49 ms 203.101.100.22
6 195 ms 195 ms 195 ms so-4-0-3-zcr2.lnt.cw.net [166.63.223.69]
7 195 ms 195 ms 195 ms so-5-2-0-dcr2.tsd.cw.net [195.2.10.134]
8 205 ms 195 ms 195 ms xe-0-3-0-xcr1.lnd.cw.net [195.2.25.1]
9 306 ms 325 ms 306 ms ge-11-0-0-xcr1.nyk.cw.net [195.2.25.18]
10 359 ms 276 ms 277 ms pat1.nyc.yahoo.com [198.32.118.24]
11 279 ms 279 ms 279 ms ae-8.pat1.dcp.yahoo.com [216.115.101.157]
12 277 ms 294 ms 294 ms ae-2-d170.msr2.re1.yahoo.com [216.115.108.69]
13 305 ms 280 ms 278 ms te-9-4.bas-a2.re1.yahoo.com [66.196.112.203]
14 277 ms 276 ms 280 ms ir1.fp.vip.re1.yahoo.com [69.147.125.65]
Trace complete.
2 comments:
Every weekend i used to pay a visit this website,
as i want enjoyment, since this this web site conations genuinely fastidious funny data too.
Feel free to visit my web site : click through the following document
It's actually very difficult in this full of activity life to listen news on Television,
therefore I just use internet for that purpose, and obtain the
newest information.
Post a Comment