Yeah, I've already bricked one that way, thats why I am not restarting this router. There must be a way to get it not to say that, and why it says that for me for 2 routers, and you for your 1, and it works without incident for others, thats my question.
I followed the instructions on the second page to a tee. But the part where it says that by default the router gets its address via DHCP, and uses port 8080 is either wrong, or my router is bricked.
My main router did assign the IP 192.168.1.235 via DHCP, but when I ping it I get a request timeout.
Joined: 25 Oct 2006 Posts: 28 Location: Pennsylvania USA
Posted: Thu Feb 22, 2007 6:57 Post subject:
Try a LAN cable and setting your PC IP to 169.254.255.2, and connect to http://169.254.255.1:8080 and see if you get the GUI, if not, try telnetting to port 9000 at that same IP, or SSHing to defualt port on that IP.
seems like you folks have tried to flash from within openwrt...
but if your fonera is already running openwrt the right way should be flashing through redboot...this way is working for sure!
Try a LAN cable and setting your PC IP to 169.254.255.2, and connect to http://169.254.255.1:8080 and see if you get the GUI, if not, try telnetting to port 9000 at that same IP, or SSHing to defualt port on that IP.
Yeah, I realized my mistake, and I started doing it with the correct instructions, and now I can get into redboot if I telnet into it early after hooking it up... but no matter what I can't seem to get the gui.
I am gonna try a few more things, but I am not sure what I'm doing wrong here.
Out of interest, when you try to do anything on 169.254.255.1, does it take a long time to time out (20secs+)? With mine, if I try to get the GUI is takes ages to time out but if it try any other IP, it times out instantly. Does this mean there is hope I can get into redboot? _________________ I love my WRT!
Out of interest, when you try to do anything on 169.254.255.1, does it take a long time to time out (20secs+)? With mine, if I try to get the GUI is takes ages to time out but if it try any other IP, it times out instantly. Does this mean there is hope I can get into redboot?
I am not sure about that right now, as I don't have the router handy to test it.
But, as far as me getting into redboot, I used 192.168.1.254 (port 9000), not 169.254.255.1. Also, I didnt try to connect right away, I plugged it in, and waited for the lan port to start blinking, and THEN I tried to connect as soon as it started blinking.
Is that dependent on which build you try to install?
I run those commands, and notice no errors at all, and yet, when I reset, it doesn't work. What am I doing wrong? I'd give you the output, but it like overwrites itself as I'm doing it in putty.