For over ten years I had DSL from Century-Link (Qwest), but in July of 2013 I switched to cable when Century Link was unable and unwilling to fix intermittent problems with my connection.
Qwest (now Century Link or whatever) either lied to me, or was clueless -- a distinction that is hard to make and equally frustrating. They told me the Cisco 678 would work at my new location. This was not true. The Cisco 678 won't handle the protcol involved with the new link (which is apparently ADSL2+ rather than vanilla ADSL).
This required me to invest in a new modem -- an Actiontec PK5000 at the cost of roughly $70. There are suggestions that I can put the 678 into "Bridge" mode rather than PPP mode and use it by connecting it to a PPPoE capable router, but I don't have the time or energy to fiddle with that. The Actiontec includes a builtin 802.11g wireless access point and a 4 port ethernet switch. It also runs embedded linux (and allows ssh access), so there would seem to be no limit to what a person with linux skills could do with this device. Initially I was unhappy with it, but I have actually grown to like it.
Here are some links:
Time for an update. It is May of 2013 and I have been here for about 3 years with Century Link DSL and the Actiontek. The Actiontek keeps on going -- every once in a while I have needed to reboot it by power cycling, but this is required maybe twice a year. What is an issue is that Century Link suffers from a variety of problems. Sometimes their DNS servers get haywire (and provide me with some stupid web page when they cannot resolve my request). Sometimes their equipment just stops working for hours on end (This happened for about 2 hours mid-day of May 9, 2013). Fairly frequently, and annoyingly they drop my ssh connections. This particularly irritates me when I am in the midst of editing some file on one of the servers I maintain.
The phone number to Century Link DSL support is 1-877-348-9005.
Things were OK for a while, then I started having serious trouble again. I got on the phone right away and a different tech came out. The guys in the field seem to really know their stuff. This guy replaced more stuff in my hookup box, then went out to the box near the street (which was buried under a foot of dirt and gravel) and discovered a second connection to my line there. He cut this and the signal levels came up to levels he liked a lot better. After this things were better ... for about a week.
We start off right away with screwy information, there ain't no black and yellow pair. The pairs are solid and striped, and there are 4 pairs to choose from.
I verified that only the center red and green wires are needed in the "phone patch" cable that runs from my wall jack to my modem. I verified this by installing a patch cable that has only these 2 wires and checking that my DSL connection (which happened to be in a good mood at the time) still worked. Good engineering practices would dictate keeping the Cat-5 cable for as much of the distance as possible right up to the modem and using as short a piece of phone cable as possible.
So, what I did was to chop off 3 inches from a phone cord in decent condition. The I took the center red and green wires and picked a pair from my Cat-5 cable to solder them to. I used the blue pair, since I like blue. I insulated this with a couple of layers of heat shrink tubing and pulled this through the wall and hooked it up to the phone box outside. This gives me a single pair of Cat-5 for as much of the distance as I can manage. I finished this repair at 5PM Friday 6-7-2013. It is working great so far.
Two days later I wait patiently, then at 1PM call to say "where the heck is the tech". Apparently my ticket is closed. The guy came and measured levels he felt were proper at the box and drove off without any communication with me. Now I am upset and have to waste another 20 minutes on the phone with a droid in India somewhere to schedule another visit two days later. This visit also gets cancelled (with my agreement). The tech called late in the day and was on the other side of town and my link was working at the time so I didn't expect a visit to be productive.
Thu May 30 --> 0.0 (0.0) minutes lost, 0.0 minutes slow Fri May 31 --> 2.3 (2.3) minutes lost, 0.0 minutes slow Sat Jun 1 --> 820.0 (855.0) minutes lost, 17.0 minutes slow Sun Jun 2 --> 55.5 (97.2) minutes lost, 31.2 minutes slow Mon Jun 3 --> 27.6 (47.2) minutes lost, 4.6 minutes slow Tue Jun 4 --> 62.4 (101.7) minutes lost, 612.5 minutes slow Wed Jun 5 --> 63.6 (95.9) minutes lost, 766.2 minutes slow Thu Jun 6 --> 51.8 (96.8) minutes lost, 95.6 minutes slow Fri Jun 7 --> 120.0 (178.8) minutes lost, 496.2 minutes slow Sat Jun 8 --> 70.3 (126.8) minutes lost, 18.4 minutes slow Sun Jun 9 --> 25.3 (46.0) minutes lost, 0.0 minutes slow Mon Jun 10 --> 65.7 (99.2) minutes lost, 12.7 minutes slow Tue Jun 11 --> 38.0 (56.4) minutes lost, 194.4 minutes slow Wed Jun 12 --> 389.9 (426.4) minutes lost, 213.2 minutes slow Thu Jun 13 --> 31.0 (55.0) minutes lost, 26.0 minutes slowI give two values for time lost. The first is simply when the modem does not report a CONNECTED status for both DSL and internet. The second adds on any uselessly short times (less than 5 minutes) when I have an unstable connection that is coming and going. The time I record as slow are when the modem says I am connected, but is reporting a speed less than I should be getting. I should get a 7168 Kbps download speed. I call anything less than 6500 slow.
I have given up hope on Century Link actually fixing anything and am waiting to see if my new modem does the trick. I am also waiting for a promotion from Cox cable that includes free installation and I will give them a try then if Century Link has not fixed my issues by then.
Wed May 29 13:57:36 MST 2013 CONNECTED CONNECTED 0 Day, 00H:19M:03S (67.1.97.106) 2656/192 Kbps Wed May 29 13:57:49 MST 2013 CONNECTING NOT CONNECTED 0 Day, 00H:00M:00S (N/A) 0/0 Kbps Wed May 29 13:58:00 MST 2013 CONNECTED CONNECTING 0 Day, 00H:00M:00S (N/A) 7168/896 Kbps Wed May 29 13:58:12 MST 2013 CONNECTED CONNECTING 0 Day, 00H:00M:00S (N/A) 7168/896 Kbps Wed May 29 13:58:23 MST 2013 CONNECTED CONNECTING 0 Day, 00H:00M:00S (N/A) 7168/896 Kbps Wed May 29 13:58:34 MST 2013 CONNECTED NOT CONNECTED 0 Day, 00H:00M:00S (N/A) 0/0 Kbps Wed May 29 13:58:45 MST 2013 NOT CONNECTED NOT CONNECTED 0 Day, 00H:00M:00S (N/A) 6336/896 Kbps Wed May 29 13:58:58 MST 2013 CONNECTED CONNECTING 0 Day, 00H:00M:00S (N/A) 0/0 Kbps Wed May 29 13:59:09 MST 2013 CONNECTING NOT CONNECTED 0 Day, 00H:00M:00S (N/A) 0/0 Kbps Wed May 29 13:59:20 MST 2013 CONNECTED CONNECTING 0 Day, 00H:00M:00S (N/A) 6880/896 Kbps Wed May 29 13:59:32 MST 2013 NOT CONNECTED NOT CONNECTED 0 Day, 00H:00M:00S (N/A) 0/0 Kbps Wed May 29 13:59:43 MST 2013 CONNECTING NOT CONNECTED 0 Day, 00H:00M:00S (N/A) 6176/736 Kbps Wed May 29 13:59:54 MST 2013 CONNECTED NOT CONNECTED 0 Day, 00H:00M:00S (N/A) 0/0 Kbps Wed May 29 14:00:05 MST 2013 NOT CONNECTED NOT CONNECTED 0 Day, 00H:00M:00S (N/A) 7072/896 Kbps Wed May 29 14:00:18 MST 2013 CONNECTED CONNECTING 0 Day, 00H:00M:00S (N/A) 0/0 Kbps Wed May 29 14:00:29 MST 2013 CONNECTING NOT CONNECTED 0 Day, 00H:00M:00S (N/A) 0/0 Kbps Wed May 29 14:00:40 MST 2013 CONNECTED CONNECTING 0 Day, 00H:00M:00S (N/A) 6304/608 Kbps Wed May 29 14:00:52 MST 2013 CONNECTED CONNECTED 0 Day, 00H:00M:05S (67.1.105.14) 6304/608 Kbps Wed May 29 14:01:04 MST 2013 CONNECTED CONNECTED 0 Day, 00H:00M:17S (67.1.105.14) 6304/608 Kbps Wed May 29 14:01:15 MST 2013 CONNECTED CONNECTED 0 Day, 00H:00M:28S (67.1.105.14) 6304/608 Kbps Wed May 29 14:01:28 MST 2013 CONNECTED CONNECTED 0 Day, 00H:00M:39S (67.1.105.14) 6304/608 Kbps Wed May 29 14:01:39 MST 2013 CONNECTED CONNECTED 0 Day, 00H:00M:52S (67.1.105.14) 6304/608 Kbps Wed May 29 14:01:50 MST 2013 CONNECTED CONNECTED 0 Day, 00H:01M:03S (67.1.105.14) 6304/608 KbpsThe above 4 minute section of log captures a connection being lost and then reacquired. This was before the latest round of repair work. Notice that the outside world IP number is logged along with my downstream and upstream speeds (which in this case are not yet what they should be).
One thing I see with this company is that nobody is empowered to do whatever it takes to fix my problem. Each person deals with their tiny realm and their hands are tied beyond a certain point. Perhaps a good strategy would have been when I had met one of the guys in the trucks and gotten their name and specific phone number to work with them as long as possible. Who knows.
I don't want cheaper internet, or even faster internet. I just want internet that is there reliably, not 20 hours out of a 24 hour day. Imagine picking up the phone and having the line dead for an hour or so every afternoon or evening!
Tom's Computer Info / [email protected]