Posted: Fri Oct 13, 2017 19:00 Post subject: Re: WNDR4500 v1 Serial Recovery
routerbricker30 wrote:
That's great, thanks very much. I've ordered the cable on eBay. Regarding firmware to use, would you recommend the 09-27-2017-r33413 as this sounds like the latest stable DD-WRT release for this router? Or perhaps the OEM stock firmware from Netgear as I've read elsewhere? Also, would I use a .chk or .bin file? Your help is much appreciated!
Keep in mind that some of the v1 units don't have any serial pins on the board. You may have to solder them yourself.
I bought a WNDR4500v2 from eBay, successfully flashed with DD-WRT, but it refuses to grab a WAN IP address.
I presume you tried a reset and manual setup already. Did you try it w/ OEM f/w first? Prob a lightning victim; try reassigning the WAN to a LAN port and see if it works that way. _________________ #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: Mon Oct 16, 2017 10:05 Post subject: Re: WNDR4500 v1 Serial Recovery
Xyro wrote:
routerbricker30 wrote:
That's great, thanks very much. I've ordered the cable on eBay. Regarding firmware to use, would you recommend the 09-27-2017-r33413 as this sounds like the latest stable DD-WRT release for this router? Or perhaps the OEM stock firmware from Netgear as I've read elsewhere? Also, would I use a .chk or .bin file? Your help is much appreciated!
Keep in mind that some of the v1 units don't have any serial pins on the board. You may have to solder them yourself.
OK so I received the cable, soldered the pins, got everything hooked up. Following the guides for serial console recovery, I've managed to upload the firmware successfully via TFTP but now in the serial console (HyperTerminal) I'm getting 'Checking crc...Invalid boot block on disk'. The router then just sits there, power LED flashing.
Here's what I'm doing:
In HyperTerminal, hitting Ctrl+C while turning on router. When I get to CFE> I type 'nvram erase' + Enter. I then type 'flash -noheader : flash1.trx' + Enter (obviously without the apostrophes). Immediately I use the TFTP client and hit 'Upgrade' to upload the latest Netgear stock firmware. The TFTP client says 'Firmware was upgraded successfully!' In HyperTerminal I then type 'go'. That's when I get 'Checking crc...Invalid boot block on disk'.
I've attached a screenshot of HyperTerminal for all the details.
Reading similar problems and other guides, I've tried a number of other things.. (1) uploading dd-wrt firmware (dd-wrt.v24-26138_NEWD-2_K3.x_mega-WNDR4500.chk) (2) Using a hex editor, removing all text up to and including HDR0 from the .chk files then saving as .bin and uploading them (3) Using a different TFTP client, including one which gives the option to upload the firmware in binary and plain text (4) Hard reset (30-30-30) before and after serial+tftp procedure (5) Using -offset=262144 in the flash line in HyperTerminal
I'm at a bit of a loss now guys.. I'm at least getting a constant ping response of TTL=100 from it now! Anyone got any other ideas? I wonder if it's something to do with the size or format/partitioning of the boot/flash drives? Or maybe the firmware I'm using to upload.. but I don't know what to try next!
Posted: Mon Oct 16, 2017 10:46 Post subject: Bricked WNDR4500 v1, SOLVED!
Malachi wrote:
After stopping the cfe try typing tftpd. Then upload netgear firmware.
You sir are a genius!! You don't get that Guru status for nothing! All seems to be working now!! Very happy chap here, thank you very much! Now to try getting DD-WRT on it again! Wish me luck...
So yes, the latest stock Netgear firmware went on fine after that, I then followed the wiki guide for my router exactly and got dd-wrt on then the upgraded with the latest dd-wrt firmware. Not sure where I went wrong in the first place. I would imagine I didn’t wait long enough after the install and update although I thought I had.. Also, I updated to what was the latest firmware at the time which has since become obsolete so maybe there was a bug...? Either way, I found that having the serial console hooked up helped a lot because I could see what the router was actually doing throughout the process - highly recommended if anyone wants to try - parts cost less than £5 and just a bit of soldering required.
Not sure where I went wrong in the first place. I would imagine I didn’t wait long enough after the install and update although I thought I had.
I don't know about the v1, but my v2 takes an incredibly long time to boot, compared to any other router I've used. I'm sure some of the trouble I had early on was due to not waiting long enough after an update. Never had to serial though. In contrast, my E1500 boots up in like 30s... _________________ #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 don't know about the v1, but my v2 takes an incredibly long time to boot, compared to any other router I've used. I'm sure some of the trouble I had early on was due to not waiting long enough after an update. Never had to serial though. In contrast, my E1500 boots up in like 30s...
I have the WNDR4500v1 and can confirm it takes A LONG TIME to boot up. I recently had an issue w/ the router, so tried a few things trying to diagnose it and get it back up, including simple resets, power cycles, and 30-30-30. I didn't time it, but it took about a minute to finish booting.
(In the end, it turned out to be an issue w/ the power supply. d'oh!)
On a tangent, has anyone tried r33525?
I'm looking for a patch to the KRACK attack and want a build that is stable/stablish.
Posted: Sun Oct 29, 2017 7:01 Post subject: problems with build 33607
hi
I had some serious problems with build 33607 on my wndr4500. After the upgrade to 33607 i could not ping my nas connected through a asus ea-n66. I could not ping the ea-n66 anymore form an other wlan device. Unforentaly I was able to ping the nas direct from the router (telnet-session) but not from a client in the wlan. Look likes ap-isolation (unwanted).
I downgraded now to 33555, that helps.
Posted: Sun Nov 05, 2017 13:31 Post subject: WNDR4500 as OpenVPN client
I've been searching trying to find the answer to this for a while, no luck. I wanted to know if dd-wrt will allow my WNDR4500 to act as a VPN client. Doesn't have to be OpenVPN, but it seems that is most likely as it is supported by dd-wrt. What would be ideal would be to bind one wireless band to the VPN connection, and the rest just as they are now, routed through my internet connection. Let me know if it's possible to do what I'm trying to do. Thanks.
@gifty74 yes all possible also openvpn (1-2mybte/sec maximum, depending on encryption strength)
Ok, with that slow speed probably won't do what I'm looking to do. Maybe I can tell you what I'm looking to do, and with all of your knowledge maybe tell me the best way to do it. I have directv, and the local NBA team is only on comcast (which I used to have, still have their cable internet). I have a good friend with comcast cable tv, and what I want to do is set up a vpn on a windows 7 machine, or his router, that I can connect to with one of my devices (preferably my ipad) and watch via the nbcsports app (and airplay hopefully). Ideally I would connect the apple tv to his vpn, as the nbcsports app is on there too, but they do not have built in vpn client support. I've read the way to do that is connect a laptop to vpn via wired LAN, then share that connection via the wifi, and have the apple tv connect to the shared wifi and then it would appear to be on his home network (where the comcast cable is). Let me know if any of this makes sense, and if anyone has an idea how to make this work. We both have WNDR4500s by the way.
So I installed Kong build dd-wrt.v24-K3_AC.bin on my wndr4500 v1. All went well with the installation, however, all of my speeds dropped. Wired went from 125 Mbps to 95, and wireless has suffered worst of all with my 5ghz dropping from 105 Mbps to 45. Anyone know what is going on? Is this typical of the dd-wrt firmware? If so think I'll be going back to stock.
So I installed Kong build dd-wrt.v24-K3_AC.bin on my wndr4500 v1. All went well with the installation, however, all of my speeds dropped. Wired went from 125 Mbps to 95, and wireless has suffered worst of all with my 5ghz dropping from 105 Mbps to 45. Anyone know what is going on? Is this typical of the dd-wrt firmware? If so think I'll be going back to stock.
Did you reset and manually set up? Otherwise use BS build 33555 and do so again. Make sure SFE accelerated NAT is enabled. _________________ #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
