[Starlink] run a few scripts behind your starlink dish?

[J Pan <Pan@uvic.ca>]

[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]

Dave allowed me to ask on this mailing list... ;-)

we are doing research to understand starlink in particular, and
leo-sat networks in general, better and possibly to improve them
further. please see our work at https://www.reddit.com/user/panuvic/

if you have (access to) a starlink dish, could you please run the
attached script behind it. the tr-sl... traceroutes to starlink
backbone ip addresses from your dish through your gateway and pop, and
if your gateway is 100.64.0.1 (if only * * * on your traceroute, you
may have vpn such as tailscale eats return icmp messages from this
address. "tailscale up --netfilter-mode off" can fix it; if you have a
public address option, please replace 100.64.0.1 by your actual
gateway address), ping-... pings your gateway quickly and briefly (if
you can "at" to start it at the beginning of a minute, great)

results from these scripts can help us (and the community at large)
understand starlink gateway, pop and backbone and their evolution
better. e.g., ulrich and his student shared their results with us, and
we can clearly see the satellite-ground station handovers, as well as
mac behaviors

thanks a lot for your help in advance. your viewpoint around the world
will help a lot. cheers.  -j
--
J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan

[-- Attachment #2: tr-sl-bb-ip.sh --]
[-- Type: text/x-sh, Size: 218 bytes --]

#!/bin/bash

for i in $(seq 108 109); do for j in $(seq 0 255); do traceroute -enm 18 -w 1 149.19.$i.$j; done; done
for i in $(seq 64 66); do for j in $(seq 0 255); do traceroute -enm 18 -w 1 206.224.$i.$j; done; done

[-- Attachment #3: ping-gw.sh --]
[-- Type: text/x-sh, Size: 71 bytes --]

ping -i 0.01 -c 10000 100.64.0.1 > ping-gw-`date "+%y%m%d-%H%M%S"`.txt

[-- Attachment #4: ping-gw-231114-085600.png --]
[-- Type: image/png, Size: 176787 bytes --]