Tony, the latency of two way satellite is defined by physics. >From the Nebulink website faq: http://nebulink.com/more_info/faqs.html
Latency is caused by the signal needing to travel from California, up to the satellite, and then back down to the user. The signal must travel approximately 23,400 miles up to the satellite and then back down to be received by the end user. The signal travels at 186,000miles/sec. Dividing the up/down trip of 46,800 miles by 186,000 miles/sec gives us latency of .25 sec. The receiver card recognizes this latency and addresses this with the TCP/IP acknowledgment. This is for oneway satellite for two way it is twice that so about half a second. Also everything I have read says if u can get dsl or cable modem stick with it since it is almost always a better deal with better service. Paonia > HI Andrew, > > Is it a two way connection, or do you have to dial up the ISP with a modem > for the return trip? What about the lag? Is there one? If so, how long is > it usually? I am happy with cable modem right now, but the idea of > satellite, especially two way sat. with the same speed and low latency would > be very interesting. > > Thanks > > Tony > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Andrew GRAY > Sent: Saturday, January 25, 2003 6:52 AM > To: 'Paonia Ezrine'; [EMAIL PROTECTED] > Subject: RE: [leaf-user] satellite with bering > > > I have a Dachstien CD box running Satellite from iHug here in Australia. I > simply downloaded the drivers from the ISPs web site for the Kernel version > and installed them. The system has been up for over a month and works well > when the ISP gives us a link from the satellite. > > Andrew Gray > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Paonia Ezrine > Sent: Saturday, 25 Jan 2003 10:47 > To: [EMAIL PROTECTED] > Subject: [leaf-user] satellite with bering > > > I am thinking about getting oneway satellite internet access from > http://www.nebulink.com or http://www.copperlink.net/satnet/index.shtml > (they both resell the same service). I am wondering if anyone has gotten > this to work with bering or any of the other similar fw's out there. If > so please let me know how you did it etc. > thanks > Paonia > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > ------------------------------------------------------------------------ > leaf-user mailing list: [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user > SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > ------------------------------------------------------------------------ > leaf-user mailing list: [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user > SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > ------------------------------------------------------------------------ > leaf-user mailing list: [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user > SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html > ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
