WRTP54G Locking up and/or dropping wireless

Posts: 80

I have been patient and I have been understanding but now when it comes time to resolve the issue, I have to say... I feel let down by Vonage. Or perhaps suckered is a better phrase.

My WRTP54G has been dropping wireless connections since I got it back in August of 2005. It was never a major problem because it wouldn't last more than a few minutes and didn't happen very often. Now it occurs at least once an hour (if not more) and makes it very hard to use a wirelessly connected machine.

The other issue is that the whole unit locks up every 72 hours. It is a hard lock and requires power cycling before it is usable again.

I have made repeated calls to Vonage to try and resolve the problem with no luck. They finally told me that the unit needs to be replaced. When I was sent to "that department" they were happy to do the replacement but since it was past the initial 90 day warranty (only 90 days?!) I would have to buy a new one for the same price I paid retail. Rebates did not and still do not apply to people who already have service.

Before I go out and buy a new router, wireless, ATA device or a mix and match thereof, does anyone have any advice? I think I am done with the WRTP54G, despite it being a Linksys product - it is just too flaky.

The regular mix of resets (hard and soft), elimination of devices from the network, UPS power instead of the AC outlet and general Vonage Tech Support troubleshooting has been done.

I have included the log file during a wireless drop for anyone who might gather anything useful from it. I couldn't convince the people from Vonage to even consider looking at it.

Wireless drop shown in the log....
============================
6816 Mon Jan 23 9:10:43 2006 192.168.100.1 [001310A3CE15] cfgmgr(manager): manager_find_defaults - !mod
6817 Mon Jan 23 9:10:43 2006 192.168.100.1 [001310A3CE15] cfgmgr(manager): manager_find_defaults - !mod
6818 Mon Jan 23 9:10:43 2006 192.168.100.1 [001310A3CE15] cfgmgr(manager): manager_get_defaults - !config
6819 Mon Jan 23 9:10:43 2006 192.168.100.1 [001310A3CE15] cfgmgr(manager): manager_get_defaults - !config
6820 Mon Jan 23 9:13: 7 2006 192.168.100.1 [001310A3CE15] cfgmgr(dhcpc-105): sys_send_event - dhcp up
6821 Mon Jan 23 9:13: 7 2006 192.168.100.1 [001310A3CE15] cfgmgr(dhcpc-105): sys_send_event - dhcp up
6822 Mon Jan 23 9:13:12 2006 192.168.100.1 [001310A3CE15] cfgmgr(manager): manager_find_defaults - !mod
6823 Mon Jan 23 9:13:12 2006 192.168.100.1 [001310A3CE15] cfgmgr(manager): manager_find_defaults - !mod
6824 Mon Jan 23 9:13:12 2006 192.168.100.1 [001310A3CE15] cfgmgr(manager): manager_get_defaults - !config
6825 Mon Jan 23 9:13:12 2006 192.168.100.1 [001310A3CE15] cfgmgr(manager): manager_get_defaults - !config
6826 Mon Jan 23 9:14:26 2006 192.168.100.1 [001310A3CE15] 1455899: Receive assoc failed from wpa,station index 2.
6827 Mon Jan 23 9:14:26 2006 192.168.100.1 [001310A3CE15] 1455899: Receive assoc failed from wpa,station index 2.
6828 Mon Jan 23 9:14:26 2006 192.168.100.1 [001310A3CE15] 1455907: Receive assoc failed from wpa,station index 2.
6829 Mon Jan 23 9:14:26 2006 192.168.100.1 [001310A3CE15] 1455907: Receive assoc failed from wpa,station index 2.
6830 Mon Jan 23 9:14:27 2006 192.168.100.1 [001310A3CE15] 1455910: Receive assoc failed from wpa,station index 3.
6831 Mon Jan 23 9:14:27 2006 192.168.100.1 [001310A3CE15] 1455910: Receive assoc failed from wpa,station index 3.
6832 Mon Jan 23 9:14:29 2006 192.168.100.1 [001310A3CE15] 1455933: Receive assoc failed from wpa,station index 2.
6833 Mon Jan 23 9:14:29 2006 192.168.100.1 [001310A3CE15] 1455933: Receive assoc failed from wpa,station index 2.
6834 Mon Jan 23 9:14:30 2006 192.168.100.1 [001310A3CE15] 1455947: Receive assoc failed from wpa,station index 2.
6835 Mon Jan 23 9:14:30 2006 192.168.100.1 [001310A3CE15] 1455947: Receive assoc failed from wpa,station index 2.
6836 Mon Jan 23 9:14:31 2006 192.168.100.1 [001310A3CE15] 1455956: Receive assoc failed from wpa,station index 2.
6837 Mon Jan 23 9:14:31 2006 192.168.100.1 [001310A3CE15] 1455956: Receive assoc failed from wpa,station index 2.
6838 Mon Jan 23 9:14:32 2006 192.168.100.1 [001310A3CE15] 1455965: Receive assoc failed from wpa,station index 2.
6839 Mon Jan 23 9:14:32 2006 192.168.100.1 [001310A3CE15] 1455965: Receive assoc failed from wpa,station index 2.
6840 Mon Jan 23 9:14:34 2006 192.168.100.1 [001310A3CE15] 1455979: Receive assoc failed from wpa,station index 2.
6841 Mon Jan 23 9:14:34 2006 192.168.100.1 [001310A3CE15] 1455979: Receive assoc failed from wpa,station index 2.
6842 Mon Jan 23 9:14:37 2006 192.168.100.1 [001310A3CE15] 1456012: Receive assoc failed from wpa,station index 2.
6843 Mon Jan 23 9:14:37 2006 192.168.100.1 [001310A3CE15] 1456012: Receive assoc failed from wpa,station index 2.
6844 Mon Jan 23 9:14:38 2006 192.168.100.1 [001310A3CE15] 1456023: Receive assoc failed from wpa,station index 2.
6845 Mon Jan 23 9:14:38 2006 192.168.100.1 [001310A3CE15] 1456023: Receive assoc failed from wpa,station index 2.
6846 Mon Jan 23 9:14:39 2006 192.168.100.1 [001310A3CE15] 1456033: Receive assoc failed from wpa,station index 2.
6847 Mon Jan 23 9:14:39 2006 192.168.100.1 [001310A3CE15] 1456033: Receive assoc failed from wpa,station index 2.
6848 Mon Jan 23 9:14:40 2006 192.168.100.1 [001310A3CE15] 1456042: Receive assoc failed from wpa,station index 2.
6849 Mon Jan 23 9:14:40 2006 192.168.100.1 [001310A3CE15] 1456042: Receive assoc failed from wpa,station index 2.
6850 Mon Jan 23 9:14:41 2006 192.168.100.1 [001310A3CE15] 1456052: Receive assoc failed from wpa,station index 2.
6851 Mon Jan 23 9:14:41 2006 192.168.100.1 [001310A3CE15] 1456052: Receive assoc failed from wpa,station index 2.
6852 Mon Jan 23 9:14:42 2006 192.168.100.1 [001310A3CE15] 1456062: Receive assoc failed from wpa,station index 2.
6853 Mon Jan 23 9:14:42 2006 192.168.100.1 [001310A3CE15] 1456062: Receive assoc failed from wpa,station index 2.
6854 Mon Jan 23 9:14:43 2006 192.168.100.1 [001310A3CE15] 1456073: Receive assoc failed from wpa,station index 2.
6855 Mon Jan 23 9:14:43 2006 192.168.100.1 [001310A3CE15] 1456073: Receive assoc failed from wpa,station index 2.
6856 Mon Jan 23 9:14:45 2006 192.168.100.1 [001310A3CE15] 1456092: Receive assoc failed from wpa,station index 2.
6857 Mon Jan 23 9:14:45 2006 192.168.100.1 [001310A3CE15] 1456092: Receive assoc failed from wpa,station index 2.
6858 Mon Jan 23 9:14:46 2006 192.168.100.1 [001310A3CE15] 1456103: Receive assoc failed from wpa,station index 2.
6859 Mon Jan 23 9:14:46 2006 192.168.100.1 [001310A3CE15] 1456103: Receive assoc failed from wpa,station index 2.
6860 Mon Jan 23 9:14:47 2006 192.168.100.1 [001310A3CE15] 1456113: Receive assoc failed from wpa,station index 2.
6861 Mon Jan 23 9:14:47 2006 192.168.100.1 [001310A3CE15] 1456113: Receive assoc failed from wpa,station index 2.
6862 Mon Jan 23 9:14:48 2006 192.168.100.1 [001310A3CE15] 1456123: Receive assoc failed from wpa,station index 2.
6863 Mon Jan 23 9:14:48 2006 192.168.100.1 [001310A3CE15] 1456123: Receive assoc failed from wpa,station index 2.
6864 Mon Jan 23 9:14:49 2006 192.168.100.1 [001310A3CE15] 1456132: Receive assoc failed from wpa,station index 2.
6865 Mon Jan 23 9:14:49 2006 192.168.100.1 [001310A3CE15] 1456132: Receive assoc failed from wpa,station index 2.
6866 Mon Jan 23 9:14:50 2006 192.168.100.1 [001310A3CE15] 1456143: Receive assoc failed from wpa,station index 2.
6867 Mon Jan 23 9:14:50 2006 192.168.100.1 [001310A3CE15] 1456143: Receive assoc failed from wpa,station index 2.
6868 Mon Jan 23 9:14:51 2006 192.168.100.1 [001310A3CE15] 1456153: Receive assoc failed from wpa,station index 2.
6869 Mon Jan 23 9:14:51 2006 192.168.100.1 [001310A3CE15] 1456153: Receive assoc failed from wpa,station index 2.
6870 Mon Jan 23 9:14:52 2006 192.168.100.1 [001310A3CE15] 1456163: Receive assoc failed from wpa,station index 2.
6871 Mon Jan 23 9:14:52 2006 192.168.100.1 [001310A3CE15] 1456163: Receive assoc failed from wpa,station index 2.
6872 Mon Jan 23 9:14:53 2006 192.168.100.1 [001310A3CE15] 1456173: Receive assoc failed from wpa,station index 2.
6873 Mon Jan 23 9:14:53 2006 192.168.100.1 [001310A3CE15] 1456173: Receive assoc failed from wpa,station index 2.
6874 Mon Jan 23 9:14:57 2006 192.168.100.1 [001310A3CE15] 1456212: Receive assoc failed from wpa,station index 2.
6875 Mon Jan 23 9:14:57 2006 192.168.100.1 [001310A3CE15] 1456212: Receive assoc failed from wpa,station index 2.
6876 Mon Jan 23 9:14:58 2006 192.168.100.1 [001310A3CE15] 1456222: Receive assoc failed from wpa,station index 2.
6877 Mon Jan 23 9:14:58 2006 192.168.100.1 [001310A3CE15] 1456222: Receive assoc failed from wpa,station index 2.
6878 Mon Jan 23 9:14:59 2006 192.168.100.1 [001310A3CE15] 1456232: Receive assoc failed from wpa,station index 2.
6879 Mon Jan 23 9:14:59 2006 192.168.100.1 [001310A3CE15] 1456232: Receive assoc failed from wpa,station index 2.
6880 Mon Jan 23 9:15: 0 2006 192.168.100.1 [001310A3CE15] 1456243: Receive assoc failed from wpa,station index 2.
6881 Mon Jan 23 9:15: 0 2006 192.168.100.1 [001310A3CE15] 1456243: Receive assoc failed from wpa,station index 2.
6882 Mon Jan 23 9:15: 1 2006 192.168.100.1 [001310A3CE15] 1456252: Receive assoc failed from wpa,station index 2.
6883 Mon Jan 23 9:15: 1 2006 192.168.100.1 [001310A3CE15] 1456252: Receive assoc failed from wpa,station index 2.
6884 Mon Jan 23 9:15: 2 2006 192.168.100.1 [001310A3CE15] 1456262: Receive assoc failed from wpa,station index 2.
6885 Mon Jan 23 9:15: 2 2006 192.168.100.1 [001310A3CE15] 1456262: Receive assoc failed from wpa,station index 2.
6886 Mon Jan 23 9:15: 3 2006 192.168.100.1 [001310A3CE15] 1456272: Receive assoc failed from wpa,station index 2.
6887 Mon Jan 23 9:15: 3 2006 192.168.100.1 [001310A3CE15] 1456272: Receive assoc failed from wpa,station index 2.
6888 Mon Jan 23 9:15: 5 2006 192.168.100.1 [001310A3CE15] 1456293: Receive assoc failed from wpa,station index 2.
6889 Mon Jan 23 9:15: 5 2006 192.168.100.1 [001310A3CE15] 1456293: Receive assoc failed from wpa,station index 2.
6890 Mon Jan 23 9:15: 6 2006 192.168.100.1 [001310A3CE15] 1456302: Receive assoc failed from wpa,station index 2.
6891 Mon Jan 23 9:15: 6 2006 192.168.100.1 [001310A3CE15] 1456302: Receive assoc failed from wpa,station index 2.
6892 Mon Jan 23 9:15: 7 2006 192.168.100.1 [001310A3CE15] 1456312: Receive assoc failed from wpa,station index 2.
6893 Mon Jan 23 9:15: 7 2006 192.168.100.1 [001310A3CE15] 1456312: Receive assoc failed from wpa,station index 2.
6894 Mon Jan 23 9:15: 8 2006 192.168.100.1 [001310A3CE15] 1456323: Receive assoc failed from wpa,station index 2.
6895 Mon Jan 23 9:15: 8 2006 192.168.100.1 [001310A3CE15] 1456323: Receive assoc failed from wpa,station index 2.
6896 Mon Jan 23 9:15: 9 2006 192.168.100.1 [001310A3CE15] 1456333: Receive assoc failed from wpa,station index 2.
6897 Mon Jan 23 9:15: 9 2006 192.168.100.1 [001310A3CE15] 1456333: Receive assoc failed from wpa,station index 2.
6898 Mon Jan 23 9:15:10 2006 192.168.100.1 [001310A3CE15] 1456342: Receive assoc failed from wpa,station index 2.
6899 Mon Jan 23 9:15:10 2006 192.168.100.1 [001310A3CE15] 1456342: Receive assoc failed from wpa,station index 2.
6900 Mon Jan 23 9:15:11 2006 192.168.100.1 [001310A3CE15] 1456352: Receive assoc failed from wpa,station index 2.
6901 Mon Jan 23 9:15:11 2006 192.168.100.1 [001310A3CE15] 1456352: Receive assoc failed from wpa,station index 2.
6902 Mon Jan 23 9:15:12 2006 192.168.100.1 [001310A3CE15] 1456363: Receive assoc failed from wpa,station index 2.
6903 Mon Jan 23 9:15:12 2006 192.168.100.1 [001310A3CE15] 1456363: Receive assoc failed from wpa,station index 2.
6904 Mon Jan 23 9:15:13 2006 192.168.100.1 [001310A3CE15] 1456373: Receive assoc failed from wpa,station index 2.
6905 Mon Jan 23 9:15:13 2006 192.168.100.1 [001310A3CE15] 1456373: Receive assoc failed from wpa,station index 2.
6906 Mon Jan 23 9:15:13 2006 192.168.100.1 [001310A3CE15] 1456375: Receive assoc failed from wpa,station index 4.
6907 Mon Jan 23 9:15:13 2006 192.168.100.1 [001310A3CE15] 1456375: Receive assoc failed from wpa,station index 4.
6908 Mon Jan 23 9:15:19 2006 192.168.100.1 [001310A3CE15] 1456432: Receive assoc failed from wpa,station index 2.
6909 Mon Jan 23 9:15:19 2006 192.168.100.1 [001310A3CE15] 1456432: Receive assoc failed from wpa,station index 2.
6910 Mon Jan 23 9:15:20 2006 192.168.100.1 [001310A3CE15] 1456443: Receive assoc failed from wpa,station index 2.
6911 Mon Jan 23 9:15:20 2006 192.168.100.1 [001310A3CE15] 1456443: Receive assoc failed from wpa,station index 2.
6912 Mon Jan 23 9:15:21 2006 192.168.100.1 [001310A3CE15] 1456453: Receive assoc failed from wpa,station index 2.
6913 Mon Jan 23 9:15:21 2006 192.168.100.1 [001310A3CE15] 1456453: Receive assoc failed from wpa,station index 2.
6914 Mon Jan 23 9:15:22 2006 192.168.100.1 [001310A3CE15] 1456463: Receive assoc failed from wpa,station index 2.
6915 Mon Jan 23 9:15:22 2006 192.168.100.1 [001310A3CE15] 1456463: Receive assoc failed from wpa,station index 2.
6916 Mon Jan 23 9:15:23 2006 192.168.100.1 [001310A3CE15] 1456472: Receive assoc failed from wpa,station index 2.
6917 Mon Jan 23 9:15:23 2006 192.168.100.1 [001310A3CE15] 1456472: Receive assoc failed from wpa,station index 2.
6918 Mon Jan 23 9:15:37 2006 192.168.100.1 [001310A3CE15] cfgmgr(dhcpc-105): sys_send_event - dhcp up
6919 Mon Jan 23 9:15:37 2006 192.168.100.1 [001310A3CE15] cfgmgr(dhcpc-105): sys_send_event - dhcp up
==================================

Posts: 2257 · Posted: Mon Jan 23, 2006 10:33 am Post subject:

You don't need to replace your WRTP54G as a Vonage adapter. Bereft of the responsibility to run your network, the WRTP54G is actually a quite wonderful Vonage phone adapter.

However, as a router, meh. I'm not all that impressed. It works OK, but I get FAR better range and reliability of wireless using a different router (which I bought to fix a couple of other deficiencies in the WRTP54G).

Go out and get yourself a regular Linksys wireless router, such as the WRT54G, and put it in front of the WRTP54G. Then turn off the WRTP54G's QoS, firewall, wireless, etc, and just use it as a "dumb" Vonage telephone adapter. Hook its WAN port to any of the LAN ports on your new router.

If you want to be able to get into the WRTP54G's administration screens, simply set up "Remote Router Access" on port 8080 (see the "Administration" menu, set up the WRTP54G with a fixed IP address outside the normal DHCP range of your WRT54G (192.168.1.200 should work well), and you can access the WRTP54G using http://192.168.1.200:8080

If you really want to get fancy, get the WRT54GL, which is the Linux variant of the WRT54G. This will allow you to add aftermarket firmware to your main router that adds features like Static DHCP (forcing the WRTP54G to have the same IP address while leaving the WRTP54G itself to "get IP automatically").

Posts: 80 · Posted: Mon Jan 23, 2006 10:37 am Post subject:

If I can't figure out why it is locking up every 72 hours, it will have to go. I'm just concerned that I seem to be the only one experiencing these two particular issues.

Posts: 1125 · Posted: Mon Jan 23, 2006 10:43 am Post subject:

"Go out and get yourself a regular Linksys wireless router, such as the WRT54G, and put it in front of the WRTP54G. Then turn off the WRTP54G's QoS, firewall, wireless, etc, and just use it as a "dumb" Vonage telephone adapter. Hook its WAN port to any of the LAN ports on your new router."

I agree, this works great, and with this the Vonage device no longer controls your connection to the outside world.

Posts: 2257 · Posted: Mon Jan 23, 2006 10:59 am Post subject:

Mine locked up every 24 hours, but that was mostly because I use BitTorrent as well as a couple of VPN connections, and I was just overloading the poor little darling's IP connections table. Put it behind a "real" router, and relegate it to Vonage duty only, and watch what that unit can do. It truly is a high quality Vonage adapter.

In fact, believe it or not, once you shut down wireless and firewall and all the other stuff you don't need when the WRTP54G is just a Vonage adapter, you'll probably see significant improvements in voice quality, in addition to having a network that works well. I know I did.

This "lockup" is a common problem with the Linksys series of routers - though Linksys has apparently fixed it in their latest WRT54G (V5) units and it can be easily fixed in the earlier series by loading aftermarket firmware. This series of router does not drop idle connections until 5 days of inactivity. The router has an IP connection table that can hold 2,048 connections. For normal web surfing on a couple of computers, this is fine. For ANY sort of heavy use, this table fills up really, really quickly.

Now, I'm not SURE this is what your problem is, but you can test it by trying to reuse an existing connection when it locks up (for example, you can hit refresh on a web page you visited recently). If that works, but you cannot make any *new* connections, then your iptable is full.

The "fix" is to lower the time limit to convert "active but idle" connections into "dead" connections in less than 5 days, allowing these connections to be recycled faster and preventing the table from being filled up. I use 4 hours as my setting, some people use as little as 5 minutes.

Now, maybe, CyberTAN will write this fix into the next firmware release. Maybe.

But consider the following: Do you REALLY want the firmware that runs your NETWORK to be controlled by someone else? Routing performance will never be a priority in the WRTP54G/RTP300 series. And with only 16MB RAM in those units, there's little enough memory to do even the basic routing functions, much less Voip. My WRT54G only has 1MB free as it stands, and it doesn't know anything about Voip.

In my case, I took some of the money I had been saving and invested it in a new router, that *I* controlled.

Posts: 80 · Posted: Fri Jan 27, 2006 7:08 pm Post subject:

NateHoy wrote:

You don't need to replace your WRTP54G as a Vonage adapter. Bereft of the responsibility to run your network, the WRTP54G is actually a quite wonderful Vonage phone adapter.

Your advice is "spot-on" so far. I went out on Monday and bought a new WRT54G wireless router and performed a labotomy on my WRTP54G to make it an attractive ATA with ultrablue lights. 100% of my issues went away the moment I brought up the new router and kicked the old one downstairs.

I have to wonder why they heck Vonage/Linksys would let that router out of the barn if it isn't capable of delivering what it promises. That is what NetGear does and they don't need any competition.

Thank you very much for your counsel.

- Mark

Posts: 13 · Posted: Sat Mar 04, 2006 1:14 am Post subject:

Hello all.

I just signed up for Vonage, ordered the Linksys WRTP54G router, and it's been locking up and dumping the wireless connection 15 seconds after it starts up. Even the wired connections sometimes are unusable when the unit locks up. I have to cycle the power to get the thing to work again.

I actually paid extra for the wireless router when I signed up and after spending 3 hours on the phone with Vonage Wreck Support in India, I came to the conclusion that the router is, as NateHoy suggests, just a bad piece of hardware for routing. I should have gotten the wired router which didn't cost anything.

As I indicated, I tried Vonage "Customer Care" and ended up having to go through the process of non-problem solving three times, being asked the same trouble-shooting questions by three different "techs." Finally I told Customer Care specialist number 3 that I wanted to talk to someone about getting a new wireless router. I ended up in "you're the next caller" limbo for nearly 45 minutes before I gave up.

Should I bother replacing the wireless unit or should I return it, get my money back, and get a wired unit instead? I have a D-Link 54G wireless router that works flawlessly so I probably could live without the Linksys WRTP54G. I do like the pretty blue lights but are they worth 50 bucks?

So far Vonage has struck out in the Tech Support Department and hardware department. At this point I live in terror of the moment that my old school Telco finishes porting over my number to Vonage.

I've only been a Vonage customer for a week and I'm already frustrated....

-Victim

BTW- cool avatar mwmcclure.....

Posts: 80 · Posted: Sat Mar 04, 2006 9:32 am Post subject:

Natehoy's suggestion of turning my WRTP54G into a terminal adapter and letting something else do the routing and wireless has worked out for me. If you have the option of taking your back to the store for a refund, do it today.

I just setup a friend with Vonage and we got her the PAP2 and a WRT54G (wired and wireless router) and it is quite stable.

My wireless, wired, TA is now at the end of the line instead of the beginning and I haven't had a lockup since I relieved it of it's routing responsibilities.

And the avatar is from Rainbow 6 by Tom Clancy. I have never played the game but I love his books.

Posts: 13 · Posted: Sat Mar 04, 2006 11:09 am Post subject: Thanks for the advice...!

Thanks for the advice. I'm glad to hear you have your connectivity problems sorted.

I guess I'll return the Linksys wireless router. I ordered it directly fromVonage so I'm sure there's going to be a lot of waiting on the phone involved.

I find it appalling that Vonage and Linksys would market a product that is defective or ineffective in its intended purpose. I am going to voice my displeasure to both companies and I hope others who have had problems with this hardware do the same.

Marketing a product that is not ready for deployment seems to be commonplace amongst IT companies these days (i.e. Microsoft's grand beta-test of Windows by selling it to the public to conduct testing in the production environment.) I understand there are a great number of complexities with technology products but please dont' compound the problem by providing Tech Support that is incapable of solving customer's issues. It would be better for both the customer and the manufacturer to not have any tech support at all. It would save the manufacturer money and getting help from "Customer Care" is a moot point for the customer anyway.

Sorry to rant, but situations like this really rankle one.

I'll let you know if Vonage and Linksys(Cisco) reply with any kind of positive action to my complaint.

Thanks,

-Victim

Posts: 80 · Posted: Sat Mar 04, 2006 2:22 pm Post subject:

You know I had the same thought. The WRTP54G is a wretched little router and Linksys should have recalled it a year ago when the problems began.

Perhaps a letter to John Chambers and Jeff Citron is in order.