<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ddwrt on RESEARCHUT</title><link>https://researchut.com/tags/ddwrt/</link><description>Recent content in Ddwrt on RESEARCHUT</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>rrs@researchut.com (Ritesh Raj Sarraf)</managingEditor><webMaster>rrs@researchut.com (Ritesh Raj Sarraf)</webMaster><lastBuildDate>Tue, 23 Feb 2016 08:54:34 -0500</lastBuildDate><atom:link href="https://researchut.com/tags/ddwrt/index.xml" rel="self" type="application/rss+xml"/><item><title>Unbricking my Linksys</title><link>https://researchut.com/blog/wireless-repeater-linksys-tplink/</link><pubDate>Tue, 23 Feb 2016 08:54:34 -0500</pubDate><author>rrs@researchut.com (Ritesh Raj Sarraf)</author><guid>https://researchut.com/blog/wireless-repeater-linksys-tplink/</guid><description>&lt;p>In trying to improve the WiFi service in my house, I recently dug out my old
Linksys WRT54G Router. It is a 802.11 bg router, which can do 54 MBPS.
Currently, I use a TPLink based router, with a DD-WRT community firmware,
which claims is 802.11 bgn and can do 300 MBPS. The overall wifi signal isn&amp;rsquo;t
adequate, so I thought of using the old router as a repeater.&lt;/p>
&lt;p>The default Linksys VXWorks firmware does not have the bridging capabilities,
so it was time to flashback, again, the dd-wrt image onto it (The last time I
did, I eventually had to revert back to the stock firmware because my ISP
claimed that the router was giving too many packet drops). Being an old
device, and me being lazy, I did not pay much attention to the exact steps;
and ended up bricking my router, wherein it wouldn&amp;rsquo;t give me the &lt;strong>Management
Console&lt;/strong> to flash a new firmware; nor would it give me the old &lt;strong>VXWorks&lt;/strong>
firmware interface. All it gave was a White Screen of Death and an active IP
connection.&lt;/p>
&lt;p>Turns out I&amp;rsquo;m not the only one bricking routers, so some good soul
&lt;a href="http://www.makeuseof.com/tag/unbrick-trashed-linksys-router/">documented&lt;/a> the
process on unbricking the router. I was in a slightly more better position
than the author, cause I did have the network available. My initial hope was
to just push the firmware image over tftp, and that it would work. But that
didn&amp;rsquo;t happen.&lt;/p>
&lt;p>So, I was forced to follow the steps in the article, i.e. to use the Windows
Tool mentioned in it (Infact that is what triggered me to write the article).
Not having Windows available, my choice was to try it out over Crossover/Wine.
It got the job done; so Thank You.&lt;/p>
&lt;p>BTW, does anyone know what goodie does the Windows Tool do that plain tftp did
not ? The Windows Tool too pushed the image over tftp, so it must be doing
something within the tftp spec to trigger the firmware upload and flash.&lt;/p>
&lt;p>&lt;img src="https://researchut.com/images/Screenshot%20from%202016-02-23%2014-17-00.png" alt="">&lt;/p>
&lt;p>That done, getting the &lt;strong>Repeater Bridge&lt;/strong> wasn&amp;rsquo;t that painful. If you build a
Repeater Bridge setup, just follow dd-wrt instructions. The only extra I&amp;rsquo;d add
is that &lt;strong>You should keep your Virtual AP&amp;rsquo;s credentials the same as that of
your Primary Router&amp;rsquo;s AP&amp;rsquo;s.&lt;/strong> I&amp;rsquo;m not sure why that is needed but that ate my
good 2-3 hrs.&lt;/p></description></item></channel></rss>