DD-WRT FAQ
Frequently asked questions about DD-WRT Firmware
What are the Advantages of DD-WRT over other Firmware?
DD-WRT has a “micro” version with a smaller set of options from standard version, but still much more than factory versions. The micro version can be installed on a wide range of Routers (See Supported Devices) with 2 MB Flash. All versions of DD-WRT have the “Repeater Bridge” mode, which allows you to easily expand your network using a second wireless router. No need for WDS with this function. The router connects like a wireless client, secured using the SSID key, so you get full Bandwidth, where WDS only uses (disputed by some) 50% of available wireless bandwidth. With two wireless Routers in use, you may want to have systems connect to the second router specifically. Another great DD-WRT option is the “Virtual Interface”. A unique SSID for the second router. DD-WRT has a large community of users and developers. A large Forum, and an excellent Wiki
What are the disadvantages of DD-WRT?
Depending on your point of view, the sheer mass of posts in the DD-WRT Forum can be viewed as a sign of problems, or very popular Firmware. Unlike Tomato and other types of Firmware, DD-WRT makes Alpha and Beta (RC) code available for anyone to use, as a way to test the wide range of supported router models. Based on my experience with DD-WRT, this practice creates two problems:
- Not setting User Expectations for Development Code
- Lack of Standards for Download Directories and Naming Conventions for all Releases
DD-WRT developers release Alpha and Beta (RC) Builds almost daily. Developers are focused on coding, not on organization and communication. I don’t mean that in a bad way, they are brilliant at what they do. Each Developer has their own style, with different build directory and naming conventions. This adds confusion to which builds can be used on which router. Each build has unique set of issues. Of course, with so many builds, the forum explodes with requests. If you don’t follow DD-WRT weekly, you will easily get lost. DD-WRT relies on the community for testing, so its not fair for me to call problems with Alpha and Beta builds a disadvantage, I am not. What I am saying is there is a disadvantage to making test builds available to a wide range of platforms without setting expectations for Alpha and Beta Code (that it is not stable, there could be problems, there may be no answer, etc.), and not keeping to some standard for names and directories of available downloads, whether its a stable final release, or an Alpha. The DD-WRT regulars know all this. First time users assume “if its available, its ok”, and take the risk, then complain when there’s a problem. In summary, DD-WRT is a great firmware provided you know that using the Alpha and Beta (RC) builds may cause problems, and that you may struggle for a while to figure out which file to install. This could be solved if DD-WRT had a Project Manager to keep things in order.
What Setup is Best for DD-WRT?
Opinions vary. Some prefer DD-WRT as the Access Point because they need to VPN the entire network, or have no choice because they have a 2mb Flash Router. In my opinion DD-WRT is best deployed as a secondary or use with multiple wireless routers on a network, because of the reasons stated in the Advantages. After 3 years of Beta Testing DD-WRT, Tomato, and X-Wrt on multiple routers, I have formed the opinion that Tomato Firmware should be at the AP, because it has by far the best QoS functionality and throughput of any alternative Firmware. Again that’s my experiences, yours may be different.
Which Routers Support DD-WRT?
Quite a few. See the GazGuzla 4+MB Master Router List, and DD-WRT’s Supported Devices List for 2 MB Routers.
Are there different Versions of DD-WRT Firmware?
Yes. DD-WRT is Free to use, but they also sell Special Editions with Support Here. As stated above in the disadvantages, the Download Directories and Naming Conventions change constantly, what was there yesterday may not be there tomorrow, so its useless to tell you anything more than the basics. You will have to search or post to the forum with further questions. The Free Stable Releases are located Here. The Releases increase in size with options:
- 1.7 MB *micro.bin (Used for routers with 2mb Flash)
- 2.7 MB *mini*
- 2.9 MB *mini_usb*
- 3.4 MB *nokaid*
- 3.5 MB *nokaid_usb*
- 3.6 MB *std*
- 3.6 MB *vpn*
- 3.6 MB openvpn
- 3.6 MB *voip*
- 5.7 MB *mega*
Note: Some of the Releases above may not yet or ever be in the stable area. The *std* indicates naming conventions could be different, so I only put the part of the file name that doesn’t seem to change.
Information about the history of DD-WRT, and the Contents of each Release Type is located Here.
Between Stable Releases, there are Alpha and Beta (RC) builds which each developer makes available. The two main developers locate their builds Here. Beware of VINT and NEWD builds. Improper flash of VINTAGE (older routers) and NEWD (New Driver) can do bad things, including creating a bricked router, requiring JTAG! Information about VINT and NEWD can be found Here. Note that NEWD is written as “normal”.
How Do I install DD-WRT?
See GazGuzla Article. DD-WRT uses a .bin file. Additional information located Here.
How Do I Configure Different DD-WRT Functions?
What is JTAG?
A way to recover a bricked router when you can’t get a response from conventional methods. Requires a JTAG cable, and router specific recovery software. The Cable connects the serial or USB adapter of you PC to the router’s hardware, usually the motherboard. Then using specific software you could recover the router. I have never had to resort to JTAG using the GazGuzla Installing Tomato, DD-WRT, X-Wrt Firmware method, because I don’t use the current firmware upgrade utility, which is many times the source of the problem. The other reason is being sure the firmware is compatible. If you think you need JTAG recovery, use the contact email, I will refer you to somebody that’s done it many times before.
How I Configure and Optimize DD-WRT QoS?
See this Article (coming soon)
Leave a Reply