I flashed to 14815 from 1.0.4.55 stock firmware after a 30/30/30 reset. Unfortunately it was not very stable for me, I had to reset it once a day (Wireless connectivity on both 2.4 and 5 would be gone after a while). I tried to go back to Stock firmware by using ddwrt's admin menu, but my attempts at flashing both 1.0.4.68 and 1.0.4.55 failed (ddwrt gave an error).
I then flashed 1.0.4.68 by TFTP, this went good. However, both wireless radios were off after the flash. Even if I clicked 'Enable Wireless Router Radio' under Advanded Wireless Settings, it would be unclicked and the LED lights would stay off. Then I noticed that I had the FF:FF:FF:FF:FF:FF mac address on my router (corrupt caldata?). I then followed Nid_fr's instructions, with a modification of the last command. Here is a list of steps once again:
1-Flash 1.0.4.31. This is necessary, because you need to use telnet, as the default user/pass will not work on 1.0.4.55 or higher. I also flashed DDWRT back, but it was unresponsive even after hard resets.
6- The router will reboot and you will have 2.4 and 5ghz back again. You can upgrade to 1.0.4.55 or .68 if you want.
I upgraded to .55, as there were some complaints on .68. I tried DDWRT as I desparately needed port translation (which is ridiculous that stock firmware does not have this feature). However, I will now wait until a stable release comes.
Joined: 27 Jun 2008 Posts: 88 Location: Europe / Austria / Vienna
Posted: Sat Jul 31, 2010 17:43 Post subject:
I have installed 14815 and its working fine. But I am missing one important Feature for me called Radio Scheduling. Does anybody know why its Not implemented?
And my iPhone can Not connect itself to the router. I have always to enter the Security Key. _________________ WNDR37000v1 @ DD-WRT v24-sp2 - build 18007
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sun Aug 01, 2010 6:48 Post subject:
netbus wrote:
And my iPhone can Not connect itself to the router. I have always to enter the Security Key.
Well.. yeah thats the point of security key.. if the iPhone is not remembering it you turned that feature off on the iPhone, mine is fine.
cremersdh wrote:
I noticed the following (error??) .....
I have configured my Netgear WNDR3700 with dd-wrt (14815) with the WAN connection type disabled and have added this port to the switch by using "Assign Wan port to switch"
This all works, but the led of my "Wan" port (so now being a regular LAN port) is burning green, even though it is connected at 1G. I would have expected this to turn amber, like the other lan ports if they are connected at 1G.
Does anyone have made a script himself to change the WNDR3700 LED configuration (gpio) ?
Cause orange WAN LED means WAN is down and green is up regardless of link speed. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
I was having issues with 14815, any type of form data (dhcp reservations) would stay blank, even after a reboot. I decided to flash the stock firmware on it using the erase and tftp method. I was able able to force it to accept tftp connections by holding the reset button before plugging in power.
Everything looked to go well until it reboot. It didn't have the wireless LEDs on, I could not ping it, and could not get to the webgui.
I am guessing the erase linux command in telnet was the cause of all this. There are not many instructions on how to get the stock firmware back on for this model, so I did what I read.
Is there anyway to salvage this or would it be best to RMA it?
I presume that your wireless is not working now because you had did erase linux command.
To solve this, all you have to do is tftp stock firmware again. replace the caldata and your wireless should work again.
good luck
I tried tftp several times with the stock firmware, but nothing seems to work. It says it transfers successfully and it reboots, but nothing works after that.
Turning on the wireless is the least of my worries right now.
Can you log onto the router interface?? If you can, then you may check for the router Mac-Address. It's located under router's status page. If you Mac reported as FFFFFFFFFFF, then you may have to replace the caldata file because it's corrupted.
Isn't it about time you update the Router database page?
It's STILL the 04-23 image.
Agreed. The build shown through the router database is one of the ones that still had the wifi issues, and is resulting in a lot of the posts in this thread - that would be prevented and avoided with more recent builds.
Can you log onto the router interface?? If you can, then you may check for the router Mac-Address. It's located under router's status page. If you Mac reported as FFFFFFFFFFF, then you may have to replace the caldata file because it's corrupted.
Just follows jackietreehorn procedure.
I cannot get to the router interface. I will just RMA it and start over, it will be a lot easier to do then try to fix it myself.
I cannot get tftp to revert me back to my stock firmware for the life of me! I've been trying to use the "hold the reset button when the switch leds come on" method but everytime I get the following error:
Transfering file WNDR3700-V1.0.4.31NA.img to server in octet mode...
Packet will be sent. len=64, opcode=2
Packet received. len=4, opcode=ACK, block=0
Packet will be sent. len=4, opcode=DATA, block=1
Packet received. len=22, opcode=18025
Error occurred during the file transfer (Error code = 0):
Invalid TFTP request received.
Any ideas? I've already tried a bunch of different firmware versions to no avail.
Just tried it on my Mac, transfer times out. I'm out of ideas.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Mon Aug 02, 2010 3:37 Post subject:
shadowdancer wrote:
Isn't it about time you update the Router database page?
It's STILL the 04-23 image.
If you are referring to me, I can't. Public has no access to the router DB. But yes alot of builds and even router specs are wrong on there. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers