so would going from 31899 to 33215 be a small upgrade?
Yes, for the most part it doesn't matter. But, the typical m.o. when someone first flashes from OEM to an old initial flash or wiki build (or even older Router Database build), then they flash a recent build, and have issues. Basically, if you have any problems and -haven't- reset, try that first then manually setup before reporting issues. This is how it should work, most don't bother. _________________ #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
is it pretty risky to be using the most current build? or in general if you're really just into having a secure stable platform you stick back a couple months?
Just trying to understand how security and builds play together. I think I have all the features I need, so not really needing new builds for features... just security updates.
is it pretty risky to be using the most current build? or in general if you're really just into having a secure stable platform you stick back a couple months?
It's extremely risky to flash any build w/o researching it first. The recent builds are a great example, as several lead to bricks for many router models. Hence one should always read the New Build threads, etc...or else know how and be prepared to TFTP, serial, or JTAG.
As for security fixes, you can search SVN for CVE's , if BS mentions it of course. Or otherwise track what packages get updated which fix their own issues. _________________ #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 see, and when you're talking about a build, you mean the build itself, not in terms of how it relates to the specific device? because I dont see day to day activity in this channel on builds that are working or not, so would be harder to know if builds break on a particular device.
because I dont see day to day activity in this channel on builds that are working or not, so would be harder to know if builds break on a particular device.
That's precisely what the "New Build" threads are for; which are created when builds are released to the ftp site. _________________ #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: Tue Sep 26, 2017 14:07 Post subject: New updates for WNDR4500 v1
Yesterday i tested all the new updates for my wndr4500v1,
all the updates brick the router and a console cable is required to reload the firmware,
the last working update is 08-03-2017-r33006
than all the new releases till 09-19-2017-r33375 simply brick the router.
you (users) are warned since it took 4 hours to test all the software.
One of the latest firmware builds bricked my WNDR4500 v1. When I power cycle it and ping it, I get one TTL=100 reply. Is this normal for a bricked unit? Trying to avoid using serial recovery.
Posted: Fri Oct 13, 2017 13:24 Post subject: WNDR4500 v1 Bricked Using Latest Firmware?
I manged to install DD-WRT on my WNDR4500 v1 using the guide on https://www.dd-wrt.com/wiki/index.php/Netgear_WNDR4500. After the 'Initial DD-WRT Installation' I then followed the instructions to upgrade DD-WRT using the latest firmware for my router 09-27-2017-r33413. During the install I think the router was rebooting but didn't seem to be doing anything for about 10 minutes. With no response I thought turning it off and back on again was a good idea (probably not).. My router now is unresponsive.
Here's what happens when I plug it in and turn it on:
The internet LED flashes very briefly then all the LEDs flash on for about a second then all LEDs turn off except the power LED. If I have an ethernet lead plugged in, the corresponding LED will also stay on.
Here's what I'm trying to do to fix it:
I've got a laptop set up with Windows XP and connected via ethernet to the router. IP on the router is 192.168.1.1. IP on the laptop is 192.168.1.10. I'm trying to TFTP flash it.
I'm following various guides on TFPT flashing and am not getting anything to work. I've tried using various firmware versions but mainly 08-03-2017-r33006 following themonsterit's advice above but the main problem at the moment is that the router doesn't seem to be responding to the tftp software 'unable to get tftp responses from the server'.
I have cmd running in the background with a continuous ping. I mostly get 'Request timed out.' and 'Hardware error.' Doing 30-30-30 and sometimes 30-5-5 hard resets I manage to get about 6 or 7 TTL=100 responses which is when I'm hitting the 'Upgrade' button in the tftp software but so far no luck. I've tried hitting 'Upgrade' at the start, during and after these responses and a number of times have anticipated the response and hit the button but still no luck.
As well as after the hard resets I do occasionally get another odd 1 or 2 TTL=100 responses every few minutes while the router is switched on but the tftp software still doesn't do anything.
Posted: Fri Oct 13, 2017 14:05 Post subject: WNDR4500 v1 Serial Recovery
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!
Posted: Fri Oct 13, 2017 17:23 Post subject: Re: WNDR4500 v1 Serial Recovery
routerbricker30 wrote:
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!
Have you tried TFTP? Might have to use OEM firmware for TFTP. Trailed files (.chk) are only for initial flash. Please read the Peacock announcement.
Also, you should always read New Build threads before flashing a build if you're not prepared to de-brick; 33413 is a bad build for MIPS routers. The latest build 33492 has been reported working on both the v2 (by me) and the v1 (I presume; by hwaddwrt). [Just don't use it on k3x 8MB routers with 7808 KB available 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
I bought a WNDR4500v2 from eBay, successfully flashed with
DD-WRT, but it refuses to grab a WAN IP address. All my other DD-WRT routers work just fine. With this particular router, the ethernet light on my cable modem doesn't turn on. I'm thinking the internet port doesn't work, or there is an ISP issue. Is there any way of testing the internet port to make sure it's functional? I think I was sold a lemon.
