Cisco Blogs

Our Response: Four Easy Steps To Securing a Linksys WRT Home Router!

- July 26, 2010 - 0 Comments

This week information technology experts from across the USA will descend on Las Vegas for the Black Hat technical security conference.

Cisco is a Platinum Sponsor of the event and may also be mentioned in presentations from some security researchers.  That’s why you may have seen some recent stories posted online about home routers being susceptible to attack.  The truth is that if you’ve changed the default settings on your router, then you’ve already protected your home network.

The presentation in question will be delivered by a security engineer from the firm Seismic and is expected to describe an attack on many different home wireless routers (Linksys, Belkin, D-Link, Netgear and others) using a DNS Rebinding technique.  We’ve tried to reach the researcher for a chat, but based on existing information doing any of these following steps on your Linksys WRT model router will help provide security:

  1. Change the Default Router Password:
  2. Change your SSID (also known as Network Name):
  3. Enable WPA2 encryption:
  4. Upgrade to the latest Linksys firmware:

Like many other routers, Linksys legacy routers (WRT models) ship with default settings that are known to anyone who uses the same router.  Changing both the default password and SSID will help ensure you’re secure and have prevented this type of attack.

Of course there’s nothing to do if you’re using one of the current line of Linksys E-Series (E1000, E2000, E2100L, E3000) or a Cisco Valet home router (M10, M20).  These devices are already protected because the Cisco Connect software program sets up a new SSID (network name) and passwords automatically during the initial setup.


Of course whatever device you’re using in your home network, it’s a good idea to use the most secure form of encryption and ensure you’re using the latest version of firmware.


In an effort to keep conversations fresh, Cisco Blogs closes comments after 60 days. Please visit the Cisco Blogs hub page for the latest content.