Joined: 06 Feb 2010 Posts: 7401 Location: Little Rock
Posted: Sun Sep 22, 2013 1:51 Post subject:
If you are indeed following the wiki instructs to the letter than i am unsure why this is failing, it may be possible that buffalo dd-wrt has a check in either of its firmware (friendly or buffalo pro dd-wrt) to not allow this type of webif flashing, not sure - when i purchased mine, it came with 15940 on it and the instructs i wrote up for it in the wiki worked fine for it then.
Most i could advise from here is either trying the TFTP flashing instructs in the wiki or possibly downgrade your buffalo dd-wrt installation to a former build and re-try the webif flashing from there. I'd also advise clearing your browser cache and cookies - BTW which web browser are you using to flash with? _________________ Wireless N Config | Linking Routers | DD-WRT Wiki | DD-WRT Builds | Peacock - Broadcom FAQ
Joined: 10 May 2011 Posts: 12 Location: Chattanooga, TN
Posted: Sun Sep 22, 2013 14:01 Post subject:
I tried flashing back to the older firmware and still received an Upgrade Failed message. I've used Chrome, Firefox and IE to attempt the upgrade.
I also tried TFTP, but I can't seem to get the timing down. I tried the 10 second delay listed on the wiki, as well as a 4 second delay I saw elsewhere. I tried doing it direct to the router, as well as through a switch. No joy.
Does Buffalo use some sort of locking mechanism, like what you find on Android phones or the iPhone? Does it need a jailbreak of some sort?
Joined: 06 Feb 2010 Posts: 7401 Location: Little Rock
Posted: Sun Sep 22, 2013 15:23 Post subject:
In linux is not much difference than TFTP'n in windows, and basically has the same effect.
And as i said in previous post, it is possible that they put a check in their later firmwares to prevent firmwares from being flashed from the webif. IIRC at one point they put out a release note on one of their latter builds that stated this kind of check. I never paid it much mind though because i pretty much always flash using TFTP, and don't have this problem, i only flash via webif when testing webflash bins, to make sure they work, and even then i am already on community dd-wrt - so its different there - no check on community dd-wrt to prevent webif flashing.
Edit: dug thru the 19154 buffalo pro build html file, and as i suspected: Version history
v24SP2-MULTI (06/03/12) std - build 19154.
To apply new wireless regulatory, build 19154 (User Friendly F/W Version 1.77 ) will not allow firmware upload to any older versions.
I received a new router from Amazon today and I couldn't access the webui, so I figure it was bricked from the factory and I went about the TFTP method of flashing.
Posted: Sat Aug 27, 2016 16:25 Post subject: WZR-600DHP
Sorry to reply to an old thread, but I'm having the same problem. I had a WZR-600DHP that recently died. I liked the router so I bought a new one. This one came stock with "DD-WRT v3.0-r29660 std (05/12/16)" and I have been unable to upgrade to the community version of DD-WRT. I tried using the router's web upgrade page, I tried tftp from Windows 10, tftp from Ubuntu 16.04, and I tried the Linksys "tftp2.exe" linked in various forums. I can't get it to work. I tried using Wireshark to see what's going on with the network. When I plug the router in I see after about 10 seconds the tftp WRQ packets going from my PC (192.168.11.2) to the router (192.168.11.1) but the router still continues on to boot the firmware that's installed instead of receiving the TFTP upgrade file. Can anyone recommend something else to try? I'm worried Buffalo may have removed the tftp from the bootloader to prevent this type of upgrade.
I got it working today after initially bricking the router. Here are some of the important things I think I missed.
1) Make sure Windows Firewall is turned off.
2) Make sure the static ARP entry for the 192.168.11.1 router is always 02-AA-BB-CC-DD-20. Also use netsh because arp -s doesn't work in Windows 10.
netsh interface ip delete neighbors "Ethernet" "192.168.11.1"
netsh interface ip add neighbors "Ethernet" 192.168.11.1 02-AA-BB-CC-DD-20
3) The timing for the tftp transfer isn't nearly as tricky as we're led to believe. Have the command queued up in your command box, plug in the router, hit enter in your command box.
4) Have Wireshark ready to help you see if anything is actually happening on the network.