Nick, <[EMAIL PROTECTED]> , wrote:
> Hello, Ive had my cable modem hooked up succesfully for over a month now,
> im using the @home services.
>
> my problem is that it doesnt seem to be as fast as its "cracked up" to be,
> particularly when telneting to my remote server and editing files remotely
The performance factor that matters when telneting is latency, not
bandwidth. I can use my own modem connection at my office for ppp
connections or i can use an ISP's connection. With the ISP I get twice the
bandwidth but much worse latency. Bandwidth isn't a big issue telneting,
but latency is. With bad latency I can type well ahead of the the
characters appearing on the screen (and I'm a SLOW typist). The problem is
that the ISP is connecting to my remote system via several internet hops.
When I use my own system as a ppp server, I have only a single local 'hop'
between me and the remote system.
Your cable modem offers large bandwidth (for downloads), but no lower
latency than a regular ISP.
Mark <[EMAIL PROTECTED]>
--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
