I'm away from home so I can't do an install, plus I'm still undecided whether to install dd-wrt or not.
I like the performance of the OEM firmware, and I'm not planning on doing anything exotic with this router.
If I do install the firmware I will most definitely post the results. _________________ WNDR3400v1 using dd-wrt.v24-24461_NEWD-2_K3.x_mega-nv64k.bin
WNDR4500v1 OEM Firmware Version V1.0.1.40_1.0.68
“Incredibly handsome and master of all villainy!”
“Ow! My giant blue head!”
Joined: 28 Nov 2012 Posts: 17 Location: Dresden, Germany
Posted: Tue Jan 20, 2015 16:47 Post subject:
Would it be technically possible to have those WLAN/LAN leds blinking on this hardware if traffic is flowing? I remember this on my WRT54Gl a very useful feature to examine if a client does a lot of traffic.
I have a Netgear N900 WNDR4500v3 and it only accepts firmware in .img format, not .chk anymore, I am not able to upload dd-wrt firmware (I have tried with dd-wrt.v24-25697_NEWD-2_K3.x_mega-WNDR4500V2.chk , dd-wrt.v24-25974_NEWD-2_K3.x_mega-WNDR4500V2.chk and dd-wrt.v24-K3_AC_ARM_STD.chk ), just after selecting the file and pushing upload it returns an error of “incorrect file format”. Renaming them to .img file neither works.
Damn it
I also tried to upload it trough TFTP and neither works, it returns a timeout (I have done so many factory resets….)
Perhaps I have to compile source in .img?, I am Windows user and Microsoft doesn't like it
Hey guys - I am running build 25794M released on 1/20/15 on my WNDR4500v1 and so far seems very stable. I do have a question about VLANs and tagging/trunking ports. Does anyone know if this indeed works or not? I created 3 VLANs and can ping the x.x.x.1 address of each VLAN but thats about as far as I can get. When I plug a device into the trunked port and assign a static IP on on of the new VLANs i get nothing. Appreciate any help possible...thanks guys!
Could someone verify that I am looking at the correct latest builds for the WNDR4500V2?
1. Although I could not find reference to a trailed build for the WNDR4500V2, I did find dd-wrt.v24-K3_WNDR4500V2.chk at http://www.desipro.de/ddwrt-ren/K3-AC/Initial. This is about a 6 meg file, so it appears that it might be a trailed build. Can someone confirm that?
2. From the discussions, it appears that dd-wrt.v24-K3_AC.bin found at http://www.desipro.de/ddwrt-ren/K3-AC/25015-SP1 is the latest stable build for this router. Again, can someone confirm this?
If these are not correct files and locations, please kindly include information on the correct files and locations. The links most commonly referred to in the thread as recently as 6 months ago are no longer there.
Could someone verify that I am looking at the correct latest builds for the WNDR4500V2?
1. Although I could not find reference to a trailed build for the WNDR4500V2, I did find dd-wrt.v24-K3_WNDR4500V2.chk at http://www.desipro.de/ddwrt-ren/K3-AC/Initial. This is about a 6 meg file, so it appears that it might be a trailed build.
Can someone confirm that?
You have the correct Initial <KONG> .chk file for your router.
Make sure you read <Kong>'s "Readme" file up one level from the .chk file.
Quote:
2. From the discussions, it appears that dd-wrt.v24-K3_AC.bin found at http://www.desipro.de/ddwrt-ren/K3-AC/25015-SP1
is the latest stable build for this router. Again, can someone confirm this?
This too appears to be correct, however new betas are released constantly. _________________ WNDR3400v1 using dd-wrt.v24-24461_NEWD-2_K3.x_mega-nv64k.bin
WNDR4500v1 OEM Firmware Version V1.0.1.40_1.0.68
“Incredibly handsome and master of all villainy!”
“Ow! My giant blue head!”
Thank you kindly. I've used DD-WRT for a couple of years now on three different routers and I know from firsthand experience how easy it is to brick a router by using incorrect builds (or not waiting long enough for NVRAM to initialize after a flash).
I believe that my wisest course, based on all my reading, is to obtain the serial cable for the router before I attempt to flash it just in case I brick the beast. I've seen quite a number of USB to TTL cables, ranging in price from $3 to $30. Are they all pretty much compatible? Or is there anything I need to keep in mind when getting a cable?
Recommendations, as always, are greatly appreciated.
Thank you kindly. I've used DD-WRT for a couple of years now on three different routers and
I know from firsthand experience how easy it is to brick a router by using incorrect builds
(or not waiting long enough for NVRAM to initialize after a flash)..
You're welcome; happy to help when possible. It's always wise to gather as much information as possible.
dsquared wrote:
I believe that my wisest course, based on all my reading, is to obtain the serial cable for the router before
I attempt to flash it just in case I brick the beast. I've seen quite a number of USB to TTL cables,
ranging in price from $3 to $30. Are they all pretty much compatible?
Or is there anything I need to keep in mind when getting a cable?
Recommendations, as always, are greatly appreciated.
Having just purchased a WNDR4500v1, I too am somewhat reluctant to install dd-wrt firmware on that router for:
1- fear of bricking it, and most importantly for me,
2- lost of performance when switching to dd-wrt; as for me, I see no reason to switch to dd-wrt, yet.
I do strongly concur with you that a USB to TTL cable be close at hand, and proper knowledge of its use be obtained as well.
Might I suggest you do the following.
Google and purchase this from your preferred web site; this cable is highly recommended by "Guru Malachi".
Read over the Serial Recovery Wiki and, if needed, connect your USB serial converter to your router using these instructions.
I would also recommend going with a stable build first.
Good luck to you on your firmware installation. _________________ WNDR3400v1 using dd-wrt.v24-24461_NEWD-2_K3.x_mega-nv64k.bin
WNDR4500v1 OEM Firmware Version V1.0.1.40_1.0.68
“Incredibly handsome and master of all villainy!”
“Ow! My giant blue head!”
I'm currently running DD-WRT v24-sp2 (04/17/14) kongac - build 23900M on my WNDR4500v1 and would like to update to something more current. I've read a couple of posts that referenced a build that, after installation, caused problems with subsequent attempts to upgrade.
Unfortunately, I don't know what version caused those problems; does anyone have any info, or can assure me that kong's build 23900M will safely permit an upgrade to 25015 or later?
I'm currently running DD-WRT v24-sp2 (04/17/14) kongac - build 23900M on my WNDR4500v1 and would like to update to something more current. I've read a couple of posts that referenced a build that, after installation, caused problems with subsequent attempts to upgrade.
Unfortunately, I don't know what version caused those problems; does anyone have any info, or can assure me that kong's build 23900M will safely permit an upgrade to 25015 or later?
Thanks . . .
I'm running DD-WRT v24-sp2 (09/16/14) kongac - build 25015M on my v1. I upgraded without issue.
@Dodge DeBoulet
know your chipset... and keep in mind if you are after Kong's K3-AC (NOT K3-AC-ARM) builds.
you have a Broadcom BCM4706, so Kong abandon your firmwares with the K26 stuff back in October 2014.
the BCM4707/4708/4709 or ARM devices are the "K3-AC-ARM" builds, that continue on via Kong's Personal Test Builds. (i.e. don't flash one of these)
PS. I've seen some of the BCM4706 folks having good results with the BS/Main SVN 26138 firmware, but I can't remember exactly where to provide links to the examples (but if I recall it was a R6300v1 user and maybe a wndr4500v2 user, diff devices from same OEM/BCM4706 chipset).
Also keep an eye out on the "new builds" threads for someone with your device reporting a successful flash. that is if you don't have serial/jtag capabilities, and if you don't want to be the first to test a new BS Build on your device. _________________ reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
@Dodge DeBoulet
know your chipset... and keep in mind if you are after Kong's K3-AC (NOT K3-AC-ARM) builds.
you have a Broadcom BCM4706, so Kong abandon your firmwares with the K26 stuff back in October 2014.
the BCM4707/4708/4709 or ARM devices are the "K3-AC-ARM" builds, that continue on via Kong's Personal Test Builds. (i.e. don't flash one of these)
PS. I've seen some of the BCM4706 folks having good results with the BS/Main SVN 26138 firmware, but I can't remember exactly where to provide links to the examples (but if I recall it was a R6300v1 user and maybe a wndr4500v2 user, diff devices from same OEM/BCM4706 chipset).
Also keep an eye out on the "new builds" threads for someone with your device reporting a successful flash. that is if you don't have serial/jtag capabilities, and if you don't want to be the first to test a new BS Build on your device.
Thanks, jheide44. I'm pretty sure I have the right architecture; what I'm trying to find out is which installed version caused issues for subsequent upgrades. There have been a couple of mentions of this issue, but I can't find any references to the specific versions that people have attempted to upgrade from.
As I've mentioned, I'm on 23900M and would like to move to something more current. But if it's possible to go straight from 23900M to the current stable or beta release in the trunk, confirmation would be appreciated.
@Dodge DeBoulet
know your chipset... and keep in mind if you are after Kong's K3-AC (NOT K3-AC-ARM) builds.
you have a Broadcom BCM4706, so Kong abandon your firmwares with the K26 stuff back in October 2014.
the BCM4707/4708/4709 or ARM devices are the "K3-AC-ARM" builds, that continue on via Kong's Personal Test Builds. (i.e. don't flash one of these)
PS. I've seen some of the BCM4706 folks having good results with the BS/Main SVN 26138 firmware, but I can't remember exactly where to provide links to the examples (but if I recall it was a R6300v1 user and maybe a wndr4500v2 user, diff devices from same OEM/BCM4706 chipset).
Also keep an eye out on the "new builds" threads for someone with your device reporting a successful flash. that is if you don't have serial/jtag capabilities, and if you don't want to be the first to test a new BS Build on your device.
Thanks, jheide44. I'm pretty sure I have the right architecture; what I'm trying to find out is which installed version caused issues for subsequent upgrades. There have been a couple of mentions of this issue, but I can't find any references to the specific versions that people have attempted to upgrade from.
As I've mentioned, I'm on 23900M and would like to move to something more current. But if it's possible to go straight from 23900M to the current stable or beta release in the trunk, confirmation would be appreciated.
I see, other than picking through this thread & the rest of the broadcom forum I have no personal experience here...
if not check out the other links generated using this search syntax (without quotes) by google...
"N900 kong build upgrade issues site:www.dd-wrt.com/forum" _________________ reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
Possibly, but that seems a bit older than I remember. I thought I read about some issues in the latter half of 2014. I could be misremembering, though.
Quote:
if not check out the other links generated using this search syntax (without quotes) by google...
"N900 kong build upgrade issues site:www.dd-wrt.com/forum"