Differences

This shows you the differences between two versions of the page.

toh:d-link:dir-825 [2012/11/30 03:40]
uvray313
toh:d-link:dir-825 [2014/02/19 21:17] (current)
swe3tdave
Line 3: Line 3:
===== Known Hardware Versions ===== ===== Known Hardware Versions =====
^ Revision ^ OpenWrt Version Supported ^ Model Specific Notes ^ ^ Revision ^ OpenWrt Version Supported ^ Model Specific Notes ^
-| A1       | **not supported** | |+| <color red> A1 </color> | **not supported** | |
| B1      | Kamikaze trunk    | working with trunk as of r18621 | | B1      | Kamikaze trunk    | working with trunk as of r18621 |
| B2      | Kamikaze trunk    | working with trunk as of r25121 | | B2      | Kamikaze trunk    | working with trunk as of r25121 |
-| B1/2    | Attitude Adjustment trunk    | Newer revisions (FW 2.05EU) store mac-addresses differently,\\ which leads to non-working wlan0/1. Working with trunk as of r29119|+| B1/2    | Attitude Adjustment trunk    | Newer revisions (FW 2.05EU) store mac-addresses differently,\\ which leads to non-working wlan0/1. Working with trunk as \\ of r29119
 +| C1      | Barrier Breaker trunk [[https://dev.openwrt.org/changeset/35403|r35403]]    | See [[https://dev.openwrt.org/changeset/35401|r35401]], [[https://dev.openwrt.org/changeset/35402|r35402]], [[https://dev.openwrt.org/changeset/35403|r35403]] | 
 +| <color red> D1 </color> | **not supported** | See [[https://forum.openwrt.org/viewtopic.php?id=46774|Forum]] |
-**NOTE:** B2 appears to only be different in labeling. The default firmware claims B1 and even ''/proc/cpuinfo'' claim to be B1 revisions even though the packaging and the sticker say B2.+**''Note:''** B2 appears to only be different in labeling. The default firmware claims B1 and even ''/proc/cpuinfo'' claim to be B1 revisions even though the packaging and the sticker say B2.
===== Hardware Highlights ===== ===== Hardware Highlights =====
^ HW Rev ^ CPU ^ Ram ^ Flash ^ Network ^ Gigabit ^ USB ^ Serial ^ JTag ^ ^ HW Rev ^ CPU ^ Ram ^ Flash ^ Network ^ Gigabit ^ USB ^ Serial ^ JTag ^
 +| <color red> A1 </color> | <color red> Ubicom IP5170U@? </color> | 16MB | ? | 4x1 | Yes | Yes | ? | ? |
| B1/B2 | Atheros AR7161@680MHz| 64MB | 8MB | 4x1 | Yes | Yes | Yes | Yes | | B1/B2 | Atheros AR7161@680MHz| 64MB | 8MB | 4x1 | Yes | Yes | Yes | Yes |
| C1 | Atheros AR9344@560MHz| 128MB | 16MB | 4x1 | Yes | Yes | Yes | Yes | | C1 | Atheros AR9344@560MHz| 128MB | 16MB | 4x1 | Yes | Yes | Yes | Yes |
 +| <color red> D1 </color> | <color red> Realtek RTL8197D@? </color> | ? | ? | 4x1 | Yes | Yes | ? | ? |
 +
 +**''Note:''** Although C1 has SoC of AR9344 but it's categorized under "target" of **ar71xx**. So you should find its related source code in 'trunk/target/linux/ar71xx' and its builds under [[http://downloads.openwrt.org/snapshots/trunk/ar71xx/|ar71xx/]] folder.
==== Switch Ports  ==== ==== Switch Ports  ====
Line 36: Line 42:
(worked on a B2 revision with Ubuntu's Firefox in 2.05NA and 2.06NA) (worked on a B2 revision with Ubuntu's Firefox in 2.05NA and 2.06NA)
It looks like Firmware 2.01EU behaves the same way. Please use the firmware recovery mode instead. It looks like Firmware 2.01EU behaves the same way. Please use the firmware recovery mode instead.
 +
 +**''Note:''** This method works for revision C2 with Firmware 3.00 using Ubuntu's Firefox. I used [[http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-dir-825-c1-squashfs-factory.bin|openwrt-ar71xx-generic-dir-825-c1-squashfs-factory.bin]]
  - Login into the factory D-Link firmware web-interface as usual. Default procedure for the freshly purchased router is:   - Login into the factory D-Link firmware web-interface as usual. Default procedure for the freshly purchased router is:
Line 49: Line 57:
==== Installation using firmware recovery mode ==== ==== Installation using firmware recovery mode ====
 +=== Phase 1: OS specific quirks ===
<color red>**''Note:''** The firmware recovery mode has following quirks:</color> <color red>**''Note:''** The firmware recovery mode has following quirks:</color>
  * If you have a Windows machine available you can use Microsoft Internet Explorer 7 (a Windows running on a VM, like VMware, does not work)   * If you have a Windows machine available you can use Microsoft Internet Explorer 7 (a Windows running on a VM, like VMware, does not work)
    * Windows 8: Firefox cannot be used to update firmware (presumably applies to other versions of Windows).     * Windows 8: Firefox cannot be used to update firmware (presumably applies to other versions of Windows).
    * Windows 8: Use Internet Explorer 10. Press F12. Select Browser Mode: IE8. Leave the compatibility setting at IE5 Quirks.     * Windows 8: Use Internet Explorer 10. Press F12. Select Browser Mode: IE8. Leave the compatibility setting at IE5 Quirks.
 +    * Windows 7: try to turn off ipv6
  * If you are running Linux you can:   * If you are running Linux you can:
    * Set your interface to 100Mbps using ''sudo ethtool -s eth0 speed 100 autoneg off'', install [[http://appdb.winehq.org/objectManager.php?sClass=version&iId=4195|IE7 in Wine]] and use it to flash.     * Set your interface to 100Mbps using ''sudo ethtool -s eth0 speed 100 autoneg off'', install [[http://appdb.winehq.org/objectManager.php?sClass=version&iId=4195|IE7 in Wine]] and use it to flash.
Line 59: Line 69:
    * firmware 2.02EU should still be available on ftp.dlink.de and it doesn't require IE, nor Mac.     * firmware 2.02EU should still be available on ftp.dlink.de and it doesn't require IE, nor Mac.
    * 2.05EUB09_7 can't be downgraded to 2.04 but fortunately can be downgraded to 2.02EU     * 2.05EUB09_7 can't be downgraded to 2.04 but fortunately can be downgraded to 2.02EU
 +    * I had to disable both avahi, cups and IPv6 to get it working. (B2 FW ver 2.01EU)
  * If you are running MacOS you can use <del>Google Chrome</del> Opera   * If you are running MacOS you can use <del>Google Chrome</del> Opera
  * FW version 2.05EU seems very difficult to flash, there may be timing issues (that's just a guess). After downgrading to 2.04EU (get it from ftp.dlink.de) it worked the first time, using IE7 on a virtualbox Win XP "guest". YMMV.   * FW version 2.05EU seems very difficult to flash, there may be timing issues (that's just a guess). After downgrading to 2.04EU (get it from ftp.dlink.de) it worked the first time, using IE7 on a virtualbox Win XP "guest". YMMV.
 +=== Phase 2: General steps ===
  - Get into the D-Link recovery console with the steps below:   - Get into the D-Link recovery console with the steps below:
    - While powering up the router, press and hold the //reset button// until the power LED starts blinking orange (usually takes around 45 (forty-five) seconds )     - While powering up the router, press and hold the //reset button// until the power LED starts blinking orange (usually takes around 45 (forty-five) seconds )
Line 67: Line 79:
    - connect to http://192.168.0.1, mind the quirks!     - connect to http://192.168.0.1, mind the quirks!
  - Click "Browse" and select your OpenWrt image file (**openwrt-ar71xx-dir-825-b1-squashfs-factory.bin**, this binary image is available in the Backfire 10.03.1rc1 download directory and above)   - Click "Browse" and select your OpenWrt image file (**openwrt-ar71xx-dir-825-b1-squashfs-factory.bin**, this binary image is available in the Backfire 10.03.1rc1 download directory and above)
-  - Click "Update" and let router flash the image (don't worry if it reboots before it reaches 100%). The page should display "Device is Upgrading the Firmware" in blue letters with the current percentage in red (with an incompatible Browser it doesn't).+  - Click "Update" and let router flash the image (don't worry if it reboots before it reaches 100%). The page should display "Device is Upgrading the Firmware" in blue letters with the current percentage in red (with an incompatible Browser it doesn't). Look at the screenshot at the end of this section.
  - The router's power LED should blink orange during bootup, as soon as it stops flashing, you can connect to it   - The router's power LED should blink orange during bootup, as soon as it stops flashing, you can connect to it
  - Tip! Note that default DHCP will allocate on 192.168.**1**.x, which is different subnet to the address you allocated above. This is why you can't connect until you change your IP address.   - Tip! Note that default DHCP will allocate on 192.168.**1**.x, which is different subnet to the address you allocated above. This is why you can't connect until you change your IP address.
  - obtain new IP from the router via DHCP and follow [[doc:howto:firstlogin]]   - obtain new IP from the router via DHCP and follow [[doc:howto:firstlogin]]
 +{{:media:d-link.dir-825.b2.firmware.recovery.mode.using.ie7.on.wine.in.linux.png?400x384|D-Link DIR-825 B2 after clicking "Update" in Firmware Recovery Mode, using IE7 on Wine in Linux}}
 +
 +
 +==== Flash Layout ====
 +
 +First, for familiarity you can look at the concept of [[doc/techref/Flash Layout]]. It is also recommended that you know flash layout of DIR-825 before [[doc/howto/generic.sysupgrade]], [[doc/howto/generic.backup]], [[doc/howto/generic.debrick]] or [[doc/howto/generic.failsafe]].
 +
 +^  D-Link DIR-825 Rev B  Flash Layout  ^^^^^^^^^
 +^ Layer0 |  m25p80 [[wp>Serial Peripheral Interface Bus|spi]]0.0: s25sl064a 8192KiB  ||||||||
 +^ Layer1 |  mtd0 **//u-boot//** 256KiB  |  mtd1 **//config//** 64KiB  |  mtd7 **//firmware//** 6208KiB  |||  mtd5 **//caldata//** 64KiB  |  mtd6 **//unkown//** 1600KiB  ||
 +^ Layer2 | | |  mtd2 **//kernel//** 1024KiB  |  mtd3 **//rootfs//** 5184KiB  || | |  mtd8 **//caldata_copy//** 64KiB  |
 +^ <color magenta>mountpoint</color> | | | |  <color magenta>''/''</color>  || | | |
 +^ filesystem | | | |  [[doc:techref:filesystems#overlayfs|overlayfs]]  || | | |
 +^ Layer3 | | | | |  mtd4 **//rootfs_data//** 3328KiB  | | | |
 +^ Size in KiB |  256KiB  |  64KiB  |  1024KiB  |  1856KiB  |  3328KiB  |  64KiB  |  1536KiB  |  64KiB  |
 +^ Name |  **//u-boot//**  |  **//config//**  |  **//kernel//**  | |  **//rootfs_data//**  |  **//caldata//**  | |  **//caldata_copy//**  |
 +^ <color magenta>mountpoint</color> |  //none//  |  //none//  |  //none//  |  <color magenta>''/rom''</color>  |  <color magenta>''/overlay''</color>  |  //none//  |  //none//  |  //none//  |
 +^ filesystem |  //none//  |  //none//  |  //none//  |  [[doc:techref:filesystems#SquashFS]]  |  [[doc:techref:filesystems#JFFS2]]  |  //none//  |  //none//  |  //none//  |
 +
 +***Note*** The partitions "mtd1 **//config//**", "mtd5 **//caldata//**", "mtd6 **//unkown//**" and "mtd8 **//caldata_copy//**" contain vendor specific raw (without filesystem) config values about your router, like WiFi calibration data, MAC addresses, etc. It's a good idea to [[doc/howto/generic.backup|make a backup from them]]. Similarly, "mtd0 **//u-boot//**" has some specific codes for Dir-825 (e.g. its "firmware recovery mode"); So you can backup that partition too.
 +
 +***Note2*** You can check mtd partitions of your router yourself by using commands "''cat /proc/mtd''" and "''dmesg''". Refer to [[https://www.mail-archive.com/kernelnewbies@nl.linux.org/msg02774.html|this link]].
==== Upgrading OpenWrt ==== ==== Upgrading OpenWrt ====
->[[doc:howto:generic.sysupgrade]] ->[[doc:howto:generic.sysupgrade]]
- 
-==== Firmware recovery ==== 
-->[[doc:howto:generic.debrick]] 
==== OpenWrt failsafe mode ==== ==== OpenWrt failsafe mode ====
->[[doc:howto:generic.failsafe]] ->[[doc:howto:generic.failsafe]]
 +==== Firmware recovery ====
 +->[[doc:howto:generic.debrick]]
===== Basic configuration ===== ===== Basic configuration =====
Line 109: Line 142:
{{:toh:d-link:dir825-b2-soldered-bridges-for-second-usb-port.jpg?400x258|D-Link DIR-825 with bridges soldered to enable second USB port.}} {{:toh:d-link:dir825-b2-soldered-bridges-for-second-usb-port.jpg?400x258|D-Link DIR-825 with bridges soldered to enable second USB port.}}
{{:toh:d-link:dir825-b2-second-usb-in-action.jpg?400x251|D-Link DIR-825 B2 with second USB port in use.}} {{:toh:d-link:dir825-b2-second-usb-in-action.jpg?400x251|D-Link DIR-825 B2 with second USB port in use.}}
 +{{:media:dir-825.b2.2nd.usb.wires.order.low.res.jpg?400x300|DIR-825 B2 2nd USB Wires Order}}
{{:toh:d-link:dir825-c1-board.jpg?400x251|D-Link DIR-825 C1 board.}} {{:toh:d-link:dir825-c1-board.jpg?400x251|D-Link DIR-825 C1 board.}}
{{:toh:d-link:dir825-c1-ar9344.jpg?400x300|D-Link DIR-825 C1 Atheros chipset.}} {{:toh:d-link:dir825-c1-ar9344.jpg?400x300|D-Link DIR-825 C1 Atheros chipset.}}
Line 205: Line 239:
==== Second USB port ==== ==== Second USB port ====
It was reported that in order to enable second USB port it is sufficient to solder in two straight bridges in place of L66 (take a look to the corresponding photo in the "Photos" section). After that you will need to solder in second USB header or - easier way - to solder in short-tailed female USB type A connector (sample photo is also available in the "Photos" section). It was reported that in order to enable second USB port it is sufficient to solder in two straight bridges in place of L66 (take a look to the corresponding photo in the "Photos" section). After that you will need to solder in second USB header or - easier way - to solder in short-tailed female USB type A connector (sample photo is also available in the "Photos" section).
 +
 +In the stock firmware, after you have soldered the bridges and USB head, if you connect a USB device (e.g. a USB Flash Drive) to the second USB head, the USB LED will turn blue.
Discussion and more information can be found in this [[https://forum.openwrt.org/viewtopic.php?id=24399|thread]]. Discussion and more information can be found in this [[https://forum.openwrt.org/viewtopic.php?id=24399|thread]].
Line 236: Line 272:
Besides flashing in recovery mode from a MacBook Pro using Google Chrome and the default Gigabit plug worked just fine! Besides flashing in recovery mode from a MacBook Pro using Google Chrome and the default Gigabit plug worked just fine!
 +
 +I had installed the openwrt-ar71xx-generic-dir-825-b1-squashfs-factory.bin using a Ubuntu system with Chrome using the original firmware update page in a DI-825 Rev B1 with FW 2.07NA
----- -----
Line 453: Line 491:
Now hit the **Save & Apply** button Now hit the **Save & Apply** button
-==== 4) Setup a machine connected to VLAN ===+==== 4) Setup machine connected to VLAN ===
This are the settings of your machine (ex. FTP): This are the settings of your machine (ex. FTP):
Line 471: Line 509:
We have recently developed a script and performed some correction based on your work you can find it here We have recently developed a script and performed some correction based on your work you can find it here
-http://openwisp.caspur.it/wiki/owf/FlashingDlinkDIR825#notextile-Automatic-flashing-script-notextile+You need to have ruby installed. 
 + 
 + 
 +Script recovered from the WayBackMachine: https://web.archive.org/web/20120418003158/http://openwisp.caspur.it/wiki/owf/FlashingDlinkDIR825#notextile-Automatic-flashing-script-notextile
**With this script it's not necessary to force your NIC to work @ 10/100 Mb/s and it's not necessary using IE7** **With this script it's not necessary to force your NIC to work @ 10/100 Mb/s and it's not necessary using IE7**
 +
 +<code ruby>#!/usr/bin/ruby
 +# Copyright (C) 2011 CASPUR (wifi@caspur.it)
 +#
 +# This program is free software: you can redistribute it and/or modify
 +# it under the terms of the GNU General Public License as published by
 +# the Free Software Foundation, either version 3 of the License, or
 +# (at your option) any later version.
 +#
 +# This program is distributed in the hope that it will be useful,
 +# but WITHOUT ANY WARRANTY; without even the implied warranty of
 +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 +# GNU General Public License for more details.
 +#
 +# You should have received a copy of the GNU General Public License
 +# along with this program.  If not, see <http://www.gnu.org/licenses/>.
 +
 +# This script will help you flashing D-LINK DIR-825 devices 'cause  they can be flashed only with IE7
 +# Your ETH Address must be 192.168.0.100/24
 +
 +require 'socket'
 +
 +HOST = "192.168.0.1"
 +PATH = "/cgi/index"
 +
 +if ARGV.count == 0
 +  puts "Usage #{$0} <filename>"
 +  exit 1
 +else
 +  filename = ARGV[0]
 +  puts "[#{Time.now}] Using firmware file '#{filename}'"
 +end
 +
 +predata = <<-eopd
 +-----------------------------7db12928202b8
 +Content-Disposition: form-data; name="files"; filename="#{filename}"
 +Content-Type: application/octet-stream
 +
 +eopd
 +
 +firmware = File.open(filename, "rb") { |io| io.read }
 +
 +postdata="\x0d\x0a-----------------------------7db12928202b8--\x0d\x0a"
 +
 +# Each line must end with cr/lf characters, and we have to know how many
 +# data the script will send to the dir-825 this is why we concatenate it before
 +# creating the header
 +
 +buffer = predata.gsub(/\n/,"\x0d\x0a") + firmware + postdata
 +
 +header = <<-eoh
 +POST #{PATH} HTTP/1.1
 +Accept: image/jpeg, application/x-ms-application, image/gif, application/xaml+xml, image/pjpeg, application/x-ms-xbap, */*
 +Referer: http://#{HOST}/
 +Accept-Language: it-IT
 +User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0)
 +Content-Type: multipart/form-data; boundary=---------------------------7db12928202b8
 +Accept-Encoding: gzip, deflate
 +Host: #{HOST}
 +Content-Length: #{buffer.length}
 +Connection: Keep-Alive
 +Cache-Control: no-cache
 +
 +eoh
 +
 +begin
 +  puts "[#{Time.now}] Firmware file laded (#{firmware.length} bytes)"
 +  http = TCPSocket.new(HOST, 'www')
 +
 +  puts "[#{Time.now}] Sending firmware to the device...  "
 +
 +  http.print header.gsub(/\n/,"\x0d\x0a") + buffer
 +  resp = http.recv(1012)
 +
 +  # Let's check if it's all ok
 +  if resp.match /Don't turn the device off before the Upgrade jobs done/
 +    puts "\n[#{Time.now}] Finished. Please wait for the device to reboot."
 +  else
 +    puts "\n[#{Time.now}] Problem sending firmware to the device. Response from device follows."
 +    puts resp
 +  end
 +
 +  http.close
 +  rescue Exception => e
 +  puts "[#{Time.now}] Problem flashing device. Error: '#{e}'"
 +end
 +
 +exit 0</code>
===== Custom IPv6 image for DIR-825 ===== ===== Custom IPv6 image for DIR-825 =====
Line 479: Line 608:
a custom image with ipv6 support: radvd, wide-dhcpv6, 3g stick support, made for RCS-RDS Fiberlink dual stack PPPoE service, a custom image with ipv6 support: radvd, wide-dhcpv6, 3g stick support, made for RCS-RDS Fiberlink dual stack PPPoE service,
but should be okay for static wan settings on other ISPs: but should be okay for static wan settings on other ISPs:
-http://www.ip6.ro/firmware/dir825/+http://www.internet6.ro/downloads/dlink-dir-825/ 
 + 
 + 
 + 
 +===== Fat images ===== 
 +Since Attitude Adjustment beta 2, some images are suffixed with "-fat" to indicate they will be able to use more flash that the factory firmware uses by default. It does this by moving the wireless interface calibration data at the end of the flash. This is a dangerous operation and should only be performed if you know how to back this flash partition (/dev/mtd5). 
 +To upgrade, you'll need to copy the whole image in /tmp and use sysupgrade -i the caldata question. Downgrading to a non-fat image will get the caldata back in place so it can be used by the factory firmware, after upgrading to a fat image, you must downgrade before getting back to a factory image. 
 + 
 +''Before: 
 +/dev/mtdblock4          576.0K    308.0K    268.0K  53% /overlay 
 +After: 
 +/dev/mtdblock4            2.1M    328.0K      1.8M  15% /overlay 
 +''
 +===== Tags =====
---- ----
-{{tag>GigabitEthernet 5Port 2PHY USB 1USB JTAG 802.11abgn_simultan detachableantenna 2Ant 2Radio ath9k 64RAM 8Flash MIPS MIPS32 24Kc}}+{{tag>GigabitEthernet 5Port 2PHY USB 1USB JTAG 802.11abgn_simultan detachableantenna 2Ant 2WNIC ath9k 64RAM 8Flash MIPS MIPS32 24Kc}}

Back to top

toh/d-link/dir-825.1354243242.txt.bz2 · Last modified: 2012/11/30 03:40 by uvray313