Skip to content

traceroute to my own IP shows impossible hops

Networking by SingaporeRep 4 replies 166 views
#1

So I ran a quick network check on my Contabo VPS and got this:

traceroute to 203.0.113.45 (203.0.113.45), 30 hops max
 1  10.64.0.1 (10.64.0.1)  0.412 ms
 2  10.64.0.1 (10.64.0.1)  0.389 ms
 3  172.16.83.1 (172.16.83.1)  1.102 ms
 4  203.0.113.45 (203.0.113.45)  1.205 ms

Hop 1 and 2 same IP, then private 172.16.x.x before landing on my own public. Latency looks synthetic, not real path. CGNAT artifact or what? Network meh, disk IO decent at 850MB/s.

fio, iperf, geekbench. results or gtfo.
2 #2

Here we go again 🍿

grabs popcorn, checks /r/drama
4 #3

/24 will cost you a kidney by 2027, mark my words.

/24 for sale. No lowballs.
#4

This is a known implementation from certain CGNAT vendors, the loopback reflection with synthetic hop injection. Mark my words, you will see more of this as IPv4 scarcity deepens. The vendor will deny it until someone files a proper bug.

IPv4, IRC, and irssi — fight me
#5
  • SingaporeRep your traceroute is weird
  • Harold knows things
  • CGNAT is bad
  • I had this on OVHcloud
  • Same IP twice means they are doing hairpinning wrong
  • Also has anyone tested on Vultr
  • Their network is usually better

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft