Before actually ordering service, there are several things you may want to explore.
Beyond the obvious consideration of price, there are many reasons to investigate which providers may be offering DSL services in your area. The large Telephone companies are everywhere, and may advertise the most. But increasingly smaller ISPs and independents are getting into the act. This is creating diversity in the DSL marketplace. A good thing of course, but possibly creating a little confusion too.
Not all DSL services are alike. Just because two local companies are offering "ADSL", does not mean that necessarily there is much in common at all. In fact, there are potentially a number of factors that make one ADSL provider's service significantly different from another's. Some things to consider:
Speed vs Price.
What hardware is provided, i.e. modem or router. Should be external ethernet in either case.
The ISP's Network architecture. PPPoX? Static IP? Servers allowed?
Is it an "always on" service, at least theoretically? Are there supplemental usage fees, or idle timeouts?
Linux friendly, Linux hostile, or Linux agnostic?
Quality of service. How is news, mail, etc.?
For a more lengthy discussion on some of these considerations and related issues, see the DSL Overview appendix for more on modems, qualifying for service, and choosing a provider.
Once you have chosen a provider, and ordered service, the next step is for the telco to "qualify" your loop. This essentially means testing your line to make sure it can handle the DSL signal, and possibly what level of service may be available to you. This may take some time, especially if the telco encounters problems with the loop. If no problems are found during this phase, then possibly there will be a two to three week wait for the installation. YMMV.
After the telco has qualified the loop and readied their end of the connection, the next step is installation of the necessary components at the customer's end of the connection: wiring modifications, splitter or filters, and, of course the modem and any necessary software.
You may or may not have a choice on how the installation is done, or who does it. This is totally at the discretion of the provider. Many providers offer a "self install" option where you do all the work. In this scenario, the provider will send a kit in order to save them from sending a tech, and thus reducing cost. Typically, self install kits will include microfilters for the POTS (Plain Old Telephone Service) phone jacks, the modem (and maybe a NIC), and a CDROM with drivers, etc. on it. In some cases, a splitter may be included instead of microfilters. In any case, some type of filtering is necessary on the non-DSL lines. If not the noise generated by the DSL signal may interfere with POTS devices.
The other possibility is for the provider to do the installation. Obviously, the cost is higher here, but it may have the advantage of having a trained tech do any wiring. There is also a better chance of getting a "splittered" installation with this option (a good thing!). Another benefit is that if something is wrong with the line, or the telco has not provisioned the line properly, an on-site tech may be able to help sort out certain kinds of problems quickly.
The self-install kit should come with full instructions, regardless of whether the installation will be splittered or filtered. So we won't go into much detail on this aspect.
There are various wiring schemes depending on how your service is being provided, who is providing it, and which DSL service is being provided.
Dedicated Line. Some DSLs require a dedicated, or "dry", wire pair, e.g. IDSL. This means a separate, physical line for DSL and Internet connectivity. Also, DSL services from CLECs (independent telcos like Covad or Rhythms), will use a dedicated line since the ILEC will not share one line with another company. (Instead the CLEC will actually lease a loop from the ILEC.) One your end, this simply means using one of the unused wire pairs in the telco wire bundle, and connecting it to the DSL jack.
Shared Line with Splitter. For DSLs like ADSL, that are provided over the same line as regular voice service (POTS), the signal must be filtered somehow so that voice services are not adversely effected. Installing a splitter splits the line into two pairs, and filters the DSL signal from one of them. This results in a inside wiring scheme where DSL goes to only one jack, and then POTS service to all other jacks. This is considered by many to be a better type of installation than "splitterless", i.e. with microfilters instead.
Splitters are available from various manufacturers and come in various shapes and sizes. Some are small enough to fit in the NID itself (sometimes called SNI, this is the telco phone box on the outside of your house), while others have a housing as large as the NID itself. Typically this is mounted near the NID, on the customer's side of the demarcation point.
Shared Line with Filters. Again, for DSLs that piggyback on the POTS line, the signal must be filtered or split at some point. The other way of doing this is by placing RJ11 "microfilters" in each phone jack -- except where the DSL modem will be. These filters are relatively small, plug-in devices and remove the higher frequencies associated with DSL. This is obviously much easier since no tools or wiring is required. This is often what is included in self-install kits, and is often referred to as a "splitterless" installation.
Shared Line, Splitterless and Filterless. Some newer DSLs, like G.Lite, have no adverse effect on regular POTS devices and thus require no filters or splitters. This would seem to be the wave of the future. Just plug and play. Though still not very common.
<--------Home/Office-----><---Loop---><--Central Office-->
POTS X-------+
phone, |
fax, |
etc, |
| CO
| -------
| | |
| | |
| ----- | |
POTS X-------+----Voice--=| S | | D |
| P | | S |=- Voice Switch
| L | 2 wire | L |
| I |=------------=| A |
| T | Local Loop | M |=- ISP --> INET
--------- | T | | |
Linux X--=| Modem |=-Data-=| E | | |
--------- | R | | |
----- | |
-------
<--------Home/Office-------><----Loop---><--Central Office-->
POTS X--Voice---[RJ11]------+
phone, (filter) |
fax, D CO
etc, a -------
t | |
a | |
POTS X--Voice---[RJ11]----- & | D |
(filter) V ----- | S |=- Voice Switch
o | N | 2 wire | L |
i-=| I |=-----------=| A |
c | D | Local Loop | M |=- ISP --> INET
e ----- | |
----------- | | |
Linux X--=| Modem |=-------| | |
----------- -------
If you are not doing the self-install option, then you may skip this section and move to Configuring Linux. If you are dong a self-install with microfilters, skip to the mircofilter section. The following procedures are meant to illustrate the wiring process. Please note that your procedures may be different at your location. Make sure you follow any warnings or safety instructions provided, that you RTFM, and that you are familiar with telco wiring procedures.
The first step will be to wire up the connections from your provider. Identify the line on which service will be installed, and the locations of your splitter and DSL jack(s). (For perhaps a better wiring scheme, see the Homerun section immediately below.)
Be aware that typical telco wire has more than one pair per bundle. Often, two pairs, but sometimes more. If you have but one phone line, the other pair(s) are unused. This makes them available for use with wiring for DSL. Wire pairs are color coded for easy identification. SDSL and IDSL require a dedicated, or "dry", pair. If an unused pair is available, then no real re-wiring is required. It is just a matter of re-wiring an existing jack for the correct pair of wires, and attaching the modem.
" I would not use microfilters if I lived across the street from my CO. A splitter is the only way to go. " | ||
| --A retired BellSouth ADSL installer | ||
Perhaps a somewhat better method of wiring for the DSL modem is sometimes called a "homerun". It is called this because it is one, straight shot from the splitter to the modem's DSL jack. What this does is bypass the existing inside wiring altogether, and any problems that might be lurking there -- like a corroded connection somewhere on a POTS jack. Inside wiring defects can be a source of headaches, especially in older homes.
It also allows you to route the cable to avoid any potential RFI (Radio Frequency Interference) sources. RFI anywhere in the circuit can be a DSL killer. Routing the cable away from items that may have electric motors, transformers, power supplies, high intensity lighting fixtures, dimmer switches and such, is a smart way to go. And you are also less likely to have a failing microfilter cause problems -- one potential point of failure instead of several. You can also use a better grade of cable such as CAT 5 or shielded twisted pair wire.
If your existing installation is "splitterless" (i.e. using microfilters) now, this will entail purchasing a splitter. And, of course, will also mean some new wiring will need to be run. Microfilters also add to the effective loop length -- as much as 700 ft per filter in some cases! So if you have several microfilters installed, and your sync rate or distance is marginal, eliminating these filters may result in a significant improvement.
If you have the splitterless design (i.e. using "microfilters") or a dedicated line, you may skip this part.
The splitter will typically consist of two parts, the splitter and a small outdoor housing. Mount the splitter and accompanying housing per the telco's instructions at the Network Interface Device (NID) point (also sometimes called the SNI or ONI), usually the side of your house where the phone line is located. Put it on your side of the NID. The phone company may need to access the splitter for maintenance, so its advisable to locate it on the outside where they can get at it, but outside is not absolutely necessary.
The wire bundle should have at least two separate wire pairs. The splitter takes one pair, and separates the signal onto two pairs. One pair in the bundle will then go to all POTS jacks, and the other to the modem's DSL wall jack. So connect the incoming telco line to the LINE side of the splitter. Then wire the inside pair for your telephone to the VOICE, and your inside wire pair for the modem to DATA.
Checkstep At this point, you should be able to pull dial tone off the voice side of the splitter. If this doesn't work, then you've wired it wrong. You can also plug the modem into the test jack in the NID box (most should have this). Plug in the modem's power cord, and if the line is provisioned correctly, you should "sync" in less than a minute. This test only requires the modem. (Internal and USB modems probably will require a driver to be loaded before syncing. This means having the computer there too.)
Wire the DSL wall jack (RJ11) at your computer location, which should already be connected to the DATA side of the splitter. The specifics differ for each situation, but basically you will have a wire pair that you will connect to the DSL jack. Make sure you read the directions, as the DSL-RJ11 wiring may be different for phones and DSL jacks. AND -- different modems may expect the signal on different pairs -- most on the inside pair, but some on the outside pair.
||
||
||
/ \
|RJ11|
| |
----
||||
^^ <-- Inside Most modems on inside pair
^ ^ <-- Outside Some on outside, e.g. Alcatel 1000, SpeedTouch Home
Pretty much a no-brainer here. If you are doing a "splitterless" installation, then install the provided microfilters in all phone jacks except the one where the DSL modem will be connected. These filter out the higher DSL frequencies and will keep the DSL noise from interfering with POTS equipment.
Warning! If you have an alarm system, it is recommended not to use microfilters. The alarm system's modem can be easily damaged by the DSL signal on the line. The recommend installation in this case is with a splitter.
To install, connect the modem's (or router's) power cord, and connect the phone line between the DSL wall jack and the modem. This cable should be provided. If not, a regular phone cord will suffice. With the ethernet interfaced modems, you may also connect the ethernet cable between the NIC and the modem (but not really necessary at this point just to verify the modem is working).
Checkstep At this point, verify that the modem syncs with the telco's DSLAM signal. Most modems have a green LED that lights up when the signal is good, and red or orange if not in sync. The modem's manual will have more details on the LEDs. If it doesn't sync, then check your wiring, or make sure that the DSL signal is being sent. Do this by calling your telco and verifying they have activated the service. Or by testing the modem at the test jack on the NID (see above). Note that having dial tone on the line does NOT confirm the presence of the DSL data signal. And vice versa -- perfectly possible to have dial tone and no DSL, or DSL and no dial tone. There should also be no static or noise on the voice line when everything is installed and functioning properly.
If you haven't already done so, install the NIC in your Linux machine, configure the kernel, or load modules, etc., etc. This is sometimes the biggest stumbling block -- getting the NIC recognized and working. See the various Linux references for doing this, such as the Ethernet HOWTO for more information. Also, see the Troubleshooting Section below. This is certainly something you could conceivably do ahead of time if you already have the NIC.
Be sure the RJ45 cable between the NIC and the modem is now connected. You can "hot plug" this cable, meaning there is no need to power down to do this.
We can do a few quick tests now to see if the NIC is functioning properly. First we'll attempt to bring up the interface. Then we'll see how well it is responding by pinging it. And lastly use ifconfig to check for errors:
# ifconfig eth0 10.0.0.1 up
$ ping -c 50 10.0.0.1
PING 10.0.0.1 (10.0.0.1) from 10.0.0.1: 56(84) bytes of data.
64 bytes from 10.0.0.1: icmp_seq=0 ttl=255 time=0.2 ms
64 bytes from 10.0.0.1: icmp_seq=1 ttl=255 time=0.2 ms
64 bytes from 10.0.0.1: icmp_seq=2 ttl=255 time=0.1 ms
<snip>
- 10.0.0.1 ping statistics -
50 packets transmitted, 50 packets received, 0% packet loss
round-trip min/avg/max = 0.1/0.1/0.2 ms
$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:50:04:C2:09:AC
inet addr:10.0.0.1 Bcast:10.255.255.255 Mask:255.0.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:428 errors:0 dropped:0 overruns:0 frame:0
TX packets:421 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:10 Base address:0xc800
|
If "eth0" comes up without errors, and you can ping it without errors, and ifconfig shows no errors, we should have all our hardware in working order now, and are ready to start configuring Linux. If not, see the Troubleshooting section below.
Gotcha: A few modems may already be wired as a 10baseT crossover, and require a direct Category 5 cable for a direct connection to a NIC, rather than a crossover cable. I lost around 12 hours figuring this one out, so don't make the same mistake - make sure you RTFM first.