OpenWrt Forum Archive

Topic: DIR-600 B5 works with OpenWRT

The content of this topic has been archived between 21 Apr 2018 and 22 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi MasterX1987,

I have just tested your instructions and have the following to report:
i) all goes well until step 4. The rooter reboots after loading the openwrt-ramips-rt305x-dir-610-a1-initramfs-uImage.bin image and I can connect with the new IP 192.168.1.1

ii) I cannot load the sysupgrade update. "The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform." I am attempting the update via the LuCi interface. Let me know if I should try another way.

iii) I have tested the new configuration as an Access Point for the wired network and it works. However, the bandwidth is really low at about 10-15 Mb, whereas the original firmware could easily reach 50 Mb with the same laptop as client.
Note that I have also disabled the firewall and I get the same poor results.

iv) The worst part of all is that the settings are lost upon reboot. This makes then entire setup quite unusable. Here is some extra information to help with the debugging:


root@OpenWrt:~# mount
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
tmpfs on /dev type tmpfs (rw,relatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
debugfs on /sys/kernel/debug type debugfs (rw,noatime)

root@OpenWrt:~# free
             total         used         free       shared      buffers
Mem:         29568        19920         9648            0            0
-/+ buffers:              19920         9648
Swap:            0            0            0

root@OpenWrt:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
tmpfs                    14784       536     14248   4% /tmp
tmpfs                      512         0       512   0% /dev

Thank you for the time and effort invested in making OpenWrt available for DIR 600 b5!!

Note that I will not be available in the next couple of days, but after that I will answer any questions and can continue the testing.

Cheers

Hello stefaniu_a...
To burn the Firmware to dlink you must type this command:
$ sysupgrade -F openwrt-ramips-rt305x-dir-610-a1-squashfs-sysupgrade.bin
(-F command = --force, the image don't was checkt,and burnt force to device ;-) )
MFG...

Hi again,

I executed the sysupgrade -F command and all works well now. The settings are saved upon reboot and I can use the router as an access point.

My initial goal was to use this router as a range extender (bridge). I have not yet succeeded in this respect, but I think I am getting closer. I have managed to setup the router as a "wifi client" and it connected nicely and got it's IP from the main router, but that's about it.
I tried the LuCi options of Client (WDS) and Access Point (WDS) but that did not work.
I think my problems come from the network settings (dhcp, etc.)

I'm still working on it.

Update (3 hours later): I managed to have the bridge working as well following these steps: https://www.youtube.com/watch?v=3rbsh2zxPnk

It is not the best situation, as the clients of the second router get IPs in a different domain (192.168.1.x for second router, while the main one has 192.168.3.x), but that's enough for me now. If I have time I will try to get it working on the same domain.

Cheers!

(Last edited by stefaniu_a on 9 Aug 2015, 00:59)

MasterX1987 wrote:

Hello Guys,
after hard working i have it done, who installing openwrt on my Dlink DIR600 B5, without connect it to Serial Port ... big_smile
Now what you are required for this?
1. You need to download this Files:
|-> My build of Original Firmware (mirror)
|-> openwrt-ramips-rt305x-dir-610-a1-initramfs-uImage.bin
|-> openwrt-ramips-rt305x-dir-610-a1-squashfs-sysupgrade.bin
2. You need a local Webhost to download a part of Firmware to your Dlink.
3. You have an NFS-Server online (to make it easier flash first part of Firmware...)
Now thats it!
...
MFG Master X


As I'm not comfortable with linux, is there another way to upload the first image rather than serial or the a nfs server ?
Like WinSCP or some tools like that ?

(Last edited by vince153 on 10 Aug 2015, 13:37)

Hi MasterX1987,

I just tried your method. When trying to mount a nfs share, I have the following error

"mount: can't read '/etc/fstab': No such file or directory"

Can you help me please

Thanks

[EDIT]

Copy/paste mistake... >:(
I forgot the "/home" in the command.
Anyway, I followed up the procedure and the first flash did not work

Please Help !

(Last edited by vince153 on 10 Aug 2015, 15:34)

Okay for everybody they had problems to set up the NFS Server, here two another Methodes to burn the first fw.bin to Device...
1, Methode:
WHAT WE NEED: Working Internet on Dlink OR a local WEB-Server....
After you Setup the web Server and copied the uImage.bin to the root destination you need connect to Device over telnet: (On Windows you can use putty ...)
$ telnet 192.168.0.1 2323
# On Device you have in /var Folder RW permissions....
$ cd /var
# Now get the fw.bin via wget ...
$ wget http://IP-of-Server/uImage.bin # (e.g. 192.168.1.169 or what ever...)
# After this flash it to /dev/mtd/2 via busybox flashcp ....
$ busybox flashcp uImage.bin /dev/mtd/2
========================================================================================================================
2. Methode:
WHAT WE NEED: busybox on local PC to use Netcat for the File transfer....
1. Connect via Telnet to device....
2. $ cd /var
3. $ nc -l -p 2525 | dd of=/var/uImage.bin # <== This Command type ON DLINK!
4. Now switch to a antoher terminal window and type this command on local PC:
$ dd if=uImage.bin | nc 192.168.0.1 2525 # (2525 is the port you have set on 3....)
# after 2-3 sec the fw.bin trans. to device and you can flash it to /dev/mtd/2 via busybox....

So i hope this help.... mfg

Hi MasterX1987, great news!

Will this new openwrt system be upgradeable in the future to new versions?

All the speeds are ok and all the functions are working now?

Thanks,
Benoe

zepingouin wrote:
depswa wrote:

I also compiled a newest release and got into a loop during boot. But then I realized that the OP wrote a post in March 2014, so I decided to try an older release from March 2014, and it worked!

Thanks for the images, it works like a charm on my DIR-600 B6 smile

Hi zepingouin,
I have the same router as you, but when I upgraded the firmware using depswa's build I wasn't as successful as you:
openwrt-ramips-rt305x-dir-600-b5-squashfs-factory.bin
https://mega.co.nz/#!PYQUgK4S!6Nl-6f4Nw … 0P4yo2eHwk

Now I have a router that doesn't work (LAN 2,3,4 Leds are always on, even though there isn't anything connected to it), and I can't get an IP from router.
Was your upgrade performed from the web interface?
Any idea how to get it to work again?

Thanks,
Gabriel

benoe77 wrote:

Hi MasterX1987, great news!

Will this new openwrt system be upgradeable in the future to new versions?

All the speeds are ok and all the functions are working now?

Thanks,
Benoe

Also i my case all Functions working perfectly....
I have successful compiled aircrack-ng rc2 (the newest version) and reaver-ng-pxi... All working fine....

And @ gabolema
You only need to boot into rs-room and flash the ori. firmware..-..

pls... 

ls
etc          sealpac      htdocs       servd        logs         porttrigger
log          tmp          TZ           passwd       gpio_ctrl    lld2d.conf
run          dnrd         hosts        session      killrc0      uImage.bin

# busybox flashcp uImage.bin /dev/mtd/2
flashcp: applet not found

Thanks MasterX1987 for your description and effort to bring OpenWRT to the DIR-600 B5.

I ran into some trouble as I tried to flash the dir600b_v2.17_bbox-v1.19.1.bin to the router. The data upload via emergency room upgrade broke after 4 to 8 percent. So I tried the upgrade via D-Link firmware upgrade, which soft bricked my router. The upload via emergency room failed, leaving me very frustrated. After several hours I tried a different PC and it worked suddenly. I don't know, what was wrong with the old setup...

Finally I was able to flash the dir600b_v2.17_bbox-v1.19.1.bin to the router, could connect via telnet and so on. The last step of using sysupgrade -F sysupgrade.bin leaves my router in a state described by gabolema: LEDs of WAN and LAN 2-4 always on and the router isn't accessible any more.
The sysupgrade was once performed though the web interface and twice via SSH.

I couldn't use the openwrt-ramips-rt305x-dir-610-a1-initramfs-uImage.bin and openwrt-ramips-rt305x-dir-610-a1-squashfs-sysupgrade.bin from MasterX1987s Post #25, because the MEGA Links are down. So I googled for these files and found these filenames on openwrt ftp-Server. They were on the trunk release branch, but I don't believe these are the same as the mega Links. Could someone, who succeeded with the sysupgrade, please relink these files or tell me which release they are?
I tried openwrt-15.05-ramips-rt305x-dir-610-a1-squashfs-sysupgrade.bin and openwrt-15.05-rc3-ramips-rt305x-dir-610-a1-squashfs-sysupgrade.bin. Since they have a release date prior to MasterX1987s Post #25. But none of them worked.

I think, I will try the trunk release and then 15.05-rc2 or 15.05-rc1 and if they fail I will go back to d-link firmware until someone has new information.

(Last edited by Merrx on 28 Sep 2015, 18:09)

MasterX1987 gave the links to my images from Post #14, which have indeed expired. I have updated that post, so you can download them again. Here are the new links (will work for approximately another half a year):

openwrt-ramips-rt305x-dir-610-a1-initramfs-uImage.bin
https://mega.nz/#!GFJSlZrI!WNX_LeDV-tN_ … seAjiiiOz0
md5: 829a60e6a5dde0e16400072ab6aa63d2

openwrt-ramips-rt305x-dir-610-a1-squashfs-sysupgrade.bin
https://mega.nz/#!DZwxzY5Y!WF-dSaDeVmKw … CT1tUNJiMo
md5: f3a265b9af2038040ad13e08a8246ff2

In principle, the last link in Post #14 is the same working image for this router (the same as the above two links), which can be flashed directly from the Web GUI, except that it has a wrong header. If someone can figure out how to repack it properly, it can be used to flash a working version of OpenWRT directly from stock web interface.

Unfortunately, I do not have this router anymore - so I cannot play with it. However, those who have soldered a serial port, could make the life easier for others smile

Thanks for your really quick answer. It worked with these two files.
It's OpenWrt Barrier Breaker and not the latest Chaos Calmer.
But at the moment I don't know, if it's worth to try the update.
I think will stick with the current setup, because I works for me.

@gilespii: Sounds like busybox didn't work properly.
Maybe re-download and re-flash the dir600b_v2.17_bbox-v1.19.1.bin.
I don't know if it's recommended, but maybe you can search on the net for a standalone busybox, extract the flashcp and copy it to the router.

(Last edited by Merrx on 1 Oct 2015, 21:19)

Can anyone point me where to start fixing this damn thing for good?
Images for DIR610 A1 (which supposedly work with DIR300 B5 and DIR600 B5) for BB and CC are broken in official repos (unable to mount rootfs). So I assume that imagebuilder is broken too. Images provided in this thread and found elsewhere that work, are long outdated and opkg doesn't work well (if at all) with current BB repo. Now, .dts file for DIR610A1 has an entry for m25p80 chip, while my DIR300 B5 has Winbond W25Q32 flash chip. So maybe these routers are not identical at all and rewriting source for winbond chip (which files? is .dts enough?) will fix it.

Hame MPR A1 images will boot on DIR300 B5, but obviously leds and buttons are all wrong and all the usb stuff is not necessary. On top of that, there seem to be other problems (mac addresses are zeroed, wifi is slow and bridging it with lan doesn't work)

DIR-600 B5
using latest trunk I changed the DIR-610-A1.dts file

                ralink,led-polarity = <1>;
-               ralink,mtd-eeprom = <&devdata 0x4000>;
+               ralink,mtd-eeprom = <&devdata 16384>;

and it seems to work

LE:now I see that hex value is the same dec value, maybe it is working now usig unmodified trunk


loged in on BARRIER BREAKER (Bleeding Edge, r39917) Linux version 3.10.32 (ilya@ubuntu) (found in this thread)

sysupgrade openwrt-ramips-rt305x-dir-610-a1-squashfs-sysupgrade.bin

and voila:

login as: root


BusyBox v1.24.1 (2015-11-11 01:16:59 EET) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 DESIGNATED DRIVER (Bleeding Edge, r47448)
 -----------------------------------------------------
  * 2 oz. Orange Juice         Combine all juices in a
  * 2 oz. Pineapple Juice      tall glass filled with
  * 2 oz. Grapefruit Juice     ice, stir well.
  * 2 oz. Cranberry Juice
 -----------------------------------------------------
root@OpenWrt:~# dmesg
[    0.000000] Linux version 3.18.23 (luci@droid) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47448) ) #1 Wed Nov 11 01:23:55 EET 2015
[    0.000000] SoC Type: Ralink RT5350 id:1 rev:3
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 0001964c (MIPS 24KEc)
[    0.000000] MIPS: machine is D-Link DIR-610 A1
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 02000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x00000000-0x01ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x00000000-0x01ffffff]
[    0.000000] Initmem setup node 0 [mem 0x00000000-0x01ffffff]
[    0.000000] On node 0 totalpages: 8192
[    0.000000] free_area_init_node: node 0, pgdat 8031c850, node_mem_map 81000000
[    0.000000]   Normal zone: 64 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 8192 pages, LIFO batch:0
[    0.000000] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 32 bytes
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 8128
[    0.000000] Kernel command line: console=ttyS0,57600 rootfstype=squashfs,jffs2
[    0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
[    0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Writing ErrCtl register=00005cc0
[    0.000000] Readback ErrCtl register=00005cc0
[    0.000000] Memory: 28752K/32768K available (2643K kernel code, 123K rwdata, 508K rodata, 172K init, 188K bss, 4016K reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:256
[    0.000000] CPU Clock: 360MHz
[    0.000000] systick: running - mult: 214748, shift: 32
[    0.060000] Calibrating delay loop... 239.61 BogoMIPS (lpj=1198080)
[    0.070000] pid_max: default: 32768 minimum: 301
[    0.080000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.100000] pinctrl core: initialized pinctrl subsystem
[    0.110000] NET: Registered protocol family 16
[    0.120000] rt2880-pinmux pinctrl: try to register 28 pins ...
[    0.120000] pinctrl core: registered pin 0 (io0) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 1 (io1) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 2 (io2) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 3 (io3) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 4 (io4) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 5 (io5) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 6 (io6) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 7 (io7) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 8 (io8) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 9 (io9) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 10 (io10) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 11 (io11) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 12 (io12) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 13 (io13) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 14 (io14) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 15 (io15) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 16 (io16) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 17 (io17) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 18 (io18) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 19 (io19) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 20 (io20) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 21 (io21) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 22 (io22) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 23 (io23) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 24 (io24) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 25 (io25) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 26 (io26) on rt2880-pinmux
[    0.120000] pinctrl core: registered pin 27 (io27) on rt2880-pinmux
[    0.120000] pinctrl core: add 3 pinmux maps
[    0.120000] rt2880-pinmux pinctrl: found group selector 0 for i2c
[    0.120000] rt2880-pinmux pinctrl: found group selector 4 for jtag
[    0.120000] rt2880-pinmux pinctrl: found group selector 2 for uartf
[    0.120000] rt2880-pinmux pinctrl: request pin 1 (io1) for pinctrl
[    0.120000] rt2880-pinmux pinctrl: request pin 2 (io2) for pinctrl
[    0.120000] rt2880-pinmux pinctrl: request pin 17 (io17) for pinctrl
[    0.120000] rt2880-pinmux pinctrl: request pin 18 (io18) for pinctrl
[    0.120000] rt2880-pinmux pinctrl: request pin 19 (io19) for pinctrl
[    0.120000] rt2880-pinmux pinctrl: request pin 20 (io20) for pinctrl
[    0.120000] rt2880-pinmux pinctrl: request pin 21 (io21) for pinctrl
[    0.120000] rt2880-pinmux pinctrl: request pin 7 (io7) for pinctrl
[    0.120000] rt2880-pinmux pinctrl: request pin 8 (io8) for pinctrl
[    0.120000] rt2880-pinmux pinctrl: request pin 9 (io9) for pinctrl
[    0.120000] rt2880-pinmux pinctrl: request pin 10 (io10) for pinctrl
[    0.120000] rt2880-pinmux pinctrl: request pin 11 (io11) for pinctrl
[    0.120000] rt2880-pinmux pinctrl: request pin 12 (io12) for pinctrl
[    0.120000] rt2880-pinmux pinctrl: request pin 13 (io13) for pinctrl
[    0.120000] rt2880-pinmux pinctrl: request pin 14 (io14) for pinctrl
[    0.120000] rt2880-pinmux pinctrl: failed to lookup the sleep state
[    0.160000] rt2880_gpio 10000600.gpio: registering 22 gpios
[    0.170000] rt2880_gpio 10000600.gpio: registering 22 irq handlers
[    0.180000] Switched to clocksource MIPS
[    0.190000] NET: Registered protocol family 2
[    0.200000] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.210000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.220000] TCP: Hash tables configured (established 1024 bind 1024)
[    0.240000] TCP: reno registered
[    0.240000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.250000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.270000] NET: Registered protocol family 1
[    0.280000] rt-timer 10000100.timer: maximum frequency is 7324Hz
[    0.290000] alarmtimer alarmtimer: no of_node; not parsing pinctrl DT
[    0.290000] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.320000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.330000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.350000] msgmni has been set to 56
[    0.400000] io scheduler noop registered
[    0.410000] io scheduler deadline registered (default)
[    0.420000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.430000] serial8250 serial8250: no of_node; not parsing pinctrl DT
[    0.430000] pinctrl core: add 1 pinmux maps
[    0.430000] rt2880-pinmux pinctrl: found group selector 3 for uartlite
[    0.430000] rt2880-pinmux pinctrl: request pin 15 (io15) for 10000c00.uartlite
[    0.430000] rt2880-pinmux pinctrl: request pin 16 (io16) for 10000c00.uartlite
[    0.430000] console [ttyS0] disabled
[    0.440000] 10000c00.uartlite: ttyS0 at MMIO 0x10000c00 (irq = 20, base_baud = 2500000) is a 16550A
[    0.460000] console [ttyS0] enabled
[    0.470000] bootconsole [early0] disabled
[    0.490000] pinctrl core: add 1 pinmux maps
[    0.490000] pinctrl core: add 1 pinmux maps
[    0.490000] rt2880-pinmux pinctrl: found group selector 1 for spi
[    0.490000] rt2880-pinmux pinctrl: found group selector 6 for spi_cs1
[    0.490000] rt2880-pinmux pinctrl: request pin 3 (io3) for 10000b00.spi
[    0.490000] rt2880-pinmux pinctrl: request pin 4 (io4) for 10000b00.spi
[    0.490000] rt2880-pinmux pinctrl: request pin 5 (io5) for 10000b00.spi
[    0.490000] rt2880-pinmux pinctrl: request pin 6 (io6) for 10000b00.spi
[    0.490000] rt2880-pinmux pinctrl: request pin 27 (io27) for 10000b00.spi
[    0.500000] m25p80 spi32766.0: found w25q32, expected f25l32pa
[    0.510000] m25p80 spi32766.0: w25q32 (4096 Kbytes)
[    0.520000] 4 ofpart partitions found on MTD device spi32766.0
[    0.540000] Creating 4 MTD partitions on "spi32766.0":
[    0.550000] 0x000000000000-0x000000030000 : "u-boot"
[    0.560000] 0x000000030000-0x000000040000 : "devdata"
[    0.570000] 0x000000040000-0x000000050000 : "factory"
[    0.580000] 0x000000050000-0x000000400000 : "firmware"
[    0.650000] 2 seama-fw partitions found on MTD device firmware
[    0.660000] 0x000000050000-0x000000170000 : "kernel"
[    0.670000] 0x000000170000-0x000000400000 : "rootfs"
[    0.680000] mtd: device 5 (rootfs) set to be root filesystem
[    0.700000] 1 squashfs-split partitions found on MTD device rootfs
[    0.710000] 0x0000003b0000-0x000000400000 : "rootfs_data"
[    0.730000] ralink_soc_eth 10100000.ethernet eth0: ralink at 0xb0100000, irq                                             5
[    0.740000] rt2880_wdt 10000120.watchdog: Initialized
[    0.750000] TCP: cubic registered
[    0.760000] NET: Registered protocol family 10
[    0.770000] NET: Registered protocol family 17
[    0.780000] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[    0.810000] 8021q: 802.1Q VLAN Support v1.8
[    0.860000] VFS: Mounted root (squashfs filesystem) readonly on device 31:5.
[    0.870000] Freeing unused kernel memory: 172K (80335000 - 80360000)
[    4.290000] init: Console is alive
[    4.300000] init: - watchdog -
[    6.730000] usbcore: registered new interface driver usbfs
[    6.740000] usbcore: registered new interface driver hub
[    6.750000] usbcore: registered new device driver usb
[    6.760000] rt2880-pinmux pinctrl: request pin 10 (io10) for pio:10
[    6.760000] rt2880-pinmux pinctrl: request pin 0 (io0) for pio:0
[    6.770000] rt2880-pinmux pinctrl: request pin 9 (io9) for pio:9
[    6.770000] rt2880-pinmux pinctrl: request pin 13 (io13) for pio:13
[    7.300000] init: - preinit -
[    8.540000] rt305x-esw 10110000.esw: link changed 0x00
[    8.870000] random: procd urandom read with 13 bits of entropy available
[   10.160000] rt305x-esw 10110000.esw: link changed 0x08
[   12.430000] jffs2: notice: (311) jffs2_build_xattr_subsystem: complete building xattr subsystem, 1 of xdatum (0 unchecked, 0 orphan) and 11 of xref (0 dead, 2 orphan) found.
[   12.470000] mount_root: overlay filesystem has not been fully initialized yet
[   12.580000] mount_root: switching to jffs2 overlay
[   12.650000] procd: - early -
[   12.650000] procd: - watchdog -
[   13.800000] procd: - ubus -
[   14.810000] procd: - init -
[   15.920000] gre: GRE over IPv4 demultiplexor driver
[   15.930000] ip_gre: GRE over IPv4 tunneling driver
[   15.950000] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   16.020000] Loading modules backported from Linux version master-2015-10-26-0-g28c26cb
[   16.040000] Backport generated by backports.git backports-20150903-4-g12cf266
[   16.070000] ip_tables: (C) 2000-2006 Netfilter Core Team
[   16.120000] nf_conntrack version 0.5.0 (451 buckets, 1804 max)
[   16.250000] xt_time: kernel timezone is -0000
[   16.360000] cfg80211: World regulatory domain updated:
[   16.370000] cfg80211:  DFS Master region: unset
[   16.380000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gan, max_eirp), (dfs_cac_time)
[   16.400000] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   16.420000] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   16.430000] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[   16.450000] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[   16.470000] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[   16.490000] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[   16.500000] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[   16.520000] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[   16.670000] PPP generic driver version 2.4.2
[   16.680000] NET: Registered protocol family 24
[   16.740000] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5350, rev 0500 detected
[   16.760000] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 5350 detected
[   16.770000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   22.750000] rt305x-esw 10110000.esw: link changed 0x00
[   24.390000] rt305x-esw 10110000.esw: link changed 0x08
[   30.320000] device eth0.1 entered promiscuous mode
[   30.330000] device eth0 entered promiscuous mode
[   30.360000] br-lan: port 1(eth0.1) entered forwarding state
[   30.370000] br-lan: port 1(eth0.1) entered forwarding state
[   32.370000] br-lan: port 1(eth0.1) entered forwarding state
[   75.880000] random: nonblocking pool is initialized

All leds are in place.
Maybe I'll try to see if I can make it flashable using original web interface

Regards!

(Last edited by jcook on 11 Nov 2015, 01:09)

I have the D-600 B6(!) with 2.18 stock firmware. I have tried 3 different firmwares, but none of them work.

I have tried

openwrt-ramips-rt305x-dir-600-b5-squashfs-factory.bin
https://mega.nz/#!7VISEDBD!6Nl-6f4NwmY7 … 0P4yo2eHwk
md5: b2a0f39930e2805ded2fd62dde0bd15c

among two others.

After flashing it is impossible to contact it through cable. I've had to use emergency rescue to flash back to original again.

Can anyone help me out?

OMG! I finally managed to flash OpenWrt firmware. Thank you so much MasterX1987!

I have DIR-300 EEU B5 Ver.:2.11 (flashed with DIR-600 B5 2.18 firemware).
First I tried flashing "openwrt-15.05-ramips-rt305x-dir-300-b7-initramfs-uImage.bin" right through Emergency Web Interface as described in OpenWrt wiki but I had "invalid image" message. The only image I managed to flash before was "DIR-600_Bx_FW218WWb01.bin" (for DIR-600 B5 Ver.:2.18) from D-link support site...

1. I successfully flashed MasterX1987’s Frimware (dir600b_v2.17_bbox-v1.19.1.bin) using emergency room (it didn’t work with Chrome, but it worked in Firefox...)

2. Started http server on my computer (192.168.0.2) and put "openwrt-15.05-ramips-rt305x-dir-300-b7-initramfs-uImage.bin (from OpenWrt downloads page) to the servers's web folder

3.
$ telnet 192.168.0.1 2323
$ cd /var
$ wget http://192.168.0.2/openwrt-15.05-ramips … initramfs-uImage.bin
$ busybox flashcp openwrt-15.05-ramips-rt305x-dir-300-b7-initramfs-uImage.bin /dev/mtd/2
# Now don't turn off device or you get a brick! .... After 1-2 min the Command are finished. You see it when a new Line are displayed. ( e.g. $ )
$ reboot -f    # Now Reboot ...

4. Changed my computer's IP to 192.168.1.2 and browsed to 192.168.1.1 and OpenWrt 15.05 was there!!!! But WiFi didn’t work  - I enabled it, the LED went green, but there was no SSID on the air. Then from OpenWrt web UI I tried flashing “openwrt-15.05-ramips-rt305x-dir-300-b7-squashfs-sysupgrade.bin”, but it didn’t help - still no WiFi.

5. Finally flashed “openwrt-ramips-rt305x-dir-610-a1-squashfs-sysupgrade.bin” from OpenWrt web UI and it works great (WiFi is OK)...

(Last edited by dicoka on 30 Nov 2015, 14:42)

Maybe someone knows why Wifi is not functional on DIR-300 B5 flashed with  15.05 and 14.07 b7 images from OpenWrt site and if anything can be done with that?

“openwrt-ramips-rt305x-dir-610-a1-squashfs-sysupgrade.bin” works great, but I don't have packages I need for this trunk.
Maybe someone knows where the packages can be found?

dicoka wrote:

OMG! I finally managed to flash OpenWrt firmware. Thank you so much MasterX1987!

I have DIR-300 EEU B5 Ver.:2.11 (flashed with DIR-600 B5 2.18 firemware).
First I tried flashing "openwrt-15.05-ramips-rt305x-dir-300-b7-initramfs-uImage.bin" right through Emergency Web Interface as described in OpenWrt wiki but I had "invalid image" message. The only image I managed to flash before was "DIR-600_Bx_FW218WWb01.bin" (for DIR-600 B5 Ver.:2.18) from D-link support site...

1. I successfully flashed MasterX1987’s Frimware (dir600b_v2.17_bbox-v1.19.1.bin) using emergency room (it didn’t work with Chrome, but it worked in Firefox...)

2. Started http server on my computer (192.168.0.2) and put "openwrt-15.05-ramips-rt305x-dir-300-b7-initramfs-uImage.bin (from OpenWrt downloads page) to the servers's web folder

3.
$ telnet 192.168.0.1 2323
$ cd /var
$ wget http://192.168.0.2/openwrt-15.05-ramips … initramfs-uImage.bin
$ busybox flashcp openwrt-15.05-ramips-rt305x-dir-300-b7-initramfs-uImage.bin /dev/mtd/2
# Now don't turn off device or you get a brick! .... After 1-2 min the Command are finished. You see it when a new Line are displayed. ( e.g. $ )
$ reboot -f    # Now Reboot ...

4. Changed my computer's IP to 192.168.1.2 and browsed to 192.168.1.1 and OpenWrt 15.05 was there!!!! But WiFi didn’t work  - I enabled it, the LED went green, but there was no SSID on the air. Then from OpenWrt web UI I tried flashing “openwrt-15.05-ramips-rt305x-dir-300-b7-squashfs-sysupgrade.bin”, but it didn’t help - still no WiFi.

5. Finally flashed “openwrt-ramips-rt305x-dir-610-a1-squashfs-sysupgrade.bin” from OpenWrt web UI and it works great (WiFi is OK)...

After I flash the dir600b_v2.17_bbox-v1.19.1.bin my router doesn't seem to be working on any lan ports.

My only working port is WAN and I can't use telnet on it.

How did you get it to work? Was your LAN port working after flashing the bin?

ryuchetval wrote:

After I flash the dir600b_v2.17_bbox-v1.19.1.bin my router doesn't seem to be working on any lan ports.
My only working port is WAN and I can't use telnet on it.
How did you get it to work? Was your LAN port working after flashing the bin?

Just keep trying. Maybe change browser. With all my experiments sometimes it didn't work after emergency room and dir600b_v2.17_bbox-v1.19.1.bin.
When flashed successfully LAN ports should be working with D-Link v2.17 web interface on 192.168.0.1 and telnet on 192.168.0.1:2323.

(Last edited by dicoka on 2 Dec 2015, 09:01)

dicoka wrote:

Maybe someone knows why Wifi is not functional on DIR-300 B5 flashed with  15.05 and 14.07 b7 images from OpenWrt site and if anything can be done with that?

“openwrt-ramips-rt305x-dir-610-a1-squashfs-sysupgrade.bin” works great, but I don't have packages I need for this trunk.
Maybe someone knows where the packages can be found?

By the way, today I flashed my DIR-300 B5 with Zyxel Keenetic Start firmware, and it works perfectly and it has all functionality I need. It's told to work much better than original d-link firmware and its web interface is just great. I think I'll stick with it until there's OpenWrt with no WiFi problem.

I flashed the Keenetic image from MasterX1987’s frimware through telnet, wget and busybox.
When flashed it's on 192.168.1.1. It had Russian interface which can be changed to English by drop down menu on upper right corner.
And I updated it from web interface with last version firmware from Zyxel Russia site.

(Last edited by dicoka on 6 Dec 2015, 07:42)

dicoka wrote:

OMG! I finally managed to flash OpenWrt firmware. Thank you so much MasterX1987!

I have DIR-300 EEU B5 Ver.:2.11 (flashed with DIR-600 B5 2.18 firemware).
First I tried flashing "openwrt-15.05-ramips-rt305x-dir-300-b7-initramfs-uImage.bin" right through Emergency Web Interface as described in OpenWrt wiki but I had "invalid image" message. The only image I managed to flash before was "DIR-600_Bx_FW218WWb01.bin" (for DIR-600 B5 Ver.:2.18) from D-link support site...

1. I successfully flashed MasterX1987’s Frimware (dir600b_v2.17_bbox-v1.19.1.bin) using emergency room (it didn’t work with Chrome, but it worked in Firefox...)

2. Started http server on my computer (192.168.0.2) and put "openwrt-15.05-ramips-rt305x-dir-300-b7-initramfs-uImage.bin (from OpenWrt downloads page) to the servers's web folder

3.
$ telnet 192.168.0.1 2323
$ cd /var
$ wget http://192.168.0.2/openwrt-15.05-ramips … initramfs-uImage.bin
$ busybox flashcp openwrt-15.05-ramips-rt305x-dir-300-b7-initramfs-uImage.bin /dev/mtd/2
# Now don't turn off device or you get a brick! .... After 1-2 min the Command are finished. You see it when a new Line are displayed. ( e.g. $ )
$ reboot -f    # Now Reboot ...

4. Changed my computer's IP to 192.168.1.2 and browsed to 192.168.1.1 and OpenWrt 15.05 was there!!!! But WiFi didn’t work  - I enabled it, the LED went green, but there was no SSID on the air. Then from OpenWrt web UI I tried flashing “openwrt-15.05-ramips-rt305x-dir-300-b7-squashfs-sysupgrade.bin”, but it didn’t help - still no WiFi.

5. Finally flashed “openwrt-ramips-rt305x-dir-610-a1-squashfs-sysupgrade.bin” from OpenWrt web UI and it works great (WiFi is OK)...

Hi dicoka. I successfully used your method to flash a DIR-600 B6 Software version 2.17. Many thanks. However, as others have noticed, this is a Barrier Breaker version, and none of the Chaos Calmer versions seem to work on this router. The update is successful, but then the router freezes upon reboot, with strange combinations of lights -- as reported by ryuchetval. Does anyone know whether there is a Chaos Calmer version that would upgrade Barrier Breaker for this hardware ? Last post was in December, maybe there has been some other activity since ? Tks.

Edit: It was dicoka, not ryuchetval who talked about the problems with Chaos Calmer (dir-300-b7).

(Last edited by dutchbrickball on 20 Jan 2016, 19:24)

Many Thanks dikota . I finally found the way to install openwrt-15.05 chaos calmer for the dir 300-b7 on my two routers DIR-600 b6. The fisrt install wasn't successfull but was ok on the other router.

First : install (point 1 to 3) on a proper install (software version 2.18) and with the wifi enabled (important). After you just have to do a system upgrade (point 4) and it's ok !

Hi Hi MasterX1987,

I follow your procedure and apparently it worked perfectly, but something it's not ok.
Every time I reboot the device I lose everything...

I tried sysupgrade with -F option many times, all of them apparently successfully. but at every reboot the key changes, password lost, and so on...

did you experienced something similar?

Thanks
Paolo

MasterX1987 wrote:

==========================================
My NFS-Server + Webhost Folder is: /var/www .In there is a Subfolder who called dlink, witch the openwrt.img's are copied into it...
($ cp openwrt-ramips-rt305x-dir-610-a1-squashfs-sysupgrade.bin openwrt-ramips-rt305x-dir-610-a1-initramfs-uImage.bin /var/www/dlink/
[ ! Don't forget the right chmod + chown ! ]
$ sudo chown -R nobody:nogroup /var/www/dlink && sudo chmod -R 777 /var/www/dlink )

So when you finished all downloads and maked your Server Live,  you are ready to bring it On:
1. Flash MyBuild Frimware (dir600b_v2.17_bbox-v1.19.1.bin) to device. (You can use the emergency room or the normal Upload Site from the router...)
2. After the Router is rebooted you can connect via telnet to your device:
$ telnet 192.168.0.1 2323
3. When you connected you need to upload the uImage.bin to device. (Via wget | tftp | ftp get/put | nfs-mount ...)
    In this case I used nfs-mount to flash it:
$ mount -o nolock -t nfs 192.168.0.2:/var/www /home
$ cd /home/dlink
$ busybox flash_unlock /dev/mtd/2 # don't use /dev/mtdblock/2, this is the wrong path to flash!
$ busybox flashcp openwrt-ramips-rt305x-dir-610-a1-initramfs-uImage.bin /dev/mtd/2
# Now don't turn off device or you get a brick! .... After 1-2 min the Command are finished. You see it when a new Line are displayed. ( e.g. $ )
$ reboot -f    # Now Reboot ...
After that the Power LED goes On, then Off, then blinking 5-10 sec... In that time when its blinking the LED for the first LAN should me lights UP. (... e.g. Your PC is connect to it ... ^^)
Now at the end of booting device the Power+LAN1 Lights are ON.
4. Then the Openwrt Web Interface are available @ 192.168.1.1 . Your PC you gived the IP: 192.168.1.2 .
You can now flash the openwrt-ramips-rt305x-dir-610-a1-squashfs-sysupgrade.bin Firmware to Device... !
After the next Reboot, IT DONE !!!!

Now Have fun with the Next Generation Firmware: Openwrt :-D

Hello,
I bought this router with the goal of installing upon it OpenWRT. I find this post very useful, but at the end my dlink is bricked (and I'm unable to unbrick).
Here is my story:
1) I followed the passages above. After some problems I was able to flash via telnet the first firmware.
2) I can't download the second, so I searched and downloaded from Openwrt website. I flashed through ssh using force option
3) After flashing I CANNOT access via webgui but I can access via ssh and Openwrt seems to be installed.
4) I manually installed Luci and basic packages
5) The webgui started to work. I setup wan connection and wireless to. All works well. I cannot access to the openwrt via wireless but I think is a security option, I'm wrong?
6) I donwload the package list via webgui. Then I tried to install some packages but the router says that there is no space left on device even if there are at least 70% or memory free. This turn on a light in my mind...
7)...I tried to reboot... all was deleted, included the webgui. So I have to restart from point 4
8) To try to solve this problem I downloaded the second file on post 37 (which I didn't see before) and I flashed it with -F parameter
9) From this point my router is bricked. I cannot connect nor ping nor telnet nor ssh. I tried to remove power, keep reset pressed, and plug to power for 5 seconds for the emergency recovery. But the power led continue to blink with no result.

Anyone can help me to unbrick the device and... maybe, to install openwrt again in a manner that save the changes?

Thanks a lot,
Jacopo

The discussion might have continued from here.