From DD-WRT Wiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 00:13, 22 September 2009 (edit)
Techie (Talk | contribs)
(deleted exterraneous, redundant, and outdated info)
← Previous diff
Revision as of 00:36, 22 September 2009 (edit) (undo)
Techie (Talk | contribs)
m (Configuration Notes)
Next diff →
Line 145: Line 145:
* You must start to configure router from scratch. Do not try to use config files from older firmware versions. * You must start to configure router from scratch. Do not try to use config files from older firmware versions.
-* It is strongly advised that you enable the "Boot Wait" option under the "Administration" tab. This will help you recover in the future should you flash your router improperly. If you use v23 or higher the "Boot Wait" option is enabled by default.+* It is strongly advised that you do not disable the "Boot Wait" option under the "Administration" tab. Boot Wait allows you recover if you flash your router improperly.
=If something goes wrong= =If something goes wrong=

Revision as of 00:36, 22 September 2009

Installing DD-WRT on a router in most cases is almost as simple as installing a program onto your computer. Installing programs on a router, known as firmware, are achieved by a method called flashing. This article helps you determine which installation process is for you on your supported router, as well as giving router suggestions and information about flashing each one.


Is Your Router Supported?

For a list of devices working with DD-WRT, please see Supported Devices.

Before You Begin

First before loading any firmware to your the English Broadcom Forum Announcement entitled Peacock Thread It contains more information than just for those that having problems. Start there...Do some research...then ask questions. Don't just load V24-Final or the English Broadcom Forum Announcements to find out why.

Downloading DD-WRT

  • Download the latest stable release from the DD-WRT Downloads page (or secure version).
    • Some newer routers are not supported by the latest stable release. Check the Supported Devices list for the minimum required DD-WRT version for your device. You may need to use a release candidate or experimental build.
  • Ensure you are using the correct version of the firmware.
    • For a comparison of the builds, see File Versions.
    • Updating through the Web GUI means you need to use the _generic version.
    • Use the _mini version when upgrading from original Linksys firmware. You only need the _micro version if your hardware has 2 MB of flash (WRT54G v5 through v8 for instance). Use the "_mini" firmware if your hardware has 4 MB or more of flash (WRT54GL for instance).
  • Read the changelog and all other information files on the download pages. They contain important information!
  • If you downloaded a .zip file, then extract the archive.
  • Confirm a good download by comparing the MD5 hash fingerprint of the firmware you downloaded with the published checksums. See Hashes & Checksums for further info and instructions.


Follow all the instructions precisely, or you may run into trouble. Incorrectly flashing can brick your router!

  • For the initial flash from the Linksys firmware, do not use Firefox, use IE to flash the router (even OS X IE works). Once DD-WRT is running, you can use any browser you like to administer or even flash the router.
  • Do NOT use a wireless connection to upload firmware. Use a wired connection. It is recommended that you disable any wireless adapters on your system to ensure that none are used for the transfer.
  • Do NOT flash/backup your firmware over an SSL (HTTPS) connection. Make sure you are using HTTP.
  • Disable your anti-virus-software, as a false-positive virus detection could interrupt the upload.
  • If you need to use TFTP to upload firmware, disable your software firewall first.
  • You will not have internet access through the router during the process of replacing the firmware. We recommend you save this webpage and the Recover from a Bad Flash and FAQ pages to your hard drive (use File->Save As, *NOT* a bookmark). This will allow you to review the information offline in the event that something goes wrong.
  • Do not forget to make note of your current settings, especially if you have static IP addresses. A quick way of doing this is to take screenshots of your current configuration screens.
    • It can be essential to record your current WAN MAC address. Some ISPs do not allow an immediate change of the routing hardware and changing the firmware changes the MAC address.
  • Have a secondary router or internet connection available while experimenting with your router's firmware, to expedite any trouble shooting and remove the risk of becoming stranded.
    • If you have a cable modem which connects to your router with ethernet, you can plug your PC straight into the modem should you have any problems. Your PC will be assigned your external IP with DHCP, and you will be on the net. Remember to use a software firewall.

Flashing with Web GUI

  • NOT for First-Time Flashing on Buffalo Devices - see Buffalo section for details
  • NOT for First-Time on ASUS WL500xx series routers - see Asus section for details

Reset to Factory Defaults or better yet a Hard reset or 30/30/30

If you know the IP address, username, and password of your router:

  1. Follow the instructions in the next section to log in to the Web GUI.
  2. Click the "Administration" tab.
  3. Click the "Factory Defaults" sub-tab.
  4. Select "Yes".
  5. Click the "Save Settings" button.
  6. A new page will open, click "continue".

If you do not know the IP address, username, or password of your router, you will need to use the reset button. Be careful when using this method! Apparently if you have OpenWRT already on your router the reset button may not function as it is assumed here and may actually brick your router! Research the functionality of your current firmware to be safe.

Logging in to the Web GUI

To use the Web interface, you will need to have Javascript enabled with any security restrictions disabled. If the Linksys firmware is currently installed, do not use Firefox as certain versions of the Linksys firmware are known to have problems with Firefox.

  1. Type in the IP address of the router (default into the address bar of your browser.
  2. You will be prompted for username and password.
    • For DD-WRT versions starting with 2006-Feb-28, the default username is root. Prior versions have a blank username by default.
    • For Linksys firmware, the default username can be left blank or set to anything.
    • For DD-WRT and Linksys firmware, the default password is admin.

Upload the Firmware


It is VERY important that you not interrupt the setup while the router is being flashed and rebooted. Do not turn off the computer, close the web browser, or turn off the router during this process! I usually just take a step back, and turn my head away so I don't breathe on it for these crucial 2 minutes.

  1. First do a hard reset on the unit that DD-WRT is to be loaded onto.
  2. You should be in the Web GUI of the router. Go there now.
  3. Click the "Administration" tab
  4. Click the "Firmware Upgrade" sub-tab.
  5. (Only applicable when DD-WRT is already installed.) Choose the option to Reset to Defaults after flashing.
  6. Click the "Browse" button and select the DD-WRT .bin file you downloaded and confirmed.
  7. Click the "Upgrade" button.
  8. The router will take a few minutes to upload the file and flash the firmware. During this time, the power light will flash.
  9. A new page will open confirming that the upload was successful (Installation#Possible errors if not). Now wait about 5 minutes before clicking "Continue".
  10. Lastly, do another hard reset on the unit.
  11. If flashed successfully you will now be able to access the DD-WRT web interface at

[Comment added 2007/03/27 by staylor] Or, you won't be at the DD-WRT web interface I have a WRT54g v1.1 (also with WRT54gl v1.1), flashing with DD-WRT v23 sp2. I waited the requisite number of minutes, and my "Wireless-G" badge lit up (a good sign), but when I clicked "Continue" after the upload was successful, I did not get to the DD-WRT web interface. Nor was the device ping-able.

[Comment added 1/04/08 by jwebste1] I can confirm Staylor's comment above for a brand new store bought WRT350N (had to soft reset the router to get the mini install to become accessible on

Holding down the reset button for 30 seconds (leaving the power cable connected) re-booted the router, and all was fine thereafter.

If the above doesn't result in a successful load of the DD-WRT web interface, try a "ipconfig -renew" in a command prompt window.

Possible Errors

During the firmware upload process, if your router says something similar to, "Upload Failed," you may be using the wrong version of DD-WRT. This may occur through the web GUI if you use a *wrt54g.bin version when you should have selected the generic version instead. It may also be that your router requires the mini version to be flashed before the full version. Be sure to double check to make sure you have the right version. If you are certain that your router is supported and that you have the correct firmware, you may simply need to use a different web browser (e.g. from Firefox to Internet Explorer).

After clicking Upgrade when upgrading firmware from one DD-WRT version to another, if you are using Firefox there may be a problem with the upload. In this instance the screen fades to white with a countdown timer and is followed by a Connection Reset message shortly after. After this you cannot access the Web GUI again, and a router reboot will result in a flashing power light (WRT54GL is the case in point). You can recover from this and use a different browser (e.g. Internet Explorer) to upload the firmware.

When logging in fails with the default username/password (see above), you can reset the password.

Reset to Factory Defaults Again

Do this only after you have confirmed that the firmware upgrade is working. At this point you may have temporary problems using Web Interface, so just ping your router.

Many Web Interface problems can be solved by a hard reset and by clearing your browser cache.

See Reset And Reboot.

Flashing with TFTP

Although TFTP is a safe method to flash many routers, it should however not be seen as the standard procedure for flashing most devices, except if you are specifically told to do so in the specific instructions for flashing your brand or type of device. Normally, the GUI flashing method should be used, as it is adequate for the vast majority of standard situations.

If you still wish to flash with TFTP, see the articles TFTP flash, Asus TFTP Flash and Recovering with TFTP.

Flashing with Command Line

This is available on routers that already have DD-WRT installed and Telnet/SSH enabled.

It's the *ONLY* recommended mode to upgrade the router wirelessly.

1) telnet or ssh into dd-wrt

2) download the firmware to the router's /tmp directory with wget or scp

cd /tmp

2a) Alternatively, you could use the mounted share if you have one, and simply download the file there.

3) compare the MD5 checksum of the original and the downloaded file

md5sum dd-wrt.v2x_generic.bin

4) write the firmware to flash

write dd-wrt.v2x_generic.bin linux

5) wait...

6) reboot

7) restore factory defaults using erase nvram command or reset button

Upgrading to a Newer Version of DD-WRT

If DD-WRT is already installed on your router, you can simply upgrade to a new version via the web interface or TFTP. However, it is highly recommended that you restore the router to defaults using the reset button before and after flash. Never restore old backups from previous versions! Skipping these steps could lead to a bricked device!

Please see wiki article Hard reset for further information on how to restore your device back to DD-WRT default settings.

Configuration Notes

  • You must start to configure router from scratch. Do not try to use config files from older firmware versions.
  • It is strongly advised that you do not disable the "Boot Wait" option under the "Administration" tab. Boot Wait allows you recover if you flash your router improperly.

If something goes wrong

  • If your router fails to reboot (power light doesn't stop flashing, no web interface, etc) you will need to Recover from a Bad Flash. Additional help can be found by doing a forum search.

Hardware-specific Information


Accton MR3202A

See LaFonera Software Flashing Page. (use only the MR3202A binaries provided, instead of the Fonera ones)

Accton MR3201A

See Accton Software Flashing Page. (use Fonera binaries)



The Allnet ALL0277 (not DSL !!!) is essentially a relabeled Linksys WRT54G v1.0. It was even reported in the forum, that you can install the Linksys firmware on these devices.

With some minor exceptions, the procedure to install DD-WRT the first time is pretty much the same as for other WRT54G devices. For flashing this device the first time you need to change the first 4 bytes of the mini_wrt54g image to read W54A (usually this is W54G). You can use a hex editor like XVI32. After the patch, you can upload using the new firmware using the standard ALLNET web interface. If the ethernet interface does not work (it did not for me on v23SP2), try the wireless LAN interface to check whether the upgrade did succeed.

After the hard reset of the router, you should be able to proceed as described above.


A major clean-up of the Asus Install section was needed (and done) in the fall of 2009 - see Asus WL500-- old descriptions for the old but working guides. Valuable information from the old guides should be generalised, summarised and added to the Install list below, in an manner that would keep the Initial Install page looking good.

All Asus WL-500xx series routers

For all Asus WL-500xx series routers there are a number of ways to do the initial flash.
The TFTP method using the two Asus specific clean-up files is the "works every time" way.
Other methods like using the ASUS Recovery tool or even using the web-GUI has however also been reported to work for some, for the intial dd-wrt flash. So your mileage may vary
Pick the one that is easier and works for you - You have now been notified of the method that is guranteed to work!

The firmware files for the Asus WL-500xx series are found under Broadcom -> dd-wrt.v24_mini_asus.trx and ...generic.bin - Read on to see when the ...asus.trx file should be used.

The recommended Asus TFTP way for all WL-500xx routers

Links to the TFTP "sure way" of doing the initial flash of the WL-500xx series routers:

Web Interface

The easiest way. If you can connect to the router and administer it via its web interface, skip to point 5:

  1. Power up the router
  2. Connect via ethernet to one of the four LAN ports (its not recommende to do any type of upgrade using a Wi-Fi connection, any loss of connection will probably brick your router)
  3. Obtain network settings via DHCP
  4. Point your browser of choice to (use the IP address of the gateway, obtained in the previous point)
  5. Reset to default settings! Can be done under Administration -> Factory defaults. Apply settings and wait for the router to reboot.
  6. Go to System Setup > Firmware Upgrade
  7. Upload the firmware file using the form provided. Select the ...asus.trx file. Also select Reset to defaults after flashing
  8. Once the ...asus.trx file is loaded and the router has rebooted,
  9. Go to System Setup > Firmware Upgrade
  10. Upload the firmware file using the form provided. This time select the ...generic.bin file. Also select Reset to defaults after flashing
  11. Wait until the page reloads, and wait even after the count down reaches 0. Wait until the DD-WRT interface reloads (this may take several minutes for Big and Mega firmware versions!).
  12. Congratulations, the DD-WRT install has been completed.

Asus Recovery Utility

You can get the utilities here, or you can browse the Asus site to download the latest version. Asus only seem to provide these for Windows.

  • Under Vista and Win7 this utility must be run as administrator.
  • In case you have multiple network interfaces and are unable to find you router, disable all but the one that is connected to your router.
  • You should also turn off your firewall, in order to allow the Asus Recovery Utility to be able to connect and send data from your PC to the Router.


  1. Remove the power connector of the WL500G.
  2. While holding the reset button, plug the power connector back in. (WL500gP - button labeled "restore")
  3. When the power LED flashes, release the reset button. The router is now in recovery mode.
  4. Wait for your PC to get an IP address (if dhcp is configured) - you may need to manually set the address of your pc to
  5. Use the Asus recovery utility to upload the DD-WRT ....asus.trx file.
  6. After the upgrade the router reboots and you should be able to access the web interface, and there do an upgrade to ......generic.bin firmware versions.

Asus WL500G (Original)

For initial flash see Asus WL-500xx series

Asus WL500G Deluxe

For initial flash see Asus WL-500xx series

Here is the Asus WL-500g Deluxe specific wiki page with pictures, comments and more

Asus WL500G Premium

For initial flash see Asus WL-500xx series

Here is the ASUS WL-500g Premium specific wiki page with pictures, comments and more

Asus WL500G Premium V2

For initial flash see Asus WL-500xx series

Here is the WL500G Premium v2 specific wiki page with pictures, comments and more

Asus WL500W

For initial flash see Asus WL-500xx series

For an indepth how to guide see Asus WL-500W

As this router has a N-type NIC it is recommended to use a new firmware that supports this, this means no v24SP1. The firmware should be newer, like v24-pre-SP2 versions (also called v24_TNG)

See download section -> others -> eko -> either BrainSlayer-V24-preSP2 [1] or V24_TNG [2] Pick dates after 07-21-09 and/or svn number higher than 12533

Asus WL550gE

For initial flash see Asus WL-500xx series

Asus WL520G

  • Simply upload dd-wrt.v24_micro_generic.bin through the web interface of the original Asus firmware.


Particularly due to the low amount of memory this router has, it is recommended to use the latest stable micro-generic build of DD-WRT. Currently:

Users have experienced successful flashes directly from the web interface on the default factory firmware i.e. the ASUS Flash tool is not required. If this fails, revert to using the tool.

Other notes

  • Same as Deluxe, but DO NOT flash the clear_nvram or recover files - it will brick your router. Only flash the firmware file itself and then do a reset to factory settings via web GUI.
  • I used a static IP address on my PC because DHCP seemed to slow down the router.
  • dd-wrt.v24_micro_generic works just fine.
  • No problems so far using it as a client bridge (Xbox), router is nothing special, but it is possibly the cheapest wireless device around here, so makes for a good budget wireless device once flashed.
  • Using web-based firmware update (rename .bin to .trx)
  • Web interface from Asus firmware and newer doesn't allow to upload DD-WRT firmware, it reports corrupted file. You have to downgrade to Asus firmware in order to flash DD-WRT firmware.
  • There also could be unable to downgrade to Asus firmware from newer version through web interface, easily soulution could be rename in order to flash DD-WRT firmware. Easy solution could be to rename a old firmware file (up to for example to "newer" WL520gc_2.0.1.2_EN.trx
  • Uploading via TFTP sometimes does not reset the router. Wait for 10-15 minutes and then power it down and up manually.

[Added by zorruno 11 Sep 2008]

  • confirmed with new WL-520GC out of box, using web interface only
  • needed first to downgrade Asus firmware to (here) using the method above by renaming it to WL520gc_2.0.1.1_EN.trx (version was in the router originally)
  • don't worry about looking for a .trx file for the next step, dd-wrt.v24_micro_generic.bin is fine (here). Did not need to rename this file as .trx, it uploaded fine with the .bin suffix.

[artemv, 16 Nov 2008]

  • needed to hard-reset the router after downgrading to (from to be able to load dd-wrt.v24_micro_generic

[kyxap, 11 Feb 2008]

  • With last stable DD-WRT firmware (v24SP1 build 1020) dhcp doesn't work with my WL520GC. This one is extended version of DD-WRT with SSH-support (unofficial build, but works perfect for me).

Asus WL520GU

For initial flash use same procedure as Asus WL-500xx series. also see:

Here is the WL-520GU specific wiki page with pictures, comments and more


Belkin F5D7230-4 v2xxx and Lower

As this Belkin router comes in several versions, this firmware build will only work for Belkin router models up to v2000. v2000 has a different switching chip than earlier versions though, so you may lose the functionality of the switch and may only be able to connect wirelessly after flashing a v2000 Belkin (see instructions below for adding limited wired capability). v3000 should work, but attempts to flash it have been unsuccessful with current versions of DD-WRT. Attempting to flash a v3000 could brick your router. (psuftbl has had success with v3000) Version 4000 and higher appear to be based on the TI chipset found in the Linksys WRT54GC. v1000, and v1111, have 4 MB flash ROMs while v1444 has only a 2 MB flash. You have to flash the router with the 2 MB micro firmware via TFTP. If you have a 4 MB model, you can reflash the router with the full version generic firmware from within the routers web interface once you've followed this procedure. Unless you need the extra features, it is best to stick with the micro firmware since it is known to work better with this router.

Flashing v1232a with the latest VINT (currently dd-wrt.v24-9517_VINT_micro.bin) worked. Flashing with the latest micro (dd-wrt.v24_micro_generic.bin) worked with the wired connection but the wireless did not seem to work (no SSID was broadcast).

Warning: These instructions will brick v1212 and v1213 Belkin F5D7231-4 routers, apparently without a hope of fixing them short of some rewiring. See the forum posts here[3] for possible help un-bricking one of these units.

  1. Download the latest micro firmware (dd-wrt.v24_micro_generic as of this writing)
  2. Reset router to factory defaults. Unplug the router.
  3. Connect your computer directly to one of the LAN ports on the router.
  4. The router starts up with IP address Set your computer's IP address manually to the following setting: IP Address:, Subnet Mask:, Default Gateway: leave blank. For more help with this step, study the instructions for the Buffalo router.
  5. Go to Start->Run->"cmd" and press Enter.
  6. Change your directory to the folder containing the firmware image. Ex. cd "C:\Documents and Settings\All Users\Desktop"
  7. Type tftp -i PUT (file name of firmware image) For example: tftp -i PUT dd-wrt.v24_micro_generic.bin. Do not press enter yet.
  8. Connect the power to the Belkin.
  9. All port LEDs will illuminate.
  10. After a few seconds, all LEDs except the one you are connected to will turn off. Wait exactly one second and hit enter to execute the command. If you get a timeout error just try again. (Also try running tftp right before powering up.) If you continue to have trouble with this step check out the alternative method below.
  11. The LED on the LAN port will flash rapidly for a while after which the power button will flash rapidly for a while. Be patient and wait for the power light to stop flashing. Wait a couple more seconds.
  12. Power cycle the router. (unplug the power, wait a few seconds, plug it back in).
  13. Set your IP address back to automatic (DHCP), or set it to something beginning with 192.168.1.
  14. The router is now accessible at
  15. The user name is 'root' and the password is 'admin'
  16. Enjoy your DD-WRT router

Alternative for Flashing F5D7230-4

If you don't enjoy spending hours, powering your Belkin router up and down. You can can try this procedure that worked for my v1444:

  1. Follow steps listed in the method above until you finish the part where you set your computer's IP address to
  2. Goto and goto their download page (You may want to do this first before you reset to the factory defaults in case resetting screws up your internet connection). If the site asks for your location, choose North America - USA.
  3. tftpd32 ( also works (at least with a v2000). Under settings, set timeout to 20 seconds and max retransmit to 30.
  4. Download the firmware for BEFW11S4 - EtherFast Wireless AP + Cable/DSL Router w/4-Port Switch (Version 1.0).
  5. Extract the tftp.exe program from the zip file.
  6. Start TFTP program and set server to: and for the file part, put the location of your "dd-wrt.v24_micro_generic.bin" file.
  7. Set retries to 20.
  8. Power up router.
  9. Click upgrade and then hit the reset button on your router. If program doesn't catch the Belkin's TFTP window, just hit reset again. The tftp program will let you know when it is upgrading and succeeds.

This method caught the Belkin narrow tftp window on retry #11 vs. my 0 catches after 40 some tries using the power up and down method. Not sure if this will work on other version of the F5D7230-4. From what I have seen with my router, a successful installation will change the LEDs on the Belkin. WLAN LED does not work. Power LED will work and connected WAN LED will blink green. Good luck.

After more than 50 unsuccessful attempts to flash my v1444 router I finally flashed my router using the alternative method described above, but only after using a hub or switch to connect the computer and the Belkin unit. All of my attempts with a direct connection between the router and the computer resulted in a timeout, but by using a hub or switch I had success on the first try. When trying to flash with a direct connection from the computer to the Belkin, it will never work. The connection fails when the router is unpluged or reset. By the time the connection is re-established, the Belkin is too far along in the boot process to accept the upgrade. So if you are having difficulty, like I did for so long, try the above method with a hub or switch connecting one of the LAN ports of the router to the computer.

I want to confirm that using a switch as mentioned above worked for me at the first try with V1000 router while other methods failed after more than 30 tries.

The linksys tftp program with a hub worked for me on the first try on version 1112. Both command line and gui tftp failed (many times) without a hub.

Second Alternative for Flashing F5D7230-4

If you're having difficulty with either of the above methods (or just don't feel like going through all the hoops required) there is a much simpler method that may work.

  1. Reset the router to factory defaults.
  2. Set your computer's IP address to as described above.
  3. Plug your computer into the router and power the router on.
  4. In a command prompt (what you get by going to Run in the start menu) type out the tftp command line but do not hit enter yet.
  5. Press and release the reset button on the back of the router.
  6. Almost immediately hit enter in the command prompt to run the tftp command you typed out.
  7. If tftp tells you the file was sent successfully wait a few seconds, unplug the router, then plug it back in. If it says the connection timed out or the transfer failed, prepare the tftp command line again (hitting the up arrow key should do it) and repeat the previous two steps.
  8. Connect to to configure (and enjoy) your vastly improved router.

After trying the first two methods a few times (the first method several times in particular) I managed to get my v1444 flashed in one try (!) using this method. As such I am unsure of the exact delay between resetting the router and starting TFTP, but it was definitely less than a second. At the very least this method is much more enjoyable than unplugging and re-plugging your router over and over again.

Linux Instructions for Flashing F5D7230-4

  • Set the IP address of your ethernet interface to be, netmask of
sudo ifconfig eth0 inet netmask
  • Make sure you have "tftp" installed.
  • Start up tftp with the router switched off:
# tftp
tftp> verbose
Verbose mode on.
tftp> trace
Packet tracing on.
tftp> rexmt 1
tftp> binary
mode set to octet
tftp> status
Connected to
Mode: octet Verbose: on Tracing: on
Rexmt-interval: 1 seconds, Max-timeout: 25 seconds
tftp> timeout 60
  • Turn on the router after typing the following command:
tftp> put dd-wrt.v24_micro_generic.bin
putting dd-wrt.v24_micro_generic.bin to [octet]
Sent 1746029 bytes in 14.8 seconds [943799 bits/sec]
  • When the lights stop rapidly blinking, reset the router.

OSX Instructions for Flashing F5D7230-4

  • Make sure the router is on and plugged into your Mac's ethernet port
  • Goto System Preferences and click on the Network icon
  • In the selection box next to the word "Show:" select the "Built-in Ethernet" option
  • Change the IPv4 Configuration to manually and set the IP address to the subnet mask to and the router to
  • Click "Apply Now" and change the selection box next to "Show:" back to "Network Status"
  • Unplug the power from the router and watch the green dot next to "Built-in Ethernet" turn red
  • Open the terminal application and type the following commands
tftp> connect
tftp> verbose
Verbose mode on.
tftp> ascii <- [Edit: I think this is a typo, should be "binary"!] 
mode set to octet
tftp> status
Connected to
Mode: octet Verbose: on Tracing: off
Rexmt-interval: 5 seconds, Max-timeout: 25 seconds
tftp> timeout 60
  • Type the following but don't hit enter yet. Make sure you can still see the System Preferences window
tftp> put dd-wrt.v24_micro_generic.bin
  • Now plug the router back in. As soon as you see the red dot next to "Built-in Ethernet" turn green, hit enter and the firmware should be flashed once the lights on the router stop blinking.
  • In order to connect to the router you must first go back to the Network Preferences and change the IPv4 configuration back to DHCP and click "Renew DHCP Lease"

Using v2000 Or FD57231-4 As A Wireless Client or Access Point with DD-WRT
(borrowed from

The Belkin F5D7230-4 v2000/FD57231-4 (with screws not under label) are still not completely functional with DD-WRT, but it can be used as either a wireless access-point or a wireless client. The reason for this limitation is due to the fact that the current robo-switch is unable to properly configure the vlan with this router's implementation of the BCM5325EKQM switch chip. By bypassing the vlan stuff we can get limited functionality from this router. In order to load DD-WRT micro you must tftp it on to the router. These instructions are for the v24 build of DD-WRT micro not the multi-language version which seems to have stripped out the reboot, ls and other shell commands.
A) Belkin F5D7230-4 v2000 as a wireless client.
1) Connect to the router wirelessly
2) Telnet to the router and sign in or use a serial console cable
3) Enter the commands below:
nvram set lan_ifnames="eth0 vlan0"
nvram set port0vlans=0
nvram set lan_ifname=eth0
nvram set wan_ifname=vlan1
nvram set wan_ifnames=vlan1
nvram commit
4) After the reboot, unplug the router and plug it back in. When it starts back up your LAN ports should be active. The router's default IP address is Just use the web interface via the LAN port to configure the router as a wireless client.
B) Belkin F5D7230-4 v2000 as a wireless access point
1) Connect to the router wirelessly
2) Telnet to the router and sign in or use a serial console cable
3) Enter the commands below:
nvram set lan_ifnames="vlan0 eth1"
nvram set port0vlans=1
nvram set remote_management=1
nvram set lan_ifname="br0"
nvram set wan_ifname=eth0
nvram set wan_ifnames=eth0
nvram commit
4) After the reboot, unplug the router and plug it back in. When it starts back up your WAN port should be active. The router's default IP address is Just use the web interface via the WLAN port to configure the router as an access-point.
If you enter in the wrong setting or can not access your router you can always hold down the reset button to restore it to the factory defaults. Remember that we are bypassing all the VLAN stuff so some of the web configurations will not work.

Belkin F5D7230-4 v2000 and v2000de

This version has a different flash chip than the other versions, and it will enter a reboot loop if a special SF build is not used. If you have already flashed the device and it is in a reboot loop, you can still flash the correct build using TFTP.

This version also has a different switch chip so only wireless will work after flashing. Wired can be enabled, but the ports can only be set to either WAN or LAN. If you only have wireless clients or want to use it as an AP or client bridge; this is not a problem. However, you are not able to use this device as a wired router with wired clients.

Flashing Instructions

Eko has made three new builds for this router. Build 12220 The file names are dd-wrt.v24-12220_Bv2000_NEWD_micro.bin, dd-wrt.v24-12220_Bv2000_NEWD_micro-plus.bin, and dd-wrt.v24-12220_Bv2000_NEWD_micro-plus_ssh.bin If you don't know what micro-plus is you should read this: Micro-plus

A v24 final SF build for this device is currently available here. The file name is dd-wrt.v24-9517_NEWD_SF_micro.bin

Flashing method is the same as other Belkin versions.

Enabling Wired Ports

After flashing, the router will only be accessible through wireless.

  1. Connect to the router over wireless. The default SSID is dd-wrt. You will be able to access the GUI at
  2. Telnet to In Windows type telnet in command prompt. The default username is root and password is admin
  3. Type the following commands:
nvram set Belkin_ver=2000
nvram commit

The default setting is for all the ports to act as LAN ports.

Setting Wired Ports to WAN

It is not possible to set only the WAN port to WAN due to the switch chip in this version. You may set all the ports to WAN after following the above instructions for enabling wired ports. In this mode, you cannot connect any other wired devices other than WAN. If you are going to use the device as an AP or client bridge, this step is not needed.

Connect to the router using wired or wireless and telnet to as explained above.

To use all ethernet ports as WAN, set

nvram set wan_to_lan=yes
nvram commit

To restore setting to LAN (default)

nvram unset wan_to_lan
nvram commit

Belkin F5D7230-4 v3000

This version needs to be flashed using build 10068 or later (micro version only). The flashing method is the same as other Belkin routers.

There have been reported problems about this router dropping the connection in Client Mode.


NOTE: Use only v23 SP1 final or later with Buffalo devices. Older releases may cause trouble!

NOTE: For some models you can use the ddadder program

Out-of-the-box: First-time-flashing for 'store-bought' Buffalo models

The web interface on a Buffalo-router cannot be used the very first time to convert the Buffalo router from factory firmware to DD-WRT.

It is very easy though to bypass this on most models (see specific models below for exceptions):

  1. Google 'tftp2.exe', and download a copy from a website.
  2. From the DD-WRT website, download dd-wrt.v24_std_generic.bin from the v2.4 SP1 folder, or the latest release.
  3. Plug your ethernet cable (not wireless!) into a LAN port on the Buffalo.
  4. Your IP address auto-assigned is usually, but you must manually set it to flash this time only.
  5. Assign the IP of to your network adapter. In most Microsoft Windows this is Start, Control Panel, Network Connections, find the LAN connection and right-click, find TCPIP and click Properties, and set the IP to and the Subnet to Do not change any other settings!
  6. Open TFTP2.EXE. Put in for the Server, and select the .bin firmware image from step 2.
  7. Unplug the Buffalo. Get your mouse ready to click on the Upgrade button in TFTP2.
  8. Plug in the Buffalo. The diag light with all the other lights may come on very quickly and go out. A few seconds later when the diag light blinks, immediately press the Upgrade button in TFTP2.

The diag light flashes for awhile, the router restarts, and you are done! Don't forget now to change your LAN TCPIP back to DHCP (Automatic).

Misc. Notes: The procedure above is necessary the first time flashing from the factory Buffalo firmware to DD-WRT firmware, because, normally, most companies let you upload firmware directly from the user interface. Buffalo, unfortunately, encrypts their firmware, meaning their routers from the Web interface will accept only their encrypted firmware.

The first time you flash, the TFTP method can be used to bypass the 'encrypted' firmware requirement. Afterwards, the router firmware can be changed through the Web interface normally.

All the Broadcom routers normally enter a special mode in the first few seconds after power is applied that allows a TFTP transfer to directly program the flash ROM with new firmware. So what you do is get everything ready to go. 1. power up the router, and then 2. send the router the new firmware, quickly.

WHR-G54S, WHR-HP-G54, WZR-HP-G54 Specifics

  • Once you flash to DD-WRT on the Buffalo WHR-G54S/WHR-HP-G54/WZR-RS-G54 and you want to flash back to the Buffalo firmware, look in the downloads section of in the "buffalo factory revert" folder for unencrypted firmware that will load from the DD-WRT GUI. The WHR-HP-G54 image is the German version. Download the English version from Buffalo's site. Flash the German version and use that to flash the English version.
  • A hidden LED behind the front panel may blink on older models. It slightly lights up the bridge icon. This LED is not used in the Buffalo firmware, but in DD-WRT it will flash on for 2 seconds, then off for 2 seconds.
  • WARNING: One person reports: I had problems using the mini version of DD-WRT v23SP2 on my WHR-G54S. When using the (standard, full) generic version, everything worked fine.

Also, see WHR-HP-G54

WHR-G125 Specifics

It is now possible to revert this unit to factory FW. Please see here for here for revert files

Support for this model is in v24 and later. Do not use earlier versions (like any v23)!

WZR-RS-G54 Specifics

Substitute as the router IP, and as your computer IP in this guide.

WBR-G54 WLA-G54 WBR2-G54 WBR2-G54S specifics

See Flash Your Buffalo WBR-G54, WLA-G54, ... also includes WBR2-G54, WBR2-G54S

Flashing WHR-G300N

See WHR-G300N

Flashing WHR-HP-AG108

See WHR-HP-AG108

More detailed flashing instructions under Windows

Vista Users: Go into Control Panel, Programs, turn Windows Features on of off, check "TFTP Client".

The computer you are using, and the router you are resetting, must be close to each other: so it is possible to have one hand on the enter key of the computer, and the other holding the power plug of the router, and able to put it in the wall or power outlet.

  1. It's good to now reset to factory defaults by holding the reset button while plugging in the router. Hold for at least 30 seconds. Unplug the router. This makes sure the router is in its 'factory fresh' state.
  2. Unplug the router. Usually, preparing by leaving the connection to the router, and unplugging the router from the wall or power cord, is the easiest way.
  3. A non-XPSP2, third-party firewall, may interfere with tftp's ability to talk to the router. It may be useful to disable any third-party firewalls now.
  4. Either:
    1. Your computer should be connected directly to one of the LAN ports on the router. (You can use a regular cable or crossover).
    2. Or if you have a larger network, the computer is connected to a switch, and then to the router LAN port. The router's power cord still needs to be within reach while you are at the computer.
      Reference Image
      Reference Image
  5. For Windows XP, the following reference image should help. After selecting "Internet Protocol (TCP/IP)," click on the Properties button to open the next screen. Enter the info as shown, an IP address of, a subnet mask of, and click 'OK'. Leave Default Gateway blank.
  6. Make a copy of the firmware file, call it 'ddwrt.bin', and put it in your user folder. For instance, "C:\Documents and Settings\yourusername".
  7. Open a command window, by using Start->Run->"cmd". Enter 'ping -t -w 10'.
    1. The router is pinged continuously from the computer, letting you know when to send the firmware.
  8. Open up a second command window, and leave the first where you can see the ping results.
  9. Without pressing Enter, type tftp -i PUT ddwrt.bin Do not press enter yet. Keep this second command window in the foreground, so all you have to press is the Enter key to send the firmware.
  10. With the power cable to the router in one hand, and the other hand on the Enter key, plug the router in while watching the first command window. When ping replies from begin, press the Enter key.
    1. Some people have found that they have better luck if you plug in the power cable for the router first, then wait a few seconds until you see the red "DIAG" light come on the front of the router. As soon as you see that, you'll want to press Enter to immediately start the TFTP transfer.
  11. All port LEDs will illuminate.
  12. The LED on the LAN port will flash rapidly for about 6 seconds. The TFTP command will complete with a success printout, like Transfer successful: 3502080 bytes in 5 seconds, 700416 bytes/s. Leave the router ALONE at this point!
  13. The router will reboot and then boot DD-WRT.
  14. At this point, the router is ready to use. There is no need to reboot it (unplug/plug).
  15. You can reconfigure your network interface on your computer to use DHCP. The computer pulls an IP address and network information from the router. Access the router via
    1. (For the WB2-G54 and some WHR-G54S models, the router may still be accessible at
  16. The user name is 'root' and the password is 'admin'.

Unplugging router can cause media detect network cards to show no media, ie "Network cable disconnected." When you start the tftp and plug the router in, the NIC doesn't detect media until after the tftp flash window has passed, so 60 seconds later tftp times out and the router boots normally. If so, don't unplug the router. Get your tftp ready, hold down the Init (Reset) button on the router, with the Init held down and the Diag blinking, start tftp and immediately release the Init button. You'll never get the 'Cable Disconnected' errors, and it should flash right up.

If you experience timeouts with TFTP

***If you are still having trouble with timeouts, etc., you may want to try using the TFTP client from Linksys. Be sure to set it to retry at least three (3) times. Five (5) would be a safe number to start with. Connect power while holding the reset button till the red diag button begins to blink, release the reset button and hit the Upgrade button on the Linksys TFTP Utility. For WHR-HP-G54 I had to flash through a switch with Windows or suffer timeouts trying.***

I tried several time on Windows XP. The result is always a timeout. Disabling Media Sense feature of Windows XP, I finally succeeded. How to disable Media Sense feature of Windows.

On Windows Vista, I used the Linksys TFTP utility and had to upload the micro version first. The mega version would never complete in time. After successfully uploading micro, I was able to login to web-based admin and perform an upgrade to mega.

One other way to prevent a timeout is to first set the NIC to 10 Mbit half duplex.

A script-method-flash-method in Windows

  1. Save the script below to a file named "install.cmd" (without quotes), and put the firmware file in the same folder.
  2. Run it.
  3. Follow the directions.

@echo off

echo ============================================================================
echo Type or paste the firmware filename below and then press Enter.
set /p dd-wrt_fn=Firmware Filename: 
if not exist %dd-wrt_fn% goto FNF_ERROR

echo ============================================================================

echo This batch file will upload %dd-wrt_fn% in the current
echo directory to during the router's bootup.
echo * Set your ethernet card's settings to:
echo      IP:
echo      Mask:
echo      Gateway:
echo * Unplug the router's power cable.

echo Press Ctrl+C to abort or any other key to continue . . .
pause > nul

echo * Re-plug the router's power cable.

echo ============================================================================

echo Waiting for the router; Press Ctrl+C to abort . . .

ping -n 1 -w 50 > nul
if errorlevel 1 goto PING

echo tftp -i put %dd-wrt_fn%
tftp -i put %dd-wrt_fn%
if errorlevel 1 goto PING


echo ============================================================================

echo * WAIT for about 2 minutes while the firmware is being flashed.
echo * Reset your ethernet card's settings back to DHCP.
echo * The default router address will be at

goto END

echo ============================================================================

echo ERROR: Make sure this batch file and the firmware are in the same directory!


Linux, OS X or other OS: TFTP flashing

  1. Obviously, be sure to observe the aforementioned procedures:
    • Disable your wireless adapter so that the tftp connection is not through a wireless connection.
    • Connect directly to the router using a wired connection (i.e. ethernet cable). Make sure you are connected to one of the four LAN ports and not the WAN port.
    • Download a copy of these instructions so that they are available to you during the procedure.
    • Most importantly, review all of these procedures before attempting them.
  2. OS X specific instructions:
    • Open up system preferences and select the network preference pane
    • Under the TCP/IP tab select from the drop down menu next to Configure IPv4 manually
    • Type in for the IP address
    • Type in for the Subnet mask
    • Type in for the router
    • Click Apply Now
  3. Change to the directory that you downloaded the dd-wrt.v23_mini_generic.bin file into. At least in Mac OS X, tftp fails to resolve either absolute or relative paths. It is simply better to cd to the directory that contains the dd-wrt.v23_mini_generic.bin file before launching the tftp app so no path resolution has to happen.
  4. Execute the tftp command and change the mode to binary by typing binary and hitting return/enter.
  5. Execute the trace command so you get feedback.
  6. Execute the rexmt 1 command so tftp will retry to send the file if you don't get the timing perfect.
  7. type in the connect command but don't execute it yet.
  8. copy the following command (ctrl-c or cmd-c): put dd-wrt.v23_mini_generic.bin.. You don't want to hit return yet, because you're going to do this when the timing is right.
  9. Now that you are ready, here we go:
    1. Plug in the router
    2. When the router is plugged back into power, all of the LEDs on the ethernet ports will turn on.
    3. Once the LEDs turn off on all ports except the connected port, hit enter on the connect command, then immediatly paste (crtl+v or cmd-v) the PUT command into the terminal and hit enter.
    4. The terminal will return with the number of bytes sent and the time that the transfer took in seconds.

Here is a recap of all the commands:

$ cd /path/to/dd-wrt.v23_mini_generic.bin/directory
$ tftp
tftp> binary
tftp> trace
tftp> rexmt 1
tftp> connect
tftp> put dd-wrt.v23_mini_generic.bin

OS X timing tip: Open the network preference pane and select "Network Status" under the "show" pull-down menu. When the router is unplugged the dot next to "Built-in Ethernet" will be red. Now plug in the router and watch for the "Built-in Ethernet" dot to turn green. As soon as it does, execute the connect and put commands.

Linux: Alternatives and Troubleshooting flash procedures

  • Within tftp, you may be able to execute multiple commands using the '&&' operator.
  • You may be able to use the following one line command:
tftp -m binary -c put dd-wrt.v23_generic.bin 
  • Be sure to remember to use for the WZR-RS-G54 router.
  • Make sure you are in the directory containing the DD-WRT binary before entering tftp.
  • If tftp fails, try atftp (available in portage for Gentoo and repositories for Debian, Ubuntu, and probably others.) With atftp, the "binary" and "rexmt 1" commands are unnecessary.
  • If the above does not work, try issuing the "put" command before powering the router. The command will retry and begin as soon as the connection is established. Finding the right timing is everything.
  • Try also holding the router's INIT button, starting the "put" command, then releasing the button.

More Troubleshooting tips

  • If you experience problems a network switch connected between the Buffalo and your PC may help.
  • If you experience problems, you may need to erase NVRAM by starting a telnet session and entering one (or both?) of the following options:
  • Option 1 :
mtd erase nvram
cd /tmp
chmod a+x /tmp/
nvram commit
  • Search for posts in the forum containing "WHR-G54S" and the problem you are having.

De-bricking (unresponsive)

  • Forums, search for "WHR-G54S bricked". There are enough debricking threads, you don't need to start your own.



See DIR300


See Dir-330


In order to flash your router you need to do the following steps:

  • Download TFTPserver, it can be downloaded from here
  • Download firmware from here
  • Download Putty client or you can use any telnet clients(try to stay away from Windows built in telnet)
  • Change your local IP adress to a static and subnet mask to
  • Connect an ethernet cable between your computer and DIR-400's WAN port
  • Prepare Putty telnet session -- port 9000
  • Start pinging your router throught a command line. Type ping -n 900 (You don't really need to ping that many times)
  • Power DIR-400 router on and wait for 2nd successful ping and then initiate putty telnet session.
  • Press CTRL-C as soon as you see that boot script is executing (if you are using Putty ver. 0.60 or newer then you don't have to worry about this)
  • Start TFTP server with linux.bin in TFTP root directory

If you did everything right then you should see the following on the window of putty:

== Executing boot script in 1.140 seconds - enter ^C to abort

Type ip_address -l -h and press Enter

You should see the following:

RedBoot> ip_address -l -h
IP:, Gateway:
Default server:

Type fis init and then

RedBoot> fis init
About to initialize [format] FLASH image system - continue (y/n)?

Type y and press Enter. Wait until the process is complete:

About to initialize [format] FLASH image system - continue (y/n)? y
*** Initialize FLASH Image System
And a descriptor for the configuration data size = 10000
... Erase from 0xbffe0000-0xbfff0000: .
... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .

Type load -r -b 0x80041000 linux.bin and press Enter

RedBoot> load -r -b 0x80041000 linux.bin
Using default protocol (TFTP)
Raw file loaded 0x80041000-0x803bafff, assumed entry at 0x80041000

Type fis create linux and press Enter (this one will take a while. DO NOT UNPLUG YOUR ROUTER)

RedBoot> fis create linux
... Erase from 0xbfc40000-0xbffba000: ........................................................
... Program from 0x80041000-0x803bb000 at 0xbfc40000: ........................................................
flash_addr = 0xbfc40000
mem_addr = 0x80041000
entry_addr = 0x80041000
length = 0x37a000
img_size = 0x37a000
... Erase from 0xbffe0000-0xbfff0000: .
... Program from 0x80ff0000-0x81000000 at 0xbffe0000: . 

Type fconfig and press Enter

RedBoot> fconfig 
Run script at boot: true 

Press Enter

Run script at boot: true
Boot script:
.. fis load -l linux
.. exec
Enter script, terminate with empty line

Type fis load -l linux and press Enter

>> fis load -l linux

type exec and press Enter

>> exec

just press Enter

Boot script timeout (1000ms resolution): 2 

press Enter

Use BOOTP for network configuration: false

press Enter

Gateway IP address: 

press Enter

Local IP address: 

press Enter

Local IP address mask:

press Enter

Default server IP address: 

press Enter

Console baud rate: 9600 

press Enter

GDB connection port: 9000 

press Enter

Force console for special debug messages: false  

press Enter

Network debug at boot time: false 

press Enter

Update RedBoot non-volatile configuration - continue (y/n)? 

type y and press Enter

Update RedBoot non-volatile configuration - continue (y/n)? y
... Erase from 0xbffe0000-0xbfff0000: .
... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .

Type reset and press Enter

RedBoot> reset
  • Re-connect an ethernet cable between your computer and DIR-400’s LAN port
  • Change your local IP adress to a static and subnet mask to

Your router will be accessible at

Gateworks Avila Network Processor GW2348

Please note: The details in these instructions apply specifically to the GW2348-4 board.

If you are using a GW2348-2 or GW2347 there are subtle but important differences in the flashing commands you must use. See the

file FLASHING.TXT for details.

The Gateworks GW234x series Network Processor boards provide an excellent platform for building high performance wireless networks using DD-WRT firmware. They are well built, flexible, and relatively much lower in cost than most commercial alternatives.

For more information see: Avila Gateworks GW234x

Installing DD-WRT on the GW2348 board is relatively simple. To install the firmware you will need the following tools:

  • Computer (I use a laptop with wireless internet connectivity as well as an ethernet port)
  • DC power supply (12 to 24 V, 1 A)
  • Coaxial power plug (2.5 mm x 5.5 mm available from Radio Shack)
  • 9 pin serial cable
  • Ethernet cable

Before you begin you will need to download and install some tools unless you already have them. If you don't already have one, download a TFTP server for your computer. I use TFTPD32 which is free and works quite well. You will also need a terminal program to communicate with the GW2348 over its serial port. I use Hyperterminal which comes with Windows XP but you can use another if you wish. What is important is that you configure it with the following settings:

  • Speed: 115200 Baud
  • Parity: None
  • Data Bits: 8
  • Stop Bits: 1
  • Flow Control: None

Image:gw2348-4 firstboot tools4b.pngImage:gw2348-4 firstboot tools2.png

You will also need to download a copy of the firmware from the DD-WRT Downloads section of the website. The firmware is (as of this writing) located under the beta subsection in a directory called AVILA GATEWORKS. The first file you should get is flashing.txt which describes, albeit in very abbreviated terms, the essential information required to complete the process of flashing DD-WRT firmware onto the GW2348 board. Next, choose the build that you are comfortable with (generally the most recent) and download root.fs and zimage. These two files should be saved in the TFTP Root directory you created when you installed TFTPD32. For the purposes of these instructions you will not need to download the file gateworx-firmware-squashfs.bin as we won't be using it. While you are on the DD-WRT website, visit the online store and purchase an activation key for the GATEWORKS firmware.

When all the files have been downloaded and installed as needed in the computer it is time to set up the computer to connect to the GW2348 board. Plug the serial cable between the serial port on the computer and the serial port on the GW2348. Connect the ethernet cable between the ethernet port on the computer and the eth0 port on the GW2348. The eth0 port is the one closest to the power connector on the GW2348. Next, open the Windows control panel and go into the network connections page. Select the local area connection item that corresponds to the ethernet adapter you connected to the GW2348. Manually configure the TCP/IP settings of this ethernet adapter as follows:

  • Manually Specified Address (no DHCP)

Remove any reference to a GATEWAY address as well as references to DNS servers on this adapter's configuration.

You are now ready to power up the GW2348 for the first time. To do this you will need to connect your 24 volt DC power supply to the coaxial power connector so that the negative (-) terminal of the supply is connected to the outer sleeve of the connector and the Positive (+) terminal is connected to the center conductor. Remember to start up Hyperterminal (or your terminal package of choice) with the settings shown in the image above. Plug in the power to the GW2348 and turn on the power supply. If no smoke comes from the board the ethernet port lights should flicker and then come on. At about the same time Windows should report that the ethernet port is connected at 100 Mb/s and text should start to appear on the Hyperterminal screen looking something like this:

+No devices on IDE controller 0

Trying NPE-B...success. Using NPE-B with PHY 0.
Ethernet eth0: MAC address 00:d0:12:xx:xx:xx
IP:, Gateway:
Default server:

RedBoot(tm) bootstrap and debug environment [ROM]
Gateworks certified release, version 2.02 - built 05:22:19, Mar  3 2006

Platform: Gateworks Avila GW234X (IXP42X 533MHz) BE
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
Copyright (C) 2004, 2005 Gateworks Corporation

RAM: 0x00000000-0x04000000, [0x000298b0-0x03fc1000] available
FLASH: 0x50000000 - 0x51000000, 128 blocks of 0x00020000 bytes each.
== Executing boot script in 2.500 seconds - enter ^C to abort

After a couple of seconds (2 and 1/2 to be exact) the text will continue scrolling by. When it is finished open a web browser and type in the URL This should give you a basic web page from the embedded copy of Linux that is running on the GW2348. If you have gotten this far you have a working GW2348 and are ready to flash in a copy of DD-WRT. be sure to start up the TFTPd32 program with both the root.fs and zimage files in the tftpd root directory. Remember to set the TFTP server address to This is easiest to do while the GW2348 is still turned on and the ethernet port is active. Image:Gw2348-4 firstboot tools3.png Unplug the power (or switch off the supply) to the GW2348 and then make sure that the Hyperterminal program is running. Also bring up a text editor such as "Notepad" and open the flashing.txt file you downloaded from the DD-WRT website when you were downloading the DD-WRT image files. You will be referring to this file during the next phase of the process and will probably be copying and pasting lines from it into the Hyperterminal window since this will save a lot of tedious typing and will likely reduce thechances of making an unfortunate error.

It's time to begin the flashing process in earnest now. Here goes nothing... Plug in the GW2348 power supply while watching the Hyperterminal Window. When you see the line:

== Executing boot script in 2.500 seconds - enter ^C to abort

you have 2 and one half seconds to hit CTRL-C. When you do you should see a prompt that looks like this:


At this prompt enter the line:

fis init -f

The GW2348 will respond with:

About to initialize [format] FLASH image system - continue (y/n)?

As long as you are ready to continue enter a Y to get the following response:

*** Initialize FLASH Image System
... Erase from 0x50080000-0x50fe0000: ...............................
... Unlock from 0x50fe0000-0x51000000: .
... Erase from 0x50fe0000-0x51000000: .
... Program from 0x03fe0000-0x04000000 at 0x50fe0000: .
... Lock from 0x50fe0000-0x51000000: .

Enter the following line: (you may want to refer to the flashing.txt file for this and subsequent lines to enter since they could change in future builds)

load -r -v -b 0x00800000 zImage

At this point you will find out for sure if your TFTP server is working correctly. If it isn't you will get something like this:

Using default protocol (TFTP)
__udp_sendto: Can't find address of server
Can't load 'zImage': some sort of network error

When I got this message it was because I had forgotten to set my TFTP server to use as its address so it was not seeing the TFTP request coming from the GW2348. I changed the setting and then the reply coming from the GW2348 looked like this:

Using default protocol (TFTP)
Raw file loaded 0x00800000-0x00967c93, assumed entry at 0x00800000

This took several seconds as the zimage file was downloaded to the Gateworks board from my computer. After this completes execute the following command:

fis create -b 0x00800000 -f 0x050080000 -l 0x00200000 -r 0x00800000 linux

The response should look like this:

... Erase from 0x50080000-0x50280000: ................
... Program from 0x00800000-0x00a00000 at 0x50080000: ................
... Unlock from 0x50fe0000-0x51000000: .
... Erase from 0x50fe0000-0x51000000: .
... Program from 0x03fe0000-0x04000000 at 0x50fe0000: .
... Lock from 0x50fe0000-0x51000000: .

Then enter this command:

fis create -n linux

You will get a caution message:

An image named 'linux' exists - continue (y/n)? y
* CAUTION * about to program 'linux'
at 0x50080000..0x501e7c93 from 0x00800000 - continue (y/n)? y

The message repeats twice since this is when you are actually overwriting the original version of Linux installed on the board. They really want you to be sure and it is wise to reread your command line to be sure that you aren't doing something stupid... but forge ahead... The GW2348 will respond:

... Unlock from 0x50fe0000-0x51000000: .
... Erase from 0x50fe0000-0x51000000: .
... Program from 0x03fe0000-0x04000000 at 0x50fe0000: .
... Lock from 0x50fe0000-0x51000000: .

Now it is time to TFTP in the second file (root.fs):

load -r -v -b 0x00800000 root.fs

If all is working well the response should look something like this:

Using default protocol (TFTP)
Raw file loaded 0x00800000-0x00d13fff, assumed entry at 0x00800000

When the loading of the root filesystem is complete (it will take a few seconds because it is a large file) you will create several files The first looks like this:

fis create -b 0x00800000 -f 0x050280000 -l 0x00D20000 ramdisk

The response from the GW2348 will look like:

... Erase from 0x50280000-0x50fa0000: ...............................
... Program from 0x00800000-0x01520000 at 0x50280000: ...............
... Unlock from 0x50fe0000-0x51000000: .
... Erase from 0x50fe0000-0x51000000: .
... Program from 0x03fe0000-0x04000000 at 0x50fe0000: .
... Lock from 0x50fe0000-0x51000000: .

Programming this block of the flash memory takes quite a while because it is a very large file. You will now do two more similar commands that will execute in exactly the same way but will finish much faster. They are:

 fis create -b 0x00800000 -f 0x050FA0000 -l 0x00020000 mampf


fis create -b 0x00800000 -f 0x050FC0000 -l 0x00020000 nvram

When these are done we will run the fconfig utility at the RedBoot> prompt. The GW2348's output is shown in regular type. Your entries are shown in italic:

RedBoot> fconfig
Run script at boot: true
Boot script: 
.. fis load ramdisk
.. fis load zimage
.. exec
Enter script, terminate with empty line
>> fis load linux
>> exec
Boot script timeout (100ms resolution): 25
Use BOOTP for network configuration: false
Gateway IP address: 
Local IP address:
Local IP address mask:
Default server IP address:
Console baud rate: 115200
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
Default network device: npe_eth0
Update RedBoot non-volatile configuration - continue (y/n)? y
... Unlock from 0x50fe0000-0x51000000: .
... Erase from 0x50fe0000-0x51000000: .
... Program from 0x03fe0000-0x04000000 at 0x50fe0000: .
... Lock from 0x50fe0000-0x51000000: .

Many of these values will be automatically filled in. You only need to backspace and edit to change them. Otherwise you can simply hit enter for the next line. when the computer pauses on a blank line that needs to remain blank such as the gateway address just hit enter to proceed to the next line. When you have finished and are at the RedBoot> prompt you are ready to reboot the GW2348. Before you do this you will need to make a few changes in your computer configuration. First, shut down the TFTP server. You won't be needing it. Then open the control panel and go back to the network connections page and change your IP address on the ethernet adapter from to Now, start up a web browser and type in the URL but don't hit enter just yet... Unplug the power to the GW2348 and repower it. Wait about 30-45 seconds then hit enter on the web browser. You should get a page that looks a lot like the one shown below:

Image:Gw2348-4 firstboot registration 1.png

If you have gotten this far successfully you have done the hard part. All that remains is to register the board using the web based registration server at DD-WRT. It might be a good time now to copy that big system key that is on the web page to the clipboard. After doing that, start up a second browser (here is where having that wireless internet connectivity comes in handy) and browse back to the DD-WRT website and go to the DD-WRT shop where you will need to log in with the email address and password you used when you bought your activation key. When you go to My Account you will see a link to the Activation Center at the bottom of the page. click on it and you will be taken to a page where you can paste in that hairy long system key from the clipboard and generate an activation key that you can take back to the first browser and paste into the available space as shown below:

Image:Gw2348-4 firstboot registration 3.png

When you press the activate button the board will reboot and you may have to restart your browser to get it to display properly but you should get the familiar DD-WRT main screen. The username and password are "root" and "admin" just like other DD-WRT versions. You can now power down the board and install up to four mini-PCI radio cards and start to have fun. Remember though that if you are using high power cards you will need a power supply with adequate voltage and current.

LaFonera (en)

See LaFonera Software Flashing Page.


Linksys WAP54G

WARNING - DD-WRT was not originally intended to be loaded on a WAP unit. It was found that it will run but it is a tricky unit to load and have function correctly. Below are a compilation of methods/instructions to assist you with creating a DD-WRT loaded WAP unit.



If you really want your WAP to have the correct MAC address when it boots up there are 2 simple but not permanent, and one not so simple but permanent.

Method 1 -

For V1.x only On the Administration>>Commands tab enter

nvram set et1macaddr=<your MAC address minus 1 here> (due to the port swap) (i.e. 00:11:22:33:44:54)

nvram commit

Run then Save as reboot the unit for the new MAC to take effect.

For V2 units - This unit version has a unique motherboard flag and should be recognized as a WAP on the Status tab.

For MAC alterations on a V2.0- V3.x - follow the same step above except substitute the et1macaddr with et0macaddr and don't use the minus 1, use your actual MAC address. (i.e. 00:11:22:33:44:55)

This will need to be re-entered if you do a hard reset (like when doing firmware upgrades).

Example of startup script for a V1:

nvram set et1macaddr=00:11:22:33:44:54
nvram set boardnum=2
nvram commit

Example of startup script for a V2.0:

nvram set et0macaddr=00:11:22:33:44:55
nvram commit

Example of startup script for a V3.X:

nvram set et0macaddr=00:11:22:33:44:55
nvram set WAPver=3
nvram commit

Once the script is run and saved as a startup....power cycle the unit. It should then be recognized as a WAP unit on the status tab.

Method 2 - Works for all WAPs (For V2.0 and V3.X use actual MAC and MAC+1) Extract your CFE, edit in your MAC address, et0macaddr = MAC, and il0macaddr=MAC+1. (For V1.x... Use your MAC-1 for the lan_hwaddr and your MAC for the wan_hwaddr), then put the CFE back on using the HairyDairyMaid or TJTAG utility. This method is risky. You could potentially turn your router into a brick. Once this is reinstalled on the unit and the firmware has been loaded, your unit will have its own MAC addresses permanently embedded and will show every time you boot.

[note] - for the V1s, search for the embedded text string "hwaddr" using your hex editor. This will find the two MAC addresses that are embedded. Again due to the port swap the LAN MAC address needs to be entered as MAC-1 and wan_hwaddr needs to be entered as the MAC for the V1.X only

[note] - my WAP 1.0 required using tftp.exe for the firmware load the first time... my V2.0 and 3.1 required using tftp.exe for the firmware load the first time.

WARNING - Use only VINT-micro firmware builds on v1.x WAP units. If you try to use the standard V24 you will brick the WAP V1.X unit.

For loading firmware on the WAP54G V1.X - Has fixed LED displays starting with V24 RC5. - redhawk

  • Connect PC to LAN port on WAP
  • Configure PC for STATIC IP as Mask, Gateway
  • Press and hold Reset Button on WAP unit for 30 seconds, unplug unit, Plug back in still holding reset button an additional 30 seconds.
  • Open Browser, URL =
  • Login as: Username/Password <blank>/admin
  • Navigate to Administration Tab. Change the DD-WRT xxx_generic.bin file to xxx_generic.trx
  • Upload the new xxx_generic.trx file to the router.
  • Wait 5 minutes after it says it completes successfully.
  • Unplug WAP unit, plug it back in.
  • Press and hold Reset Button on WAP unit for 30 seconds, unplug unit, Plug back in still holding reset button an additional 30 seconds.
  • Now use URL =
  • Go to the Administration>>Commands tab.
  • Enter the following

nvram show | grep boardnum (then click on "Run Commands")

If it returns blank then issue the following commands... if it returns a boardnum=2 then you won't have to.

nvram set boardnum=2
nvram commit

  • Click "Run" button and then: "Save Startup" button. - (only if you had to enter boardnum=2 manually)
  • Power cycle the WAP unit.
  • Check the Status page... it should now display the unit as a "Linksys WAP54G v1.x"
  • Configure as you would any other router.

Power = Power, Diag = Diag or Commit

WLAN - Link LED is now a Radio On/Off indicator, Act = Wireless Activity

LAN - Link = Link, Full/Col = Full, 100 = 100

Thanks goes to Eko for making this unit display correctly.

For loading the firmware on the WAP v2.0 - follow the steps for the WAP v3.x below... except don't include the nvram variable for WAPver=3. The v2 units have a unique board and should be already recognized by the RC5 and later firmware. Eko informed me that there are no special variables needed for the v2 units. [redhawk - 11/16/07]

NOTE: On my V2.0 unit, it has original 2.07 Linksys firmware installed... this FW would not upgrade to DD-WRT. I first downloaded the latest 3.04 FW from the Linksys site and upgraded to it first. Then it would accept the DD-WRT micro_generic build (renamed to .trx extension) directly from the web GUI in the Linksys pages.

If you receive a error message saying "Unable to downgrade firmware" go to, set pull-down menu "DownGrade Header :" to disable and click [apply]. If this setting executed successful you see a message "Your changes have been saved". [ddvelzen - 18/01/08]

WARNING - Use NEWD-Micro build on the WAP v2.0 and 3.X units.

For loading the firmware on the WAP54G v3.X Use V24-RC5 or later for Reset button function

  • Connect PC to LAN port on WAP
  • Configure PC ethernet port to IP:, SM:, GW:
  • Unplug power. Wait 15 seconds
  • Press and hold Reset Button on WAP unit for 30 seconds, unplug unit, Plug back in still holding reset button an additional 30 seconds.
  • Open your favorite browser (I used Firefox) and go to:
  • Login as:

User: <blank>

Password: admin

Hit the Administration tab, and upload the MICRO version of the firmware.

  • Wait 5 minutes after it says it completes successfully.
  • Press and hold Reset Button on WAP unit for 30 seconds, unplug unit, Plug back in still holding reset button an additional 30 seconds.
  • Go to: in your browser and login with the default un/pw for DD-WRT...

[Added by redhawk - 11/16/07]

  • Next go to the Administration>>Command tab
  • Type in: [note] - this is only needed for v3.x WAP units with V24-RC5 and later firmware.

(do not include these next two lines if it is a V2.0 unit...the WAPver variable is not needed except on V3.X units)

nvram set WAPver=3
nvram commit

  • Click on the "RUN" button and then the "Save Startup" button... you want this to run each time it reboots.
  • Reboot the router again then configure.

[Added by lerley - 1/29/08]

I kept getting "upgrade failed" message when trying to update the micro firmware on my WAP54G v3.1 - I ended up doing the following to make it work:

  • Reset as above
  • Upload micro firmware through web interface and get failed message
  • Power cycle router
  • Tftp micro firmware to router (still at as per instructions in Recover from a Bad Flash#Recovering with TFTP
  • When router boots, go to and log in with DD-WRT defaults
  • Go to Administration - Upgrade Firmware and upload micro firmware again
  • Power cycle router

At this point it worked great and I could configure it. Probably still need the nvram stuff as above...

[Added by rfuhrman 19 April 2008]

WAP54v31 hardware, running Firefox on brand new WAP54v31, loading dd-wrt.v24_micro_generic.bin ....on upload completion received "upload failed" message ala 'lerley'. My WAP54 was unaffected, I was still in Admin page, so no need to panic.... Simply switched to IE and ran same exact commands at, perfect upload 1st try. Then I could later use Firefox for finishing the configuration.

So I assume do not use browser of choice, but rather use IE for 1st upload (this is same as suggested for WRT54GL install notes).

[Added by redhawk0 02 March 2009] If you are having trouble reconnecting to your WAP unit after firmware upgrade it could be due to the arp table holding the old MAC address for that unit. Try the trick listed here for tip goes to sprocket87...much thanks.

Linksys WRT54G, WRT54GL, WRT54GS, or WRT54GGX

See Linksys WRT54G/GL/GS/GX page.

Linksys WRT54G-TM and WRT54G-RG

These routers are identical in terms of hardware, but differ in terms of firmware, so you MUST USE THE CORRECT files. The WRT54G-TM was a t-mobile router put out by linksys, and the WRT54G-RG was a Rogers router put out by rogers in Canada.

To Flash the WRT54G-TM


To Flash the WRT54G-RG

  1. Download the CFE_Updater-WRT54G-RG.bin from here:
  2. For the RG Router double check that you got the file with RG in the filename!
  3. Download the TFTP.exe file from here:
  4. Download the svn 12548 NEWD_Mini.bin (NOT NEWD2!) file from here:
  5. Read the peacock announcement here:
  6. Do a proper hard reset on your router, according to the instructions at note 1 of the peacock announcement. Because you do not have dd-wrt firmware on the router at this point, you will not be prompted for a password.
  7. Connect your computer to your router with a lan cable, connecting to a LAN port on the router.
  8. Set your computer to a static IP address of and a subnet mask.
  9. Open your browser window to You should see the linksys webgui. If you don't power cycle your router.
  10. Go to administration, firmware upgrade
  11. Select the file CFE_Updater-WRT54G-RG.bin (the one you downloaded in the first step) and click upgrade.
  13. Change your computer to a static IP of THIS IS VERY IMPORTANT!
  14. Open a command window and try to ping with the "ping -t" command. You should get some timeouts. When you get a ttl=100, wait two more minutes. Keep this window open.
  15. Open up tftp.exe
  16. Select the address of Leave the password blank. Set it to 99 retries and pick the file dd-wrt.v24-12548_NEWD_mini.bin that you previously downloaded.
  17. Hit upgrade.
  18. GO FOR ANOTHER WALK. WAIT AT LEAST 5 MINUTES. Watch the ping window. You should see ttl=64. When you do, wait two more minutes.
  19. Set your web browser to You should see the dd-wrt password page.
  20. Power cycle your router.
  21. Try to open the webgui again a When you can, change your password and user name to anything.
  22. Do ANOTHER Hard reset on the router. Again try to open When you can, you should see the password page again. Now finally set your password and configure your router.
  23. Set your computer back to auto IP and auto DNS.

If you wish to use another build rather than the mini build, you can upgrade with the webgui, following the instructions at note 1 of the peacock thread. This router will take any generic build.

Please note that there is no way to go back to Rogers firmware on this router without a jtag cable and a stock rogers wholeflash.

Linksys WRT54G2

See Linksys WRT54G2 page.

Linksys WRTSL54GS

See Linksys WRTSL54GS page.

Linksys WRT150N

1. Read Note 1 of the peacock announcement

2. Read Note 3 of the peacock announcement

3. Download svn 12548 NEWD_Mini.bin (NOT NEWD2!)

4. Do a HARD reset on your router

5. Plug a cable into the lan port of the router and your computer, and disable any wireless to the computer. Disable all firewalls and virus protection.

(Setting your computer to a static IP should not be required)

6. Set your browser to This will open up the linksys webgui.

7. Go to the administration tab. Click on firmware upgrade.

8. BROWSE to the 12548 NEWD_Mini.bin file you downloaded.

9. Click on the upgrade button and WAIT for the upgrade successful message.

10. Power cycle your router. (very important) WAIT until you can relogin at

11. Do a PROPER HARD 30-30-30 reset on your router (very important) WAIT until you can login at

12. Click on any tab. Reset your username/password by TYPING in a new username/password

You can now upgrade to any generic dd-wrt build except Mega and Micro. Be sure to always to a hard reset prior to flashing another build, do a power cycle followed by another hard reset after flashing, and NEVER re-use a configuration file from a previous build or another router. Reconfigure from scratch.

Linksys WRT300N v1

See Linksys WRT300N v1 page.

Linksys WRT310N v1.0

The WRT310N accepts only the mini, standard, and VPN builds; no other versions are supported on this device. Do not even attempt to flash it with the micro (does not support gigabit ethernet so switch will not work for LAN ports) or mega-build (requires 8 MB of flash, WRT310N only has 4 MB), you will end up with a non-responding router or worse, a very expensive brick! Flashing a virgin WRT310N with the default Linksys firmware will require a special "trailed" mini-build to be flashed first. As of May 27, 2009 you should use a build from the BS Broadcom folder with a build date of 5/21/2009 for the initial flash. The name of this file specifically is "dd-wrt.v24_mini_wrt310n.bin". You may proceed to flash it with a generic STD or VPN build next. Remember to do the 30/30/30 Hard Reset after every successful flash. It is absolutely essential.

The proper process for flashing is found at note 1 of the peacock announcement:

You can download the mini310N.bin firmware from this folder:

Recovery information available in this thread.

Linksys WRT350N

See Linksys WRT350N page.

Linksys WRT600N v1 and 1.1

See Linksys WRT600N page.

Linksys WRT610N v1 WIP

See Linksys WRT610N page.


Microsoft MN700

  • See MN-700 Page - summary of steps include:
    • Similar to Asus Deluxe.
    • First perform MN-700 hack to enable Linux-based firmware to be installed.
    • Install DD-WRT firmware using Asus Recovery Utility in recovery mode
    • Clear filter_services variables if necessary (SP2 and earlier)

v23 SP2 and earlier work but require filter_service NVRAM variables to be cleared and reset button does not work.
Full support in SVN 3949+ (you can get SVN 3953 here)

Mikrotik Routerboard RB/532

Mikrotik Routerboard RB/532 is supported starting with DD-WRT v23 SP1. See Mikrotik Routerboard RB/532.


Mitsubishi R100 Gateway

The Mitsubishi R100 is a relabeled Asus WL500G that is only available in Australia. As such, you can use the Asus tools on the Mitsubishi product. The R100s are usually found at lower prices compared to the Asus product. They also come with a three year warranty. Obviously, flashing with a third-party firmware voids this warranty.

Motorola WR850G

See Flash Your Motorola WR850G


Netgear WGR614v8/L/WW

Initial flash of DD-WRT firmware is done though Netgear update GUI using a device specific .chk file

If the firmware you are loading is before svn11600 then you will need to update the firmware using this file first before upgrading to a newer build. After the initial .chk flash (after svn11600) any generic .bin file can be used to upgrade firmware to the router using the DD-WRT Firmware update tab.

These are the notes provided by Eko.

Files listed are located here


Flashing Netgear WGR614v8, WGR614L, WGR614WW

For first flash (running original Netgear's firmware) or for tftp please use dd-wrt.v24-11604_NEWD_mini_wgr614v8-L.chk file.

For upgrade when already running DD-WRT (IMPORTANT!):

- if your DD-WRT build is less then 11600 please use dd-wrt.v24-11604_WGR614v8-L_mini.bin file. Then you can upgrade to any build listed below.

- if your DD-WRT build number is greater then 11600, you can upgrade directly using any build listed below. Keep in mind that as newer builds come out (higher svn numbers than 11600) they are also compatible.

Compatible builds:

  • dd-wrt.v24-11604_NEWD_mini.bin
  • dd-wrt.v24-11604_NEWD_mini_hotspot.bin
  • dd-wrt.v24-11604_NEWD_std.bin
  • dd-wrt.v24-11604_NEWD_std-nokaid.bin
  • dd-wrt.v24-11604_NEWD_std-nokaid_nohotspot_nostor.bin
  • dd-wrt.v24-11604_NEWD_voip.bin
  • dd-wrt.v24-11604_NEWD_openvpn_jffs_small.bin
  • dd-wrt.v24-11604_NEWD_openvpn.bin

Additional wiki information about the WGR614v8 can be found here. Some of this data is outdated but it could still provide to be useful.

Netgear WNR834Bv1

This model (the V1) does NOT have a JTAG header, only serial, so caution must be exercised when working on this unit.

Not much is said about this device other than flash it with a modified header. All information I found was that there was not modified header build for this unit except that which was created by SveaSoft with theire Talisman 1.3.1 package.

So... after much investigation it was found that the firmware needs to be updated in the form of an .img file. Original Netgear firmware was a .img file and would only accept TFTP input or web GUI input of a .img file.

[NOTE] - further investigation proved that the .img file is actually a .zip file. You can rename the .img to .zip and extract the contained WNR834B.bin file. Using a hex editor this .bin file contains both the CFE and FW for the by removing the first byte through the last byte before the HDR0 in the file will leave just the FW of the .bin file... this is a .bin file and CAN be flashed directly to the unit using TFTP.

Also found was that any .bin file can be flashed using TFTP to the unit unless the nvram has been erased using the CFE's "nvram erase" command then it will need flashing with the original .img file again. Once the Netgear FW .img is flashed navigate to the upgrade FW tab and use the 1158_mini build of .img provided below.

I found that Simri created a .img build for this unit and it works very well. The first loading of DD-WRT firmware must be an .img file and can be loaded from the Netgear firmware update tab.

11580_mini build of .img

Hard reset
Load firmware ( with admin/password for un/pw)
wait 5 minutes
power cycle router
hard reset again

Subsequent DD-WRT firmware updates can be done from the DD-WRT firmware update page and you can load any .bin file except for the mega build. (I suggest you don't downgrade lower than the 11580 build that you used for the initial flash)

Here is the original Netgear firmware as well for those that want to revert back.

Additional information about this unit can be found here


[NOTE] - if you have DD-WRT on the unit and have the wrong MAC address. You can use another method of obtaining the correct MAC address permanently.

Extract the cfe.bin by using the HTTP backup method (save this file to your disk drive) Edit the cfe.bin file using a hex editor...locate and modify both the et0macaddr and et1macaddr to be the MAC address with that which is found on the sticker of your unit (yes...both et0 and et1 will be that address)....Make sure you do not ADD any bytes to the file (only overwrite current bytes)....if you do add to the will have an unrecoverable brick....guaranteed...remember you only have serial communication and the CFE must work for serial to work.

Then using WinSCP (SSH must be enabled in DD-WRT) copy the newly edited CFE to the unit's /tmp directory. Now you can use a telnet session to mtd the new CFE over the old must have the exact same CFE with only the MAC address's changed for this to work...if you don't you will have an unrecoverable brick...guaranteed.

the commands for overwriting the CFE is

mtd unlock cfe
mtd write /tmp/cfe.bin cfe

When it finishes reboot the router. The correct MAC addresses should now show up on the Status tab.

Thanks to Sparky and Simri for sharing their knowledge of these Netgear units on the forum. redhawk

Netgear WNR834Bv2

(See Important Notes below before attempting to flash)


Do not use bin/chk files from the router database older than svn12188. Currently, they are bricking routers. Once this problem is sorted out, this message will be removed.
Sparkie Updated by redhawk0

The Netgear WNR834Bv2 is now fully supported as of 3rd July 2008. Thanks to Eko, Brainslayer, etc. for their superb work in getting this router supported.

These (slightly modified) instructions were first posted by sparkie here. Read that complete thread for the hairy details on getting this device fully supported, if you are so interested or suffer from insomnia.

Step 1: Download the mini version of DD-WRT version 24, build 12121, new driver in the dot CHK format here.

Step 2: Flash the firmware to your router using Netgear's factory firmware standard web interface. Note that to successfully flash this device, you may need to use IE or Firefox 3 or higher. sparkie has reported in the thread linked above that Firefox 2 will not work with the Netgear factory web upgrade page to flash this device.

Step 3: If the mini build is insufficient for your needs, you may download your preferred flash BIN file from here. Then flash up the new .BIN file using the DD-WRT web interface from the Administration tab, then the Firmware Upgrades tab.

Important Notes (Please read these in full before attempting to flash):

  • DO NOT ATTEMPT TO FLASH ANY BUILDS EARLIER THAN 9856 DATED 3RD JULY 2008, or you risk bricking your router. Some of the v24 release candidate 7s worked with minor bugs. But the first final v24 bricked the router for some users as a result of a problem with JFFS.
  • TFTP flashing only works when the router detects a bad flash and puts itself in diagnostic mode. This can be seen by a flashing green power light, and also a ping trace will show response immediately after powerup with TTL=100. Proper flashes will stop replying to pings after about 15 seconds, then will reply with TTL=64. Diag mode will stay at TTL=100. Diag mode can be forced by opening the router and shorting pins 16 and 17 on the MX flash chip during powerup. Some suggest you try the pin short first, other suggest JTAG. Both have their pros and cons.
  • TTL=100 3~6 times means your router is bricked. No amount of uploading an image via tftp at the proper time will work. It will require a pin short, or jtag to fix. It is futile to try and achieve perfect timing to upload an image in this mode.
  • NEWD = New Drivers; VINT = Vintage Drivers. Use only NEWD firmwares with this router. VINT builds are for much older routers.
  • DO NOT INSTALL the generic broadcom dd-wrt.v24_std_generic.bin file (2.4 SP1). It will likely brick your router.
  • If your router is stuck in 'tftp only' mode (characterized by a constant TTL=100 ping response), you can rescue it by TFTPing the original Netgear firmware less the header file located here, which will flash your router back to Netgear's stock 1.0.22 North America firmware. This file is called wnr834bv2_1_0_22_na.bin
  • For routers will a more recent flash, you will need the 2.1.13 version of the flashes 2.1.13_NA / 2.1.13_WW
  • Your router has only 4 MB of Flash RAM. Do not attempt to flash the MEGA version of DD-WRT to this device.

DOUBLE SUPER DUPER Extremely Important Note:

According to Eko, the NVRAM of this router has an additional partition on it which contains your router's serial number, MAC address, and board code. DD-WRT builds prior to 9856 would overwrite this section of NVRAM, if the user enabled JFFS. Builds 9856 and higher include support for turning JFFS on with this model router. In the event that you accidentally erase this part of the NVRAM, you can only recover your router by flashing it via JTAG.

This also implies that if you want to use the OpenVPN version, you'll want one with an openvpn_jffs_small suffix like THIS one (current as of 15/5/2009).

WNR834Bv2 JTAG Pinout:

J12 Pin 1 connected to JP1 pin 1 via 100 ohm resistor. 

J12 Pin 3 --100r--> TDI (Pin 2 of parallel port) 
J12 Pin 5 --100r--> to TD0 (Pin 13 of parallel port) 
J12 Pin 7 --100r--> to TMS (Pin 4 of parallel port) 
J12 Pin 9 --100r--> to TCK (Pin 3 of parallel port) 
J12 Pin 10 -------> to GND (Pin 20&25 of parallel port)  

  • Functional NVRAM backup is here.
  • Functional CFE backup is here.
  • Functional Custom backup is here. (REQUIRES MODIFICATION OF MAC ADDRESS)
  • Tornado's JTAG v2.1.4 is here.


One of the best threads that has been found for debricking the WNR834Bv2.

The fastest way to recover a bricked WNR834Bv2 is to wipe the kernel portion of the flash, and reflash the custom section.

  • 1. Download one of the binpacks WNR834Bv2 World Wide. WNR834Bv2 North America, and the custom.bin
  • 2. JTAG the router
  • 3. Erase the kernel portion of the flash
  • 4. Reflash the 'custom' section of the flash (hex edit the custom.bin and put your own MAC address in at offset 40~45!)
  • 4a. flash parameters: -flash:custom /window:1fc00000 /start:1ffe0000 /length:10000
  • 5. Power cycle the router and the router will respond with a constant ttl=100 ping response
  • 6. TFTP a dot CHK file appropriate to your router (NA or WW)
  • 6a. You will know that the transfer was completed and the flash process is working when router power light blinks amber on and off once per second. After a few minutes, the router will begin to respond with a ttl=64 ping and will be functional again.


  • Pin Locations.
  • Short pins 16 & 17
  • Power up router
  • Open two command prompt/console windows
  • Start a ping of the router, it should respond with TTL=100
  • Initiate TFTP upload of a .chk file (DD-WRT or one of the stock Netgear ones)
  • Immediately remove the short
  • You will know that the transfer was completed and the flash process is working when router power light blinks amber on and off once per second. After a few minutes, the router will begin to respond with a ttl=64 ping and will be functional again. (Yes, it actually does take 2~3 minutes)


Many of the factory refurb WNR834B v1 and v2 routers sold in 2008 through,,, and were shipped with a marginal or defective power supply manufactured by DVE. These units are smaller than traditional power supplies, and can be identified by the following information:

P/N: 332-10006-01

MODEL: DSA-12R-12 AUS 120120

The routers will operate perfectly with only 9VDC @ 800mA, but older-style surplus Netgear power supplies that output 12VDC @ 1A are available from as DCTX-1216

Netgear WNDR3300

Initial flash of dd-wrt firmware can be done though Netgear factory firmware GUI using a device specific .chk file

Just get this .chk file (as of 2009, May First) and use Netgear GUI to upload to your router. All done.

Few things I noticed so far.

- You can try but std never worked for me so far.

- If you brick it (green power light keeps blinking), unbricking is easy. Just use tftp to upload above .chk or factory firmware. (tftp info here)

These are the notes provided by Eko.

Files listed are located here


Flashing Netgear WNDR3300

For first flash (running original Netgear's firmware) or for tftp please use dd-wrt.v24-12030_NEWD_mini_wndr3300.chk file.

If you need additional info WNDR3300 is discussed here.

Siemens SE505

DD-WRT v23 (starting from 27/10/05 version) does now officially support the Siemens Gigaset SE505 router. That means you can use the very latest features like WPA2 on this unit too. Due the limited RAM of this unit, you cannot use all features at the same time, but from the base it is much better than the original firmware for this router.

Flash Your Siemens SE505

Related Links

Ubiquiti Litestation 2 (LS2/LS5/PS2/PS5/NS2/NS5/LSX)

Upgrading Ubiquiti LS2 to DD-WRT v24 (the same procedure works for other Ubiquiti products as well, just the files and filenames are different)


   * Direct ethernet cable connection between PC and LiteStation
   * Network settings of PC:
   * TFTP client on PC
   * LiteStation firmware file (e.g. LS2.dd-wrt.bin for LiteStation2)

Flashing procedure:

   1. Please ensure that the latest firmware revision of Ubiquiti is already installed using the web upgrade utility (e.g.V 2.1.9)
      If not, please reflash it using the Ubiquiti LS2 web interface. This is important to ensure that the latest RedBoot bootloader
      is installed.
   2. power off the device and power it on again while holding the reset button for about ~10 seconds
   3. flash LS2.dd-wrt.bin using tftp to in binary mode

Windows  : tftp -i put LS2.dd-wrt.bin Linux/Unix/MacOS X: tftp

                           tftp> bin
                           tftp> put LS5.dd-wrt.bin
                           tftp> exit
   4. after successfully flashing the unit will be accessible with web on