Remote Rig

RRC 1258 Support in English => General discussion forum => Topic started by: Gerryb on 2024-08-17, 19:29:28

Title: Latency and Starlink
Post by: Gerryb on 2024-08-17, 19:29:28

I would like fire my twin on a remote location with my Yaesu 857D.   I know long latency times stop this working using the older control of the 857.    The latency I get with Starlink is 40ms, but they say can reach 100.  Once I attempted to reach australia. before Starlink and and that did not work with a ping of 300ms!   What is the max ping time that it could tolerate?

Gerry

Title: Re: Latency and Starlink
Post by: sm2o on 2024-08-17, 20:24:39

Hi

This has not been an Issue for many years as Internet latency has imporved.

I found a answer I gave you in 2015

We do not have any documentation about it, but some where between 200-300 ms I think the limit is.

Remember that ordinary Starlink plans do not include public IP so you must have a business plan in the Radio end if you want to use Starlink

73 de mike

Title: Re: Latency and Starlink
Post by: Gerryb on 2024-08-19, 10:40:52

Thanks… and for looking back to 2015!  that long ago.

I will experiment when next back at the remote location that has starlink

To get past fibre, 4g 5g and Starlink’ CGNAT, instead of  paying for a fixed IPv4 I use reverse tunnels. IPV6 rollout allows direct connection with pinholes so my use of reverse tunnels is reducing. iPv6 to IPv4 I use SOCAT. All these solutions need a raspberry Pi which in someways defeats the object of RRC 1258, but I find RRC but better that any software to control the radio

Starlink has IPV6, and as yet