Skip to content

Linksys/Amazon/Firefox/DNS bug causes router crash

A lot of us have Linksys home routers. They are cheap, effective, and easy to use. I’ve have a BEFSR81 8 port fast ethernet broadband router/firewall for many years… it recently started locking up when anyone in the house shops Amazon.com using Firefox (started in early May we think).

Frequently the router will lock up on pages other than Amazon’s home page; usually while doing DNS queries to get some of the many sub-domains Amazon uses… Occasionally the whole router will crash and I have to reset it to get it working again.

I am running hardware version 3.1 and firmware 2.51.0 (though I swear I applied 2.51.4 update successfully in the past, it’s reporting 2.51.0). While re-applying firmware update this morning the trusty old Linksys died and would not recover.

A mad scramble to get internet again led me to buy a D-Link EBR-2310 from a local Office Depot (how cool that Office Depot carries the entire D-Link line!)… which will give me time to recover the Linksys I hope, and time to research running a linux server with two network ports as a router and firewall.

http://homecommunity.cisco.com/t5/Wired-Routers/BEFSR81-crashes-when-accessing-amazon-com/td-p/333269/page/5 the second to last post on this topic is very informative, and it looks like a DNS specific bug…

I love D-Link’s new line of gear, especially their “EtherGreen” low power high speed gigabit ethernet switches… so I suspect this router from D-Link will be fine, but it only has a four port hub on the LAN side. The Linksys BEFSR81 had an amazing 8 port switch on the LAN side… excellent and still cheap.

{ 3 } Comments

  1. Joe | August 31, 2010 at 5:17 pm | Permalink

    Back in 2001 I was working as QA for a communications software company, and was testing proxy and firewall communications with our product. We kept having this problem though where a couple executives in the company kept having our software crash their Linksys router. After an arduous process of trying to troubleshoot the problem, we found that the DHCP-based proxy script request that we were sending did not have Source Port (I think) proerply defined in the packet, and that would crash the DHCP server on the Linksys, which would then not renew leases (which expired very quickly at the default setting) and it would also cause any DNS forwarding to get locked, so you would have to reboot the router.

    We found so many bugs in the Linksys system that to this day I refuse to use any of their products.

  2. snolan | August 31, 2010 at 10:29 pm | Permalink

    Wow! Amazon is a LOT faster through the D-Link than it was through the Linksys… amazing.

  3. snolan | September 2, 2010 at 10:06 am | Permalink

    Damn! The brand new D-Link EBR-2310 died at 24 hours of use…

    Office Depot replaced it, but I am worried about the replacement.

    The good news is that I figured out how to reset the old Linksys BEFSR81:

    1. press and hold reset button for 30 seconds
    2. unplug for 30 seconds
    3. get the new firmware ready on your laptop, rename the file from “FW_BEFSR81v3.1_2.51.4.006_20090821_code.bin” to “code.bin”
    4. Download MacTFTP Client 1.2 and install it, the TFTP command that comes with Mac OS X does not handle passwords that the Linksys needs…
    5. plug ethernet directly into a LAN port on the router from your laptop
    6. turn off Wi-Fi, enable ethernet, set to 192.168.1.5 (IP), 255.255.255.0 (mask), 192.168.1.1 (gateway)
    7. Start MacTFTP Client, put in 192.168.1.1, “admin” for password, and “code.bin” file selected from the firmware download; but do NOT press send yet
    8. begin a ping test of 192.168.1.1 from a terminal window
    9. plug in the router, and when pings appear, and quickly press Send in MacTFTP; when the update is complete, the router will reboot, pings will stop working, then resume working a minute or two later
    10. when pings work again, point a browser at 192.168.1.1 and set up your router normally (change the password!!!)

Post a Comment

Your email is never published nor shared. Required fields are marked *