Note: This guide is for users who have “bricked” their routers while trying to upgrade to dd-wrt v24 rc7 from dd-wrt v24 rc6. For flashing to dd-wrt from the stock firmware, you can refer to the Mini Flashing Guide for DIR-300.

It seems like quite a few users have “bricked” their router while trying to upgrade to the final dd-wrt v24 from rc6. Well, the device have not really bricked, it is just that the name of the flash image has changed and hence the system cannot boot pass the redboot. Not sure if it due to the new firmware, bootp was also switched to on, causing the system to take its own sweet time to get into redboot. It took around 30 to 40 seconds before I could actually telnet in.

Read the rest of this entry »

If you are flashing to DD-WRT v24 RC7. Check out this flashing guide instead.

Similar models: DIR-301

If you are using DIR-400, check out Mini Flashing Guide for DIR-400 instead.

FAQ

The FAQs for Flashing DIR-300 to DD-WRT can be found here

Note: It seems like x will not be represented as alphabet “x” after copy and pasting. Do take note of this.

Required

1. Temporary RedBoot (ap61.ram): Download file
2. ap61.rom, linux.bin from DD-WRT v24 RC4 or newer
3. TFTP Server up and running, ready to serve the required files, e.g. PumpKIN
4. Putty (telnet client) – Chosen because it helps you to Ctrl + C

Getting into RedBoot

1. Connect the network cable to your ethernet port and the WAN port of DIR-300.
2. Configure your System IP address (static) to be 192.168.20.80/255.255.255.0.
3. Hold on to the reset behind the DIR-300.
4. Power on the DIR-300 while holding on to the reset button. Hold the reset button for 30 seconds while it is booting.
5. Release the reset button
6. Telnet to 192.168.20.81 on port 9000
7. You should be greeted by the RedBoot prompt. RedBoot>

Loading in the temp boot loader

RedBoot> load ap61.ram
Using default protocol (TFTP)
Entry point: 0x800410bc, address range: 0×80041000-0x800680d8
RedBoot> go

It is normal to be disconnected from the telnet session.
Note: Do not reboot the router.

Loading a new boot loader
Before proceeding, set your system IP to 192.168.1.2/255.255.255.0 and then telnet to the new address 192.168.1.1, port 9000.

Note: You may need to connect to the LAN port instead of the WAN port on the DIR-300

After you are connected, follow the steps below

DD-WRT> fconfig -i
Initialize non-volatile configuration – continue (y/n)? y
Run script at boot: false
Use BOOTP for network configuration: true
Default server IP address:
Console baud rate: 9600
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
Update RedBoot non-volatile configuration – continue (y/n)? y
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0x80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> fis init
About to initialize [format] FLASH image system – continue (y/n)? y
*** Initialize FLASH Image System
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0x807f0000-0×80800000 at 0xbffe0000: .

DD-WRT> ip_address -h 192.168.1.2
Default server: 192.168.1.23

DD-WRT> load -r -b %{FREEMEMLO} ap61.rom
Using default protocol (TFTP)
Raw file loaded 0×80080000-0x800a8717, assumed entry at 0×80080000

DD-WRT> fis create -l 0×30000 -e 0xbfc00000 RedBoot
An image named ‘RedBoot’ exists – continue (y/n)? y
… Erase from 0xbfc00000-0xbfc30000: …
… Program from 0×80080000-0x800a8718 at 0xbfc00000: …
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0x807f0000-0×80800000 at 0xbffe0000: .
DD-WRT> reset

Your DIR-300 will reset at this point.  Telnet to it (192.168.1.1, port 9000) after it has finish resetting. (approximately 30+ seconds)

Note: You may need to connect to the LAN port instead of the WAN port on the DIR-300

Configuring the Putty Client

1. Right-click on PuTTY Client’s title bar
2. Select “Change Settings…”
3. On the “PuTTY Reconfiguration” window, change close window on exit to Never
4. Click on the Apply button

Loading in the new firmware
It is important that you don’t disconnect the power or ethernet cable for this section. Those fis create commands take quite some time to complete, so do be patient and don’t interrupt the process.

DD-WRT> ip_address -h 192.168.1.2
IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.2
DD-WRT> fis init
About to initialize [format] FLASH image system – continue (y/n)? y
*** Initialize FLASH Image System
… Erase from 0xbfc30000-0xbffe0000: …………………………………………………..
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0x80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> load -r -b 0×80041000 linux.bin
Using default protocol (TFTP)
Raw file loaded 0×80041000-0x803cffff, assumed entry at 0×80041000
DD-WRT> fis create linux
… Erase from 0xbfc30000-0xbffbf000: …………………………………………………
… Program from 0×80041000-0x803d0000 at 0xbfc30000: …………………………………………………
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0x80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> fconfig boot_script true
boot_script: Setting to true
Update RedBoot non-volatile configuration – continue (y/n)? y
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> fconfig boot_script_timeout 4
boot_script_timeout: Setting to 4
Update RedBoot non-volatile configuration – continue (y/n)? y
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> fconfig bootp false
bootp: Setting to false
Update RedBoot non-volatile configuration – continue (y/n)? y
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> fconfig
Run script at boot: true
Boot script:
.. fis load -l vmlinux.bin.l7
.. exec
Enter script, terminate with empty line
>> fis load -l linux
>> exec
>>
Boot script timeout (1000ms resolution): 4
Use BOOTP for network configuration: false
Default server IP address:
Console baud rate: 9600
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
Update RedBoot non-volatile configuration – continue (y/n)? y
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0x80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> fconfig bootp_my_ip 192.168.1.1
DD-WRT> fconfig bootp_my_ip_mask 255.255.255.0
DD-WRT> fconfig bootp_my_gateway_ip 0.0.0.0
DD-WRT> reset

The default username and password are “root” and “admin” (without the quotes) respectively. Enjoy your new DIR-300!

Note: Don’t worry if you can’t get an IP from your modem (through the DIR-300 on DD-WRT). It is a bug of DD-WRT. Do the following steps to resolve it:

1. Disconnect the network (ethernet) cable between your modem and DIR-300
2. Reboot both the modem and DIR-300 and wait until they have fully booted up
3. Connect the network (ethernet) cable between the modem and DIR-300

Note: If you need to change the value of “Run script at boot:” from false to true, use the following command before running fconfig:

fconfig boot_script true

Like to buy shadowandy a cup of Starbucks for his work?

Brainslayer has released DD-WRT v24 pre-RC4 and it supports another two of D-Link’s router, namely – DIR-300 and DIR-320.

He’s kind to enclose this flashing guide. He flash his DIR-300 using console cable while I did mine without one. After skimming through the guide, I would say the process is similar to flash the fonera (which is also based on Atheros chipset + RedBoot). The tricky part would be breaking out of the boot script under 1 second. Nonetheless, I would say the flashing process is pretty safe (after I have flashed so many foneras and routers through RedBoot/Broadcom console)

The usual tools needed would be a tftp server, a telnet client which allows you to send Ctrl+C (hyperterminal on windows would work fine), an ethernet cable and the DIR-300 itself.

Check out the flashing guide

Miscellaneous
The required files: dd-wrt v24 pre-RC4 for DIR-300
My DIR-300 Flash Log: Download file

for (int count = 0; count < 101; count++)
“Reason ” + (count + 1) + “: Because IPKG doesn’t work\n”

Alright I cheated, there aren’t really alot of reasons why I don’t encourage people to use dd-wrt.

Firstly, the IPKG is broken (I only tried V23 SP2 and in V24, it is still broken) hence those who wish to maximise the use of their routers wont be able to do it.

Secondly, getting donations from end users are pretty alright. But selling of GPL derivatives and making a profit out of them is a big no no. Check out their online stores! Exclusive firmwares for those who pay!

Thirdly, the command interpreter is called “BusyBox” and not “Very BusyBox” after changing maybe zero lines of the source code. Google around to find out the spicy news.

Fourth, it is an opensource project and you should list all the contributers. Not take credits. Google for the spicy news again.

Fifth, it isn’t customisable due to the fact that IPKG is broken.

Anymore to add on to my list?

Anyway, seems to take quite a fair bit of stuffs from openwrt.

Further ensure that your hardware is supported by the openwrt firmware. Using the firmware on an unsupported or work in progress hardware could render the hardware unusable! So make sure you check the Table of Hardware Supported.

The webif that come with the stock whiterussians firmware is really a no no. The only reason I could think of why people uses it is they don’t need the web interface.

Download the openwrt whiterussians firmware with x-wrt webif included from the x-wrt page. Then follow the Method #1 of the installation.

Just remember to hard-reset your hardware after all is done to remove unnecessary stuffs from the nvram.

Found out that DD-WRT V23 SP2 doesn’t really suit my purpose. The IPKG is buggy or rather most of the installed package doesn’t work, hence changed the firmware to openwrt. My aim of getting a WRT54G is not to use it as a router. It’s ultimate aim is to work as a dedicated unix box. Was amazed at how people do configuration or administration of servers using command line interface. This WRT54G provided me with a chance to toy with command line interfaces. Best of all, exploring the limits of these embedded devices (hopefully I don’t brick it). Currently installed packages are – nano (using nano as I yet to master VI or VIM), nmap, BitchX, kismet (client and server), and the list goes on.

Just incase you are wondering how come there is so much space on the router. I mapped a share over and did all the installations down there. Edited the startup script to do the mapping of samba share over automatically as well.

Just a piece of advise, after getting the openwrt firmware. Install the x-wrt webif package. It makes web administration easier. Need to allow remote administration through web or ssh or both and cant find the webif configuration page? Just edit the firewall rules to allow listening on the ports.