On 5/13/23 13:10, Ulrich Speidel via Starlink wrote:
3) We know that they aren't an artifact of the Starlink WiFi router
(our traceroutes were done through their Ethernet adaptor, which
bypasses the router), so they must be delays on the satellites or the
teleports.
Here is what bypass mode does:
https://github.com/SpaceExplorationTechnologies/starlink-wifi-gen2/blob/main/openwrt/package/base-files/files/sbin/setup_iptables.sh#L19
https://github.com/SpaceExplorationTechnologies/starlink-wifi-gen2/blob/main/openwrt/package/base-files/files/sbin/wifi#L213
https://github.com/SpaceExplorationTechnologies/starlink-wifi-gen2/blob/main/openwrt/package/base-files/files/etc/init.d/wifi_control#L26
So packages still going through this chain:
Dishy -> Mediatek PHY -> Linux kernel -> br-lan -> Linux kernel ->
External LAN PHY (Marvell or MTK).
It's better to use a PoE injector and run tests without the Starlink router.
--
Best regards,
Oleg Kutkov
_______________________________________________
Starlink mailing list
[email protected]
https://lists.bufferbloat.net/listinfo/starlink
