I just turned up AT&T DSL service to our home. I wanted to get Verizon Fios or AT&T Uverse which are both offered “near” where I live, but I can’t get either yet - hopefully the trucks with the bright orange cable will arrive soon. So I went with AT&T for a bundled package over Time Warner. It includes 6Mbps DSL, Dish Network programming and phone service. I hope to uprade to Uverse IPTV at some point. The Dish programming and voice service is fine - but setting up the DSL service was an experience.
I opted out of the $200 fee to have a tech come to the house to setup the DSL service. I also opted out of their built in WiFi modem, for which I was lectured extensively by the rep that they wouldn’t guarantee Internet access to anything but the modem. Thanks for that.
Two days later a box arrived with my modem and filters for all of the phones in the house. You have to install a filter wherever a device uses a standard phone line since the DSL data portion of the signal is present on every phone jack. I plugged the modem in and it trained up indicating that it had a good DSL signal. I plugged my Mac laptop in and . . . nothing.
You see, I’m not big on instructions, and I had missed the part where I needed to run an installer on my Mac to start my service. AT&T provides a “wizard” of sorts that gets you setup before you can actulaly use the Internet service. Unlike Cable, AT&T uses an additional layer of authentication called PPP which allows AT&T to control access to service through the use of a username and password. Once I had run the setup, my Mac connected just fine, although I’m sure I’ve now collected a raft of adware. I also have an att.net throwaway email address in case I ever want to have yet another mailbox full of spam.
So at that point, I switched the connection from my Mac to my Linksys Wireless router and . . . nothing. Switching back to the Mac everything worked fine. In combing through the Linksys settings I realized that the Linksys was receiving a private IP address from the DSL modem. With a cable modem, the IP address is a public IP and it is bridged straight through to the home router - very simply to setup; you plugin and go. Not the case with the DSL modem. In fact, the IP address that the Linksys received was in the same IP address range as the IP addresses that the Linksys was giving to my Mac (and other devices) over WiFi. This is a “no no” in routing. To fix it, I changed the IP assignment range on the Linksys to be in a different range from the address the modem was handing out, and . . . it worked.
Now, I know that last paragraph will make some eyes glaze over. Suffice to say, most consumers, who opt for the “self install” package and wish to connect a Wifi router downstream of the modem are going to have issues. The linksys brand Wifi routers all come with 192.168.1.1 address by default and assign IP addresses somewhere in that address space. I suspect other brands do as well. The Motorola DSL modem also shipps with these same settings. Short of understanding some basic routing principles, it won’t be obvious to most consumers what the problem is when their PCs can’t find Google. Why Motorola didn’t pick a 10.0.0.0 range, or at least do some testing with popular Wifi routers to find non conflicting settings, I have no idea. Oh wait, maybe AT&T cuts them in on the follow up service call fees . . .
In any case, I got it all working and went straight to the Speakeasy bandwidth speed test program. If you want to get a good view on your actual throughput, both up and downstream, I highly recommend this little application. Point your browser to: http://www.speakeasy.net/speedtest/ and select the city nearest to you. I was a little dissapointed when the needle barely registered above 5 Megabits per second on my 6 Megabit per second service, but I knew why. The reason is all of the overhead in moving data across the DSL line. It is acronym alphabet soup in terms of the network stack: IP over TCP over PPP over Ethernet over AAL5 over ATM over ADSL. Holy . . .
What this translates into is a 16-20% loss of throughput for all of that overhead depending on how they package the TCP/IP portion. So, on the brightside, I’m getting a full 6 Megabit per second service, I’m just losing about 1 of those megabits on the downstream and about 200K or so on the upstream. Maybe they should just call it a 5 Megabit per second service . . . or do they just love the phone calls?