You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was trying to run iPerf between 2 different ground stations with Starlink constellation of 100 satellites and 36 ground stations. The two ground stations are node 101 and node 104. I found that, even though, node 101 can perform iPerf as a client to 104 (as a server), it does not work the other way around. They can ping each other, and their routing tables are the same and are shown as follows:
node 101:
9.104.104.0/24 proto bird metric 32
nexthop via 9.1.32.50 dev B101-eth32 weight 1
nexthop via 9.1.88.50 dev B101-eth88 weight 1
node 104:
9.101.101.0/24 proto bird metric 32
nexthop via 9.4.32.50 dev B104-eth32 weight 1
nexthop via 9.4.88.50 dev B104-eth88 weight 1
I also used traceroute to understand the routing hops for both directions. The packets from 101 can reach node 104 through 1 satellite hop, but packets from 104 cannot reach 101. The results from traceroute are shown as follows:
101 to 104:
traceroute to 9.104.104.10 (9.104.104.10), 30 hops max, 60 byte packets
1 ovs_container_32.GSL_32-101 (9.1.32.50) 35.379 ms 35.363 ms 35.370 ms
2 9.104.104.10 (9.104.104.10) 70.115 ms 70.126 ms 70.131 ms
It seems that you use the main branch of StarryNet. Depending on the OS release and Docker version, Docker may apply some filter rules to packets with specific address, port or other conditions. I guess that's why iperf packets are intercepted.
We recommend that you use the dev branch of StarryNet,which deprecates Docker for its high memory consumption and long start-up time. For your problem, it doesn't apply filter rules anymore so the iperf packets can reach the other end. This branch is experimental and we will continue to improve it.
If you are interested in the filter rules mentioned above, you can check the nftable or iptable rules for verification. Use Linux command nft or iptables to check those rules related to Docker.
Hi,
I was trying to run iPerf between 2 different ground stations with Starlink constellation of 100 satellites and 36 ground stations. The two ground stations are node 101 and node 104. I found that, even though, node 101 can perform iPerf as a client to 104 (as a server), it does not work the other way around. They can ping each other, and their routing tables are the same and are shown as follows:
node 101:
node 104:
I also used
traceroute
to understand the routing hops for both directions. The packets from 101 can reach node 104 through 1 satellite hop, but packets from 104 cannot reach 101. The results fromtraceroute
are shown as follows:101 to 104:
104 to 101:
Does anyone know what might go wrong in my setup?
Thank you.
The text was updated successfully, but these errors were encountered: