[TriLUG] bricked wrt54g.. or WTF54g?

[Greg Brown]

This goes from odd to surreal.  I know I'm missing something basic
here, but how I can do the following:

1. install openwrt, screw it up
2. unbrick it, put it back in tftp mode and reinstall linksys code
3. put a static ip on the wan port, put the device into boot_wait
4. reinstall openwrt, problem presists
5. unbrick, reinstall linksys code
6. boot back to linksys and my static port is still configured to the
IP Address I set it to in step #3?  This AFTER installing openWRT?

Where is the configuration file for these images being stored?  I
imagine the image goes to flash (duh) but how can a specific
configuration survie a tftp upload and boot of a totally differnt file
system?  I'm confused.

Greg

On 5/31/05, Greg Brown <gwbrown1 at gmail.com> wrote:
> my absolute last-ditch effort is going to be:
> 
> 1. revert back to Linksys code
> 2. upload new(er) built binary
> 
> After that, I'm stumped.  I like your "bad memory" theory.  Well, I
> hate it, really, but I can see how that can happen though I try to
> forget my expirence taking down JP Morgan's trading floor with a as
> then undiscovered firmware bug.
> 
> Greg
> 
> 
> On 5/31/05, Jeff Groves <jgroves at krenim.org> wrote:
> > My guess is that you've got a glitch in your system.
> >
> > Possibly the firmware chip has a bad memory location at a critical point
> > where the telnet server config/software resides.
> >
> > My old Linksys router has a similar problem where the firmware has
> > always had a problem taking a new firmware upload.
> >
> > I blame cheap Linksys parts.
> >
> > Jeff G.
> >
> > Greg Brown wrote:
> >
> > >This is strange.  Back to the bricked unit of mine (the one that
> > >wouldn't allow ssh connections and would no longer allow telnet
> > >because the root pw was set).
> > >
> > >It was time for hardcore battle, I needed this little unit to work so
> > >I went for desperate measures.  It is a v.2 unit so, per Shane's
> > >instructions, I shorted pins 15 and 16, and applied power.  Whoopie!
> > >>From there I re-TFTP'ed the openwrt code.  Upon reboot, same problem:
> > >telnet would fail with the following erorr:
> > >
> > >Login failed.
> > >Connection closed by foreign host.
> > >
> > >Crap.  So I go back, short the pins, then upload an older version of
> > >Linksys code.  This loads up all well and good and even allows me to
> > >log into the web interface as Admin, just like it should.  I then
> > >proceed to run the ping exploit, put the unit into boot_wait, pull the
> > >power, then set up my tftp server to upload OpenWRT.  When the code is
> > >uploaded again.. guess what?  Same telnet error and no ssh.  I mean..
> > >say what?!?!  If I went as far as to reupload the linksys code,
> > >exploit the unit from there, THEN put back the openWRT code wouldn't
> > >it be logical that it would work?
> > >
> > >Is anyone not as confused by this as me?
> > >
> > >Greg
> > >
> > >
> >
> > --
> > Jeff Groves
> > email: jgroves at krenim.org             Web Site: http://www.krenim.org/
> >
> >
> > --
> > TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
> > TriLUG Organizational FAQ  : http://trilug.org/faq/
> > TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
> > TriLUG PGP Keyring         : http://trilug.org/~chrish/trilug.asc
> >
>