5 ms·
The thing with satellite internet (up and downlink) is mostly to do with jitter. You can get pretty good rates on a nice day, but you can’t control air refracti
by withinboredom 6y ago
The thing with satellite internet (up and downlink) is mostly to do with jitter. You can get pretty good rates on a nice day, but you can’t control air refraction 2 miles off the ground doing weird stuff to your signal. I experimented with many things, but the best solution I had was using TCP over UDP with a server in a data center able to resend TCP (over UDP) packets if they were dropped. I think http3 will help out immensely here.
Source: I ran a small satellite ISP on a base in Afghanistan.
- beams 6y agoWhy TCP over UDP? The whole point of TCP is retransmission. What did you gain by encapsulating this way?
- TYMorningCoffee 6y agoHe probably saw benefits from using UDP because he's no longer limited by TCP's congestion control and can flood the pipe with duplicates of his packets.
- dvdkhlng 6y ago> He probably saw benefits from using UDP because he's no longer limited by TCP's congestion control and can flood the pipe with duplicates of his packets. But he wrote that he'd used "TCP over UDP". The first lines of the TCP over UDP spec already state "It provides exactly the same congestion control, flow control, reliability, and extension mechanisms as offered by TCP." [1] [1] https://tools.ietf.org/id/draft-baset-tsvwg-tcp-over-udp-01.html https://tools.ietf.org/id/draft-baset-tsvwg-tcp-over-udp-01....
- TYMorningCoffee 6y agoThen I'm wrong. Thanks for the clarification.
- dvdkhlng 6y agoYes, I had the same confusion. There seems to be a standard for TCP over UDP [1]. But in general, I would assume that it does not help at all WRT any of the packet loss/latency problems posed by satellite links. TCP is designed for encapsulation in IP, this is why it is called TCP/IP. And UDP is very similar to IP, only difference is that UDP gives you source and destination port numbers and a payload checksum, where IP only gives you a protocol numbers and non-checksummed data. None of these "features" is going to have any effect on how TCP is delivered. So the only effect that use of TCP over UDP would have here is: - increase the overhead used for headers, thereby decreasing the MSS (segment size) - "cloak" the TCP traffic as UDP and thereby prevent any routers and/or middleboxes [2] from applying special treatment to TCP (i.e. traffic shaping, buffering etc.) Maybe the latter effect is what made a difference for the link in question. [1] https://tools.ietf.org/id/draft-baset-tsvwg-tcp-over-udp-01.html https://tools.ietf.org/id/draft-baset-tsvwg-tcp-over-udp-01.... [2] https://en.wikipedia.org/wiki/Middlebox https://en.wikipedia.org/wiki/Middlebox edit: formatting
- bhk 6y agoTCP does have retransmission, but it was designed for networks with very low packet loss and where most packet loss is due to congestion, so it does not react quickly to packet loss and when multiple packets are lost it slows down dramatically. TCP typically uses an exponential backoff in re-transmission times to avoid exacerbating congestion. When dealing directly with UDP, one can implement different application-level logic for dealing with packet loss: "NAK" packets, different backoff strategies, and even forward error correction.
- walrus01 6y agoSorry but you're wrong, dedicated 1:1 capacity scpc geostationary links will always be 492-495ms rtt ping latency between teleport and far end. Latency will never be less than the laws of physics and modem FEC dictate, but jitter will be very low. If you saw a lot of jitter it was because you were in an oversubscribed, contended tdma network. What was your terminal hardware, what modems were you using and what was the rf chain and modem setup at the far end (not in Afghanistan)? Latency on terrestrial ptp microwave also does not vary. Ducting and diffraction and temperature inversions on long 6GHz links affects rsl and modulation, not latency. In the case of starlink, each satellite is functioning as a bent pipe relay between cpe and starlink earth station. Latency will vary a ms or two based on satellite position during a pass overhead, but no more than that. The rest of the latency is the same as from any terrestrial internet customer in the same geographic location as the earth station. For instance one of the beta test earth stations is in north bend, wa, colocated with a level3 long haul dwdm site. People in WA have been posting tests with latencies of 25-26ms to speed test servers in downtown Seattle. That's actually really, really good, considering that latency to your default gateway on a residential cable docsis3 coaxial connection can easily be 16ms on a terrestrial connection. North bend is a few ms from seattle, the brewster starlink teleport site several ms more. In the case of starlink they are competing against 32:1 or worse oversubscribed geostationary consumer grade vsat services like viasat and Hughesnet. Starlink is far superior tech.
- definetheword 6y agoI want to take a class/course/certficate on space communications. Do you have any great recommendations? Edit: And, any really good blog series on this? so I know what to expect in such a course
- walrus01 6y agoUnfortunately I do not, I learned on the job. I would recommend learning general network engineering and study radio, microwave, physics and wireless communication stuff generally to have a good basis to begin.
- 6y ago
- anko 6y agodo you think having lower altitude satellites will help with the jitter much?
- TaylorAlexander 6y agoWe definitely lost both of our internet uplinks at our California farm when the wildfires filled the air with smoke this summer. One uplink is satellite and for weeks it had no signal as the farm is only a few kilometers from one of the largest fires. The other uplink was a solar powered 4G connection and despite several deep cycle batteries and a few 200 watt panels, the station did not get enough light to stay powered over those weeks. We finally found a hilltop wireless ISP that can serve us. We’ll try to get Starlink too but I don’t expect that to work well during fire season. It’s tough to be offline for weeks at a time.
- simonebrunozzi 6y ago> Source: I ran a small satellite ISP on a base in Afghanistan. Irrespective of how right or wrong your first paragraph is; this is one of the reasons I absolutely love the HN community.
- LinuxBender 6y agoI found a youtuber that has Starlink and had them run the dslreports bufferbloat test. They received an "A". This suggests that the jitter should be acceptable to most people on Starlink. Note: If running the test on Starlink, select "cable modem" as the Satellite tests on dslreports have not been updated to deal with Starlinks different behavior. [1] - http://www.dslreports.com/speedtest http://www.dslreports.com/speedtest