BillyG wrote:I've sent you 2 other files with ping, one is tftp attempt during ping and the other is ping, tftp attempt and ping again...
Yep, I see the echo requests and responses then 5 tftp write requests and not a peep back, then more echo requests and responses.
I can't beleive it is dead, it wouldn't ping i suppose but again i'm not an expert ;)
I never used the term dead. Screwed was the term I used in #1 in my last post. :) It is possible that when shorted the tcp/ip stack gets loaded but something is preventing the tftp server from loading. This would exhibit the observed behavior. I do believe this scenerio is not as likely as the other 2 though.
If you had a second machine that you could sniff from on a hub with the first machine that would eliminate scenerio #2 (firewall blocking).
Scenerio #3 is very possible if you aren't really getting the pins shorted properly. You might also check very carefully that you haven't damaged the pins so that they are touching each other. Also, you might try just a plain nmap to see if any other ports are open. This might indicate whether it has booted all the way up:
# nmap 192.168.1.1
i'll go on trying ! i've decided i wouldn't stop untill i succeed (yes i'm optimistic kind a guy) ;))
I think if none of this gets you going and you really won't stop until you succeed then your next step would be building a serial console connection so you can actually see the boot messages while you boot it. You could see exactly why the tftp server isn't starting. Another easier option to try first might be to build the JTAG connection. I have never done either of these as I have never bricked a router bad enough to need to so I can't help much beyond this. There are several threads on how to do this on the openwrt.org forums and wiki.