old-www/HOWTO/Sat-HOWTO-8.html

97 lines
3.4 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
<TITLE>Sat (Satellite Technology) HOWTO: Appendix A - Notes</TITLE>
<LINK HREF="Sat-HOWTO-9.html" REL=next>
<LINK HREF="Sat-HOWTO-7.html" REL=previous>
<LINK HREF="Sat-HOWTO.html#toc8" REL=contents>
</HEAD>
<BODY>
<A HREF="Sat-HOWTO-9.html">Next</A>
<A HREF="Sat-HOWTO-7.html">Previous</A>
<A HREF="Sat-HOWTO.html#toc8">Contents</A>
<HR>
<H2><A NAME="s8">8. Appendix A - Notes</A></H2>
<H2><A NAME="ss8.1">8.1 Translation Dynamic IP -&gt; MAC Address</A>
</H2>
<P>The translation used by some ISPs to calculate MAC address (which need
to have your DVB card to receive their packets) is:
<P>00 : 01 : IP[0] : IP[1] : IP[2] : IP[3]
<P>where
<P>IP[0].IP[1].IP[2].IP[3] is your
dynamic IP address.
<P>This feature is used, for example, by EON.
<H2><A NAME="ss8.2">8.2 TCP Window</A>
</H2>
<P>Satellite connections are an interesting example of very high RTT (round
trip time, access time): another example is the Mars - Earth communication
or also the Moon - Earth one.
<P>These connections have a very bad feature: very low interactively.
<P>Typical network (or digital, generally) connections use the so called transmission
"window", which represents the data buffer can be sent before waiting for an
answer. In TCP/IP protocol stack this is the TCP Window.
<P>
<PRE>
----------------------
| - - - - - - - &gt; can continue |-|-|-|----&gt;
| ----------------------
| Buffer sendable before confirm
|
| - - - - - - - &lt;----------------------
Confirmation Answering
</PRE>
<P>Now, if our communication has an high access time and if we had a little
TCP Window we would lose very much time only waiting for the data confirmation
(ACK), so the real bandwidth would decrease (for example if you have a 16KB
TCP window, typical of Windows systems and a RTT of 400 ms, you cannot overcome
16KB/0.4 = 40 KB/s)
<P>Solution is to use a very high TCP Window (such as 256 KB or some MB).
<P>Unfortunately, under many systems, is not so simple to have a great TCP
Window, so, in latest years, it starts to appear new applications ("download
accelerators" described in next section) that split in many pieces a file and
download all them in the main time: this is just equivalent to download only
one file with a single piece size, avoiding the RTT problem.
<H2><A NAME="ss8.3">8.3 Download accelerator</A>
</H2>
<P>We report here some useful link to so called "download accelerator" which
is an application that does 2 things:
<P>
<OL>
<LI>resuming session management, it allows stopping downloading and restarting
later (this can be done thanks to "resuming feature" introduced in Http and Ftp
server, which allows you to specify at what byte number start to download).</LI>
<LI>splitting, divide the file in many pieces and let them start in a multithreaded
fashion.</LI>
</OL>
<P>As we saw in the previous section, a download accelerator allows us to
increase satellite bandwidth.
<H3>Under Linux</H3>
<P>
<UL>
<LI>
<A HREF="http://aria.rednoah.com/">Aria</A></LI>
</UL>
<H3>Under Windows</H3>
<P>
<UL>
<LI>
<A HREF="http://www.amazesoft.com">FlashGet</A></LI>
<LI>
<A HREF="http://www.getright.com">GetRight</A></LI>
<LI>
<A HREF="http://www.metaproducts.com">Mass Downloader</A></LI>
</UL>
<HR>
<A HREF="Sat-HOWTO-9.html">Next</A>
<A HREF="Sat-HOWTO-7.html">Previous</A>
<A HREF="Sat-HOWTO.html#toc8">Contents</A>
</BODY>
</HTML>