Quote:
Originally Posted by Natsheh
Code:
3 * * * Request timed out. // and why here request timed out ?!
|
Not all packets flowing throw the web can successfully reach their destiny.
So usually there is small a percent loss (or big if the bad cables/traffic overflow).
Therefore, everytime there is a miss hit, is it necessary to try again until you get
what you want to send. Or not, and just accept the failure. It depends on the protocol
you are using. The most famous today I think it it the
TCP/IP pair.
Quote:
Originally Posted by Natsheh
Code:
1 1 ms <1 ms 1 ms 10.0.0.138 // this my router ip address
2 17 ms 17 ms 19 ms 100.68.0.1 // but what is this ip for? is this for my ISP
3 * * * Request timed out. // and why here request timed out ?!
4 19 ms 18 ms 37 ms 10.17.110.90 // and what these three ip's for ??
5 36 ms 18 ms 21 ms 10.17.111.27 // and here i get (Destination net unreachable.)
...
trace route to my public ip address
|
Seems that your ISP could be using several private router before let you reach the internet.
And at the other edge, it is not finding that the ip requested is your own. However,
to respond to a traceroute I think your computer should be running some server as an webserver
accessible from the internet. As you cannot successfully be reachable from the internet,
your cannot trace a route to yourself, until you fix the port forwarding. On the other edge,
I do not if makes sense to trace route to yourself, or if your router can respond a route trace.
__________________