Hello
I’m trying to make a traceroute from Mikrotik using winbox every time I get 100% loss packet
but when I make a traceroute using cmd it gives me 0% loss
I tried other pc the same problem and there are no firewall rules
All useless without concrete example and details.
I did a traceroute for a lot of websites in MikroTik like(8.8.8.
to check the reachability When I do this by using traceroute tool I get loss packet 100% Knowing that I can access to this website .
I tried to do that using cmd and WinMTR I didn't get loss packet (0%)
I just want to know why does it appear like this in winbox?
I’m afraid to write the question… Do you know the difference between traceroute and ping?
amazon.com is not 8.8.8.8
Maybe testing with the same IP would be better…
Have you tried “pinging” amazon.com?..
amazon.com do not like traceroute, also on windows
C:\WINDOWS\system32>tracert amazon.com
Traccia instradamento verso amazon.com [205.251.242.103]
su un massimo di 30 punti di passaggio:
1 <1 ms <1 ms <1 ms cpe.local [192.168.0.101]
2 7 ms 9 ms 6 ms 100.64.0.0
3 8 ms 8 ms 8 ms 100.64.0.255
4 11 ms 7 ms 10 ms xe-6-6-6.cr3-rom4.ip4.gtt.net [212.222.23.47]
5 147 ms 106 ms 108 ms ae23.cr3-nyc6.ip4.gtt.net [89.149.116.227]
6 109 ms 108 ms 109 ms ip4.gtt.net [209.120.155.138]
7 109 ms 108 ms 124 ms 150.222.68.16
8 233 ms 251 ms 121 ms 150.222.68.17
9 * * * Richiesta scaduta.
10 126 ms 121 ms 112 ms 150.222.68.8
11 * * * Richiesta scaduta.
12 * * * Richiesta scaduta.
13 * * * Richiesta scaduta.
14 * * * Richiesta scaduta.
15 * * * Richiesta scaduta.
16 * * * Richiesta scaduta.
17 * * * Richiesta scaduta.
18 * * * Richiesta scaduta.
19 * * * Richiesta scaduta.
20 * * * Richiesta scaduta.
21 * * * Richiesta scaduta.
22 * * * Richiesta scaduta.
23 112 ms 110 ms 111 ms s3-console-us-standard.console.aws.amazon.com [205.251.242.103]
Traccia completata.
by using traceroute tool I get loss packet 100%
Depends on what you understand by 100% loss.
You show an exemple where the first 13 hops are all reponding properly.
From the 14th hop there is no answer anymore . Either those routers are configured to not answer (very common setup on the internet) or the answer does not reach you.
As @rextended shows, some router further away (more hops away ) may answer, even if intermediate routers do not answer.
Carefull also with Google and Amazon and CDN (content delivery network), they have many servers with exact the same IP address but on different locations
(https://networkengineering.stackexchange.com/questions/48125/single-public-ip-address-for-multiple-physical-locations)
thank you for reply
the thing is I can reach the website correctly without any issues but on the Mikrotik (winbox) when I make a traceroute it gives me 100% loss(last 5 hops there is no answer Like the picture that I sent I tried winMTR it worked and gave me 0% loss packet. And as you said if the routers are configured to not answer can I reach the website?
on winbox traceroute result 100% loss packet
on winMTR 0% loss packet
my website is reachable but the result on Winbox gives me 100% packet loss !!
(Note: I do a traceroute for a certain website ,there is no firewall rules to block ICMP traffic)
Ahem … Traceroute in Winbox, is actually Traceroute of the RouterOS with start and output in WinBox.
Could also be started from “Terminal”, or Webfig
And it seems that the RouterOS by default gives up early. After 5 timeouts? Or limit number of Hops?
http://forum.mikrotik.com/t/why-tool-traceroute-limited-to-14-hops/153581/1
Force the number of Max Hops (via Winbox, Terminal (CLI) or Webfig), and see if it gets any further.
PC’s tend to have Max Hops of 32.
I increased the Max hops to 50 the same as well and the host is empty (no reply ) as you see after hop 15 to 50 no reply
50 hops … that’s far away. Might hit the 1000ms time-out setting.
Also happens when there is a loop somewhere … even my 28 was already a very very long path