1. Introduction

This document was written to assist the Linux user in setting up their cable modem, and includes information on configuring a DHCP client, enabling the device with or without USB support and troubleshooting. I have successfully configured Motorola and Toshiba brand cable modems with the methods herein, and others have informed me that the configuration methods of other manufacturers' hardware is almost identical. A mostly-complete laundry list of hardware specific tidbits is addressed in Section 4; if you have a model working that is not listing or have some specific informtion that you think will be helpful, please send it along via the address in Section 1.5

1.1. Copyright Information

This document is Copyright 2004 by Howard Shane.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found in Appendix A.

1.2. Disclaimer

No liability for the contents of this document can be accepted. Use the concepts, examples and other content entirely at your own risk. As this is a new edition, there may be technical or other inaccuracies that may result in the loss of irreplaceable data. In any case, proceed with caution, and realize that although errors are highly unlikely, the author can accept no responsibility for them.

All copyrights are held by their by their respective owners, unless specifically noted otherwise. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark.

Naming of particular products or brands should not be seen as endorsements.

1.3. New Versions

This is the initial release.

The latest version number of this document can be found here.

1.4. Credits

I would like to thank Brad Hards, the primary author of the Linux CDCEther kernel driver for graciously volunteering several useful bits of information, as well as Rob McGee and Jess Portnoy for encouraging me to morph this document into the new Cable-Modem HOWTO and contributing useful suggestions.

Also, I would like to thank Marla, who has stood by me confidently even when the outlook was dimmest and others unforgiving. I'm yours forever.

1.5. Feedback

Please send any additions or comments pertaining to this document to the following email address: .

1.6. Conventions Used in this Document

The following conventions are used in this document and are outlined here for those who may not yet have a complete understanding of how to access and control the underlying operating system in Linux, which is almost always the bash shell.

First, filenames are referenced in a paragraph like so: /path/file

Commands in Linux are executed (or 'called') at the command prompt, otherwise known as the 'command line.' If you are in the non-graphical (text-based) environment you will usually be presented the bash shell prompt which is a dollar sign:
$
...or the hash mark:
#
...if you have logged in as root or have acquired root, or 'superuser' privileges. You can also access the bash shell in the X window system, otherwise known as X or X11, with an xterm or similar X-terminal-emulator. Commands to be performed at the bash prompt, but referenced in a paragraph of this document, usually look like this: do this now

Commands and/or the resulting output of commands may also be outlined with screen output in their own paragraph or heading:

$
date Sun Jul 27 22:37:11 CDT 2003

When a command is written in front of the bash prompt (e.g. $ date above), it is assumed the [Return] or [Enter] key has been depressed after the command, possibly followed by the output (e.g., the date).