Trace route

Have you ever wondered which route your packets take to reach their destination host when you use the internet, or even how it works ? Before we jump into the route tracing part, you must know some basic stuff about the IP(internet protocol) protocol.

Generally a workstation is somehow connected to the internet. When the user (client) request an website using his/her browser, or performs other activities on the internet, the IP protocol has work to do. The IP protocol is responsible for routing packets (or datagrams) over the internet. Don’t think packets will directly reach their destination, actually the IP protocol transfers packets from host to host. This “from host to host” is technically called “hops”.

When you landed on this website, you’re browser used the TCP/IP protocol to get this page. You actually did send a request(first hop) to your ISP(Internet Service Provider) and your ISP forwarded your request to another host (second hop) which is closer to this website. The receiving host will forward your request accordingly (third hop) and so on till the packet has reached it’s destination using the quickest way possible…. After a some “hops” your request will reach it’s destination which answers accordingly using some other or maybe the same hops back.

Simple scheme how the IP protocol works (hops)

You are able to check out how many hops, including the identity’s, your packet makes on it’s ride on the IP train.
If you are using windows, open a new “prompt” window (Start -> Run -> type: “cmd”).

If you are using Unix use: “traceroute”.

Now type:

tracert online-source.net

You’re box should show something like the above screenshot. Right now all passed DNS-names along with their IP addresses are shown. If you only want to know the IP addresses (also a little faster) you have to type:

tracert -d online-source.net

For the complete syntax type:

tracert

• 

Mail this!