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.
If i specify Record Route option in IP header, it will record the ip address of at most 9 intermediate hops. My question is how this packet with ip Record Route option enabled reaches to the destination host get processed.
I used ICMP ping with record route option enabled and the destination sends a normal ICMP echo reply in which the recorded route is copied back. But if i want to send a UDP or TCP and not ICMP echo request with Record Route option then how the destination will send the recorded route back to source?
It is possible to have the packet sent back by setting the TTL value (Time To Live as number of router hops) to an appropriately low value. In this case, the reply is an ICMP Time Exceeded message with a code indicating that the TTL expired in transit. Your original packet, including IP header and options (Record Route), will be encapsulated in this ICMP message.
In practice however, I found that TCP SYNs with the Record Route option are often silently dropped unlike ICMP echo requests. When combining all three (ICMP Echo, low TTL, and Record Route), I was able to detect routers that did not decrement the TTL and routers that forwarded the Record Route option unaltered.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.