Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Mon May 18, 2009 22:44 Post subject:
ThETImo wrote:
LLB wrote:
That's bad. `Try note 6 of the peacock thread sticky... ...Power cycle during pings and see if you can get a ttl-100. Peacock thread has the process. If you can't, it's jtag time.
Nope. Just 'timed-out', regardless of the time the plug being in. I'm afraid this was it, messing with Jtag is not for me. 35€ is not a bad price for this lesson though... :?
Thanks anyway.
i would wonder how you got it killed. if you didnt overwrite the bootloader, all is still in place and the tftp server within the bootloader responses on boot up _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
1. Power off router
2. Turn off firewall
3. Start tftp2 . select the firmware.tftp set Server : to 192.168.11.1
4. Set your networkcard to 192.168.11.x Gateway 192.168.11.1
5. Power on router , when the networkcard detects connection klick upgrade.
6. Wait
7. When the router have rebootet set your networkcard to 192.168.1.x Gateway 192.168.1.1
8 Try http://192.168.1.1 and set login name and Password.
Thanks, I'll try that. What's the difference between tftp and tftp2? Otherwise I've gone through the procedure you described several times.
I'll be using server 192.168.1.1 though. The 280209 fw was successfully uploaded and I believe it is there. Or is there a reason I should use ... 11.1. ?
What the heck, one more try. _________________ At home:
WHR-G125/v24-preSP2
2xWHR-G54S (WDS, yet to be flashed)
WL-500gPv2
WCA-G
-
At summer cottage:
TW-3G
2xWHR-G125 (WDS, ytbf)
WAP54G v3 (yet... )
i would wonder how you got it killed. if you didnt overwrite the bootloader, all is still in place and the tftp server within the bootloader responses on boot up
Although I'm not deep enough to know what bootloader does, it would make also to my sense that the older (280209) software should be in the device. The big mystery to me is the ping response which should be something else but 'timed-out'. Network card is working, that I checked.
It would be just great to get the box recovered. _________________ At home:
WHR-G125/v24-preSP2
2xWHR-G54S (WDS, yet to be flashed)
WL-500gPv2
WCA-G
-
At summer cottage:
TW-3G
2xWHR-G125 (WDS, ytbf)
WAP54G v3 (yet... )
Another no. The confusing thing is that the leds hardly blink. When plugging in, all of them blink once, then only the diag led blinks occasionally. The rest of the leds keep on blinking just now and then. Just as mentioned earlier... _________________ At home:
WHR-G125/v24-preSP2
2xWHR-G54S (WDS, yet to be flashed)
WL-500gPv2
WCA-G
-
At summer cottage:
TW-3G
2xWHR-G125 (WDS, ytbf)
WAP54G v3 (yet... )
Is tftp the way to go for an initial flash of a new WHR-G300N with original firmware?
The flashing instructions at http://www.dd-wrt.com/wiki/index.php/WHR-G300N (assuming they are up to date) seem to imply either tftp or a 2-step web flashing can be used. _________________ 2x WRT54G v2
1x F5D7230 v1444
1x WHR-HP-G54
1x WHR-G300N v1
1x WRT300N v1.1
1x RT-N16
1x WNR3500L
Joined: 10 May 2008 Posts: 1380 Location: Pacific North West, USA
Posted: Wed May 20, 2009 13:46 Post subject:
Do a TFTP flash... its very quick.
It's just a matter of catching it in the first few seconds when you power up the router.
030309 and now 051809 builds work on the WHR-G300N
When you power the router on, the first 3 seconds are RECOVERY mode for the router.
You have to TFTP to 192.168.11.1
Even if you already have a build loaded and working, you do NOT tftp to 192.168.1.1
Set your PC to 192.168.11.whatever (not .1)
then TFTP or TFTP2 to the 192.168.11.1 IP
If you get timeout errors when tftp-ing - you're not catching the recovery mode in time. _________________ Soylent Green Is People ! =-=-=-=-=-=-=-=-=-=-=
Netgear Nighthawk R7000 - DD-WRT Build R46220
Linksys EA8500 - OpenWRT IPQ806x Trunk R16375 5.4 Kernel
Beyond the initial flash, is tftp still the way to go or one can safely use the web-ui method?
Quote:
...
Even if you already have a build loaded and working, you do NOT tftp to 192.168.1.1
Is this true with only this router, or with other routers as well -- i.e. you can only tftp to the IP address originally set by the manufacturer? _________________ 2x WRT54G v2
1x F5D7230 v1444
1x WHR-HP-G54
1x WHR-G300N v1
1x WRT300N v1.1
1x RT-N16
1x WNR3500L
Beyond the initial flash, is tftp still the way to go or one can safely use the web-ui method?
Depends on the router, but for most it is fine to use the webgui. Don't for Belkin.
Quote:
Is this true with only this router, or with other routers as well -- i.e. you can only tftp to the IP address originally set by the manufacturer?
You have to flash to the IP of the router. If you changed the router IP, you have to flash to that IP. If you haven't changed it, or if you have reset it to factory defaults, you have to flash to the one assigned by the firmware. This is true of all routers. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Wed May 20, 2009 19:20 Post subject:
for linksys the tftp ip is always 192.168.1.1. for buffalo whr g300n its 192.168.11.1
all other routers (also buffalo) will use the last configured lan ip for tftp within the bootloader _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Is this true with only this router, or with other routers as well -- i.e. you can only tftp to the IP address originally set by the manufacturer?
You have to flash to the IP of the router. If you changed the router IP, you have to flash to that IP. If you haven't changed it, or if you have reset it to factory defaults, you have to flash to the one assigned by the firmware. This is true of all routers.
I had previously assumed the same, but I am interpreting BrainSlayer's post above as saying that Linksys routers and Buffalo WHR-G300N are the exceptions: their tftp address are always respectively 192.168.1.1. and 192.168.11.1, regardless of the particular firmware being used and the IP address configured by the router admin. _________________ 2x WRT54G v2
1x F5D7230 v1444
1x WHR-HP-G54
1x WHR-G300N v1
1x WRT300N v1.1
1x RT-N16
1x WNR3500L
Is this true with only this router, or with other routers as well -- i.e. you can only tftp to the IP address originally set by the manufacturer?
You have to flash to the IP of the router. If you changed the router IP, you have to flash to that IP. If you haven't changed it, or if you have reset it to factory defaults, you have to flash to the one assigned by the firmware. This is true of all routers.
I had previously assumed the same, but I am interpreting BrainSlayer's post above as saying that Linksys routers and Buffalo WHR-G300N are the exceptions: their tftp address are always respectively 192.168.1.1. and 192.168.11.1, regardless of the particular firmware being used and the IP address configured by the router admin.
I am not sure you are interpreting that properly, although it is possible that user configurations are irrelevant in initial flashing as the CFE could override the user settings during a kernel flash. However, you should do a hard reset prior to flashing which will return the router to factory defaults, which would then require you to flash to that address. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
...
I am not sure you are interpreting that properly, although it is possible that user configurations are irrelevant in initial flashing as the CFE could override the user settings during a kernel flash. However, you should do a hard reset prior to flashing which will return the router to factory defaults, which would then require you to flash to that address.
I am not sure either so at the risk of belaboring the point I really hope the Gurus would elucidate me on this. Not having the right TFTP address would likely lead one to the wrong conclusion about a TFTP attempt failure ...
Basically my question boils down to whether the so-called "factory default" IP address (to be used in TFTP) as a result of a firmware flash always (i.e., for all router types and firmware) gets over-written with a new value that is dependent on the specific firmware (e.g., 192.168.1.1 for DD-WRT). _________________ 2x WRT54G v2
1x F5D7230 v1444
1x WHR-HP-G54
1x WHR-G300N v1
1x WRT300N v1.1
1x RT-N16
1x WNR3500L
Every router that I have that has dd-wrt on it (Linksys and Asus) defaults to 192.168.1.1 upon a hard reset, but those Buffalo 300N's seem to be different, so I would not want to comment on those. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
Hows the latest firmware status now for G300N? I heard there were features not working before (something related to WPA IIRC), and flash method now can be directly via tftp seems? Any feedback on users? _________________ Need Routers? Visit our shop!
)
Soylent Green Is People ! 
so at the risk of belaboring the point I really hope the Gurus would elucidate me on this. Not having the right TFTP address would likely lead one to the wrong conclusion about a TFTP attempt failure ...