Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
traceroute or mtr showing only my router and final destination.
No other hops.
Why?
traceroute to yahoo.com (98.137.246.7), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 1.005 ms 1.329 ms 1.620 ms
2 media-router-fp1.prod1.media.vip.gq1.yahoo.com (98.137.246.7) 180.807 ms 190.120 ms 190.305 ms
or:
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 1.155 ms 1.491 ms 1.786 ms
2 google-public-dns-a.google.com (8.8.8.8) 19.509 ms 19.702 ms 20.754 ms
or any other destination IP that answer to traceroute.
Only 2 hops.
The next router upstream has for some reason been configured to override the TTL (Time To Live) in the packet and substitute some new, default number. traceroute operates by setting a low TTL value (starting with 1) and successively incrementing that, thus causing each intermediate router to return a "TTL equals 0" ICMP response. That can't work if some router along the chain overrides that TTL.
If that next router is not under your control, there is nothing you can do.
But, which is the reason for such action (TTL modification) ?
Quote:
Originally Posted by ferrari
I've read of it being implemented so that a router isn't explicitly identified eg avoiding ddos attacks.
Indeed. I have one router that I wish to have invisible in my own network, but I do that by having it increment TTL by 1. That prevents that router from ever seeing TTL==0, but allows traceroute to see the rest of the hops. You are apparently behind an internal network that someone wants to keep entirely hidden.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.