Broadband Satellite Internet Protocols and Applications
Skycasters is a TCP/IP Service, built that way from the ground up.
The term "TCP/IP" refers to the layered combination of TCP and IP protocols, on which many higher-level application protocols (like HTTP, FTP, SMTP) have been built.
Skycasters service supports TCP/IP applications with hardware acceleration performed on its satellite gateway units and equipment at the customer’s remote site. Acceleration is more thoroughly described elsewhere on this site, but essentially, it is a product of hardware in the network that allows TCP/IP to function without regard to the latency
in the connection.
Acceleration makes multi-megabit speeds possible over satellite. Protocols other than TCP/IP are not in any way blocked, however they cannot be accelerated. Internet applications like email and web browsing perform very well over satellite, delivering high-speed service similar to T-1, DSL or cable.
The service is asymmetrical, meaning that around 80% of the bandwidth is allocated towards download traffic with the remaining balance allocated for uploads—the typical traffic pattern used in most applications. With our high performance platinum service options, VSAT
can even support applications that require a high-speed upload such as 2-way video conferencing
or streaming video
. However, satellite remote sites should not be expected to host any applications, especially web servers. Users with these requirements should consider co-locating their server in our data center, remotely managing the server over the satellite link.
Satellite latency in the range of 700ms is typical in the Skycasters network. Although this is far less latency than our competitors, applications that are affected by high latency may experience technical issues. Known latency-affected applications include interactive gaming, VoIP, and most non-TCP/IP applications. Examples:
- UDP - a protocol that cannot be accelerated because it is not a connection-based protocol.
- NetBIOS - a LAN technology that cannot be accelerated. NetBIOS was not designed to function in a WAN environment and will function slowly over satellite.
- Drive-mapping is not supported over satellite except through a VPN
tunnel. - RDP (Citrix) and RCP (Exchange) can also be slow over a satellite connection.
If a customer needs to use shared folders, web folders can be created in a directory using an application such as Microsoft Internet Information Server, Apache or another web front-end. Shared folders and drive mapping will perform slowly over any satellite connection unless set up in this manner.
Microsoft Internet Information Server (IIS) or an equivalent also needs to be set up with SQL server for optimum performance. Any application that is compatible with IIS will perform better in this fashion. Skycasters recommends that hosted applications be configured with an IIS or another web front-end.
Generally, any application that requires client software loaded at the remote site can have issues with satellite connections unless adjustments are made at both the client and server end. These types of applications need to be evaluated individually by checking with the manufacturer to determine the effects of latency on the particular application. Depending on the underlying application, Citrix can be affected by latency, and will perform more slowly over satellite. Some customers will have better results with Citrix than others, based on the configuration and application involved. A Citrix engineer should be consulted prior to its use over satellite to determine how a particular customer-specific application will perform.
IPSec VPN
clients like Cisco, Nortel, Checkpoint, etc. will have performance issues using standard configurations, although they can be used in a single-user environment occasionally. Proper configuration of these solutions can improve performance. Skycasters does offer VPN solutions that function well over satellite. Please discuss your specific VPN requirements with your sales engineer.
Multi-site configurations requiring remote-to-remote communications will have twice the latency (due to the double hop through the satellite), and may have difficulty communicating directly with each other, although it is possible to successfully use the system in this manner. If your requirements include frequent remote-to-remote communications, please discuss this with your sales engineer. A mesh configuration may be a more appropriate solution for your needs.
And last but not least, terminal emulators must have local-echo enabled at the remote site in order to perform properly.