Frys FR-300RTR is the same as E1 [[https://​forum.openwrt.org/​viewtopic.php?​pid=131673#​p131673|Forum]]

+

**NOTE:** ONLY revision C1 and C2 are fully supported yet.

+

*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 [[https://​forum.openwrt.org/​viewtopic.php?​pid=131673#​p131673|Forum]] ​\\

+

* April 2013 - **Version E4 is supported and known to work with attitude adjustment 12.09** [[http://​downloads.openwrt.org/​attitude_adjustment/​12.09/​ar71xx/​generic/​openwrt-ar71xx-generic-dir-615-e4-squashfs-factory.bin|(link to flash file))]] , see installation instruction below \\

Installation is fairly straight forward for this router, you will need to access the D-Link recovery console with the steps below.

Installation is fairly straight forward for this router, you will need to access the D-Link recovery console with the steps below.

-

- As per the note at http://​www.dd-wrt.com/​wiki/​index.php/​DIR-615C , "If your dlink 615 C1 is at f/w 3.12 or 3.11 you may have to revert it to 3.10"​. ​ The older firmware is available from D-Link: ​http://​www.dlink.com/​products/?​tab=3&​pid=DIR-615&​rev=DIR-615_revC

+

- As per the note at http://​www.dd-wrt.com/​wiki/​index.php/​DIR-615C , "If your dlink 615 C1 is at f/w 3.12 or 3.11 you may have to revert it to 3.10"​. ​ The older firmware is available from [[http://​www.dlink.com/​us/en/​support/​product/​dir-615-wireless-n-300-router?​revision=us_revc|D-Link support]].

-

​- Press and hold the reset button until the power LED starts blinking orange (usually takes ~45 seconds). Or, hold down the reset button while powering on the router, this is much quicker and only takes 5-10 seconds.

​- Press and hold the reset button until the power LED starts blinking orange (usually takes ~45 seconds). Or, hold down the reset button while powering on the router, this is much quicker and only takes 5-15 seconds.

+

​- Go to '​http://​192.168.0.1'​ from your PC web browser. (Note: most modern browsers don't work, see below, Firefox 13 portable version is known to work)

- Let router flash the image, don't worry if it reboots before it reaches 100%. If the page loads forever or times out, your browser is unsupported. See below.

- Let router flash the image, don't worry if it reboots before it reaches 100%. If the page loads forever or times out, your browser is unsupported. See below.

Line 53:

Line 68:

The firmware update system doesn'​t support the HTTP header ''​Expect:​ 100-continue'',​ which is used in POST requests by most modern browsers. If the browser sends this header, it will wait for the server to send a provisional response with status ''​100 Continue''​ before sending the file contents. This feature was added in HTTP/1.1 to allow servers to reject uploads without needing to upload the file first. The router'​s built-in HTTP server claims to support HTTP/1.1, but it never sends the ''​100 Continue''​ response so the browser waits forever or eventually times out.

The firmware update system doesn'​t support the HTTP header ''​Expect:​ 100-continue'',​ which is used in POST requests by most modern browsers. If the browser sends this header, it will wait for the server to send a provisional response with status ''​100 Continue''​ before sending the file contents. This feature was added in HTTP/1.1 to allow servers to reject uploads without needing to upload the file first. The router'​s built-in HTTP server claims to support HTTP/1.1, but it never sends the ''​100 Continue''​ response so the browser waits forever or eventually times out.

-

Internet Explorer 7 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:

+

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.

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 [[http://​sourceforge.net/​projects/​portableapps/​files/​Mozilla%20Firefox%2C%20Portable%20Ed./​Mozilla%20Firefox%2C%20Portable%20Edition%2013.0.1/​|FF 13 portable]] also should work.

-

==== Rev. D1-D4 ====

+

**

+

==== Rev. C2 ====

+

+

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: \\

+

​{{:​media:​dir615c2hex_edit_image.png}}

+

+

===== Rev. D1-D4 =====

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.

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.

Line 65:

Line 89:

| FIXME: D1/D2 build instructions |

| FIXME: D1/D2 build instructions |

-

| FIXME: D3/D4 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

+

+

**Wireless**:​

+

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

+

+

**Ethernet**:​

+

The only way to get this fully working is to recompile using old ramips ethernet drivers (from revision: 24328)

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 [[http://​www.intel.com/​p/​en_US/​support/​highlights/​wireless/​1000|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

+

* Trigger: netdev

+

* 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: [[https://​dev.openwrt.org/​ticket/​14827|Ticket]],​ [[​https://​forum.openwrt.org/​viewtopic.php?​id=47998|Forum]],​ [[http://​superuser.com/​questions/​693534/​openwrt-regular-connection-resets|SuperUser]]

| FIXME: The DIR-825 has a better description:​ [[toh/​d-link/​dir-825#​installation]]. |

| FIXME: The DIR-825 has a better description:​ [[toh/​d-link/​dir-825#​installation]]. |

+

+

==== Rev. H1 ====

+

+

As of [[https://​dev.openwrt.org/​changeset/​36213/​trunk|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):​

+

+

<​code>​

+

config interface '​loopback'​

+

option ifname ​ '​lo'​

+

option proto '​static'​

+

option ipaddr ​ '​127.0.0.1'​

+

option netmask ​ '​255.0.0.0'​

+

+

config interface '​lan'​

+

option ifname ​ '​eth0'​

+

option hostname '​DIR-615_H1'​

+

option proto '​dhcp' ​

+

</​code>​

+

+

Now you should be able to telnet to DIR-615_H1

+

+

+

=== Rev. H1 Build Instruction ===

+

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.

- Edit the file "​package/​base-files/​files/​etc/​config/​network"​ with the settings you want. For example:

+

<​code>​

+

# Copyright (C) 2006 OpenWrt.org

+

config interface '​loopback'​

+

option ifname '​lo'​

+

option proto '​static'​

+

option ipaddr '​127.0.0.1'​

+

option netmask '​255.0.0.0'​

+

+

config interface '​lan'​

+

option ifname '​eth0.1'​

+

option type '​bridge'​

+

option proto '​static'​

+

option ipaddr '​192.168.0.1'​

+

option netmask '​255.255.255.0'​

+

+

config interface '​wan'​

+

option ifname '​eth0.2'​

+

option hostname '​DIR-615-H1'​

+

option proto '​dhcp'​

+

+

config switch

+

option name rt305x

+

option reset 1

+

option enable_vlan 1

+

+

config switch_vlan

+

option device rt305x

+

option vlan 1

+

option ports '0 1 2 3 6t'

+

+

config switch_vlan

+

option device rt305x

+

option vlan 2

+

option ports '4 6t'

+

</​code>​

+

- In case you have already build something make a dirclean

+

<​code>​

+

make dirclean

+

</​code>​

+

- Configure the image:

+

<​code>​

+

make menuconfig

+

</​code>​

+

<​code>​

+

Target System (Ralink RT288x/​RT3xxx)

+

Subtarget (RT305x based boards)

+

Target Profile (DIR-615 H1)

+

</​code>​

+

- Build the image:

+

<​code>​

+

make -j 5

+

</​code>​

==== Upgrading OpenWrt ====

==== Upgrading OpenWrt ====

Line 76:

Line 268:

-

Revisions D1 to D4 are pretty much unbrickable as they have a built-in firmware recovery mode. Revision D5 does not have built in recovery.

+

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.

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.

Line 87:

Line 279:

->​[[doc:​howto:​wireless.overview]] This router requires the packages ''​kmod-ath9k''​ and ''​wpad-mini''​.

->​[[doc:​howto:​wireless.overview]] This router requires the packages ''​kmod-ath9k''​ and ''​wpad-mini''​.

+

+

===== Specific configuration =====

+

+

==== Switch Ports (for VLANs) ====

+

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.

+

+

^ GPIO # ^ Original use ^ SD signal ​ ^ SD pin ^

+

| 0 | WPS button ​ | MISO | 7 |

+

| 7 | Power LED amber | MOSI | 2 |

+

| 9 | Power LED green | SCK | 5 |

+

| 14 | WPS LED blue | /SS | 1 |

+

| | +3.3V | +3.3V | 4 |

+

| | GND | GND | 3 |

+

| | GND | GND | 6 |

+

+

{{:​toh:​d-link:​dir-615:​dir615h1-sd-card-mod.jpg|}}

===== Failsafe mode =====

===== Failsafe mode =====

Line 307:

Line 676:

* If done right the DMZ LED will quickly flash 3 times every second.

* 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)

* You should be able to telnet to the router at 192.168.1.1 now (no username and password)

+

FIXME What is the DMZ LED? It's not mentioned anywhere else in this article.

==== What to do in failsafe mode? ====

==== What to do in failsafe mode? ====

Line 330:

Line 700:

How to configure LEDs in general, see the LED section in the [[doc/​uci/​system|Wiki]].

How to configure LEDs in general, see the LED section in the [[doc/​uci/​system|Wiki]].