Max transit cat 18 traceroute shows only last hop?

Got a Max Transit Cat 18 on Friday and am using it with T-mobile.

Strange thing I noticed today is that from a windows client, a tracert or winmtr shows only the max transit first hop and last hop of the destination. All hops in between are not there. I have not seen this before, and thought it may be a windows 10 issue, so I logged into the max transit itself.

From system, traceroute, I did the following traceroutes from the max transit, and it shows only one hop:

Connection: Cellular
Destination: google.com
Results
traceroute to google.com (216.58.193.142), 30 hops max, 60 byte packets
1 dfw25s34-in-f14.1e100.net (216.58.193.142) 70.670 ms 70.465 ms 70.278 ms

Connection: Cellular
Destination: 8.8.8.8
Results
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 dns.google (8.8.8.8) 45.529 ms 45.226 ms 57.258 ms

Connection: Cellular
Destination: peplink.com
Results
traceroute to peplink.com (104.25.205.4), 30 hops max, 60 byte packets
1 104.25.205.4 (104.25.205.4) 51.357 ms 51.110 ms 63.160 ms

Has anyone seen this before with a max transit or t-mobile?

Edit: installed an AT&T sim, and Iā€™m getting the same thing on AT&T in the max transit. So it appears there must be a setting in the max transit causing this. Any ideas?

With AT&T SIM installed, going to system, tools, traceroute on the max transit cat 18, the following is the result (all hops missing except for final destination hop)

Connection: Cellular
Destination: peplink.com
Results
traceroute to peplink.com (104.25.205.4), 30 hops max, 60 byte packets
1 104.25.205.4 (104.25.205.4) 54.749 ms 66.563 ms 66.391 ms

Plugged the Max Transit Cat 18ā€™s wan port into the lan of another router.

System -> Traceroute using the Max Transit Cat 18ā€™s Ethernet WAN returns a normal traceroute to google.com (14 hops listed.)

System -> Traceroute using the Max Transit Cat 18ā€™s Cellular WAN returns a truncated traceroute with only one hop
Results
traceroute to google.com (172.217.2.78), 30 hops max, 60 byte packets
1 mia09s01-in-f14.1e100.net (172.217.2.78) 44.847 ms 32.584 ms 32.391 ms

Any ideas?

Doh ā€“ I had experimented with entering an Enforced TTL value of 65.

When I removed the value under Enforced TTL (leaving that field blank) traceroute returned to normal from windows and from the device.

2 Likes