JohnAckermann wrote:I think the issue with satellite connections and VPN is the latency -- the trip up to the bird and back down is long enough that the timing tolerances of the VPN protocols are screwed up (just a guess).
Both physical (~650 ms) and imposed through traffic shaping / scheduling / accelerating wrapper by consumer satellite options.
I think over any satellite encrypted protocols aren't going to be stellar, but over consumer satellite it seems the priority is on http and "every man's" use so you see things many times worse for vpn/ssh/other encrypted protocols than they could be over high-dollar satellite options.
Wildblue has been a lifeline for me until DSL became available, and I was thankful to have it. In 2005 wildblue "changed the rules" of the consumer satellite industry -- before that with hughes for example, for 100 kbps real-world upload you needed $1000 of equipment. Wildblue came on the scene and for $299 of equipment they delivered 250 kbps upload, quite an improvement. (Hughes went from 60-100 up plans to 300 and 500 plans to match a short time later, and I believe they would have not done this had it not been for wildblue.) Also when wildblue was new many things that had been very problematic over starband for the previous 3 years "just worked on wildblue." However, once wildblue got past tens of thousands of customers and loaded up their gateways more, in November of 2006 they changed the scheduling routines at their gateways in order to maintain advertised speeds for larger file transfers, but at the expense of non http and latency sensitive protocols.
2005:
Code: Select all
# Wildblue 2005
Pinging yahoo.com [66.94.234.13] with 32 bytes of data:
Reply from 66.94.234.13: bytes=32 time=648ms TTL=48
Reply from 66.94.234.13: bytes=32 time=727ms TTL=48
Reply from 66.94.234.13: bytes=32 time=730ms TTL=48
Reply from 66.94.234.13: bytes=32 time=726ms TTL=48
Reply from 66.94.234.13: bytes=32 time=723ms TTL=48
Reply from 66.94.234.13: bytes=32 time=723ms TTL=48
Reply from 66.94.234.13: bytes=32 time=641ms TTL=48
Reply from 66.94.234.13: bytes=32 time=642ms TTL=48
Reply from 66.94.234.13: bytes=32 time=654ms TTL=48
Reply from 66.94.234.13: bytes=32 time=643ms TTL=48
Ping statistics for 66.94.234.13:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 641ms, Maximum = 730ms, Average = 685ms
became this instead:
Code: Select all
# Wildblue 2007
Pinging 66.94.234.13 with 32 bytes of data:
Reply from 66.94.234.13: bytes=32 time=1367ms TTL=45
Reply from 66.94.234.13: bytes=32 time=2491ms TTL=48
Reply from 66.94.234.13: bytes=32 time=1471ms TTL=47
Reply from 66.94.234.13: bytes=32 time=1414ms TTL=46
Reply from 66.94.234.13: bytes=32 time=1234ms TTL=45
Reply from 66.94.234.13: bytes=32 time=1556ms TTL=49
Reply from 66.94.234.13: bytes=32 time=1346ms TTL=45
Reply from 66.94.234.13: bytes=32 time=1603ms TTL=45
Reply from 66.94.234.13: bytes=32 time=1258ms TTL=45
Reply from 66.94.234.13: bytes=32 time=1302ms TTL=49
Ping statistics for 66.94.234.13:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1234ms, Maximum = 2491ms, Average = 1504ms
Not only is the average much higher, but the deviation is huge now as well and those spikes can really make latency sensitive applications frustrating now. Uploads or downloads over 1 MB still go at or over advertised speed, and over a few months from when they made the change http browsing seemed to be re-accelerated to nearer previous speeds, but "chatty" interactive and encrypted protocols really suffered for me. Hughes delivers a bit lower pings now, but no where near the original 2005 wildblue near-physical satellite latency (they do have the new spaceway satellite, but I fear that they will actually deliver less performance than they could to consumer accounts over the new bird in order to not have to upgrade all the existing ku customers right away and so they can clear out their 7000 inventory, keeping higher performance for their big high-dollar enterprise customers on that new satellite with switching in the sky.)
As we move more and more to encrypted protocols and 'ajax-y' web pages, wildblue was and is great compared to dialup, but no comparison to low latency "everything I throw at it works quickly" goodness.
Code: Select all
# TDS DSL 2008
Pinging 66.94.234.13 with 32 bytes of data:
Reply from 66.94.234.13: bytes=32 time=122ms TTL=55
Reply from 66.94.234.13: bytes=32 time=122ms TTL=55
Reply from 66.94.234.13: bytes=32 time=120ms TTL=55
Reply from 66.94.234.13: bytes=32 time=114ms TTL=55
Reply from 66.94.234.13: bytes=32 time=109ms TTL=55
Reply from 66.94.234.13: bytes=32 time=118ms TTL=55
Reply from 66.94.234.13: bytes=32 time=126ms TTL=55
Reply from 66.94.234.13: bytes=32 time=120ms TTL=55
Reply from 66.94.234.13: bytes=32 time=137ms TTL=55
Reply from 66.94.234.13: bytes=32 time=125ms TTL=55
Ping statistics for 66.94.234.13:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 109ms, Maximum = 137ms, Average = 121ms