[OpenWrt-Users] Arrggh, so studpid!!

[Harmon Seaver]

      All right, I know this was stupid -- I overclocked my cpu to 220
instead of 216, and after the reboot, the power light blinks constantly,
the DMZ light never go on, but if I plug in a compter by ethernet cable,
the correct lan light comes on, and, when I "ifup eth0" that computer, I
get an ip, but it's getting it straight from my DHCP server that the
linksys router is plugged into, and, apparantly, the linksys is not
asking for it's own ip. The computer hooked up thru the linksys router
actually is connected to the internet, like the linksys is just a hub.
    So, what can I do to fix this?
  And yes, I looked at the troubleshooting page before posting. I tried
compiling the recvudp.c source (since there is no linux binary) but when
I run it, I don't get a "blank window" opening, up, just a blank line in
the present window, so I'm not at all sure it's working or not. Anyway,
having run that, and having prior to that set my eth0 to 192.168.1.10, I
don't get any messages at all after plugging in the linksys, nor does
the DMZ light ever flash. Just the power light flashing continually. And
so then I've tried to ping 192.168.1.1 but can't ping it, and, needless
to say, I can't telnet or ssh to it either.
   So does this mean it's bricked?

-- 
Harmon Seaver