News for hackers. Stuff that matters.
Re:A transport protocol's view of Starlink by alfons_foobar on Friday May 17, 2024 @01:20AM (#40386630)
That is true for ICMP packets directed at the router itself.

Pretty sure that is the reason why he used

> ping across a Starlink connection from the customer side terminal to the first IP end point behind the Starlink earth station

instead of pinging the terminal itself.

(ICMP packets passing _through_ a router are handled just like any other traffic and are therefore OK for an analysis like this)

Re:A transport protocol's view of Starlink by maxmouchet on Friday May 17, 2024 @01:37AM (#40386708)
Additionally, I would not expect such “baseline” changes in the minimum RTT to be due to variation in CPU processing time.

These changes are more typical of a physical path change, as suggested by the author.

CPU/soft processing latency would look more like additive noise.

I give some examples of RTT patterns in this talk: https://ripe77.ripe.net/archives/video/2250/

Re:A transport protocol's view of Starlink by CaliforniaKarl on Friday May 17, 2024 @01:45AM (#40386759)
It's unclear to me. `traceroute` typically just returns router IPs, so I'm assuming that "the first IP end point behind the Starlink earth station" is the IP address of a router of some sort.
Re:A transport protocol's view of Starlink by alfons_foobar on Friday May 17, 2024 @02:14AM (#40386958)
Hm, I understood "ip endpoint" to mean something else than a router (because I am very sure that Geoff is aware of the "ICMP is not handled on the ASIC"-issue).