Posted: Mon Jan 14, 2019 18:32 Post subject: Recommended flash verion for update of older version
I'm running version
dd-wrt v24sp2 )3/25/13) mini build 21061
Which is the newest flash version I can/should run that will allow all features?
On dd-wrt.com I saw a "big" and "mega" build recommended.
dd-wrt.v24-37305_NEWD-2_K2.6_big-nv64k.bin
dd-wrt.v24-37305_NEWD-2_K2.6_mega-nv64k.bin
=============================================
If I do an update style flash, will it retain my current settings or would I have to do them all over?
Posted: Sat Mar 16, 2019 9:12 Post subject: Re: Recommended flash verion for update of older version
dootsie wrote:
I'm running version
dd-wrt v24sp2 )3/25/13) mini build 21061
Which is the newest flash version I can/should run that will allow all features?
On dd-wrt.com I saw a "big" and "mega" build recommended.
dd-wrt.v24-37305_NEWD-2_K2.6_big-nv64k.bin
dd-wrt.v24-37305_NEWD-2_K2.6_mega-nv64k.bin
=============================================
If I do an update style flash, will it retain my current settings or would I have to do them all over?
Your settings should be retained. But your doing a big jump in version, so a reset is most likely recommended.
According to this post it seems that build r39144 runs well on wndr4000. I have not tried it myself, but will do later.
K2.6 builds have issues with GUI (ticket), so would recommend you to try out a K3.x build.
Posted: Mon Mar 18, 2019 22:41 Post subject: Re: exact meaning of reset
o-l-a-v wrote:
dootsie wrote:
If I do an update style flash, will it retain my current settings or would I have to do them all over?
Your settings should be retained. But your doing a big jump in version, so a reset is most likely recommended.
dootsie wrote:
Would you please tell me exactly what you mean when you say to do a "reset" and would that delete all my settings?
Thanks.
o-l-a-v is correct; upgrading will not affect settings, but a reset is generally recommended for a jump like that. However, you could just upgrade it and see how it does. If you have issues, then do a reset and manually setup to retest.
A reset can be done in several ways, but usually just means using the Admin->Factory Defaults reset, and then manual setup. Or press and hold the reset button until the lights flash. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Posted: Sun Jun 16, 2019 23:53 Post subject: Upgraded to r39144
Awesome, thank you jwh7 & o-l-a-v.
I upgraded my WNDR4000 from Kong [DD-WRT v24-sp2 (06/07/14) vpnkong - build 22000M] to r39144[DD-WRT v3.0-r39144M mega (03/11/19)].
No Reset was required. I had VAP-Bridge-OpenVPN, Ad Blocking, QoS, crons and multiple custom scripts and the upgrade worked flawlessly retaining everything.
[EDIT]
Eventually had issues with VAP, so reverted and upgraded to r40048
Posted: Fri Nov 01, 2019 19:57 Post subject: jffs or cdc_ether
Hi guys!
Have you ever successed in internal jjfs mounting? I know it could be achieved with mini builds only. What version were you used?
Alternatively I neeed a firmware with pre-installed cdc_ether.ko because my modem ZTE MF823D requires it in CDC mode.
Or wait for 42078 to (probably) come out today, as it backported a tcp fix to retransmitt lost marked packets. I'll be flashing it tonight on my 4000. But in general, always read the build threads.
And you should probably do an `nvram erase && reboot` from telnet afterward, then manually set up.
Edit: I updated from k3x 42015 to 42078 (test build) via GUI no problem. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
v3.0-r44251 mega (08/28/20) seems to be fast & stable on my parents' WNDR4000 on a GigE connection. Was only getting 350Mbps bidirectionally via speedtest.net, but not sure if that's a limitation of the WNDR4000 or of the ISP. Either way, 44251 is faster and more stable than 42132, which also had GUI accessibility issues.
thank you for sharing. i'm going to try that build. where can i find release notes or info about builds?
any try running their wndr-4000 at 500mhz? i have wifi disabled on mine and use ubiquiti APs after the wifi radios started going bad.
EDIT: i'm not so sure it liked an upgrade from v 3.0-r33215M mega. i thought it was wierd it started with v3.0 and the rest talked about and linked started with v24. i bet one is like a kong vs a mega or something. i bet some settings features are different.
it pings but, the web page doesn't respond and it still say updating 10+ minutes later.
EDIT: upgrade failed!
i bet it's bricked or needed reset and re configure / or reset and flashed back
EDIT: maybe it was a kong build!!!
of course i find this now!
Kong builds (deprecated)
Broadcom only! Kong stopped DD-WRT development and removed his repository in Jul 2019.
Kong builds were cryptographically signed to verify authenticity, tested on hardware before upload, could upgrade via the command line ddup tool, and had a bootstrap tool to install the opkg package manager for additional features. Since the original repository was removed, these features are no longer relevant. It is not recommended to use these builds.
---
Step 2: Choose the correct build folder:
Atheros, Ralink, and Marvel builds are in the router-named folders. Ensure you have the right version!
Broadcom ARM (and MIPS with NAND flash, ex: Netgear WNDR4500) routers also have named folders
Broadcom MIPS routers with NOR flash use one or more of the broadcom* folders
broadcom - kernel 2.4 builds for very old routers (ex: Linksys WRT54Gv5)
Builds with special in the name can authenticate with 802.11x in client mode (PEAP, TLS, etc.)
broadcom_K26 - kernel 2.6 builds for old routers, but many routers that run K26 can also run K3X (ex: Linksys E2500) with better USB support, and k3.10+ supports SFE accelerated NAT since 33006
Some routers can use k2.4 or k2.6, others can use k2.6 or k3.x, but many will brick on different versions
broadcom_K3X - kernel 3.x builds for newer Broadcom MIPS models with NOR flash (ex: Asus RT-N66U).
so there is a difference between 2.4 and 3.x???
i guess i better not reboot the router huh?
EDIT: rebooted and no hard no foul!!!! still on DD-WRT v3.0-r33215M mega (08/25/17)
but, still the above firmware is called dd-wrt.v24-44251_NEWD-2_K3.x_mega-nv64k
whats up with the v24? and why does mine say v3.0?
EDIT: IT WORKED!!! I used IE to update firmware! IT IS V3.0!!! It says v24 in file name but, it's V3.0!!!! my settings are intact so far!!!
Router/Version: Netgear WNDR4000
File/Kernel: DD-WRT v3.0-r44980 mega (12/12/20)/Linux 4.4.247 #5325 Sat Dec 12 18:57:50 +07 2020 mips
Previous/Reset: r40048 / yes
Mode/Status: AP/full access wifi on both 2.4 GHz and 5 GHz
Issues/Errors: None so far
Hello Netgear WNDR4000 Router Users,
If you are looking for the latest stable version of dd-wrt for this specific router and have found this post, I wanted to provide some details of my experience in hopes that it helps someone out there. After realizing that my previous version was very out of date, I decided to try upgrading to the latest -- r46316 (09-Apr-21) -- at that time.
However, after doing this (and even resetting the router with nvram erase && reboot), I discovered that the 5 GHz AP had disappeared -- i.e., it did not seem to be transmitting at all -- even though all the settings and related items appeared in the Admin UI. Thinking that there may have been a bug in that latest version, I tried several previous versions -- ranging from March all the way back to January (beginning of the year) -- and none of them worked as the same issue persisted even after resets between each.
After some digging into dd-wrt’s SVN, I noticed that other users had reported wifi-related issues in late December 2020. So, I decided to downgrade to the mid-December version, r44980 (12-Dec-20); and suddenly, my 5 GHz AP was showing up again, accepting connections, and holding a stable connection across my wireless devices. Thus, for the moment, I think that I am going to remain on this version until someone else can confirm this odd issue to be resolved.
Joined: 08 May 2018 Posts: 14244 Location: Texas, USA
Posted: Fri May 14, 2021 0:28 Post subject:
Flash and report in the build release threads, please. Threads like this turn into a cesspool of useless information that folks have to wade through and get confused by. If you are not flashing current releases, testing and reporting, then you are not helping the community at large.