News for hackers. Stuff that matters.
Re:Show HN: How did your computer reach my server? by nullindividual on Tuesday December 05, 2023 @04:06PM (#38536889)
This is sourced from https://archive.nanog.org/sites/default/files/traceroute-201..., Page 32-36. Feel free to disagree with the presentation, but it would be nice if you could offer a source rather than "I think".
Re:Show HN: How did your computer reach my server? by inowland on Tuesday December 05, 2023 @04:41PM (#38537317)
Thats a nice reference, but those slides agree with me. He is explicitly talking about "ICMP Generation" getting punted, exactly as I am.
Re:Show HN: How did your computer reach my server? by marcus0x62 on Tuesday December 05, 2023 @04:56PM (#38537499)
You misunderstand how TTL errors are signaled.

In IPv4, ICMP is used to send TTL exceeded messages regardless of what upper level protocol was used in the packet that expired in transit. UDP, TCP, ICMP, doesn’t matter.

The slides you linked to are correct, in general, about router slow path behavior, but that isn’t what makes UDP ping “more reliable”. It’s “more reliable”, theoretically, because UDP is less likely to be subject to indiscriminate filtering than ICMP.

Additionally, generally only ICMP sent to or generated from a router goes through the slow path. An IP packet being sent through a router generally goes through that device’s fast path, regardless of the payload type.

Re:Show HN: How did your computer reach my server? by Hikikomori on Tuesday December 05, 2023 @05:18PM (#38537712)
We're not disagreeing with the presentation, you're misunderstanding it.

No matter which protocol you use the packet only has one destination, the destination IP, so it does not go through the slow path on any hop on the way just because its ICMP. When a packet hits the TTL limit on a hop it will go through the slow path as the CPU will generate the response ICMP. The protocol used for traceroute makes no difference here.