Skip to main content
Beantwoord

Traceroute Only Shows Gateway and Destination – Is Anyone Else Experiencing This?

  • June 6, 2025
  • 1 reactie
  • 34 Bekeken

Hello everyone,

For some time now, I’ve noticed that whenever I run a traceroute from my home internet connection, it only ever shows my local gateway as the first hop and then immediately jumps to the destination. Here are a few examples:
 

sudo traceroute -I amazon.nl
traceroute to amazon.nl (52.95.120.64), 30 hops max, 60 byte packets
 1  _gateway (192.168.178.1)  0.383 ms  0.406 ms  0.440 ms
 2  52.95.120.64 (52.95.120.64)  19.301 ms * *

sudo traceroute -T -p 443 amazon.nl
traceroute to amazon.nl (52.95.116.117), 30 hops max, 60 byte packets
 1  _gateway (192.168.178.1)  0.497 ms  0.482 ms  0.444 ms
 2  52.95.116.117 (52.95.116.117)  21.999 ms  20.967 ms  19.347 ms

sudo traceroute -T -p 80 amazon.nl
traceroute to amazon.nl (54.239.33.93), 30 hops max, 60 byte packets
 1  _gateway (192.168.178.1)  0.504 ms  0.468 ms  0.445 ms
 2  54.239.33.93 (54.239.33.93)  23.038 ms  22.217 ms  20.243 ms

As you can see, hop 1 is always my router (192.168.178.1) and hop 2 is the remote host (Amazon’s IP). There are never any intermediate hops listed.

Has anyone else on the Odido’s broadband observed traceroute showing only the gateway and then the destination IP?

Beste antwoord door Decker

Sorry, it's resolved—the issue was on my end. I had mistakenly applied a firewall rule on my router that modified the TTL on all outgoing packets, which caused the traceroute to break. This post can be deleted—everything is OK now.

Bekijk origineel

    1 reactie

    • Deckeris een Master Poster
    • Auteur
    • is een Master Poster
    • Antwoord
    • June 6, 2025

    Sorry, it's resolved—the issue was on my end. I had mistakenly applied a firewall rule on my router that modified the TTL on all outgoing packets, which caused the traceroute to break. This post can be deleted—everything is OK now.

    ForumvoorwaardenAccessibility statement