Well the tried and true build, which is in my signature link "Firmware Recommendations" is 13525, i personally use the latest Eko builds right now, which is 14826. Just consider the later builds to be test builds.
i'm trying to upgrade via the web gui to 13525 (a .chk file) but it's giving me an invalid file error when I click the upgrade button - am I missing something?
ok, think i figured it out - to upgrade from existing dd-wrt, I should use the generic .bins for the build right?
so if i wanted to get to the newest build, i'd flash with: dd-wrt.v24-14826_NEWD_mini.bin ?
also, are we restricted to mini's?
I think I was flashing to a newer standard nokaid version when I initially bricked it - although that could have been because I didn't do a 30-30-30 reset, I'm just afraid to do anything else now.
so would I be safe to put this ? (just want the newest & most features):
dd-wrt.v24-14826_NEWD_std-nokaid.bin 3.5 MB
so would I be safe to put this ? (just want the newest & most features):
dd-wrt.v24-14826_NEWD_std-nokaid.bin 3.5 MB
Check the file size in bytes after download, exact measure - not some rounded MB value, and compare to the max value for Netgear (see the sticky Peacock thread) _________________ Kernel panic: Aiee, killing interrupt handler!
okay, so just to make sure (don't want to risk bricking again) the firmware I'm about to flash to on my WNR834Bv2 is:
dd-wrt.v24-14826_NEWD_std-nokaid.bin
3.53 MB (3,706,880 bytes)
and according peacock thread it's below
"4MB flash chip Netgear routers: 3735552 bytes "
I would use the latest eko or bs beta build over the recommended build in the router database. I've read several top guns state that it isnt the best to go on(the router DB), some of the builds suggested aren't the best. First flash with the .chk if you dont have dd-wrt yet(stock router,eg), and then update to the newest std_nokaid file in the downloads - Other Downloads /others/eko/v24_tng/ directory and look for the newest date at the bottom. I always check the build number and search the forums for its related thread and see how its working for everyone whose been testing it first, esp if its the newest. But in most cases here for us, newer is better. Plus if you brick it you can always recover
Heres the forum thread for build 14583
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=73621&postdays=0&postorder=asc&start=0
But just download std_nokaid if you want the most features that you can fit. i believe the no_kaid is support for classic xbox networking features (correct me if im wrong) so not much missing compared to a std build. If you happen to use kaid, just download a mini build
just remember like the previous poster mentioned, NEWD build only
I hope this helps someone out![/url]
damn you ! i followed your instructions to upgrade using bin (from previous mini version) and it bricked my router. is the only way to unbrick involving taking it apart and putting wires on it? sigh
Tried the above on my 2nd router and bricked that one 2. Yay for 2 brick routers.
Hello everyone. I haven't visited this thread in ages, and I just wanted to share my experience with upgrading from 13000 to 14853 (vpn-small). The only issue I encountered involved Static Leases. It appears that the schema changed somewhere around 14205. At any rate, the resolution was to rebuild all of my Static Lease entries. Sorry if this was documented somewhere else...
Finally today I've updated to Eko's openvpn_jffs rev 14853. Everything seems to be working as expected, except JFFS, which tells me that it is 320 Kb in size but 0 available.
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 2432 2432 0 100% /
/dev/mtdblock/4 320 320 0 100% /jffs
Finally today I've updated to Eko's openvpn_jffs rev 14853. Everything seems to be working as expected, except JFFS, which tells me that it is 320 Kb in size but 0 available.
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 2432 2432 0 100% /
/dev/mtdblock/4 320 320 0 100% /jffs
Can anyone help on this one ?
This build seems too big.
You have to use the mini one if you want to use jffs.
With this you should get arround 300kb free jffs space. _________________ Netgear WNR834B v2 - Eko build v24-sp2 15943M mini NEWD K2.4 (running MINIUPNPD)
Tested with BS 15943 mini build with my 32/1 line over wireless:
crap .. the problem is that my router is a openvpn hub to connect from my workplace and/or from my netbook while I'm away.
I wish I could have a mini with openvpn
Did you use a NEWD or a NEWD-2 build?
The NEWD radio driver is sufficient for your router and that build is 128KB smaller than the NEWD-2. _________________ Kernel panic: Aiee, killing interrupt handler!
Also "funny" that I had an old Eko build - Release: 09/26/08 (SVN revision: 10431) openvpn+jffs and I could write into the jffs.
The only thing I want to store in there is my openvpn certs and additional config, so I won't risk that much flash wear by pushing them via "nvram set".
I don't have the old firmware image to compare the filesizes. I will try to find it.
LOM wrote:
carpediem wrote:
crap .. the problem is that my router is a openvpn hub to connect from my workplace and/or from my netbook while I'm away.
I wish I could have a mini with openvpn
Did you use a NEWD or a NEWD-2 build?
The NEWD radio driver is sufficient for your router and that build is 128KB smaller than the NEWD-2.
$ ls -l dd-wrt.v24-1*
-rw-r--r-- 1 diem diem 3260416 Aug 15 19:32 dd-wrt.v24-10431_NEWD_openvpn_jffs_small.bin
-rw-r--r-- 1 diem diem 3313664 Aug 15 11:07 dd-wrt.v24-14853_NEWD_openvpn_jffs_small.bin
The 14853 NEWD_openvpn_jffs_small should from what I can see give you a small jffs data partition around 64Kb.
Did you remember to tick the box for jffs cleaning and reboot the router? _________________ Kernel panic: Aiee, killing interrupt handler!