public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Kirk Wood <cpt.kirk@1tree.net>
To: Speakup List <speakup@braille.uwo.ca>
Subject: Re: truth in cable
Date: Mon, 16 Jul 2001 23:18:01 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.21.0107162308560.32629-100000@ignatious> (raw)
In-Reply-To: <Pine.LNX.4.21.0107161940140.17508-100000@localhost>

Franke,

Thanks for the more detailed info. I don't know what the caps are on users
per local loop in cable either. I do know that they can add channels (each
able to support the 27Mbs) as they need more localized bandwidth. I have
had my service for over three years and also have only noticed bandwidth
problems much further upstream then the local loop.

As for the local download speed, while theoretically possible to obtain
27Mbs, I had a measured download speed of 3.2Mbps when they installed the
cable. Again, three years later I have yet to notice a slow down. What may
be of note, is that cable is the only afordable option for broadband in my
area. My local loop covers includes apartments about three miles away. So
at least in my area the slowdown is nothing but marketing hype to convince
you to by DSL.

As for real world experiances I have a close friend with DSL. He
experiances downloads slightly slower in speed. We have had about the same
amount of trouble with the lines. The big thing is that his ISP allows for
him to buy a routed subnet consisting of 5 available IPs. I can have
up to three non-routed IPs that are normally in different subnets.

=======
Kirk Wood
Cpt.Kirk@1tree.net

The mind is like a parachute; it works much better when open.
If you're too open minded, your brains will fall out.



  reply	other threads:[~ UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Kirk Wood
 ` Kaare Dehard
 ` Frank Carmickle
   ` Kirk Wood [this message]
     ` Kaare Dehard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.21.0107162308560.32629-100000@ignatious \
    --to=cpt.kirk@1tree.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).