注意: 現今只有 C1 和 C2 硬體版本有完全支援.
*You might have to change the magic number at the end of the OpenWrt firmware to the one used by the stock DIR-615 firmware to get it to upload.
Frys FR-300RTR is the same as E1 Forum
* 2013 四月 - Version E4 is supported and known to work with attitude adjustment 12.09(link to flash file)) , see installation instruction below
Ubicom & SPI Flash with 2 MB only
Ralink RT3352F SoC, you could try DIR-620 D1 image
大多現代的 Web Browser 在 POST 時會送出 Expect: 100-continue 的 HTTP 表頭(header), 但軔體更新系統 (firmware update system) 不支援此協定. 如果 Web Browser 出這個訊息, 它會等到 server 回覆 100 Continue 才會開始傳送檔案內容.
這個協定開始存在於 HTTP/1.1, 用來讓 server 在檔案傳送前就有機會拒決檔案上傳(而不是等到傳完後). 雖然 Router 的內建 HTTP Server 宣稱支援 HTTP/1.1, 但它永遠不會送出 100 Continue, 以致瀏灠器(Web Browser)永遠在乾等, 到最後 Times out.
Internet Explorer 6,7,8 on Windows is known to work, as well as Firefox 13.0.1 on GNU/Linux, but problems have been reported with newer versions and most other browsers on GNU/Linux. Older versions of Firefox (4.x and below) are known to have problems, several people have been more successful with newer versions. Alternatively, you can use the curl command-line HTTP client like so:
There seems to be some compatibility issues with the firmware update system network stack and at least a Linux 3.5.3 kernel and curl 7.27.0. Even forcing curl down to HTTP/1.0 resulted in a hang. One known working configuration is NetBSD 5.1.2 with curl 7.26.0.
*A use of Firefox 13 portable edition (on windows 7) was verified as successful. Also known that local IP should be 192.168.0.10. Then FF 13 portable also should work.
Same actions(C1 and C2 have same hardware and openwrt image), but to upload openwrt image in recovery mode, you must to edit C1 openwrt image by hex editor.
Just add 30 31 before lastest not zero values:
These use a Ralink chipset that only has preliminary support and requires a manual build. D1/D2 models are known to have problems with the latest ethernet driver(s) and require the use of an older driver. D3/D4 are relatively stable with an unmodified trunk build.
The D4 works well if you treat it exactly the same as a DIR-600/B2
: D1/D2 build instructions
The DIR-615D maps to DIR-300b1 therefore there is no dedicated target for 615-D.
D2 can be flashed with Attitude Adjustment - RC1: openwrt-ramips-rt305x-dir-615-d-squashfs-factory.bin
Problems when flashing with AA RC1 firmware:
ethernet only works when trying to connect over 10baseT/UTP (10mbit/sec)
wireless needs workaround
It is fixed in the recent Attitude Adjustment branch and works out of box. However, if you are using precompiled AA RC1 you will need a workaround: https://dev.openwrt.org/ticket/12636
The only way to get this fully working is to recompile using old ramips ethernet drivers (from revision: 24328)
To do this:
get the desired branch/trunk
navigate to target/linux/ramips/files/drivers/net/ethernet/ramips
5. There could be a problem, that the WAN connection is not automatically configured because the 'wan' interface is not enabled during boot. To fix it:
Variant 1: login via telnet/ssh and type 'ifup wan'; edit /etc/rc.local and add 'ifup wan' there to automatically enable it during boot.
Variant 2: go to luci → System → Startup → 'Local startup' and add line 'ifup wan' before 'exit 0' line in rc.local. Reboot router.
6. There could be serious problems (reconnects, very high packet loss rate) with Intel Wi-Fi Link 1000 BGN Cards on Windows (the factory firmware from D-Link works just well with these cards). To fix it with OpenWrt, download and install latest drivers from Intel web site). Then go to
Network and Sharing Center, open properties of your wireless adapter, then Configure, then Advanced and disable 802.11n mode there.
7. By default the WAN LED is not configured correctly. To fix it:
Go to System → LED Configuration and change the first LED config as follows:
Name: Status LED (green)
LED Name: d-link:green:wan
Default state: unchecked
Device: eth0.2 (you can find this on Network → Interfaces under WAN)
Trigger Mode: All checked (Link On, Transmit, Receive)
8. There could be a regular connection resets. The problem is described here: Ticket, Forum, SuperUser
As of R36213 this router no longer needs a custom build. The following only applies to older revisions.
Requires at minimum a customized /etc/config/network. If you have a working network with DHCP server you can put the following in your /etc/config/network (you have to edit via serial connection for the first time or have a custom build with the modified /etc/config/network):
This documentation refers to current trunk of 03.04.2013.
Instead of using the above procedure, you can build the image following the next steps. It will create a working image with dhcp on wan and fixed ip 192.168.0.1 on lan.
- Download current trunk. I've downloaded it from git mirror:
# Copyright (C) 2012 OpenWrt.org
# This is free software, licensed under the GNU General Public License v2.
# See /LICENSE for more information.
kmod-usb-core kmod-usb-ohci \
kmod-usb2 kmod-ledtrig-usbdev \
usb-modeswitch usb-modeswitch-data \
Package set for DIR-615 H1
$(eval $(call Profile,DIR615H1))
- edit file “target/linux/ramips/base-files.mk”, remove the line :
rm -f $(1)/etc/config/network
- Edit the file “package/base-files/files/etc/config/network” with the settings you want. For example:
Revisions D1 to D4, H1 as well as I1 are pretty much unbrickable as they have a built-in firmware recovery mode. Revision D5 does not have built in recovery.
To access, simply hold down the reset button while powering on the router. The power LED should blink orange. Set your computer with a static IP in the 192.168.0.x range, and open 192.168.0.1 in a web browser. Recovery mode loads up within a few seconds, but doesn't respond to pings. If the power LED is blinking orange the above page should be accessible.
You will need to flash either a stock firmware image or Openwrt-factory image, *not* a sysupgrade image.
Numbers 0-3 are Ports 1-4 as labeled on the unit, number 4 is the Internet (WAN) on the unit, 5 is the internal connection to the router itself. Don't be fooled: Port 1 on the unit is number 3 when configuring VLANs. vlan0 = eth0.0, vlan1 = eth0.1 and so on.
The Device uses a DDR1 16Mbit x 16bit (16Mibit*16=256 mebibit. 256 mebibit/8=32MiByte) 400MHz chip Zentel A3S56D40FTP. Replace it with any 32Mbit x 16bit chip. 333MHz instead of 400MHz also works fine. It's quite hard to find these chips. One of the ways to get them is to have a look at DDR SO-DIMM (because SO-DIMM modules are shipped with x16 chips). Since there are no 64Mbit x 16bit DDR1 Chips available → no 128 MB mod!
The most easy approach is to seek for a 4-chip DDR 256 MB module. These all have x16 chips too. Chips only on one side (not to be confused with double-sided 256 MB modules with 4 chips on each side) and only 4 of them - that's the best chance to get some. They represent a small percent among usual 8-chip modules but this is equalized with the amount and “cheap as dirt” price of such DDR 256 MB modules.
Take some GPIOs which are connected to LEDs or switches, 3.3V and GND from the JTAG header and use the mmc-over-gpio kernel module. The kmod-leds-gpio and kmod-input-gpio-keys-polled kernel modules have to be unloaded before. The blue WPS LED will show when the SD-Card is being accessed and the power LEDs will flicker while data is being transfered.
Power LED amber
Power LED green
WPS LED blue
If you forgot your password, broken one of the startup scripts, firewalled yourself or corrupted the JFFS2 partition, you can get back in by using OpenWrt's failsafe mode.
Boot into failsafe mode
Unplug the router's power cord.
Connect the router's LAN1 port directly to your PC.
Configure your PC with a static IP address between 192.168.1.2 and 192.168.1.254. E. g. 192.168.1.2 (gateway and DNS is not required).
Plug the power on and wait for the DMZ LED to light up.
While the DMZ LED is on immediately press any button (Reset and Secure Easy Setup will work) a few times .
If done right the DMZ LED will quickly flash 3 times every second.
You should be able to telnet to the router at 192.168.1.1 now (no username and password)
What is the DMZ LED? It's not mentioned anywhere else in this article.
What to do in failsafe mode?
NOTE: The root file system in failsafe mode is the SquashFS partition mounted in readonly mode. To switch to the normal writable root file system run mount_root and make any changes. Run mount_root now.
Forgot/lost your password and you like to set a new one passwd
Forgot the routers IP address → 'uci get network.lan.ipaddr'
You accidentally run 'opkg upgrade' or filled up the flash
by installing to big packages (clean the JFFS2 partition and start
over) → 'mtd -r erase rootfs_data'
If you are done with failsafe mode power cycle the router and boot in normal mode.
The D-LinkDIR-615 has two buttons. They are WPS and RESET. The WPS button has its own blue led.
The buttons can be used with hotplug events. E. g. wifitoggle.
How to configure LEDs in general, see the LED section in the Wiki.
Rev C: The DIR-615c2 has 1 blue, 3 green and 2 orange controlled LEDs:
Rev H1: The same LED configuration applies to Rev H1.
Free GPIO ports
Revision C2 has 6 free (non-used) GPIO ports. To use them you should do some solder work. Please train you solder skills on broken motherboards before trying to do this on working hardware.
unpopulated resistor pad near LED21, pcb bottom left corner
unpopulated resistor pad to the left of the CPU
unpopulated resistor pad near LED20 near gpio0
testpoint on the bottom side of pcb near cpu
testpoint on the bottom side of pcb near cpu
testpoint on the bottom side of pcb near cpu
There is also one free GPIO5 used by dir-615c1:green:wancpu led interface. This
led interface is useless so we can just desolder r218 (located between q7 transistor and led10),
remove led definition from mach-dir-615-c1.c recompile/reflash kernel and use GPIO5 as we want.
To activate GPIO interface you should export it using command 'echo N > /sys/class/gpio/export'
(N is a GPIO number). Then you can use /sys/class/gpio/GPION interface to control GPIO
(set/get direction, value, etc). Also you can use i2c_gpio_custom/w1_gpio_custom kernel
modules for 1wire/i2c protocols over gpio to connect devices/sensors/actuators to your router.