Hi
We are having issues with Static trace. We have RB1200 Firmware 3.07, Package Version 5.26.
196.6.242.1 (RB1200)
196.6.242.30(Linux Server)
41.162.57.148(Provider SBC)
172.24.29.17(Provider Gateway)
__Static:
8 A S ;;; Crossconnect
dst-address=41.162.57.148/32 gateway=172.24.29.17 gateway-status=172.24.29.17 reachable via ether5 distance=1 scope=30 target-scope=10
From the Router to 41.162.57.148:
/tool traceroute 41.162.57.148
ADDRESS RT1 RT2 RT3
1 172.24.29.17 1ms 1ms ms
2 0.0.0.0 0ms 0ms 0ms_**
From Server to 41.162.57.148 ;
[root@kensington ~]# tracepath 41.162.57.148
1: 196.6.242.30 (196.6.242.30) 0.136ms pmtu 1500
1: 196.6.242.1 (196.6.242.1) 0.282ms
2: no reply
3: no reply
From the Server the second hop should be 172.24.29.17 as it is on the router. That is the provider Gateway. 
Please assist a bigginer._**
You see hops only if router/gateway decrease TTL of packet…
Is this a new circuit?
Sadly more often than not I have providers mis-provision address ranges to the clients we work with. It is possible if your seeing zeros that your provider doesn’t know how to get back to you.
Ryan
rextended,
Because the forums do not allow me to message you privately I am posting this here.
It seems you have reduced my karma and posted these couple of links which the forum has attached to a message and sent to me.
I do not understand your actions here. I diagnose remote networks for a living and have just recently joined the forums as a way to give back to the community.
I also find your removal of karma insulting as I know I am correct in these matters. Anytime a 0.0.0.0 shows up in trace (unless it is MPLS) this means that a route is invalid and the provider does not know how to get back to the sending device which includes means of ICMP reply to notifiy the end device that such an end point isn’t available. According to your prior post a router that would decrement the TTL to 0 would send back an ICMP TTL Expired in transit message to the sending device so that it understands the route is too long or there is a modification changing TTL length to zero. According to the OP their trace is not doing so indicating a bad return route from the provider since they can ping the provider demarc gateway.
Until you can respond decisively and intelligently to karma changes I would appreciate you not giving anyone, not just me, negative karma as it was your choice to do this and you could have left it alone and posted a useful response instead.
Remember you who has wrote this?
Is this a new circuit?
The Karma is decreased accordingly.
In this forum each one can tell their opinion without “making fun” the others…