Not able to Reverse Traceroute/MTR.

Lolita_Magnum

Lolita_Magnum

ᓚᘏᗢ
Messages
2,150
Location
Mumbai
ISP
AS17665
AS11158
Traceroute client-side works just fine, but traceroute from server-side does not work. I understand since it's CG-NAT that the main Public IP assigned will not be pingable but at least shouldn't it trace to my nearest gateway?
A different ISP using CG-NAT was also traceable at least to my nearest gateway.

From Server-Side:
1.|-- 217.146.12.50 0.0% 0 10 10 0.2 0.2 0.3 0.4 0.1 0.2 0.0 0.1 0.1 0.4
2.|-- 103.224.241.1 0.0% 0 10 10 1.1 1.1 2.2 3.9 0.9 2.1 1.3 0.8 2.1 6.2
3.|-- 59.163.29.81.static.vsnl.net.in (59.163.29.81) 0.0% 0 10 10 1.6 1.5 1.8 2.5 0.4 1.8 0.0 0.4 1.0 3.1
4.|-- 172.28.176.205 0.0% 0 10 10 2.4 2.2 2.6 4.6 0.7 2.5 0.1 0.6 2.2 3.8
5.|-- 121.241.7.78.mumbai-static.vsnl.net.in (121.241.7.78) 0.0% 0 10 10 15.7 15.6 25.2 64.4 16.9 21.7 0.0 18.8 48.7 146.7
6.|-- ??? 100.0 10 0 10 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Click to expand...

From Client-Side:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 1 ms 1 ms 103.170.80.3
3 2 ms 2 ms 2 ms 103.170.80.1
4 3 ms 4 ms 3 ms 121.241.7.78.mumbai-static.vsnl.net.in [121.241.7.78]
5 5 ms 5 ms 3 ms ix-ae-1-100.tcore2.mlv-mumbai.as6453.net [180.87.39.25]
6 * * * Request timed out.
7 131 ms * 132 ms if-ae-2-2.tcore2.l78-london.as6453.net [80.231.131.1]
Click to expand...

It seems that '103.170.80.1' and '103.170.80.3' are missing in reverse, is this a common/normal occurrence? Do you guys experience the same on Excitel?
I hope my question is not stupid.

By the way, the mentioned IPs are pingable from outbound.

PING 103.170.80.3 (103.170.80.3) 56(84) bytes of data.
64 bytes from 103.170.80.3: icmp_seq=10 ttl=50 time=243 ms
--- 103.170.80.3 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 895ms
rtt min/avg/max/mdev = 242.703/248.776/283.819/12.663 ms, pipe 2
Click to expand...
 
Can you try different variations of MTR.
With ICMP, UDP and TCP. One of them will work.

Though this is expected, atleast on excitel. I. See the same results as above.
The 103.xx based routers seem to drop non icmp packets on the outbound facing link.
 
Reverse trace is only possible if you have access to the destination router.
Most ISPs provide with a looking glass, unless your issue is not specific that should help.
 

Top