D-Link Forums

The Graveyard - Products No Longer Supported => Routers / COVR => DIR-685 => Topic started by: atarian on March 06, 2013, 05:00:26 AM

Title: DIR-685 Firmware development ressurection
Post by: atarian on March 06, 2013, 05:00:26 AM
As many of you, I have been dealing with all the annoyances and issues of DIR-685 router. I was living in a hope that eventually, D-Link will fix all the issues with firmware, but as we know it never actually happend and DIR-685 was simply marked as EOL.
Afer a while, I have chosen to pick up where D-Link dropped and decided to continue releasing bugfix firmwares on my own, if possible.

So last month I have downloaded sources from D-Link website, setup new build enviroment box and went ahead only to realise its just a complete mess that will not even compile at all.
Long story short, it took me three weeks to fix entire mess into the point it actually compiles and produces valid firmware images.

So I am happy to announce first beta release of DIR-685 ressurection firmware, revision R0.9 with following changes from original D-Link source packages (whose appear to be as old as 1.01 from 2005):

r0.90: 20130306
fix: build process fixes: done      
     (finally, whole build now does make and make clean w/o errors; this was actually quite a challenge)
rem: bogus text files on rootfs: done
     (to save precious fs space with a goal to unify NA and WW images and possibly to include more features)
upg: freetype-2.3.8 -> 2.4.11: done
     (just proof of concept, verification of build process. no biggy.)
fix: libiconv-1.9.1 -> 1.14: done
     (fix situations, where UTF-8 encoded filenames are not displayed corretly on NAS fs, FTP fs and iTunes server)
fix: samba-3.0.25a -> 3.6.12: done
     (get rid of nasty POSIX on-access log errors on Linux box, increase reliability of SMB server)
upg: hdpardm-8.9 -> 9.43: done
     (a prerequisity needed for future NAS speed improvement)
rem: optimize router OSD pictures:done
     (entire OSD pics folder directfb/images occupied over 2MB of space, now its below 300kB)
upg: zlib-1.2.1 -> 1.2.7:done
     (security fixes, mainly: www.kb.cert.org/vuls/id/238678 and www.kb.cert.org/vuls/id/680620)
upg: ligpng-1.2.25 -> 1.5.14:done
     (performance improvements and security fixes)
upg: directFB 1.1.1 -> 1.4.9:done
     (performance and stability improvements)
upg: jpeg v6 -> v9:done
     (support for JPEG200 pictures, bugfixes)
upg: l7-protocols 2008 -> 2009:done
     (firewall rules upgrade)
fix: missing /var/log directory:done
     (router logs should now be available)

r0.91 (maitenance release): 20130310
fix: more build process fixes and cleanups: done      
     (smartmon and ntfstools related fixes, /lib & /etc clean-ups, binaries and libraries are now stripped)
upg: gdbm 1.8.3 -> 1.10: done
     (maitenance and bugfix upgrade)
upg: libid3tag 0.15.0 -> 0.15.1b: done
     (maitenance and bugfix upgrade)
upg: libgsasl 0.2.6 -> 1.8.0: done
     (to support authentification methods of modern OSes)
upg: wireless_tools 26 -> 29: done
     (wireless connectivity improvements)
upg: openssl 0.9.8g -> 1.0.1e: done
     (improved ssl security)
fix: samba rebuilt with essential functions only: done
     (to save some more rootfs space)
del: iTunes server disabled by default: done
     (currently used server is obsolete, unmaintained since 2008 incompatible with iTunes >= 10)

todo:
upg: iptables-1.3.5 -> ?
upg: iproute2-2.6.8 -> ?
upg: dhcp server
     to decrease time DIR-685 needs to assign an IP adddress to host. a huge motivation factor for me.
upg: busybox 1.0.1 -> ?
fix: add fsck command into build
     a prerequisity for later
fix: force fsck during HDD mount
     currently, every power surge or forced unmount leave NAS HDD unsanitised untill eventually, NAS HDD fs fails and needs to be checked-fixed on Linux box
imp: framechannel UI replacement
     Framechannel service is no longer available, to be replaced with available option (i.e. FrameAlbum?)
imp: bittorrent-sdk UI
upg: ssh/telnet enable (temporarly)
upg: kernel 2.6
imp: enable ext4 fs support for nas
upg: pureftp
imp: more build process fixes
     support for recent make (3.82) version
fix: all nasty security holes in http interface
merge USA and WW builds - get rid of CUSTOMER_DUSA race conditions
include more languages, if there is a demand
include http server, if there is a demand
replace as much D-LINK closed-source stuff with GPL alternatives as possible

So why do I post this on public forum? Maintaing such a software package is a huge task for single person with limited knowledge and capacities. Therfor, I would like not only to share my progress and work results with you, but I would also appreciate any help from you.
So if you are tester, GUI desiger, PHP programmer, or just an experienced linux user who knows how to get around various issues with compilation from source, please drop me an email: atarian@seznam.cz

I will also appreciate your suggestions for next releases, if you do have any, lets discuss them here.

Download sources and firmware builds here: https://mega.co.nz/#F!gFhwTKjY!DKL_Xj5chXRNfDFKWiKgpA (https://mega.co.nz/#F!gFhwTKjY!DKL_Xj5chXRNfDFKWiKgpA)

Disclaimer: Use at your own risk. I take no responsibiliies for possible damage to your device.
Title: Re: DIR-685 Firmware development ressurection
Post by: ambercap on March 06, 2013, 10:06:59 AM
Hi atarian. I found a bug on the DIR-645 that I couldn't wait for D-Link to fix. So I also decided to download the 1.01 GPL source and build a fixed version. It is a different model of router to yours but the process must be very similar. In my case I built it on the exact version of Fedora that they requested in the GPL readme and it built first time without any errors at all. However the latest f/w 1.03 is newer than the GPL version so I landed up rather extracting the already compiled kernel from the newest f/w and the rootfs and I just changed the files I needed.
Title: Re: DIR-685 Firmware development ressurection
Post by: ph0enix on March 06, 2013, 04:54:44 PM
 :o you manage to compile the source code, this looks promising  ;D
Title: Re: DIR-685 Firmware development ressurection
Post by: ambercap on March 07, 2013, 04:47:58 AM
Here are the steps I used:
I downloaded and installed VirtualBox from Oracle (free).
The GPL readme.txt says:
  Install fedora linux 10 (choose Software Development) on 32bit CPU.
Fedora 10 is EOL so you can't find it on their website anymore, but I did manage to find a torrent for this which worked (took about 8 hours to download)!
So I created a new Fedora VM in VirtualBox with 1GB memory installed and 8GB dynamic HDU, with Fedora 10 32-bit, and selected the install options for "Software Development".
After installing system updates, I then followed the remaining instructions exactly:
Copy the DIR645.tar.gz file to ~/
cd ~
tar zxvf DIR645.tar.gz
cd DIR645

Then run su to become root.
cp -rf mipsel_gcc-4.3.3_uclibc-0.9.30.1 /opt
rpm -ivh ./build_gpl/fakeroot-1.9.7-18.fc10.i386.rpm
Then exit su

source ./setupenv
Then run make 3 times:
make
make
make
Enter yes to build the kernel and choose defaults
F/w will be in ./images/.
Title: Re: DIR-685 Firmware development ressurection
Post by: atarian on March 10, 2013, 07:48:43 AM
new release 0.91 ready, see first post for details and changelog
Title: Re: DIR-685 Firmware development ressurection
Post by: stukka on March 11, 2013, 03:33:28 AM
about what fw are we talking?
the na or the european one?
Title: Re: DIR-685 Firmware development ressurection
Post by: atarian on March 12, 2013, 12:24:06 PM
You can build is as both NA or WW, just edit .config in your root build directory. Actually the only difference between the two is that WiFi b is disabled for NA build and mediaserver ui is disabled for WW.
Title: Re: DIR-685 Firmware development ressurection
Post by: Hard Harry on March 12, 2013, 02:57:42 PM
Hmm, even though I don't have anything against it (I think its great) may want to be careful how public you make this. Fixing a bug is one thing, rewriting firmware and offering it on a public Dlink forum..might raise some red flags with Dlink and their IP lawyers. Just FYI. Then again, if the Mods are cool with it...
Title: Re: DIR-685 Firmware development ressurection
Post by: Hard Harry on March 13, 2013, 05:55:16 PM
Actually, I had a thought. Could this same method of data extraction give insight on how some of the DIR-685's features work? Like DNS relay, QoS, DMZ and such? I think it could really help me and the other guys troubleshoot better. Like to actually know how Dlink implemented it beyond what the Support definition says.

BTW, seems like you guys blew in from another forum? Blackhat? Very impressive.
Title: Enabling 5 GHz band request and other development tips
Post by: albert.zweistein on March 14, 2013, 04:11:52 PM
Great work so far.

I'd like to add some features that might be useful to develop:


Title: Re: DIR-685 Firmware development ressurection
Post by: FurryNutz on March 14, 2013, 04:28:44 PM
Let us know if any actual Builds will be done for those who don't have all the coding programs loaded. Just interested in the .bin file to send to the router to test.
Title: Re: DIR-685 Firmware development ressurection
Post by: atarian on March 15, 2013, 03:49:10 PM
Fixing a bug is one thing, rewriting firmware and offering it on a public Dlink forum..
You might want to learn a bit about GPL. Once Dlink decided to build their routers on GNU system, they agreed to the terms of GPL.
Title: Re: Enabling 5 GHz band request and other development tips
Post by: atarian on March 15, 2013, 03:59:25 PM
I'd like to add some features that might be useful to develop:
  • According to this review http://www.smallnetbuilder.com/wireless/wireless-reviews/30864-smashed-mash-up-d-link-dir-685-reviewed?start=1 (http://www.smallnetbuilder.com/wireless/wireless-reviews/30864-smashed-mash-up-d-link-dir-685-reviewed?start=1) DIR-685 is equiped with RT2850L 2.4/5 GHz 2T3R dual band transciever. It would be great to have the 5 GHz enabled or even better simultaneous 2.4 and 5 GHZ bands running together.
I will take a look at driver eventually.

  • Also it would be great to improve performance of the built-in NAS drive access. I observed improvement from 3 MB/s to 6 MB/s (on 7200 RPM disk) with some later FW, however it is still too slow. I never tested connection to another drive using USB, but I'd love to and get some meaningful data transfer perfromance.
That is one of the goals. This will however require kernel update too. Userspace program needed (HDPARM) is part of the image already.

  • USB ports might be nice to utilize the 3G modem, but my country/phone provider isn't listed in the settings and I think it would be good to have this feature fully parameterizable.
This is actually aready in image, only not compiled by default. However, I do not own 3G modem so I will be able to build and test. Someone else has to help.

  • Or even capability of usb tethering from an Android phone.
  • 12/24h time on display with various formats of date
  • Maybe some unused or obsolete media features might be removed to save space and computing capacity or be updated
Working on that. Check todo.
Title: Re: DIR-685 Firmware development ressurection
Post by: Hard Harry on March 17, 2013, 12:23:40 AM
You might want to learn a bit about GPL. Once Dlink decided to build their routers on GNU system, they agreed to the terms of GPL.

Alright then. Excuse my ignorance. I really like what your doing overall, sorry I over reacted, just never saw a thread like this on this forum. Still feels like you guys jumped over from another forum, but what ever, glad to have ya. :-)
Title: Re: DIR-685 Firmware development ressurection
Post by: txdk on April 08, 2013, 02:46:05 PM
is it just me or where is the link to the file i can't see anything in the builds folder
Title: Re: DIR-685 Firmware development ressurection
Post by: Paul2 on April 13, 2013, 01:54:16 AM
Hi, I'm trying to compile this firmware with fedora 18 but i get always this error:
Code: [Select]
make[6]: Entering directory `/home/paul/builds/dir685/progs.gpl/fuse/fuse-2.9.2/lib'
  CC     fuse.lo
  CC     fuse_kern_chan.lo
  CC     fuse_loop.lo
  CC     fuse_loop_mt.lo
  CC     fuse_lowlevel.lo
  CC     fuse_mt.lo
  CC     fuse_opt.lo
  CC     fuse_session.lo
  CC     fuse_signals.lo
  CC     buffer.lo
  CC     cuse_lowlevel.lo
  CC     helper.lo
  CC     subdir.lo
  CC     iconv.lo
modules/iconv.c:17:19: iconv.h: No such file or directory
modules/iconv.c:27: error: syntax error before "iconv_t"
modules/iconv.c: In function `iconv_convpath':
modules/iconv.c:66: error: dereferencing pointer to incomplete type
modules/iconv.c:68: error: dereferencing pointer to incomplete type
modules/iconv.c:68: error: dereferencing pointer to incomplete type
modules/iconv.c:90: error: dereferencing pointer to incomplete type
modules/iconv.c:96: error: dereferencing pointer to incomplete type
modules/iconv.c:96: error: dereferencing pointer to incomplete type
modules/iconv.c:97: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_getattr':
modules/iconv.c:108: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_fgetattr':
modules/iconv.c:121: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_access':
modules/iconv.c:133: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_readlink':
modules/iconv.c:145: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_opendir':
modules/iconv.c:166: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_readdir':
modules/iconv.c:196: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_releasedir':
modules/iconv.c:209: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_mknod':
modules/iconv.c:221: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_mkdir':
modules/iconv.c:233: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_unlink':
modules/iconv.c:245: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_rmdir':
modules/iconv.c:257: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_symlink':
modules/iconv.c:272: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_rename':
modules/iconv.c:289: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_link':
modules/iconv.c:306: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_chmod':
modules/iconv.c:320: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_chown':
modules/iconv.c:332: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_truncate':
modules/iconv.c:344: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_ftruncate':
modules/iconv.c:357: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_utimens':
modules/iconv.c:369: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_create':
modules/iconv.c:382: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_open_file':
modules/iconv.c:394: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_read_buf':
modules/iconv.c:407: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_write_buf':
modules/iconv.c:420: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_statfs':
modules/iconv.c:432: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_flush':
modules/iconv.c:444: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_release':
modules/iconv.c:456: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_fsync':
modules/iconv.c:469: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_fsyncdir':
modules/iconv.c:482: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_setxattr':
modules/iconv.c:495: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_getxattr':
modules/iconv.c:509: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_listxattr':
modules/iconv.c:521: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_removexattr':
modules/iconv.c:533: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_lock':
modules/iconv.c:546: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_flock':
modules/iconv.c:558: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_bmap':
modules/iconv.c:570: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_init':
modules/iconv.c:579: error: dereferencing pointer to incomplete type
modules/iconv.c: In function `iconv_destroy':
modules/iconv.c:586: error: dereferencing pointer to incomplete type
modules/iconv.c:587: error: dereferencing pointer to incomplete type
modules/iconv.c:588: error: dereferencing pointer to incomplete type
modules/iconv.c:589: error: dereferencing pointer to incomplete type
modules/iconv.c:590: error: dereferencing pointer to incomplete type
modules/iconv.c:591: error: dereferencing pointer to incomplete type
modules/iconv.c: At top level:
modules/iconv.c:641: error: dereferencing pointer to incomplete type
modules/iconv.c:641: error: initializer element is not constant
modules/iconv.c:641: error: (near initialization for `iconv_opts[2].offset')
modules/iconv.c:641: error: initializer element is not constant
modules/iconv.c:641: error: (near initialization for `iconv_opts[2]')
modules/iconv.c:642: error: dereferencing pointer to incomplete type
modules/iconv.c:642: error: initializer element is not constant
modules/iconv.c:642: error: (near initialization for `iconv_opts[3].offset')
modules/iconv.c:642: error: initializer element is not constant
modules/iconv.c:642: error: (near initialization for `iconv_opts[3]')
modules/iconv.c:643: error: initializer element is not constant
modules/iconv.c:643: error: (near initialization for `iconv_opts[4]')
modules/iconv.c: In function `iconv_new':
modules/iconv.c:681: error: invalid application of `sizeof' to incomplete type `iconv'
modules/iconv.c:695: error: dereferencing pointer to incomplete type
modules/iconv.c:695: error: dereferencing pointer to incomplete type
modules/iconv.c:696: error: dereferencing pointer to incomplete type
modules/iconv.c:696: error: dereferencing pointer to incomplete type
modules/iconv.c:700: error: dereferencing pointer to incomplete type
modules/iconv.c:701: error: dereferencing pointer to incomplete type
modules/iconv.c:701: error: `iconv_t' undeclared (first use in this function)
modules/iconv.c:701: error: (Each undeclared identifier is reported only once
modules/iconv.c:701: error: for each function it appears in.)
modules/iconv.c:706: error: dereferencing pointer to incomplete type
modules/iconv.c:707: error: dereferencing pointer to incomplete type
modules/iconv.c:717: error: dereferencing pointer to incomplete type
modules/iconv.c:725: error: dereferencing pointer to incomplete type
modules/iconv.c:727: error: dereferencing pointer to incomplete type
modules/iconv.c:729: error: dereferencing pointer to incomplete type
modules/iconv.c:730: error: dereferencing pointer to incomplete type
make[6]: *** [iconv.lo] Error 1
make[6]: Leaving directory `/home/paul/builds/dir685/progs.gpl/fuse/fuse-2.9.2/lib'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory `/home/paul/builds/dir685/progs.gpl/fuse/fuse-2.9.2'
make[4]: *** [all] Error 2
make[4]: Leaving directory `/home/paul/builds/dir685/progs.gpl/fuse'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/home/paul/builds/dir685/progs.gpl'
make[2]: *** [progs] Error 2
make[2]: Leaving directory `/home/paul/builds/dir685'
make[1]: *** [all_without_kernel] Error 2
make[1]: Leaving directory `/home/paul/builds/dir685'
make: *** [all] Error 2
[paul@localhost dir685]$


Many thanks ;)
Title: Re: DIR-685 Firmware development ressurection
Post by: ambercap on April 13, 2013, 02:10:25 AM
It looks like you don't have the package iconv-devel installed. Are you using a 32-bit build of Fedora 18? If 64-bit then I can't see it working easily. Doesn't iconv-devel ship with glibc? Maybe you're picking up the wrong version on Fedora 18? Which version of Fedora does the GPL code ask for? Isn't it Fedora 10?
Title: Re: DIR-685 Firmware development ressurection
Post by: Paul2 on April 13, 2013, 02:34:50 AM
Thanks for your help!
I'm using standard 32bit version downloaded from fedora site.

Doesn't iconv-devel ship with glibc?

does not seem to

It looks like you don't have the package iconv-devel installed.

The only package available is "Development files for psiconv" and is installed :(

I will try with virtualbox which distro do you recommend?

Thanks again
Title: Re: DIR-685 Firmware development ressurection
Post by: Paul2 on April 13, 2013, 02:46:44 AM
Seems a fedora 18 bug
https://github.com/wayneeseguin/rvm/issues/1597
Title: Re: DIR-685 Firmware development ressurection
Post by: ambercap on April 13, 2013, 03:01:30 AM
I have not looked at the source for the 685, only the 645. For the 645 they explicitly state to use Fedora 10 in the readme. I would recommend using the Fedora version that is specified (assuming it is specified for the 685?). Since Fedora 10 is EOL I had to search for a torrent of it.
Title: Re: DIR-685 Firmware development ressurection
Post by: ambercap on April 13, 2013, 04:12:18 AM
I downloaded the DIR-685 GPL and see the readme does not mention which OS to build on. However I do see it mentions downgrading make to v3.80 if you get syntax errors, which implies Fedora 4 perhaps? Furthermore, the readme for the linux kernel mentions using gcc 2.95.3 which also would indicate an ancient distro of Fedora. So I'd try find a really old distro - certainly not 18 - unless you're prepared to try fix the source code to work with a newer version of make, gcc, and all the other libraries. I don't have access to my computer running Fedora 10 at this moment (my daughter is hogging it) but I could try the build when I have a chance and see if it works.
Title: Re: DIR-685 Firmware development ressurection
Post by: Paul2 on April 13, 2013, 04:26:24 AM
Thanks!

So I'd try find a really old distro - certainly not 18

You can find them here:
http://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/fedora/linux/releases/
Title: Re: DIR-685 Firmware development ressurection
Post by: TokTias on June 20, 2013, 06:52:00 PM
Wow ! This looks promising !
I am trying to compile with Fedora 10 (in VBox) but get stuck on this one :

Code: [Select]
make[6]: Entering directory `/home/me/builds/dir685/progs.gpl/fuse/fuse-2.9.2/lib'
  CCLD   libfuse.la
/opt/storlink_arm_920t_le_uclibc.20080713/usr/bin/arm-linux-uclibc-ld: cannot find -liconv
collect2: ld returned 1 exit status
make[6]: *** [libfuse.la] Error 1

I understand the iconv is included in gcc, so does anyone know what's going on here ?

Cheers !
Title: Re: DIR-685 Firmware development ressurection
Post by: otanger on August 23, 2013, 11:25:33 PM
I just wanted a date now with the new framephoto someone has already done?
Title: Re: DIR-685 Firmware development ressurection
Post by: kinkist on September 09, 2013, 09:57:13 PM
GPL source code has bug.

I using DIR-685 USA N/A A1 version.
this model using RTL8366SR.

after building custom firmware from GLP source, wan device did not working and system was hanged during booting.

because GPL souce has compiled RTL8366 driver but not has RTL8366SR driver.
- "boards/wrgns01/apps/rtl8366/rtl8366rb/switch.ko"

this driver will loaded at booting - "insmod /lib/modules/switch.ko"
but failed load this driver. (hang!)

I find switch.ko module on directory "/lib/modules" - that using dir685_fw_101NA.bin firmware file.
I could not found switch.ko module, this means RTL8366SR driver was built in kernel.

I extracted kernel.img from dir685_fw_101NA.bin and build custom firmware base GLB source and extracted kernel.img.


after this, I success "building custom firmware".
Title: Re: DIR-685 Firmware development ressurection
Post by: albert.zweistein on October 10, 2013, 06:14:13 AM
Kinkist, is your firmware mature enough to be tested in the device?

I have the international version of DIR-685.
Title: Re: DIR-685 Firmware development ressurection
Post by: kinkist on October 13, 2013, 07:34:56 PM
yes, my firmware is mature and it is tested on my device during 1 month.
but my device is N/A version of DIR-685.
my firmware is customized to N/A version.

this is my working log : https://mega.co.nz/#!Bko1Raya!SZtOKD82eU4XZ-piVczOCXbLNFUuS1cxaX8RBhF7pJE

Kinkist, is your firmware mature enough to be tested in the device?

I have the international version of DIR-685.
Title: Re: DIR-685 Firmware development ressurection
Post by: FREEEEMAN on December 10, 2013, 08:23:14 PM
Any updates/news on the new firmwares ?

What works better or bug fixed or ?

Title: Re: DIR-685 Firmware development ressurection
Post by: FurryNutz on December 13, 2013, 07:26:27 AM
Link>Welcome! (http://forums.dlink.com/index.php?topic=41537.0)


Any updates/news on the new firmwares ?

What works better or bug fixed or ?


Title: Re: DIR-685 Firmware development ressurection
Post by: Pajn on January 16, 2014, 11:33:04 AM
Great initiative!
However this project seems pretty dead, is it so?
There are no build available to download.
Title: Re: DIR-685 Firmware development ressurection
Post by: FurryNutz on January 16, 2014, 11:48:26 AM
The OP hasn't been on since summer of last year...You could PM him and see whats going on.
Title: Re: DIR-685 Firmware development ressurection
Post by: kinkist on May 24, 2014, 11:32:27 PM
I will share my GPL souce file.
this is customized to DIR-685 N/A version. if you using WWW version's router, you can not using this source.
(sorry, but My DIR-685 Router is N/A version)

Download URL : https://mega.co.nz/#F!klhi1KiJ!ifq5igdoxKPJywfN-rzc2Q

Change
- add tramsmission (Migrated from bt)
- add drobear for ssh
- add polipo
- upgrade samba 3.6.23

router has some bug(Memory issue), that is kernel issue.
before D-LINK release new kernel source of DIR-685, It will not fixed.
because, current GPL kernel source has not some driver souce.
Title: Re: DIR-685 Firmware development ressurection
Post by: FurryNutz on May 21, 2015, 10:45:04 AM
FYI:
http://forums.dlink.com/index.php?topic=56542.0 (http://forums.dlink.com/index.php?topic=56542.0)
Title: Re: DIR-685 Firmware development ressurection
Post by: FurryNutz on June 16, 2015, 10:39:14 AM
http://forums.dlink.com/index.php?topic=62876.0 (http://forums.dlink.com/index.php?topic=62876.0)