<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>M and L Adventures &#187; DD-WRT</title>
	<atom:link href="http://www.mandladventures.com/category/tech-stuff/dd-wrt/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mandladventures.com</link>
	<description>Leading you on the technical adventure</description>
	<lastBuildDate>Sun, 07 Mar 2010 05:10:56 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>DD-WRT Vulnerability</title>
		<link>http://www.mandladventures.com/2009/07/27/dd-wrt-vulnerability/</link>
		<comments>http://www.mandladventures.com/2009/07/27/dd-wrt-vulnerability/#comments</comments>
		<pubDate>Tue, 28 Jul 2009 01:44:20 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[DD-WRT]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.mandladventures.com/?p=419</guid>
		<description><![CDATA[For all of my readers who are DD-WRT users you may want to stop using v24 SP1, SANS Internet Storm Center (ISC) has a brief post about a DD-WRT vulnerability that will allow an attacker to run programs with root privileges on a vulnerable router. In other words, this is a really bad vulnerability. Root [...]]]></description>
			<content:encoded><![CDATA[<p>For all of my readers who are DD-WRT users you may want to stop using v24 SP1, SANS Internet Storm Center (ISC) has a brief post about a DD-WRT vulnerability that will allow an attacker to run programs with root privileges on a vulnerable router. In other words, this is a really bad vulnerability. Root privileges in Linux is the equivalent to admin privileges in Windows. With root access, a hacker could do anything with your router. Since your router controls what you do on the Internet, that could be really, really bad. The SANS post has a link to the dd-wrt forum which provides additional details regarding the problem as well as some options on how to mitigate it and/or patch the DD-WRT firmware. I highly recommend checking it out right now. Now that I&#8217;ve stressed it enough, here&#8217;s the link to the SANS ISC page:  <a href="http://isc.sans.org/diary.html?storyid=6853&#038;rss">http://isc.sans.org/diary.html?storyid=6853&#038;rss</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mandladventures.com/2009/07/27/dd-wrt-vulnerability/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Change Your WRT54GL Firmware from DD-WRT to Tomato</title>
		<link>http://www.mandladventures.com/2008/12/03/how-to-change-your-wrt54gl-firmware-from-dd-wrt-to-tomato/</link>
		<comments>http://www.mandladventures.com/2008/12/03/how-to-change-your-wrt54gl-firmware-from-dd-wrt-to-tomato/#comments</comments>
		<pubDate>Thu, 04 Dec 2008 03:03:02 +0000</pubDate>
		<dc:creator>Lauren</dc:creator>
				<category><![CDATA[DD-WRT]]></category>
		<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[WRT54GL]]></category>

		<guid isPermaLink="false">http://www.mandladventures.com/?p=346</guid>
		<description><![CDATA[**DISCLAIMER**The following instructions are provided without warranty of any kind. Flashing firmware does not come without risk. I will not be held responsible for any resulting equipment failure or otherwise undesirable results. Proceed at your own risk. This tutorial explains how I successfully re-flashed my Linksys WRT54GL version 1.1 to use the Tomato 1.22 firmware [...]]]></description>
			<content:encoded><![CDATA[<p class="alert"><strong>**DISCLAIMER**</strong><em>The following instructions are provided without warranty of any kind. Flashing firmware does not come without risk. I will not be held responsible for any resulting equipment failure or otherwise undesirable results. Proceed at your own risk.</em></p>
<p><span  class="alignleft"><iframe src="http://rcm.amazon.com/e/cm?t=tomato05-20&#038;o=1&#038;p=8&#038;l=as1&#038;asins=B000BTL0OA&#038;md=10FE9736YVPPT7A0FBG2&#038;fc1=000000&#038;IS2=1&#038;lt1=_blank&#038;m=amazon&#038;lc1=0D78B6&#038;bc1=FFFFFF&#038;bg1=FFFFFF&#038;f=ifr" style="width:120px;height:240px;" scrolling="no" marginwidth="0" marginheight="0" frameborder="0"></iframe></span>This tutorial explains how I successfully re-flashed my Linksys WRT54GL version 1.1 to use the Tomato 1.22 firmware rather than dd-wrt version 23 SP2 VPN firmware (generic) I have been using for the past couple of years. I decided to write this tutorial because lots of sites have instructions on flashing from the default Linksys firmware to Tomato but far fewer sites offer lots of detail on how to flash from other firmware such as dd-wrt.</p>
<p>I have provided directions with enough detail for the non-technical user to feel comfortable with the procedure. To make things faster for the technical users, I have highlighted the major steps. At the bottom of the post, I&#8217;ve included links to related articles I&#8217;ve published if you&#8217;d like to learn more.<span id="more-346"></span></p>
<p>As a bit of background information, I’m used a fully patched (as of November, 2008) Windows Vista Ultimate 64-bit with Service Pack 1 (SP1) Operating System and up-to-date Firefox 3 during the firmware upgrade process. The OS and web browser shouldn’t matter that much, but I thought I share in case you were worried about such things.</p>
<p>Before you begin, <a href="http://www.polarcloud.com/tomato">download</a> the latest version of the Tomato firmware that is suited for most routers. This tutorial walks through flashing to version 1.22. The files are zipped in the great, but uncommon, 7zip format so you&#8217;ll need <a href="http://www.7-zip.org/">7zip</a> or another program that supports the 7zip format to unzip the files. The zip package contains several files, <span class="highlight">you will only need the &#8220;WRT54G_WRT54GL.bin&#8221; file but it is a good idea to checkout the &#8220;readme.&#8221;</span> </p>
<p><span class="highlight">I recommend verifying the MD5SUM hash of the &#8220;WRT54G_WRT54GL.bin&#8221; file to ensure the download wasn&#8217;t corrupt or hasn&#8217;t been comprised.</span> If you don&#8217;t already have a tool to calculate MD5SUMs, I recommend using <a href="http://www.download.com/HashCalc/3000-2250_4-10130770.html">HashCalc</a> although you must manually compare the sums with this tool unlike some other tools. Unfortunately, Polarcloud does not provide the MD5SUM of the download on their site but luckily for you, I calculated the hash of my download. <span class="highlight">The signature of the file should be 866251021d42608c69bff558115f95f8.</span></p>
<p><!--adsense--></p>
<p>I recommend printing (or at least saving, not bookmarking, to your hard drive) the following web pages for reference since you will not have Internet access during this process:</p>
<ul>
<li><a href="http://www.mandladventures.com/2008/12/03/how-to-change-your-wrt54gl-firmware-from-dd-wrt-to-tomato/">How to Change Your WRT54GL Firmware from DD-WRT to Tomato</a></li>
<li><a href="http://www.polarcloud.com/tomatofaq">Tomato FAQ</a></li>
<li><a href="http://en.wikibooks.org/wiki/Tomato_Firmware">Tomato Firmware Wikibook</a></li>
<li><a href="http://dd-wrt.com/wiki/index.php/Reset_And_Reboot">Reset and Reboot</a></li>
<li><a href="http://dd-wrt.com/wiki/index.php/Recover_from_a_Bad_Flash">Recover from a Bad Flash</a></li>
</ul>
<p><span class="highlight">It is best to turn off your firewall and anti-virus during this process to ensure that nothing interrupts the firmware flash.</span> An interruption could cause the flash to fail and <a href="http://dd-wrt.com/wiki/index.php/Glossary#Brick">brick</a> your router. If something does go wrong you may be able to <a href="http://dd-wrt.com/wiki/index.php/Recover_from_a_Bad_Flash">recover from a bad flash</a>.</p>
<p><span class="highlight">You should ONLY perform the flash through an Ethernet cable using standard http (not https). Do not do this wirelessly (its best to temporarily disable the wireless adapter on your computer). If your super paranoid or live in an area with unreliable electricity, you should plug your router an PC into an <a href="http://en.wikipedia.org/wiki/Uninterruptible_power_supply">uninterruptible power supply</a> because a power failure during a firmware flash could brick your router. Plug the blue Ethernet (Cat5/RJ45) cable that came with your router into the Network Interface Card (NIC) on the back of your computer and into one of the ports labeled 1, 2, 3, or 4. The &#8220;Internet&#8221; port on your router should be connected to your broadband source (e.g., cable or DSL modem).</span>  <em>Please ignore the extra cable in the picture. It is not needed for the flash to work.</em></p>
<p><center><img src="http://www.mandladventures.com/wp-content/uploads/2007/04/plugs.jpg" alt="Cables" /></center></p>
<p><span class="highlight">I recommend reviewing all of your dd-wrt settings so you can quickly configure the Tomato firmware to offer similar functionality</span>. I took screenshots of all of the pages where I had non-default settings. I also used the same security settings, including WPA2 password, after I loaded Tomato so that all of my wireless devices would not have to be updated. However, if you have poor wireless security, after flashing to Tomato is the perfect time to implement stronger security. You can reference my <a href="http://www.mandladventures.com/2007/04/21/securing-your-wireless-network/">Securing Your Wireless Network</a> article if you want to learn how to have a really secure wireless network. </p>
<p><span class="highlight">In addition to the screenshots of your settings, it is also a good idea to perform a backup of your dd-wrt configuration.</span> Please note you can only restore this backup on the same model router and firmware with which the backup was made. To perform a backup, go to the &#8220;Administration&#8221; tab and then the &#8220;Backup&#8221; sub-tab. Once there, just click the &#8220;Backup&#8221; button and save the file.</p>
<p><center><img src="http://www.mandladventures.com/wp-content/uploads/2008/12/backup.jpg" alt="Backup" /></center></p>
<p><span class="highlight">The last item that needs to be completed before uploading the new firmware is to reset your dd-wrt firmware to the default settings.</span> A few ways to do this exist. I chose to use the standard web interface because it is easy and should always work. Nonetheless, pressing and holding the reset button on the back of your router for 30 seconds should also work (assuming you have not disabled that feature in your custom firmware). </p>
<p>To reset the router to firmware defaults, go to the internal IP address of your router (most likely 192.168.1.1) and login with the user name and password you setup when you first installed the router (if you have trouble with the login use the reset button method). Once logged in, go to “Administration” tab and the “Factory Defaults” sub-tab. I forgot to write down the exact buttons and also forgot to take a screenshot of this step but I think you just select the “Yes” radio button next to “Restore Factory Defaults” then select “Save Settings.” If that&#8217;s not it exactly, you shouldn&#8217;t have any trouble determining what to select. Be patient and don&#8217;t touch anything because the reset could take a couple of minutes.</p>
<p><span class="highlight">The <a href="http://www.polarcloud.com/tomatofaq#why_doesnt_my_password_work">Tomato FAQ</a> recommends that you Telnet into your router before performing the flash and type the &#8220;nvram get http_passwd&#8221; command to obtain the password that will be used by Tomato after the flash.</span> You cannot just use the dd-wrt password because of a change in the way dd-wrt uses the standard http_passwd variable. I must admit that I did this step but the password I obtained during the Telnet session did not allow me to login. However, as I was writing this tutorial, it occurred to me that I may have obtained the password via Telnet before I reset dd-wrt to the default settings which may explain why the password I obtained did not work.</p>
<p>In order to Telnet into your dd-wrt router, open up the run box by hitting the &#8220;Window&#8221; key and &#8220;R&#8221;. Next type &#8220;cmd&#8221; and hit &#8220;Ok.&#8221; In the command window, type &#8220;telnet 192.168.1.1&#8243; where 192.168.1.1 represents the IP address of your router. You will be prompted for a user name and password. <span class="highlight">The telnet user name is always root even if you login to the web interface with a different user name. The password should be the default dd-wrt password of &#8220;admin&#8221; since you just performed a reset. If not, try your old web login password.</span></p>
<p>Just so you know, Telnet is not enabled in Windows Vista by default but is in XP. To enable Telnet in Vista follow the instructions at <a href="http://www.tech-recipes.com/rx/1793/vista_install_telnet_client/">Tech-Recipes</a> site. Alternatively, you could use a tool like <a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">Putty</a>. </p>
<p><center><img src="http://www.mandladventures.com/wp-content/uploads/2008/12/telnet_dd-wrt.jpg" alt="telnet session" /></center></p>
<p>The screenshot above shows the password command being typed into a Telnet session; it does not show the output of the command (i.e., my password). </p>
<p><span class="highlight">Write down the password provided because you will need it later.</span></p>
<p>The next few steps is where the magic starts to happen. <span class="highlight">Go back to the dd-wrt web interface. You may have to renew the DHCP lease and login again. Since you have reset the firmware to default settings, the user name and password is now &#8220;root&#8221; and &#8220;admin&#8221;, respectively. Once logged in, navigate to the &#8220;Administration&#8221; tab and the &#8220;Firmware Upgrade&#8221; sub-tab.</span></p>
<p><span class="highlight">Next, select the &#8220;Browse&#8221; button and select the &#8220;WRT54G_WRT54GL.bin&#8221; file you downloaded early. Once located, hit open (no brainer). Then hit the “Upgrade” button. Please wait patiently for the upload to complete. Whatever you do, don’t interrupt it.</span> If you’re going to be tempted, walk away for a few minutes and come back.</p>
<p><center><img src="http://www.mandladventures.com/wp-content/uploads/2008/12/firmware_upgrade.jpg" alt="Firmware Upgrade" /></center></p>
<p>After a couple of minutes, you should see a screen that says &#8220;Upgrade successful. Unit is rebooting now. Please wait a moment&#8230;&#8221; </p>
<p><center><img src="http://www.mandladventures.com/wp-content/uploads/2008/12/upgrade-successful.jpg" alt="Upgrade successful" /></center></p>
<p><span class="highlight">Once the reboot completes, you will be prompted to login to the Tomato firmware. This is where you use the &#8220;root&#8221; user name and the password you obtained via Telnet.</span> Don&#8217;t freak out if you can&#8217;t login&#8230;the same thing happened to me. The next paragraph has a solution for you.</p>
<p><center><img src="http://www.mandladventures.com/wp-content/uploads/2008/12/authentication_screen.jpg" alt="Login Box" /></center></p>
<p><span class="highlight">Since the Tomato interface did not accept the password I obtained through the Telnet session before the flash, I had to perform a hard reset. To do this you need to hold the reset button on the back of the router while unplugging the router. Continue to hold the reset button as you re-plug in the router. Once the router is plugged in you should continue holding the reset button for 30 seconds to complete the hard reset.</span></p>
<p><span class="highlight">After the hard reset is complete, go back to Firefox and navigate to <a href="http://192.168.1.1">http://192.168.1.1</a>. At the prompt enter in “root” for the user name and “admin” as the password. The Tomato web interface should come up.</span></p>
<p>Once you&#8217;ve logged in, you should see the new Tomato firmware. <span class="highlight">Since you are upgrading from dd-wrt, the <a href="http://www.polarcloud.com/tomatofaq#should_i_reset_the_configurati">Tomato FAQ</a> recommends performing a full reset by navigating to the &#8220;Administration&#8221; section and then the &#8220;Configuration&#8221; sub-section. From there, select &#8220;Erase all data in NVRAM memory (thorough)&#8221; from under the &#8220;Restore Default Configuration&#8221; menu and then hit &#8220;OK.&#8221;</span> If you had to do a hard reset in order to get your login to work, you&#8217;re probably could skip this step but it won&#8217;t hurt to do an additional reset just to be safe.</p>
<p><center><img src="http://www.mandladventures.com/wp-content/uploads/2008/12/restore_default_configuration.jpg" alt="Restore Default Configuration" /></center></p>
<p><span class="highlight">After restoring the default configuration, you need to log back in using with the user name of &#8220;root&#8221; and password of &#8220;admin&#8221;. Once logged in, hit the &#8220;Renew&#8221; button that is on the &#8220;Overview&#8221; page.</span></p>
<p><span class="highlight">After renewing you may need to reboot your computer to get Internet access. Alternatively, in Vista you may type &#8220;Network and Sharing Center&#8221; in the Start Search box. Within the Network and Sharing Center select the red &#8220;X&#8221; between the network on Internet on the map. The Windows Network Diagnostics menu should appear. On that menu select &#8220;Reset the network adapter&#8230;&#8221; option at the bottom. Windows will repair the network and you should see a message that says &#8220;the problem has been resolved.&#8221;</span> </p>
<p><center><img src="http://www.mandladventures.com/wp-content/uploads/2008/12/network_and_sharing_center.jpg" alt="Network and Sharing Center" /></center></p>
<p><span class="highlight">Now that everything is working, don&#8217;t forget to turn your anti-virus and firewall back on. Also, be sure to check out my <a href="http://www.mandladventures.com/2007/04/21/securing-your-wireless-network/">Securing Your Wireless Network</a> article if you want to learn how to have a really secure wireless network. </span></p>
<p><span  class="alignright"><iframe src="http://rcm.amazon.com/e/cm?t=tomato05-20&#038;o=1&#038;p=8&#038;l=as1&#038;asins=1597491667&#038;fc1=000000&#038;IS2=1&#038;lt1=_blank&#038;m=amazon&#038;lc1=0D78B6&#038;bc1=FFFFFF&#038;bg1=FFFFFF&#038;f=ifr" style="width:120px;height:240px;" scrolling="no" marginwidth="0" marginheight="0" frameborder="0"></iframe></span></p>
<p><span class="highlight">Congratulations, you’ve successfully flashed your router!</span> Since you’ve successfully flashed your WRT54G, you should checkout the <a href="http://www.amazon.com/gp/product/1597491667?ie=UTF8&#038;tag=tomato05-20&#038;linkCode=as2&#038;camp=1789&#038;creative=9325&#038;creativeASIN=1597491667">Linksys WRT54G Ultimate Hacking Guide</a><img src="http://www.assoc-amazon.com/e/ir?t=tomato05-20&#038;l=as2&#038;o=1&#038;a=1597491667" width="1" height="1" border="0" alt="" style="border:none !important; margin:0px !important;" />to make the most out of your new found knowledge of router firmware. </p>
<p><strong>Further Reading</strong></p>
<ul>
<li><a href="http://www.mandladventures.com/2008/01/19/tomato-firmware-option-for-wrt54gl/">Tomato Firmware Option for WRT54GL</a></li>
<li><a href="http://www.mandladventures.com/2008/11/01/tomato-firmware-upgrade-and-demo-video/">Tomato Firmware Upgrade and Demo Video</a></li>
<li><a href="http://www.mandladventures.com/2007/04/12/how-to-flash-the-wrt54gl-with-dd-wrt-firmware/">How to Flash the WRT54GL with DD-WRT Firmware</a></li>
<li><a href="http://www.mandladventures.com/2007/04/21/securing-your-wireless-network/">Securing Your Wireless Network</a></li>
</ul>
<p>If you liked this post, consider subscribing to my <a href="http://feeds.feedburner.com/MAndLAdventures">feed</a> and/or sending me something from my <a href="http://www.amazon.com/gp/registry/wishlist/W77D6UZQZW9X">wish list</a>. Thanks in advance for your support of this guide &#038; site!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mandladventures.com/2008/12/03/how-to-change-your-wrt54gl-firmware-from-dd-wrt-to-tomato/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
		<item>
		<title>Tomato Firmware Upgrade and Demo Video</title>
		<link>http://www.mandladventures.com/2008/11/01/tomato-firmware-upgrade-and-demo-video/</link>
		<comments>http://www.mandladventures.com/2008/11/01/tomato-firmware-upgrade-and-demo-video/#comments</comments>
		<pubDate>Sun, 02 Nov 2008 00:03:07 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[DD-WRT]]></category>
		<category><![CDATA[WRT54GL]]></category>

		<guid isPermaLink="false">http://www.mandladventures.com/?p=318</guid>
		<description><![CDATA[I&#8217;ve been running DD-WRT on my WRT54GL for well over a year not and even documented detailed firmware flashing instructions. However, I&#8217;ve been debating on switching to the Tomato firmware for close to year now. With Comcast&#8217;s new 250 GB bandwidth limit and Tomato&#8217;s impressive bandwidth monitor, I&#8217;m getting even closer to taking the time [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been running DD-WRT on my WRT54GL for well over a year not and even documented detailed firmware flashing <a href="http://www.mandladventures.com/2007/04/12/how-to-flash-the-wrt54gl-with-dd-wrt-firmware/">instructions</a>. However, I&#8217;ve been debating on switching to the <a href="http://www.mandladventures.com/2008/01/19/tomato-firmware-option-for-wrt54gl/">Tomato firmware</a> for close to year now.</p>
<p>With Comcast&#8217;s new 250 GB bandwidth limit and Tomato&#8217;s impressive <a href="http://www.polarcloud.com/img/ssbwm100.png">bandwidth monitor</a>, I&#8217;m getting even closer to taking the time to make the switch from dd-wrt to Tomato. I believe the <a href="http://www.dd-wrt.com/wiki/index.php/What_is_DD-WRT%3F#Features">v24</a> of dd-wrt does support bandwidth monitoring but I like the looks and basic features of Tomato.</p>
<p>The <a href="http://revision3.com/systm/tomato/">Systm episode 71</a> by Revision3 recently covered the process to flash a Linksys WRT54G with Tomato firmware and also showed off some of the application&#8217;s coolest features. If you&#8217;re debating on upgrading your very basic Linksys router to something much better for free, I highly recommend you watch this video. It&#8217;ll make you want to do it right away.</p>
<p>Now, if I can just determine the best process to switch from dd-wrt to Tomato, I&#8217;d be good&#8230;</p>
<p>Also should also mention that if you&#8217;re interested in hacking your Linksys router, you should checkout the <a href="http://www.amazon.com/gp/product/1597491667?ie=UTF8&#038;tag=wrt54g-20&#038;linkCode=as2&#038;camp=1789&#038;creative=9325&#038;creativeASIN=1597491667">Linksys WRT54G Ultimate Hacking</a><img src="http://www.assoc-amazon.com/e/ir?t=wrt54g-20&#038;l=as2&#038;o=1&#038;a=1597491667" width="1" height="1" border="0" alt="" style="border:none !important; margin:0px !important;" />book.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mandladventures.com/2008/11/01/tomato-firmware-upgrade-and-demo-video/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>DD-WRT v24 Released</title>
		<link>http://www.mandladventures.com/2008/05/24/dd-wrt-v24-released/</link>
		<comments>http://www.mandladventures.com/2008/05/24/dd-wrt-v24-released/#comments</comments>
		<pubDate>Sat, 24 May 2008 16:08:37 +0000</pubDate>
		<dc:creator>Lauren</dc:creator>
				<category><![CDATA[DD-WRT]]></category>
		<category><![CDATA[WRT54GL]]></category>

		<guid isPermaLink="false">http://www.mandladventures.com/?p=308</guid>
		<description><![CDATA[On May 18, 2008 the DD-WRT website announced the final release of DD-WRT v24 to the public. I haven&#8217;t had a chance to install the update or to even research all of the new features but based on the popularity of my How to Flash the WRT54GL with DD-WRT Firmware post I felt obligate to [...]]]></description>
			<content:encoded><![CDATA[<p>On May 18, 2008 the DD-WRT website announced the final release of DD-WRT v24 to the public. I haven&#8217;t had a chance to install the update or to even research all of the new features but based on the popularity of my <a href="http://www.mandladventures.com/2007/04/12/how-to-flash-the-wrt54gl-with-dd-wrt-firmware/">How to Flash the WRT54GL with DD-WRT Firmware</a> post I felt obligate to write a quick post informing everyone of this new update. You can read more about the new release at the <a href="http://www.dd-wrt.com/dd-wrtv3/index.php">DD-WRT website</a>. [via <a href="http://lifehacker.com/393093/open+source-router-firmware-dd+wrt-updates">Lifehacker</a>].</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mandladventures.com/2008/05/24/dd-wrt-v24-released/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Linksys WRT54GL Cross Site Request Forgery (CSRF) Vulnerability</title>
		<link>http://www.mandladventures.com/2008/01/26/linksys-wrt54gl-cross-site-request-forgery-csrf-vulnerability/</link>
		<comments>http://www.mandladventures.com/2008/01/26/linksys-wrt54gl-cross-site-request-forgery-csrf-vulnerability/#comments</comments>
		<pubDate>Sat, 26 Jan 2008 15:07:52 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[DD-WRT]]></category>
		<category><![CDATA[Tech Advice]]></category>
		<category><![CDATA[WRT54GL]]></category>

		<guid isPermaLink="false">http://www.mandladventures.com/2008/01/26/linksys-wrt54gl-cross-site-request-forgery-csrf-vulnerability/</guid>
		<description><![CDATA[The quite common Linksys WRT54GL v4.x has a serious vulnerability that can be exploited by hackers remotely (i.e., from across the Internet). The vulnerability is Cross Site Request Forgery (CSRF). This is possibly the second most common web vulnerability (second only to Cross Site Scripting aka XSS). Despite its prevalence, CSRF is not well known [...]]]></description>
			<content:encoded><![CDATA[<p>The quite common Linksys WRT54GL v4.x has a serious vulnerability that can be exploited by hackers remotely (i.e., from across the Internet). The vulnerability is Cross Site Request Forgery (CSRF). This is possibly the second most common web vulnerability (second only to Cross Site Scripting aka XSS). Despite its prevalence, CSRF is not well known or understood by many people. I thought about writing a short explanation of CSRF but I don&#8217;t have my head around it well enough to feel comfortable explaining it to you. So, I&#8217;ve done the next best thing&#8211;I&#8217;ve located an excellent article by CSO magazine titled &#8220;<a href="http://www2.csoonline.com/exclusives/column.html?CID=33395">Threat Watch: Cross Site Request Forgery (CSRF) Why a little-known web application vulnerability could cause big problems</a>.&#8221;</p>
<p>As far as I know, this vulnerability is unpatched by Linksys which means there is update to fix this problem if you want to keep running the standard Linksys firmware. However, you can fix this vulnerability and gain additional features by upgrading to an open source firmware such as <a href="http://www.mandladventures.com/2007/04/12/how-to-flash-the-wrt54gl-with-dd-wrt-firmware/">DD-WRT</a> or <a href="http://www.mandladventures.com/2008/01/19/tomato-firmware-option-for-wrt54gl/">Tomato</a>. I happen to own a Linksys WRT54GL version 1.1 and have flashed it with the DD-WRT firmware. Because flashing a router&#8217;s firmware is not for the faint of heart, I have composed very detailed <a href="http://www.mandladventures.com/2007/04/12/how-to-flash-the-wrt54gl-with-dd-wrt-firmware/">how-to instructions</a> for those who are interested.</p>
<p>Another mitigation method I almost forgot to mention is to actually quite simple. Do not visit other websites while logged in to administer the Linksys WRT54GL. [via <a href="http://secunia.com/advisories/28364/">Secunia</a>]</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mandladventures.com/2008/01/26/linksys-wrt54gl-cross-site-request-forgery-csrf-vulnerability/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Tomato Firmware Option for WRT54GL</title>
		<link>http://www.mandladventures.com/2008/01/19/tomato-firmware-option-for-wrt54gl/</link>
		<comments>http://www.mandladventures.com/2008/01/19/tomato-firmware-option-for-wrt54gl/#comments</comments>
		<pubDate>Sat, 19 Jan 2008 05:24:50 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[DD-WRT]]></category>
		<category><![CDATA[WRT54GL]]></category>

		<guid isPermaLink="false">http://www.mandladventures.com/2008/01/19/tomato-firmware-option-for-wrt54gl/</guid>
		<description><![CDATA[Lifehacker has an interesting post on the Tomato custom router firmware. When a friend emailed me about the Lifehacker post, I first dismissed the article because when I was deciding on which firmware to flash my Linksys WRT54GL with, I looked at Tomato but didn&#8217;t think it was as powerful as DD-WRT or OpenWRT. However, [...]]]></description>
			<content:encoded><![CDATA[<p>Lifehacker has an interesting post on the <a href="http://www.polarcloud.com/tomato">Tomato</a> custom router firmware. When a friend emailed me about the <a href="http://lifehacker.com/344765/turn-your-60-router-into-a-userfriendly-superrouter-with-tomato/">Lifehacker post</a>, I first dismissed the article because when I was deciding on which firmware to flash my <a href="http://www.amazon.com/gp/product/B000BTL0OA?ie=UTF8&#038;tag=wrt54g-20&#038;linkCode=as2&#038;camp=1789&#038;creative=9325&#038;creativeASIN=B000BTL0OA">Linksys WRT54GL</a><img src="http://www.assoc-amazon.com/e/ir?t=wrt54g-20&#038;l=as2&#038;o=1&#038;a=B000BTL0OA" width="1" height="1" border="0" alt="" style="border:none !important; margin:0px !important;" /> with, I looked at <a href="http://www.polarcloud.com/tomato">Tomato</a> but didn&#8217;t think it was as powerful as <a href="http://www.dd-wrt.com/dd-wrtv2/index.php">DD-WRT</a> or <a href="http://openwrt.org/">OpenWRT</a>. However, when I read Lifehacker&#8217;s post my interest was re-sparked in Tomato. The author did admit that dd-wrt had a more robust feature set and polished admin interface. However, he also indicated that Tomato had a better layout, better Quality of Service (QOS) support, and prettier graphical charts than dd-wrt. Also, the average user probably wouldn&#8217;t use the more powerful dd-wrt features anyway.</p>
<p>I wish I had the time/patience to re-flash my <a href="http://www.amazon.com/gp/product/B000BTL0OA?ie=UTF8&#038;tag=wrt54g-20&#038;linkCode=as2&#038;camp=1789&#038;creative=9325&#038;creativeASIN=B000BTL0OA">Linksys WRT54GL</a><img src="http://www.assoc-amazon.com/e/ir?t=wrt54g-20&#038;l=as2&#038;o=1&#038;a=B000BTL0OA" width="1" height="1" border="0" alt="" style="border:none !important; margin:0px !important;" /> with <a href="http://www.polarcloud.com/tomato">Tomato</a> just to try it out. Its very unlikely that I will because I don&#8217;t want to risk bricking my perfectly functioning dd-wrt enabled router. I also really like <a href="http://www.dd-wrt.com/dd-wrtv2/index.php">dd-wrt</a>. Too bad flashing a router is a lot more complex than just installing software. </p>
<p>Also, the <a href="http://lifehacker.com/344765/turn-your-60-router-into-a-userfriendly-superrouter-with-tomato/">Lifehacker article</a> doesn&#8217;t mention <a href="http://openwrt.org/">OpenWRT</a> (a couple of commenters do) but <a href="http://openwrt.org/">OpenWRT</a> seems to be the hard-core geek&#8217;s choice. I&#8217;ve thought about making the switch to it but it is probably more complex than I want to deal with. I really considered OpenWRT over <a href="http://www.dd-wrt.com/dd-wrtv2/index.php">DD-WRT</a> but DD-WRT&#8217;s site looked better maintained and easier to read. Plus, until recently all <a href="http://openwrt.org/">OpenWRT</a> management seemed like it when through a Linux shell (i.e., command line). Now though <a href="http://x-wrt.org/">x-wrt</a> seems to address what some would call a short coming of <a href="http://openwrt.org/">OpenWRT</a>.</p>
<p>If anyone wants to send me a <a href="http://www.amazon.com/gp/product/B000BTL0OA?ie=UTF8&#038;tag=wrt54g-20&#038;linkCode=as2&#038;camp=1789&#038;creative=9325&#038;creativeASIN=B000BTL0OA">Linksys WRT54GL</a><img src="http://www.assoc-amazon.com/e/ir?t=wrt54g-20&#038;l=as2&#038;o=1&#038;a=B000BTL0OA" width="1" height="1" border="0" alt="" style="border:none !important; margin:0px !important;" /> so I can experiment with it and write more tutorials on firmware flashing, let me know and I can add it to my <a href="http://www.amazon.com/gp/registry/wishlist/W77D6UZQZW9X">Amazon Wish List</a> so you can send it to me easily. Also, don&#8217;t forget to check out my ever-popular &#8220;<a href="http://www.mandladventures.com/2007/04/12/how-to-flash-the-wrt54gl-with-dd-wrt-firmware/">How to Flash the WRT54GL with DD-WRT Firmware</a>&#8221; tutorial. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.mandladventures.com/2008/01/19/tomato-firmware-option-for-wrt54gl/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>Securing Your Wireless Network</title>
		<link>http://www.mandladventures.com/2007/04/21/securing-your-wireless-network/</link>
		<comments>http://www.mandladventures.com/2007/04/21/securing-your-wireless-network/#comments</comments>
		<pubDate>Sat, 21 Apr 2007 17:54:52 +0000</pubDate>
		<dc:creator>Matt</dc:creator>
				<category><![CDATA[DD-WRT]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Tech Advice]]></category>

		<guid isPermaLink="false">http://www.mandladventures.com/?p=205</guid>
		<description><![CDATA[I&#8217;ve been on a bit of a security kick lately&#8230;more than usual anyway. I&#8217;ve always been a bit of a security fanatic but lately I&#8217;ve been learning a whole lot more. Working as an IT auditor by day and just naturally being attracted to technology, security is of great interest to me. I&#8217;m also becoming [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been on a bit of a security kick lately&#8230;more than usual anyway. I&#8217;ve always been a bit of a security fanatic but lately I&#8217;ve been learning a whole lot more. Working as an IT auditor by day and just naturally being attracted to technology, security is of great interest to me. I&#8217;m also becoming a huge fan of the open source <a href="http://dd-wrt.com/wiki/index.php/What_is_DD-WRT%3F">DD-WRT firmware</a> as I start to use more and more of its features on my home network.</p>
<p>A lot of security topics exists that I&#8217;d love to write about sometime, but securing your wireless network is one that should be useful to most of my blog readers. Plus, this is a natural progression from my recent post about <a href="http://www.mandladventures.com/2007/04/12/how-to-flash-the-wrt54gl-with-dd-wrt-firmware/">How to Flash the WRT54GL with DD-WRT Firmware</a>. This post will not cover the intricate details of the hows and whys of wireless security nor will provide a ton of details on how to circumvent (i.e., crack) common security settings. Maybe I&#8217;ll cover those topics at a later date. For now, I just want to tell you about what security settings you should use on your home or small business wireless network to ensure no one is able to sniff (see what your doing on your wireless connection) or use your wireless connection without your permission.<span id="more-205"></span></p>
<p><strong>Table of Contents</strong></p>
<ul>
<li><a href="#Encryption">Select Your Encryption Method</a></li>
<li><a href="#Password">Select Your Password</a></li>
<li><a href="#SSID">Disable SSID Broadcast</a></li>
<li><a href="#MAC">MAC Filtering</a></li>
<li><a href="#UPnP">Turn Off UPnP</a></li>
<li><a href="#Default">Change Default Router Log-In Settings</a></li>
<li><a href="#Firewall">Setup Your Firewall</a></li>
<li><a href="#Patch">Patch Windows Client</a></li>
<li><a href="#Client">Configure Client Devices</a></li>
<li><a href="#Resources">External Resources</a></li>
</ul>
<p><center><!--adsense--></center></p>
<p><a id="Encryption"></a><strong>Select Your Encryption Method</strong><br />
The first thing you must decide on is what encryption to use. The decision is pretty simple; pick the strongest form of wireless encryption that your network will support (excluding the Radius methods for reasons noted below). Remember, even if your wireless router supports the strongest encryption but some of the wireless cards joining the network does not then you will have problems connecting from those machines if you don&#8217;t pick a level of encryption supported by all of your devices. Most people with remotely up-to-date hardware will not have trouble supporting all of the encryption levels mentioned below.</p>
<p>Below I&#8217;ve listed the DD-WRT&#8217;s wireless encryption security mode options (these will be available in most other wireless routers) from strongest to weakest:</p>
<ol>
<li>WPA2 Radius Only</li>
<li>WPA2 Radius Mixed</li>
<li>WPA Radius</li>
<li>WPA2 Pre-Shared Key Only</li>
<li>WPA2 Pre-Shared Key Mixed</li>
<li>WPA Pre-Shared Key</li>
<li>Radius</li>
<li>WEP</li>
<li>Disabled</li>
</ol>
<p>All of the <abbr title="Remote Authentication Dial In User Service">RADIUS</abbr> methods are too complex for most home users because they require a separate <a href="http://en.wikipedia.org/wiki/RADIUS">Radius server</a> for for authentication. <abbr title="Remote Authentication Dial In User Service">RADIUS</abbr> is designed for a Corporate type environment.</p>
<p>The DD-WRT firmware provides a second option for WPA Algorithms (for WPA security modes) or Encryption (for WEP security modes).</p>
<p>The <a href="http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access">WPA</a> preferred order is:</p>
<ol>
<li><a href="http://en.wikipedia.org/wiki/Advanced_Encryption_Standard">AES</a></li>
<li>AES + TKIP</li>
<li><a href="http://en.wikipedia.org/wiki/TKIP">TKIP</a></li>
</ol>
<p><small><em>The DD-WRT help file suggests using WPA2 Mixed/TKIP+AES for maximum interoperability. So if you&#8217;re having trouble getting WPA2 AES to work on your network, try this configuration. Also note that WPA2 TKIP is not supported. Don&#8217;t worry, any form of WPA is very secure.</em></small></p>
<p>For <a href="http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy">WEP</a>, the preferred order is:</p>
<ol>
<li>128-bits 26 hex digits</li>
<li>64-bits 10 hex digits</li>
</ol>
<p>Below is a screenshot of the encryption settings I recommend:</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/encryption.png' alt='Encryption Settings' /></p>
<p><small><em>Note:  Both forms of WEP are easy to hack due to poor implementation of the RC4 Stream Cipher; don&#8217;t worry what this means right now, just know its really insecure. Also, note some people call 128 bit 105 bit WEP and 64 bit WEP 40 bit because they subtract the 24 initialization vector (IV).</em></small></p>
<p><a id="Password"></a><strong>Select Your Password</strong><br />
Password selection is of vital importance as well because if someone can easily <a href="http://en.wikipedia.org/wiki/Brute_force_attack">brute force</a> your password (quickly determine your password by trying all possible values) then the strongest form of encryption is worthless. Some people claim WPA has been broken, but in reality all that has really happened is someone sniffed a lot of packets and then carried out a <a href="http://en.wikipedia.org/wiki/Dictionary_attack">dictionary</a> or brute force attack and correctly guessed the password. A WEP password doesn&#8217;t really matter as a WPA password because a hacker with a little time and some free tools can quickly determine your WEP password due to the improper implementation of the encryption algorithm.</p>
<p>So, how can you make it practically impossible to brute force your password? The answer is simple&#8230;use a long, random password. The longer the password the more time brute forcing takes to work (as in thousands of years for a strong password). Basically, brute forcing tries all possible combinations of letters and number (or a predetermined sub-set of them) until the combination works so the longer the password the more guesses required. Randomness protects against dictionary attacks. A dictionary attack is just like it sounds. A very large list of common passwords is tried; therefore, you don&#8217;t want to use any words that may be in a dictionary.</p>
<p>Because you are not required to enter your wireless password more than once on each client you want to connect to your wireless network, you can easily select a very long and complex password and not worry about having to memorizing it. <abbr title="Gibson Research Corporation">GRC</abbr> has an excellent random <a href="https://www.grc.com/passwords.htm">password generator</a> perfect for wireless security. Use the 63 random printable ASCII character for ultimate security. Why 63 characters? Its the maximum length accepted by WPA.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/passwords.Png' alt='Passwords' /></p>
<p>Although I trust <a href="https://www.grc.com/passwords.htm">GRC&#8217;s Ultra High Security Password Generator</a>, I still hit the refresh button a few times to collect a small selection of passwords. Then, I cut and pasted tidbits of each password to ensure its security&#8211;I know you think I&#8217;m crazy.</p>
<p>Of course, you must store this password in a protected place to keep others from finding it. I recommend putting it on a portable storage device such as a CD or USB drive. If you want to be ultra secure, and geeky, store the password in an encrypted form with a tool such as <a href="http://www.truecrypt.org/">TrueCrypt</a>.</p>
<p>WEP requires you to use an exact password length so you won&#8217;t be able to use the full 63 character long password generated by <a href="https://www.grc.com/passwords.htm">GRC&#8217;s Ultra High Security Password Generator</a>. 26 hexadecimal characters equates to 13 alpha-numeric characters and 10 hexadecimal characters equals 5 alpha-numeric characters. If you must use WEP, you can just select the appropriate subset (26 characters for 128bit WEP and 10 characters from the 64bit WEP) from the 64 random hexadecimal characters section of the password generator.</p>
<p><a id="SSID"></a><strong>Disable SSID Broadcast</strong><br />
Hiding Your Service Set IDentifier (SSID) doesn&#8217;t provide much security because anyone using a tool such as <a href="http://en.wikipedia.org/wiki/Kismet_%28program%29">Kismet</a> can still find your <a href="http://en.wikipedia.org/wiki/SSID">SSID</a>, but at least your wireless network ID will be hidden from the average Joe. If you do hide your <abbr title="Service Set IDentifier">SSID</abbr>, your network will not show up when you scan for wireless networks in Windows or OS X so you must manually type in the SSID name you selected on each client when you first time connect to your network.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/ssid.png' alt='SSID' /></p>
<p><strong><a id="MAC">MAC Filtering</a></strong><br />
<abbr title="Media Access Control">MAC</abbr> Filtering is a way to limit what network cards can connect to your network. Every networking device has a unique <a href="http://en.wikipedia.org/wiki/MAC_address">MAC address</a> assigned to it during the manufacturing process. To set up MAC filtering, you will need to determine the MAC address of every device you want to connect to your network and enter this information into the router.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/mac_filter.png' alt='Mac Filtering' /></p>
<p>As you can tell, I have MAC Filtering disabled. Why? Its takes quite a bit of time to setup and it doesn&#8217;t provide much security. The idea behind MAC filtering is good, but its flawed because a user is able to <em><a href="http://en.wikisource.org/wiki/Changing_MAC_addresses">change</a></em> their MAC address to anything they want. So, a someone wanting to access your network would use a good wireless sniffer (i.e., Kismet) to determine what MAC addresses are connected to your network. They would then change their MAC address to one of those allowed addresses. Because MAC addresses are supposed to be unique, your access point will get confused if two clients with the same MAC address is connected to it. So, a smart hacker will kickoff the original machine whose MAC address they stole using a common <a href="http://en.wikipedia.org/wiki/Denial-of-service_attack">Denial-of-service</a> (DOS) attack or simply wait for that machine to disconnect.</p>
<p>You must decide whether or not MAC Filtering is worth the trouble because it does provide some protection.</p>
<p><a id="UPnP"></a><strong>Turn Off UPnP</strong><br />
Another worthwhile security measure is turning of <a href="http://en.wikipedia.org/wiki/Universal_plug_and_play">Universal Plug and Play</a> (UPnP) on both your PC and your router. <abbr title="Universal Plug and Play">UPnP</abbr> is bad because it lets software automatically open ports on your router without your knowledge. To make it even worse, you can&#8217;t tell which ports have been opened. The idea behind <abbr title="Universal Plug and Play">UPnP</abbr> was to make it easy for network software/devices to work without a user having to manually configure <a href="http://en.wikipedia.org/wiki/Port_forwarding">Port Forwarding</a>.</p>
<p>The problem is that malware could also use this auto-configuration feature to open ports behind your back in order to communicate with the outside world. Additionally, <abbr title="Universal Plug and Play">UPnP</abbr> has several major vulnerabilities in the past such as buffer overruns that could lead to remote code execution. Although the known vulnerabilities have been patched, turning off <abbr title="Universal Plug and Play">UPnP</abbr> would prevent any future exploits.</p>
<p>The easiest way I know of to turn off <abbr title="Universal Plug and Play">UPnP</abbr> on your PC is to use the <a href="http://www.grc.com/unpnp/unpnp.htm">UnPlug n&#8217; Pray</a> utility.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/unplugpray.png' alt='UnPlug and Pray' /></p>
<p>Go to the Applications and Gaming tab and the UPnP sub-tab to disable <abbr title="Universal Plug and Play">UPnP</abbr>.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/upnp.png' alt='UPnP' /></p>
<p><small><em>Note: I believe most routers not running the DD-WRT firmware have a similar option to disable <abbr title="Universal Plug and Play">UPnP</abbr>. If not, disabling it on your PC should be enough as long as Windows, as it has bad habits of doing, doesn&#8217;t decide to turn the feature back on.</em></small></p>
<p>It is important to reset your router to factory defaults to undo any ports opened by <abbr title="Universal Plug and Play">UPnP</abbr> when it was enabled. Please note that resetting your router to factory defaults will also reset any of your custom options, so think twice before doing this.    Be sure to reset your router before completing the rest of the security steps or else you&#8217;ll probably have to re-do them. See the following two pages on the DD-WRT wiki for information on how to perform a reset: <a href="http://www.dd-wrt.com/wiki/index.php/Factory_Defaults">Factory Defaults</a> &#038; <a href="http://www.dd-wrt.com/wiki/index.php/Reset_And_Reboot">Reset and Reboot</a>.</p>
<p>I am uncertain, but simply rebooting (not resetting) your router may also undo the ports opened by <abbr title="Universal Plug and Play">UPnP</abbr>. One way to ensure all your important ports have been closed is to check out the <a href="https://www.grc.com/x/ne.dll?bh0bkyd2">Shields Up</a> web service. If you want to do a full port scan check out <a href="http://en.wikipedia.org/wiki/Nmap">NMAP</a>.</p>
<p><a id="Default"></a><strong>Change Default Router Log-In Settings</strong><br />
Changing the User Name and Password used to configure your router is very important (this is the info you type in when going to 192.168.1.1 o whatever your router&#8217;s internal IP address is). The default router user names and passwords are widely known&#8230;you can easily find a massive list of them. Symantec published an article on a very interesting concept they coined &#8220;<a href="http://www.symantec.com/enterprise/security_response/weblog/2007/02/driveby_pharming_how_clicking_1.html">Drive-By Pharming: How Clicking on a Link Can Cost You Dearly</a>.&#8221; The basic concept is <a href="http://en.wikipedia.org/wiki/Cross-site_request_forgery">Cross Site Request Forgery</a> can be used to log in to your wireless router if you haven&#8217;t changed the default log-in settings. Once access has been gained to your router, your <a href="http://en.wikipedia.org/wiki/Domain_Name_System">DNS</a> Server setting can be changed to a malicious <abbr title="Domain name system">DNS</abbr> server. This is a major problem because <abbr title="Domain name system">DNS</abbr> associates domain names (web site addresses) with server&#8217;s IP addresses. A malicious <abbr title="Domain name system">DNS</abbr> server could associate your-bank.com with spoofed site that looks just like your bank&#8217;s site and collect your user name and password when you try to log in. However, the simple change of your router&#8217;s user name and password protects against this attack.</p>
<p>Go to the Administration tab and the Management sub-tab to change the default settings. While your there, go ahead and disable all Remote Access as well.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/router_management.png' alt='Router Management' /></p>
<p><a id="Firewall"></a><strong>Setup Your Firewall</strong><br />
Firewalls are set rules for what can come in and out of your network. One of the main benefits of all routers is Network Address Translation (NAT). Basically, it only allows connections into your network if one of your computers made the initial request. Sometimes you will need to use <a href="http://en.wikipedia.org/wiki/Port_forwarding">Port Forwarding</a> to allow connections through certain ports for services running behind your router that you won&#8217;t make the initial request&#8230;for instance you&#8217;re running a web server on your network that needs to accept connections on port 80. If you recall, <abbr title="Universal Plug and Play">UPnP</abbr> automatically configures port forwarding which could open up ports you don&#8217;t want open.</p>
<p><a href="http://en.wikipedia.org/wiki/Stateful_firewall">Stateful packet inspection</a> (SPI) provides an extra layer of security to NAT routers. I recommend enabling <abbr title="Stateful packet inspection">SPI<abbr>, blocking anonymous Internet request, filtering multicast, and filtering <a href="http://en.wikipedia.org/wiki/Ident">IDENT</a>. You can set all of these by going to the Security tab and the Firewall sub-tab.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/firewall.png' alt='Firewall' /></p>
<p><a id="Patch"></a><strong>Patch Windows Client</strong><br />
One thing I do recommend is downloading the following patchs from Microsoft: <a href="http://support.microsoft.com/kb/893357">The Wi-Fi Protected Access 2 (WPA2)/Wireless Provisioning Services Information Element (WPS IE)</a> and <a href="http://support.microsoft.com/?kbid=917021">Wireless Client Update for Windows XP with Service Pack 2</a>.</p>
<p>The first update &#8220;enhances the Windows XP wireless client software with support for the new Wi-Fi Alliance certification for wireless security. The update also makes it easier to connect to secure public spaces that are equipped with wireless Internet access.&#8221;</p>
<p>The second update &#8220;enhances support for Wi-Fi Protected Access 2 (WPA2) options in Wireless Group Policy. This update helps prevent a Windows wireless client from advertising the wireless networks in its preferred networks list.&#8221; Please note that this patch was never included in any automatic updates from Microsoft. Unless you specifically went to Microsoft to download this patch, your system will not have it (as far as I know anyway). Don&#8217;t ask me why Microsoft didn&#8217;t include this in their standard update cycle.</p>
<p><a id="Client"></a><strong>Configure Client Devices</strong><br />
You should configure Windows to only connect to Access Points because Ad-Hoc (computer-to-computer) networks are dangerous. To do this go to Start > Control Panel > Network and Internet Connections >Network Connections then right-click on Wireless Network Connection device and select properties. On the Wireless Network Connections properties screen select the Wireless Networks tab and then the Advanced button. Make sure to select Access point (infrastructure) networks only and uncheck Automatically connect to non-preferred networks.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/access_point_only.png' alt='Access Points Only' /></p>
<p>You will also need to add your network to the preferred networks list by going back to the Wireless Networks tab and selecting Add. Then type in the appropriate information for you wireless setup.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/association.png' alt='Wireless Configuration' /></p>
<p><a id="Resources"></a><strong>External Resources</strong><br />
To learn more about Wi-Fi security, I recommend listening to the following episodes of Security Now:</p>
<ul>
<li><a href="http://www.grc.com/securitynow.htm#10">Episode 10:  Open Wireless Access Points</a></li>
<li><a href="http://www.grc.com/securitynow.htm#11">Episode 11:  Bad WiFi Security (WEP and MAC address filtering)</a></li>
<li><a href="http://www.grc.com/securitynow.htm#13">Episode 13:  Unbreakable WiFi Security</a></li>
<li><a href="http://www.grc.com/securitynow.htm#14">Episode 14:  Virtual Private Networks (VPN): Theory</a></li>
<li><a href="http://www.grc.com/securitynow.htm#15">Episode 15:  VPN Secure Tunneling Solutions</a></li>
</ul>
<p><small><em>Note: Each Security Now podcast also have text transcripts.</em></small></p>
<p>I also recommend checking out the following articles:</p>
<ul>
<li><a href="http://en.wikipedia.org/wiki/Wireless_security">Wireless Security</a></li>
<li><a href="http://en.wikipedia.org/wiki/Wireless_LAN_Security">Wireless LAN Security</a></li>
<li><a href="http://www.cs.wright.edu/~pmateti/InternetSecurity/Lectures/WirelessHacks/Mateti-WirelessHacks.htm">Hacking Techniques in Wireless Networks</a></li>
</ul>
<p>I realize this is a long, fairly technical post so feel free to ask any questions, correct any mistakes, offer suggestions, or anything else using the commenting feature below. If nothing else, just let me know if you found this post useful. Thanks!</p>
<p><small><em>Note: Although I touched on a few ways to get around wireless security, I do not advocate doing so. I mentioned some of the techniques because the best way to secure against attacks is to know what attacks are out there.</em></small></p>
<p><center><!--adsense--></center></p>
]]></content:encoded>
			<wfw:commentRss>http://www.mandladventures.com/2007/04/21/securing-your-wireless-network/feed/</wfw:commentRss>
		<slash:comments>42</slash:comments>
		</item>
		<item>
		<title>How to Flash the WRT54GL with DD-WRT Firmware</title>
		<link>http://www.mandladventures.com/2007/04/12/how-to-flash-the-wrt54gl-with-dd-wrt-firmware/</link>
		<comments>http://www.mandladventures.com/2007/04/12/how-to-flash-the-wrt54gl-with-dd-wrt-firmware/#comments</comments>
		<pubDate>Thu, 12 Apr 2007 23:38:36 +0000</pubDate>
		<dc:creator>Matt</dc:creator>
				<category><![CDATA[DD-WRT]]></category>
		<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[WRT54GL]]></category>

		<guid isPermaLink="false">http://www.mandladventures.com/?p=191</guid>
		<description><![CDATA[**DISCLAIMER** The following instructions are provided without warranty of any kind. Flashing firmware does not come without risk. I will not be held responsible for any resulting equipment failure or otherwise undesirable results. Proceed at your own risk. This tutorial explains how I successfully flashed my Linksys WRT54GL version 1.1 with the open source dd-wrt [...]]]></description>
			<content:encoded><![CDATA[<p class="alert"><strong>**DISCLAIMER**</strong>  <em>The following instructions are provided without warranty of any kind. Flashing firmware does not come without risk. I will not be held responsible for any resulting equipment failure or otherwise undesirable results. Proceed at your own risk.</em></p>
<p><span  class="alignleft"><iframe src="http://rcm.amazon.com/e/cm?t=wrt54g-20&#038;o=1&#038;p=8&#038;l=as1&#038;asins=B000BTL0OA&#038;fc1=000000&#038;IS2=1&#038;lt1=_blank&#038;lc1=0D78B6&#038;bc1=FFFFFF&#038;bg1=FFFFFF&#038;f=ifr" style="width:120px;height:240px;" scrolling="no" marginwidth="0" marginheight="0" frameborder="0"></iframe></span><span class="highlight">This tutorial explains how I successfully flashed my Linksys WRT54GL version 1.1 with the open source dd-wrt version 23 SP2 VPN firmware (generic).</span> If you happen to have Linksys WRT54GL version 1 rather than 1.1 (you can tell by the serial number prefix of CL7A for version 1.0 and CL7B for version 1.1 per the <a href="http://en.wikipedia.org/wiki/WRT54G#WRT54GL">Wikipedia entry</a> and <a href="http://www.dd-wrt.com/wiki/index.php/Linksys_WRT54G/GL/GS/GX">dd-wrt Wiki</a>), you may have to follow slightly different instructions. The main difference is that you will need to flash to a smaller version of the dd-wrt firmware (the mini version) first due to a flash file size limit on the version 1.0 WRT54GL firmware before flashing to the standard, VOIP, or VPN versions.</p>
<p>As a bit of background information, <span class="highlight">I&#8217;m used a fully patched (as of April 6, 2007) Windows XP Pro with Service Pack 2 (SP2) and Internet Explorer 6 during the firmware upgrade process.</span> The OS and web browser shouldn&#8217;t matter that much, but I have heard reports of Firefox causing some problems with the Flash for some people in the past though others have claimed to use Firefox without any problems&#8211;just a word of caution.</p>
<p><center><!--adsense--></center></p>
<p>Before you begin, <a href="http://dd-wrt.com/dd-wrtv2/downloads.php">download</a> the package and version of the dd-wrt firmware best suited to your needs though this tutorial walks through flashing to the open source dd-wrt version 23 SP2 VPN firmware. Once you&#8217;ve downloaded the file, go ahead an unzip the files. The zip package contains several files, <span class="highlight">you will only need the &#8220;dd-wrt.v23_vpn_generic&#8221; file</span>. We&#8217;re going to be using the generic file rather than the wrt54g file because we&#8217;re going to be using the web <abbr title="graphical user interface">GUI</abbr> to upload the file.<span id="more-191"></span></p>
<p><span class="highlight">I recommend verifying the MD5SUM hash of the &#8220;dd-wrt.v23_vpn_generic&#8221; file to ensure the download wasn&#8217;t corrupt or hasn&#8217;t been comprised.</span> If you don&#8217;t already have a tool to calculate MD5SUMs, I recommend using <a href="http://www.download.com/HashCalc/3000-2248_4-10130771.html?tag=lst-0-3">HashCalc</a> although you must manually compare the sums with this tool unlike another tool I can&#8217;t seem to think of right now. <span class="highlight">The signature of the file should be baf91850d3204fd64b120467425b4a11.</span> If you plan on flashing a different version, you can find of list of signatures on the dd-wrt <a href="http://dd-wrt.com/wiki/index.php/Hashes">hashes page</a>.</p>
<p><span class="highlight">While your at the dd-wrt website, I recommend printing (or at least saving, not bookmarking, to your hard drive) the following pages for reference since you will not have Internet access during this process:</span></p>
<ul>
<li><a href="http://www.mandladventures.com/2007/04/12/how-to-flash-the-wrt54gl-with-dd-wrt-firmware/">How to Flash the WRT54GL with DD-WRT Firmware</a></li>
<li><a href="http://dd-wrt.com/wiki/index.php/Installation">Installation</a></li>
<li><a href="http://dd-wrt.com/wiki/index.php/Linksys_WRT54G/GL/GS/GX#WRT54GL">WRT54GL Specific Instructions</a></li>
<li><a href="http://dd-wrt.com/wiki/index.php/Reset_And_Reboot">Reset and Reboot</a></li>
<li><a href="http://dd-wrt.com/wiki/index.php/Recover_from_a_Bad_Flash">Recover from a Bad Flash</a></li>
</ul>
<p><span class="highlight">It is best to turn off your firewall and anti-virus during this process to ensure that nothing interrupts the firmware flash.</span> An interruption could cause the flash to fail and <a href="http://dd-wrt.com/wiki/index.php/Glossary#Brick">brick</a> your router. If something does go wrong you may be able to <a href="http://dd-wrt.com/wiki/index.php/Recover_from_a_Bad_Flash">recover from a bad flash</a>.</p>
<p><span class="highlight">Almost forgot to mention, you should ONLY perform the flash through an Ethernet cable using standard http (not https). Do not do this wirelessly (its best to temporarily disable the wireless adapter on your computer). Plug the blue Ethernet (Cat5/RJ45) cable that came with your router into the Network Interface Card (NIC) on the back of your computer and into one of the ports labeled 1, 2, 3, or 4. The &#8220;Internet&#8221; port on your router should be connected to your broadband source (e.g., cable or DSL modem).</span>  <em>Please ignore the extra cable in the picture. It is not needed for the flash to work.</em></p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/plugs.jpg' alt='Cables' /></p>
<p><span class="highlight">The last item that needs to be completed before uploading the new firmware is to reset your Linksys router to the factory defaults.</span> A few ways to do this exist. I chose to use the standard web interface, but the pressing and holding the reset button on the back of your router for 30 seconds should work just as well (assuming you&#8217;re using the factory Linksys firmware, if not be careful). <span class="highlight">To reset the router to firmware defaults, go to the internal IP address of your router (most likely 192.168.1.1) and login with the user name and password you setup when you first installed the router (if you don&#8217;t know those use the reset button method). Once logged in, go to &#8220;Administration&#8221; tab and the &#8220;Factory Defaults&#8221; sub-tab. Select the &#8220;Yes&#8221; radio button next to &#8220;Restore Factory Defaults&#8221; then select &#8220;Save Settings&#8221;.</span></p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/1_linksys_restore.jpg' alt='Linksys Restore' /></p>
<p>If the reset was successful, you will say a page that says &#8220;Settings are successful. You will be returned to the previous page after several seconds.&#8221;</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/2_linksys_reset_confirmation.jpg' alt='Linksys Reset Confirmation' /></p>
<p>Now that everything is setup we can begin the process of actually performing the flash. <span class="highlight">To upload the firmware, navigate to the &#8220;Firmware Upgrade&#8221; sub-tab under the &#8220;Administration&#8221; tab. On this page, select &#8220;Browse&#8221; to go to the place where you saved the &#8220;dd-wrt.v23_vpn_generic&#8221; file. Once located, hit open (no brainer). Then hit the &#8220;Upgrade&#8221; button. Please wait patiently for the upload to complete. Whatever you do, don&#8217;t interrupt it.</span> If you&#8217;re going to be tempted walk away for a few minutes and come back.</p>
<p><span class="highlight">If all goes well, you will great a screen that says &#8220;Upgrade is successful&#8221;. On that screen hit the &#8220;continue&#8221; button to, you guessed it, continue.</span> If not successful, simply re-try the same steps or research the <a href="http://dd-wrt.com/wiki/index.php/Main_Page">dd-wrt wiki</a> for more info.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/3_firmware_upload.jpg' alt='Firmware Upload' /></p>
<p><span class="highlight">The next thing you should see is a prompt to login to the new dd-wrt interface. The default user name is &#8220;root&#8221; and the default password is &#8220;admin&#8221;. Be warned, I wasn&#8217;t able to log-in initially even though I got this prompt.</p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/5_dd-wrt_login.jpg' alt='dd-wrt log-in' /></p>
<p>To confirm that your router is working you should <a href="http://en.wikipedia.org/wiki/Ping">ping</a> it. To ping your router, go to &#8220;Start > Run&#8221; in windows. Then type in &#8220;cmd&#8221; and hit &#8220;ok&#8221;. At the command prompt type in &#8220;ping 192.168.1.1&#8243;. If the router is online, you will get a ping response that says Packets Sent = 4, Received = 4, Lost = 0 (0% lost).&#8221;</span></p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/6_ping.jpg' alt='Ping' /></p>
<p>Since the dd-wrt web interface didn&#8217;t come up right after the flash, I rebooted my computer (the common solution to lots of Windows problems). That didn&#8217;t work even though rebooting probably isn&#8217;t a terrible idea. What did work was resetting the new dd-wrt firmware back to firmware defaults. <span class="highlight">To do this you need to hold the reset button on the back of the router while unplugging the router. Continue to hold the reset button as you re-plug in the router. Once the router is plugged in you should continue holding the reset button for 30 seconds to complete the hard reset.</span> I had to do this a couple of times because I didn&#8217;t reset it correctly on the first try.</p>
<p><span class="highlight">Once reset, go back to Internet Explorer and navigate to 192.168.1.1. At the prompt enter in &#8220;root&#8221; for the user name and &#8220;admin&#8221; as the password. Mysteriously, the dd-wrt web interface should come up.</span></p>
<p><img src='http://www.mandladventures.com/wp-content/uploads/2007/04/7_dd-wrt_iterface.jpg' alt='dd-wrt Interface' /></p>
<p><span  class="alignright"><iframe src="http://rcm.amazon.com/e/cm?t=wrt54g-20&#038;o=1&#038;p=8&#038;l=as1&#038;asins=1597491667&#038;fc1=000000&#038;IS2=1&#038;lt1=_blank&#038;lc1=0D78B6&#038;bc1=000000&#038;bg1=FFFFFF&#038;f=ifr" style="width:120px;height:240px;" scrolling="no" marginwidth="0" marginheight="0" frameborder="0"></iframe></span></p>
<p><span class="highlight">Congratulations, you&#8217;ve successfully flashed your router!</span> Since you&#8217;ve successfully flashed your WRT54G, you should checkout the <a href="http://www.amazon.com/gp/product/1597491667?ie=UTF8&#038;tag=wrt54g-20&#038;linkCode=as2&#038;camp=1789&#038;creative=9325&#038;creativeASIN=1597491667">Linksys WRT54G Ultimate Hacking</a><img src="http://www.assoc-amazon.com/e/ir?t=wrt54g-20&#038;l=as2&#038;o=1&#038;a=1597491667" width="1" height="1" border="0" alt="" style="border:none !important; margin:0px !important;" /> guide to make the most out of your new found knowledge of router firmware. </p>
<p class="alert">Now that your running DD-WRT firmware, make sure to make use of all the available security features. See my post on <a href="http://www.mandladventures.com/2007/04/21/securing-your-wireless-network/">Securing Your Wireless Connection</a> and other post in the <a href="http://www.mandladventures.com/category/tech-stuff/dd-wrt/">dd-wrt category</a>.</p>
<p>If you liked this post, consider subscribing to my <a href="http://feeds.feedburner.com/MAndLAdventures">feed</a> and/or sending me something from my <a href="http://www.amazon.com/gp/registry/wishlist/W77D6UZQZW9X">wish list</a>. One other option is to send me a <a href="http://www.amazon.com/gp/product/B000BTL0OA?ie=UTF8&#038;tag=wrt54g-20&#038;linkCode=as2&#038;camp=1789&#038;creative=9325&#038;creativeASIN=B000BTL0OA">Linksys WRT54GL</a><img src="http://www.assoc-amazon.com/e/ir?t=wrt54g-20&#038;l=as2&#038;o=1&#038;a=B000BTL0OA" width="1" height="1" border="0" alt="" style="border:none !important; margin:0px !important;" /> so I can do some more experiments and write more tutorials. Thanks in advance for your support of this guide &#038; site!!!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mandladventures.com/2007/04/12/how-to-flash-the-wrt54gl-with-dd-wrt-firmware/feed/</wfw:commentRss>
		<slash:comments>199</slash:comments>
		</item>
	</channel>
</rss>
