Posted: Fri Dec 01, 2017 6:06 Post subject: Re: RE: Bricked WNDR4500V2??
camelriders wrote:
I tried several builds, not all.
Is there a particular version I should try? Should I go to the initial release?
I think I used the initial release, myself. I don't know if that's what your problem is. I just know that with the wndr3700; after a certain version of the factory firmware, netgear had added some type of check that will screw up the installation process for anything except netgear firmware. I'm guessing it may be a similar thing with the 4500 firmware but I honestly don't know if that's the problem or not. I'd give a it a shot.
nevermind: Firmware Version 1.0.0.60 is my go-to recovery firmware for the v2 before I reinstall. you're using the chk file, not the bin right? _________________ n17tech blog
hw: r4500; WNDR4500v2; WNDR3700v2; WNR2000v3; WNR2000v5; BEFS841v3.1; WRT54GSv.4; WRT54G2v1.5; E900; E1000; E1200v2; WRT610Nv1; M20; RT-68P; DIR-601A1; DIR-615; DIR-635
Posted: Fri Dec 01, 2017 6:35 Post subject: Re: RE: Bricked WNDR4500V2??
november17 wrote:
camelriders wrote:
I tried several builds, not all.
Is there a particular version I should try? Should I go to the initial release?
I think I used the initial release, myself. I don't know if that's what your problem is. I just know that with the wndr3700; after a certain version of the factory firmware, netgear had added some type of check that will screw up the installation process for anything except netgear firmware. I'm guessing it may be a similar thing with the 4500 firmware but I honestly don't know if that's the problem or not. I'd give a it a shot.
Worth the shot... didn't work; bricked the router once again.
I can't try it on my v1 because it died tw weeks ago when I unplugged it. Probably best to have powered it off before unplugging the power supply
Tomorrow I'll try downloading the DD-WRT release via an FTP client to make sure it's not getting corrupt.
Posted: Fri Dec 01, 2017 6:37 Post subject: Re: RE: Bricked WNDR4500V2??
november17 wrote:
camelriders wrote:
I tried several builds, not all.
Is there a particular version I should try? Should I go to the initial release?
I think I used the initial release, myself. I don't know if that's what your problem is. I just know that with the wndr3700; after a certain version of the factory firmware, netgear had added some type of check that will screw up the installation process for anything except netgear firmware. I'm guessing it may be a similar thing with the 4500 firmware but I honestly don't know if that's the problem or not. I'd give a it a shot.
nevermind: Firmware Version 1.0.0.60 is my go-to recovery firmware for the v2 before I reinstall. you're using the chk file, not the bin right?
I read the basic guides and now I wanna ask... What is the current recommended build/version for WNDR4500(v1)?
I probably must use 33525+ because of KRACK...
Does the latest version (33772) work fine with WNDR4500?
And, which version should I use for the initial flash? The Peacock thread suggests Blainslayer 14929 while the wiki page does 26138.
The 'final' Broadcom krack fixes were in build 33678, and 33679 was missing many builds, so you want at least 33772. The Peacock doesn't indicate minimum builds to flash a particular device; that's in Supported Devices. So, you -definitely- don't want 14929. It is advised to follow the wiki for initial flash. I will be putting 33772 on my WNDR4500v2 and WNDR4000 today, as I have it on all my other DD devices atm. I will update this when I do; the v1 and v2 appear to have identical h/w specs except the latter has a BCM53125 switch (vs 53115).
Update: I have 33772 on my 4500v2 now, setup as a 2.4 GHz Client Bridge and 5 GHz Access Point, running fine.
Were you able to dirty install any of these builds after 33555? I hadn't had a problem updating until 33607 and 33772. Both are giving me problems with wifi when trying to connect to other bridge routers(Asus RT-N10P also running ddwrt). I have a couple debian boxes connected on the bridge routers that run security cams and Pi-Hole. When I try connecting to them through putty, sometimes it won't connect at all or if it does connect, it's very slow. Pi-Hole doesn't work either obviously since connection is flaky.
I flashed back to build 33555 and everything works perfectly once again. I can access the boxes in putty, access bridge routers webgui and Pi-Hole works once again. Just skimming some of the new build threads, there did seem to be some people having wifi issues starting with builds 33607 onward.
Were you able to dirty install any of these builds after 33555? I hadn't had a problem updating until 33607 and 33772. Both are giving me problems with wifi when trying to connect to other bridge routers(Asus RT-N10P also running ddwrt).
I flashed it from 33555 to 33772 w/ no reset, and also set up a guest wireless network on it. No issues observed, but I used the CB ethernet more than the AP/guest wireless side. _________________ #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
I flashed it from 33555 to 33772 w/ no reset, and also set up a guest wireless network on it. No issues observed, but I used the CB ethernet more than the AP/guest wireless side.
Ok. I'll stick with 33555 for now. Something definitely causing problems with bridge connections. I'll wait for future builds to see if it gets fixed. Thanks.
I flashed it from 33555 to 33772 w/ no reset, and also set up a guest wireless network on it. No issues observed, but I used the CB ethernet more than the AP/guest wireless side.
Your reports have been very helpful about what versions work and procedures to follow.
Posted: Mon Mar 19, 2018 19:36 Post subject: DD-WRT v3.0-r34080 giga (12/14/17) not stable
Hi,
After more than year I decided to upgrade with newer version r34080 available at that time (changes history does not indicated big issues).
After some months I can say this release is not stable on WNDR4500v1:
- 2.4 GHz WiFi sometimes stops working after 3-5 days after reboot (even SSID is visible I am not able to connect)
- after longer (up to 30-40 days) period, there is lost wl1/5GHz (5GHz disabled in my case) tab in menu, also wl0 menu is strongly reduced (like FW gets to some corrupt state), wifi does not work completely
- wifi scheduling does not work (ticket opened 3 months withouth fix)
Unfortunately there is no OpenWrt build for this HW, otherwise I already migrated to OpenWrt.
Anybody has better experiences with some newer DD-wrt FW release?
I have 2 WNDR4500 routers successfully running v3.0-r35452 giga 03/20/18 as client bridges on my network. They have the 3com user interface configured and have been up now for over 8 days. Prior to that, I performed some thorough testing with them configured as access points. They are both functioning perfectly* at this point.
They were flashed by following the instructions in the wiki exactly:
*The only issue these are having is that for some reason the NTP time server settings don't seem to work but this is not required for my client bridge configuration.
FYI, to anyone else attempting this on a WNDR4500v2, these instructions provide the proper .chk file for the v2, but the recommended update .bin file, Kong 25015-SP1, will brick your router hard. I learned this the hard way, but hopefully nobody else makes this error....
Note in a simlar vein to the previous post: I was having many problems with the r36168 build: Unless I kept a ping going, I would have to re-connect to the wifi every 5 minutes (computer showed as connected but couldn't do anything) and after a few days the router would need to be rebooted. Additionally trying to talk between devices on the network would often report "no route to host".
Hopefully I have a better time with the r36006!
FYI, to anyone else attempting this on a WNDR4500v2, these instructions provide the proper .chk file for the v2, but the recommended update .bin file, Kong 25015-SP1, will brick your router hard. I learned this the hard way, but hopefully nobody else makes this error....
I am actually running Kong 25015-SP1 for quite a while now. Admittedly I upgraded to it from a earlier version and didn't flash it directly after the chk from wiki
I'll try to upgrade to dd-wrt.v24-36006_NEWD-2_K3.x_mega-WNDR4500V2.bin
Reverted back from 36410 to 33555 on N900v1->WNDR4500 AP after having constant issues with WiFi disconnects as reported by others. Tried a few others in 36168-36410 range, same issues. Will run with 33555 to see if these WiFi issues postdate 33555 firmware. _________________ Netgear N900v1 > WNDR4500:
dd-wrt.v24-33555_NEWD-2_K3.x_mega-WNDR4500.bin
Linksys WRT610Nv2 > E3000:
dd-wrt.v24-36247_NEWD-2_K3.x_mega.bin
Linksys E1200v1:
dd-wrt.v24-29519_NEWD-2_K2.6_mini-nv64k
Joined: 30 Sep 2018 Posts: 47 Location: United Kingdom
Posted: Sun Sep 30, 2018 22:55 Post subject:
Hello everyone, I just started with ddwrt on my netgear WNDR4500v1.
I started with initial build and than after time spent on this thread I installed dd-wrt version 33555 - that looked most stable for me.
Everything is great, but I see small slowdown on my WAN interface, and I don't know it its caused by firmware, config or its provider issue.
Normally (on genuine netgear firmware) I had around 65Mbit download and 15Mbit upload.
Now its dl 45Mbit and ul is 12Mbit.
So first question is to users of WNDR4500v1: Could you post your max WAN speed (from speedtest.net or from fast.com)?
Second question (also to users of V1) - What is your current version of dd-wrt ? How it works, should I stay with 33555 or maybe in past year appeared something worth upgrade?
Thanks