Simon <(E-Mail Removed)> wrote:
> Chris wrote:
>> On Mon, 14 Jul 2003 11:19:59 +0100, Simon <(E-Mail Removed)> wrote:
>>
>> >Hi There,
>> >
>> >I'm looking into sat broadband access for a colleague. Does anyone have
>> >any experience of the performance of the 2 way systems. I'm interested
>> >in the latency as this will be used for VPN access. What is the typical
>> >ping time of somewhere like www.yahoo.com ?
>> >Thanks all
>> >Simon
>>
>> have a look at http://www.aramiska.net/
>>
>> quite a few counties are being supported by a funded DTI scheme which
>> could give you a 12 month free trial and supply of all hardware.
>>
>> We got this for both of our companies sites in NE Lincs c/o Yorkshire
>> Forward and Business Insight. This free trial is due to expire in 2
>> months though for us.
>>
>> Typical download speeds for the 512k service are at max 110k/sec.
>>
>> we're looking at VPN also but from what i understand the aramiska
>> service at the end of the 12 month trial would be approx 200ukp/month.
>> for the little use our connection gets it would be cheaper for us to go
>> with ntl's broadband package for 100ukp/month if they would take on new
>> customers!
> Thanks Chris,
> I was looking at this outfit anyway as they say they support VPN access,
> BT's don't. What sort of ping time do you get to say yahoo.com ?
> Thanks again
> Simon
We have been using Aramiska for the last year or so. Their service has
gradually been getting better as they upgrade equipment. We typically
get 500 kbps streaming rate on the 1 Mbps service during working hours
(I do an automatic test transfer every hour), peaking at 800-900 kbps
outside working hours. Ping time:
$ ping
www.yahoo.com
PING
www.yahoo.akadns.net (216.109.125.74) from 192.168.0.246 : 56(84) bytes of data.
64 bytes from w1.
www.dcn.yahoo.com (216.109.125.74): icmp_seq=0 ttl=47 time=932.444 msec
64 bytes from w1.
www.dcn.yahoo.com (216.109.125.74): icmp_seq=1 ttl=47 time=934.938 msec
64 bytes from w1.
www.dcn.yahoo.com (216.109.125.74): icmp_seq=2 ttl=47 time=741.988 msec
64 bytes from w1.
www.dcn.yahoo.com (216.109.125.74): icmp_seq=3 ttl=47 time=708.099 msec
64 bytes from w1.
www.dcn.yahoo.com (216.109.125.74): icmp_seq=4 ttl=47 time=705.444 msec
64 bytes from w1.
www.dcn.yahoo.com (216.109.125.74): icmp_seq=5 ttl=47 time=810.638 msec
64 bytes from w1.
www.dcn.yahoo.com (216.109.125.74): icmp_seq=6 ttl=47 time=708.965 msec
64 bytes from w1.
www.dcn.yahoo.com (216.109.125.74): icmp_seq=7 ttl=47 time=678.667 msec
We use VPN quite a bit - it's fine for email and intranet browsing, a
bit slow for telnet as you'd expect. Fiddling with MTU and window size
can improve streaming VPN performance. I think I can get about 110
kbps over my home NTL 150k cable connection via VPN to work. Aramiska
support port forwarding for both PPTP and IPSEC. They also support SMTP
port forwarding for outgoing mail to be redirected to your internal
server. They have HTTP cacheing both on the access box on the customer
site and elsewhere in their network.
If we could get cable or ADSL, I would almost certainly go for that
instead - based on monthly cost and responsiveness of web surfing - but
we don't currently have the option.
Andrew.