Residential VSAT experiences?

Mon Jun 22 23:12:32 UTC 2015

I too have had customers in a previous life where the 500ms delay
really didn't cause any big issue.

Same with SSH and even heavier stuff like SMB.  Sure, it was slower
than expected, but I could still saturate the pipe pretty good.

Thing is...the kind of setups where you're getting 500ms delay with
little jitter is stupidly expensive.  Those are generally going to be
an SCPC (single carrier per channel) uplink with hopefully something
like IP over DVB providing a large pool of downlink bandwidth.  Expect
to pay over 4k per Megahertz (roughly translated to 1 Mbps
unidirectional depending your link budgets) of bandwidth (sometimes
substantially more, depending on what bird and provider you're using).

O3B looks really interesting.  I'm not aware of what they're current
state of deployment is, but they've got a MEO (I think) constellation
planned which will help a lot of with that latency.  Viasat had
something that looked promising too.

I mean..if you're looking at doing sysadmin type stuff where you're
already going to be pulling out your hair at times, doing so over
hughesnet is going to suuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuck.

On Mon, Jun 22, 2015 at 4:04 PM, Hugo Slabbert <hugo at slabnet.com> wrote:
> Personally, 500-700ms of delay is well within distinguishable range and
> causes challenges in verbal communication.  If the speakers are both
> expecting and accustomed to delay like that (e.g. sailors that are used to
> being hundreds/thousands of miles away from anywhere and any other comms
> solution sucks anyway), it could be workable.
>
> For regular consumer/business voice applications, 100ms and lower is decent,
> but above that starts to get into various degrees of suckage.
>
> Just my 2c.
>
> --
> Hugo
>
>
> On Mon 2015-Jun-22 15:54:49 -0700, Mike Lyon <mike.lyon at gmail.com> wrote:
>
>> I never had good luck with VSAT and SIP. Maybe you had a better kit than I
>> did :)
>>
>> -Mike
>>
>>
>> On Mon, Jun 22, 2015 at 3:49 PM, Dovid Bender <dovid at telecurve.com> wrote:
>>
>>> Interesting that you say that about sip. We had a client that would use
>>> it
>>> for sip on ships all the time. It wasn't the best but it worked. Ping
>>> times
>>> were between 500-700ms.
>>>
>>>
>>>
>>> Regards,
>>>
>>> Dovid
>>>
>>> -----Original Message-----
>>> From: Mike Lyon <mike.lyon at gmail.com>
>>> Sender: "NANOG" <nanog-bounces at nanog.org>Date: Mon, 22 Jun 2015 15:33:43
>>> To: Nicholas Oas<nicholas.oas at gmail.com>; NANOG<nanog at nanog.org>
>>> Subject: Re: Residential VSAT experiences?
>>>
>>> SIP will suck. VPN will suck. RDP will suck.
>>>
>>> Have you looked to see if you have any local wireless ISPs in your area?
>>> Hit me up offlist if you want me to check for you.
>>>
>>> -Mike
>>>
>>>
>>> On Mon, Jun 22, 2015 at 1:39 PM, Nicholas Oas <nicholas.oas at gmail.com>
>>> wrote:
>>>
>>> > Would anyone mind sharing with me their first-hand experiences with
>>> > residential satellite internet?
>>> >
>>> > Right now I am evaluating HughesNet Gen4 and ViaSat Exede and I'm
>>> thinking
>>> > specifically as a sysadmin who needs to use the uplink for work, not
>>> surf.
>>> >
>>> > What are your experiences with the following applications?
>>> > -SSH, (specifically interactive CLI shell access)
>>> > -RDP
>>> > -SIP over SSL
>>> > -IPSec Tunneling (should be a non-starter due to latency)
>>> > -GRE Tunneling
>>> >
>>> > Thank you,
>>> >
>>> > -Nicholas
>>> >
>>>
>>>
>>>
>>> --
>>> Mike Lyon
>>> 408-621-4826
>>> mike.lyon at gmail.com
>>>
>>> http://www.linkedin.com/in/mlyon
>>>
>>
>>
>>
>> --
>> Mike Lyon
>> 408-621-4826
>> mike.lyon at gmail.com
>>
>> http://www.linkedin.com/in/mlyon

-- 
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0