Member OP
This is driving me crazy. My VPS it traceroute to anywhere, stars in middle hops, but ping he works perfect. No packet loss, nossa!
I try from my home ISP, same thing. Try from Contabo VPS, same stars. Caramba, what is this?
I think maybe my network he is broken? But ping more fast than ever.
Someone help this poor please.
Member
Not a deal, not a steal. Sounds like middlebox eating your ICMP time-exceeded but passing echo-reply. Classic cheap hosting move, man. They "filter for security" but really it's to hide oversubscribed transit. I'd demand refund.
JokoNord what cheap hosting you mean, Contabo or OP home ISP
Member
ICMP rate-limiting on intermediate routers. Common for DDoS mitigation at 40+ Gbps scrubbing layers. Traceroute needs TTL-expired replies; ping only needs echo-reply. Different code paths through filtering policy.
Not a fault. Expected behavior behind anycast scrubbing or tier-2 residential CPE.
1. This is normal behavior, not a problem
2. Causes:
2. A) routers deprioritize or drop ICMP time-exceeded
2. B) middlebox filters it entirely
2. C) asymmetric routing returns through different path
3. What still works:
3. I) TCP traceroute (different probe type)
3. Ii) Paris traceroute
3. Iii) just accepting stars and moving on
4. Your ping is fine
5. Your network is fine
6. This should be FAQ entry
Middlebox theory checks out. I've seen this on three hosts now.
Which kernel, mano
Member OP
ByteSuper I use Ubuntu 22.04 with 5.15 kernel. But wait, I test from my home Windows machine too, same stars! Is not kernel thing I think.
Ubuntu default traceroute uses UDP probes, not ICMP. Some middleboxes only eat ICMP time-exceeded but let UDP through, or opposite. Try
traceroute -ItcptracerouteMember
ByteSuper has the right angle. Kernel matters for probe type selection, but the path behavior is what it is. CarlosBilby, if you want to see the path, install
paris-traceroute