3 ms·
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
by alfons_foobar 2y ago
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)
- maxmouchet 2y agoAdditionally, 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/ https://ripe77.ripe.net/archives/video/2250/
- CaliforniaKarl 2y agoIt'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.
- alfons_foobar 2y agoHm, 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).