Usually illegal, always unethical and generally a violation of your contract, "u

ncapping" refers to removing the download or upload bandwidth cap imposed by you
r cable or xDSL ISP.
Uncapping xDSL.
Three words: "Don't even bother".
xDSL technology doesn't work in a way that permits you to have any settings that
diverge in the slightest from what you're supposed to have. Any differences and
the system cuts you off. Period. This is because xDSL is shared at the DSLAM an
d not on the medium. Each line is treated as a individual connection, and config
ured as such. You get what you pay for. And no more. Cable, on the other hand, w
orks differently.
Uncapping Cable.
Cable is a shared medium, each area it serves is somewhat like a LAN.
This means there's X amount of bandwidth for ALL the users on the node to share,
and there's a lot of bandwidth. Now, there is a LOT less upstream bandwidth tha
n down, for a variety of technical reasons I won't go into, just understand it i
s a necessary part of the design. Some people feel cheated by this and want a wa
y around this inherent limitation. Some other folks just want their share of the
bandwidth, YOUR share of that bandwidth, and MY share as well, as much as they
can get away with and damn the consequences to everyone else.
Fair?
Not really, but then again we're talking about people you can't see, and apparen
tly it's okay in some folks' mind to steal from others, as long as they can't se
e them. It's an infantile "nyah-nyah-nyah I can't see you so you don't exist so
this has no consequences" type behavior.
My dog is smarter than that. She at least has figured out that even if she can't
see something, it might still be there. Apparently though, the "reality is defi
ned only by what I *see*" thing is about as heavy a concept as some folks can ha
ndle. Anyways, back to "uncapping".
The Myth.
Unfortunately there is this persistent urban myth that simply changing one or tw
o 'super secret settings' somewhere on some 'hidden interface' will magically tu
rn any cable or xDSL modem into WOPR from Wargames. Giving it the ability to: Co
ntrol nuclear missiles remotely, Blazing fast downloads and uploads, 2 milliseco
nd pings to the MIR space station, and play a helluva game of Tic-Tac-Toe while
it's at it! Now, all good urban myths have some tiny kernel of fact, and this on
e does as well.
The Origin.
See, in one or two older NON-DOCSIS systems, using a particular brand of modem a
nd one version of firmware it WAS possible to put the modem into a sort of "rout
er bypass" mode, and ignore configuration instructions, by ignoring the CMTS. A
clever fellow created a program and a series of instructions to do just that aga
inst the European cable provider UPC. That was pre-DOCSIS though.
CMTS? DOCSIS? What are they, and what are the facts?
The Facts.

So you know, DOCSIS is the "Data Over Cable Service Interface Specification". It
's a standard that governs how cable modems behave and interoperate. The majorit
y of systems out there, especially from the big cable ISPs, are DOCSIS compliant
. The rest are headed that way.
The upside is that if you own your modem, and move to a new locality, if they ar
e DOCSIS compliant you can use the same modem regardless of what kind they norma
lly lease or sell. The downside is that boo-hoo, you can't steal from others. No
uncapping.
The reason it doesn't work is that under DOCSIS, the modem goes through a whole
series of steps before you are ever allowed on line. The short version is as fol
lows:
After power is applied:
The modem "ranges" for useable download/upload frequencies that no one else is u
sing.
Having found useable frequencies, it contacts the Cable Modem Termination System
, (CMTS) sometimes called the headend.
The headend responds with some information, one part of which is the address and
name of a configuration file.
The modem goes to this address at the headend and downloads the configuration fi
le which contains IP addresses, cap settings, and a whole host of other signalli
ng and troubleshooting instructions.
The modem applies this file internally.
The modem then authenticates these settings with the CMTS.
NOW it may begin to transmit.
As you can see, it's a complicated process, and until it's complete, you MAY NOT
transmit data. Period. It's also periodically refreshed. The modem recieves the
"config settings" file every so often from the CMTS and re-applies the settings
, making any changes the new settings may dictate. This means that system adjust
ments can be done on the fly, which is an advantage from a systems management pe
rspective.
There are multiple reasons why it's so complicated. Remember that the process mu
st make sure that:
No one can simply plug a modem in and start using the service.
To make sure the service caps are enforced.
It's also designed to allow for reliability throughout the system so that no sin
gular haywire modem is jamming the entire spectrum and taking down multiple user
s.
Finally, each modem MAY have it's own file. So that if you buy a work account, y
ou might have more access than your neighbor with the home account. You pay more
for that of course. This is a business after all. So that's the brief version o
f the DOCSIS system, and why uncapping it is a semi-myth.
As to the guy who wrote the "uncapper" program?
Last we heard, he was headed into court on some fairly serious charges. And the
firmware has long since been fixed.
The Conclusion.
It would be easier if "uncapping" were simply a myth end to end, then I wouldn't
have to explain all this. Point is still the same though. If you have DOCSIS, y
ou get what you pay for. Stop trying to steal from your neighbors, they'll be ha
ppier and you'll be happier. And you won't have to go to court on 'theft of serv

ice' or possibly Federal equipment tampering charges.

On a personal note I'd like to extend my thanks to all the engineers who've take
n time out of their schedules to detail the inner technical working of DOCSIS to
me, and to my fellow Moderators and the Administrator here at SpeedGuide.net fo
r all their help as well. Any errors are my responsibility. As always, if you ha
ve RFCs or white papers on DOCSIS or related specs on this subject I'd love to t
ake a look at them.

Regards,
Thomas (Bouncer) Blakely