I had everything working well in white Russian. I decided to make the move to kamikaze. When i flashed the firm wear the browser just froze. It stayed on the browser for about a hour but i turned it off as that it froze. Now i can get a ping from 192.168.1.1
but can not get a page in my web browser from the same address. I saw that some people say there is no web interface in kamikaze.

Now I only have windows units here but could set up a Linux box (but i am a Linux noob) and was wondering how exactly I could get in and put it back to white Russian. I tried to t ftp the firmware back in  for about 3 hours experimenting with the timeout, but it always times out. Spend about 5 hours working with link sys to try to get back in. to no avail. They say its covered under warranty but when i try to turn it in they say to take it to sprint, then sprint says take it to link sys.

any ideas?

You should be able to get in via telnet.  Then you can reflash White Russian from there:

http://forum.openwrt.org/viewtopic.php?id=14321

ok got it to go to failsafe mode. I am a little fuzzy on how to get the white russian software back in. Keep in mind I am in windows xp. I do have a linux install on a cd disk and could reboot the the computer connected to the router with the cd. I am a linxu noob though.

any possiblity doing this from windows xp?

well i found that in this post

http://forum.openwrt.org/viewtopic.php?id=14321

that you could somehow get to the router using ssh, not sure how to do that but had a utility called putty. I tried 192.168.1.1 with port 22 but no go.

I also saw in the post where he said to open up a web server. any ideas how to do that? Are they talking linux there? I am on a xp pc.

Its amazing everonone on the board here talks about this kind of thing like its second nature.

After you have installed Kamikaze, SSH is initially disabled.  You will have to telnet in.  PuTTY supports telnet too.  You just need to specify Telnet instead of SSH.  The port should show as 23.

(If you want to be able to use SSH to get into the router, you first have to telnet in and run the "passwd" command to set the root password.  Then log out and you should be able to SSH in.)

When you are in, you can try the "cd /tmp", "wget ...", "mtd ..." as mentioned in that post.

If that doesn't work, (e.g. because the router can't talk to the Internet, then first download the trx file to your PC, set up a web server on your PC, and then telnet to the router again, and do the "cd /tmp", "wget", etc., but use the IP address of your PC instead of downloads.openwrt.org in the "wget" command.

It is possible to install X-Wrt (which is basically a web interface for OpenWrt) on Kamikaze.  I have never tried that myself, but there should be instructions at x-wrt.org.

Ok, well I thought I would ask about this bit, "set up a web server on your pc". Well i have never heard about that. Will try to google that to see how to do it. I know it sounds funny but I really have never heard about that.

Ok well I got the router to where it says its in failsafe mode. The first light on the router is continually blinking the network link to the computer is solid, although the network link in the tray has the little yellow triangle on it I believe thats because in this mode there is no dhcp.

I opened putty and then checked telnet, then port 23 and the web address 192.168.1.1 it looks like its going to work but then after a bit it makes a windows error sound (sounds like "bonk") then closes putty.

Ok then so then i open up the network connection and check the ip address. I set the ip address to 198.168.1.7 and the dns servers to open dns which is  208.67.222.222 and 208.67.220.220. then the link says connected instead of having the little yellow triangle.

This looks a little better.

Now to putty, wow now i see a nice little text based open wrt deal and says root, etc. and a recipe for a drink. NIIIIIIICE.

now i am in new waters, or old if you count dos prompt. My world will be back to normal when I can flash over the white Russian I was using that was stable back on to the router and go back to "GUI noob" world. So now I ham staring at a terminal wondering about "open a web server on your pc" means. I have the firmware I need on the root of this drive named open.bin I guess i need a trx version.

I will check that other post and see if i can make sense of it. any ideas? "Hold my hand mommy this rides scary." jk

ok then i put the trx at the root of the c: file
I then type in

cd /tmp wget http://192.168.1.7/blah.trx

But i bet this wont work unless I find out how to "make a web server on my pc"

???/

ok am looking at a page on how to open a web server on my computer.
http://lifehacker.com/software/feature/ … 124212.php
says download a apache web server. doing that, but thinking maybye this is over kill, but don't know

ok so i am in the terminal i opened that is connected to my router.
i typed in cd /tmp
then I am typing in wget http://192.168.1.7/code.trx
I changed firmwears name to code.trx (it was a trx file to start with)

I am waiting to push enter until I get through setting up the apache server. Thats all new to me.

ok in apache server setup I put in

server adress               192.168.1.7
adn name of server      avery
then my e-mail adress timjordan AT cheerful DOT com

going to try to see hwo to do this, wondering where i put the firmwear file and how It knows where to get file from.

the mystery deepens

ok in apache web server

opening up a file
C:\Program Files\Apache Group\Apache2\conf\httpd.conf file.

renamed DocumentRoot "C:/" because this is where the code.trx file is

C:\Program Files\Apache Group\Apache2\conf\httpd.conf file.

renamed #DocumentRoot "C:/Program Files/Apache Group/Apache2/htdocs"
to:
DocumentRoot "C:/" because this is where the code.trx file is

then

Last, about 20 lines below that <Directory line, there is a line that reads:

AllowOverride None

Change it to:

AllowOverride All

then is says i should be able to go to localhost and see my files listed, opps I get

Forbidden

You don't have permission to access / on this server.
Apache/2.0.63 (Win32) Server at localhost Port 80

Don't remember changing a pass word. I wonder what to do now...

well goofed around with modifying this file for about a hour it doesnt work. Sio am looking at some other solutions. hopefully one with a gui and not a text file to edit that is unrelaiable in my experience. I hate editing text files and such cause one error and its toast.

going to download something from this page until it works

http://microsoft.toddverbeek.com/phttpd.html

ok downloaded the server called bad blue. Then went to the terminal and said wget http://192.168.1.7/files/code.trx

it took it and said 100%

I guess the new firmwear is on?
lets go to 192.169.1.1 and see

hmmm i try to open 192.168.1.1 and it says file not found.

I ping it and i get a return

Hmmmm maybe I am missing a step. One i got the file code.trx over to the router was I supposed to do anything after?

I unplugged the router then plugged it back in and did the above where I tried to reach it in the web browser. I would really like to get the firmware back on where I can access through web page.

ok then go to the putty deal again, put in 192.168.1.1 and it says login as:

I first try admin then it asks for password

i try the old password i had in white Russian, also Admin as the password, then 0000 nothing seems to work.

Now the firmware i stuck over there was the current linksys firmware in trx form, I know it is a good firmware because I used it before.
I am wondering if after I got the firmware over there I was supposed to do something with it, I will put my NOOB cap on and think about it.

tried to go online and go to google and find the default kamakazie password, no suce luck.
I WGEt ove the firmwear that is the linksys version but a trx file. It took it.
The password should be admin. but does not work when i try to use PUTTY to get on in.

any ideas on what to do next?

ok got in the router again with telnet
said cd /tmp
then i said
wget http://192.168.1.7/files/open.bin

Open.bin is the firmware i really want on there. it is 7_openwrt-3g-r75-wrt54g3g-st-squashfs but in bin form
I don't have it in trx form
anyway to get this open.bin to be my firmware instead of whats on there now?
when i telenet in it says I am in kamakazie 7.09

I wish i could look this up but don't know how to make this work.

Its like i am allmost there but not quite

here is my unfruitful attempt to try to make sure boot wait is on, and how do i get this firmware flashed on there.

BusyBox v1.4.2 (2007-09-29 09:36:14 CEST) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
|       |.-----.-----.-----.|  |  |  |.----.|  |_
|   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
|_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
KAMIKAZE (7.09) -----------------------------------
  * 10 oz Vodka       Shake well with ice and strain
  * 10 oz Triple sec  mixture into 10 shot glasses.
  * 10 oz lime juice  Salute!
---------------------------------------------------
root@OpenWrt:/# tmp
/bin/ash: tmp: not found
root@OpenWrt:/# /cd tmp
/bin/ash: /cd: not found
root@OpenWrt:/# cd /tmp
root@OpenWrt:~# wget http://192.168.1.7/files/open.bin
Connecting to 192.168.1.7 [192.168.1.7:80]
open.bin             100% |*****************************|  1941 KB 00:00:00 ETA
root@OpenWrt:~# %mtd -e linux -r write open.bin linux
/bin/ash: %mtd: not found
root@OpenWrt:~# tmp
/bin/ash: tmp: not found
root@OpenWrt:~# %mtd -e linux -r write open.bin linux
/bin/ash: %mtd: not found
root@OpenWrt:~# nvram set boot_wait=on
/bin/ash: nvram: not found
root@OpenWrt:~# nvram set boot_wait=on nvram commit reboot
/bin/ash: nvram: not found
root@OpenWrt:~# nvram set boot_wait=on
/bin/ash: nvram: not found
root@OpenWrt:~# #nvram set boot_wait=on
root@OpenWrt:~# #nvram get boot_wait
root@OpenWrt:~# #nvram commit
root@OpenWrt:~# #nvram get boot_wait
root@OpenWrt:~# #nvram get boot_wait
root@OpenWrt:~# set boot_wait on
root@OpenWrt:~# set nvram boot_wait
root@OpenWrt:~# commands
/bin/ash: commands: not found
root@OpenWrt:~# Connecting to 192.168.1.7 [192.168.1.7:80]
/bin/ash: Connecting: not found
root@OpenWrt:~# open.bin             100% |*****************************|  1941 KB 00:00:00 ETA
/bin/ash: open.bin: not found
/bin/ash: dhcp.leases: not found
/bin/ash: 1941: not found
root@OpenWrt:~# root@OpenWrt:~# %mtd -e linux -r write open.bin linux
/bin/ash: root@OpenWrt:~#: not found
root@OpenWrt:~# /bin/ash: %mtd: not found
/bin/ash: /bin/ash:: not found
root@OpenWrt:~# root@OpenWrt:~# tmp
/bin/ash: root@OpenWrt:~#: not found
root@OpenWrt:~# /bin/ash: tmp: not found
/bin/ash: /bin/ash:: not found
root@OpenWrt:~# root@OpenWrt:~# %mtd -e linux -r write open.bin linux
/bin/ash: root@OpenWrt:~#: not found
root@OpenWrt:~# /bin/ash: %mtd: not found
/bin/ash: /bin/ash:: not found
root@OpenWrt:~# root@OpenWrt:~# nvram set boot_wait=on
/bin/ash: root@OpenWrt:~#: not found
root@OpenWrt:~# /bin/ash: nvram: not found
/bin/ash: /bin/ash:: not found
root@OpenWrt:~# root@OpenWrt:~# nvram set boot_wait=on nvram commit reboot
/bin/ash: root@OpenWrt:~#: not found
root@OpenWrt:~# /bin/ash: nvram: not found
/bin/ash: /bin/ash:: not found
root@OpenWrt:~# root@OpenWrt:~# nvram set boot_wait=on
/bin/ash: root@OpenWrt:~#: not found
root@OpenWrt:~# /bin/ash: nvram: not found
/bin/ash: /bin/ash:: not found
root@OpenWrt:~# root@OpenWrt:~# #nvram set boot_wait=on
/bin/ash: root@OpenWrt:~#: not found
root@OpenWrt:~# root@OpenWrt:~# #nvram get boot_wait
/bin/ash: root@OpenWrt:~#: not found
root@OpenWrt:~# root@OpenWrt:~# #nvram commit
/bin/ash: root@OpenWrt:~#: not found
root@OpenWrt:~# root@OpenWrt:~# #nvram get boot_wait
/bin/ash: root@OpenWrt:~#: not found
root@OpenWrt:~# root@OpenWrt:~# #nvram get boot_wait
/bin/ash: root@OpenWrt:~#: not found
root@OpenWrt:~# root@OpenWrt:~# set boot_wait on
/bin/ash: root@OpenWrt:~#: not found
root@OpenWrt:~# root@OpenWrt:~# set nvram boot_wait
/bin/ash: root@OpenWrt:~#: not found
root@OpenWrt:~# root@OpenWrt:~# commands
/bin/ash: root@OpenWrt:~#: not found
root@OpenWrt:~# /bin/ash: commands: not found
/bin/ash: /bin/ash:: not found
root@OpenWrt:~# root@OpenWrt:~#
/bin/ash: root@OpenWrt:~#: not found
root@OpenWrt:~#

went to ssh to try to get the boot wait on.

asks me for the login as and the password

Hi.  Sorry, I don't have time to read through all your posts right now.

When flashing from a telnet/SSH session you want the trx version, not the bin version.  The different bin versions are identical to the trx version in the same directory, except that they have a few bytes tacked on the beginning.  The bin files are needed if you flash through the original Linksys web interface.

There is no password by default.  OpenWrt does not have a default password.  When you flash it, you can telnet in without a password.  SSH is disabled until you set the password via telnet (or via the web interface if there is a web interface).

The White Russian firmware is at:
http://downloads.openwrt.org/whiterussi … uashfs.trx

Here's an explanation of the procedure to flash from the command line:

cd /tmp
(this changes you into the /tmp directory, which is a sort of RAM disk on OpenWrt.)
wget http://...
(This downloads the image to the current directory.  i.e. it puts it into the /tmp directory on the router.)

Then the step you seem to have missed:
(See http://forum.openwrt.org/viewtopic.php?id=14321 again)
mtd -r write openwrt-brcm-2.4-squashfs.trx linux

(mtd is the command that writes the image to the flash.  "-r" means to reboot after flashing.  "write openwrt-brcm-2.4-squashfs.trx" tells mtd you want to write the image called openwrt-brcm-2.4-squashfs.trx.  "linux" is the name of the partition on the flash that mtd will write the image to.)

It should print out [e] and [w] over and over again to show that it is erasing a block of the flash and then writing a block of the image to it, then erasing the next block etc., etc. until it's finished.

I hope that gets you going.

The command is "cd /tmp"

Getting closer...

Aha! 

OK, except as I said, you want a trx file, not the bin file.

Almost.  The command is "mtd", not "%mtd".  Also, you need the trx file, not the bin file.

See comments above.

Kamikaze does not have to nvram command installed by default.  If the router can access the internet (if you don't know, just try it) you can install it as follows:

ipkg update
ipkg install nvram

Then you can run the "nvram set boot_wait=on" command followed by the "nvram commit" command.

Again, the nvram command is not installed.  Also, you would need to put the "nvram commit" and "reboot" commands on separate lines.  i.e. press enter after "on" and after "commit".

See comment above.

The # character, when you enter it at the shell prompt, means "ignore the rest of this line", so your command above is completely ignored.  Some instructions you see on the 'Net might have the command written with the #, but that's just to indicate the shell prompt, which might look different on different systems.  e.g. on yours it looks like "root@OpenWrt:~#", but it could look like "root@myrouter:~#" or "myrouter#" or almost anything else.  (I hope I haven't confused you.)

These are all ignored because you started the command with a #.  (as per my comment above.)

The set command does not do what you want

There is no command called "commands".

This is a bit like a text adventure game, isn't it?

OK, now you're just cutting and pasting random stuff.  Probably not what you want to do.

The dhcp.leases etc. show up because of the asterisks you pasted in there, but I'm not going to get into why that is now.

Still pasting random stuff.  "root@OpenWrt:~#" is the shell prompt.  It's not a command, so if you paste that in it won't work.

Ouch!   See comments above about pasting random stuff.

I hope my comments shed some light on what went wrong above.

well thank god that worked! got it to code bin and then re loaded white russian on it. Woot Thanks!!!