I am using a Linksys WRT54G v1.1, with firmware OpenWrt Kamikaze 7.07 (squashfs). After installing OpenWrt using linksys web interface, i tried to install the web interface but not suscefull. Also, when try to change the firmware image to the orginal linksys using tftp in windows XP, i always recive "Timeout" error even when i disable the firewall. when i tried the "Tftp32 by Ph. Jounin" it shows that the transimmtion will begine and only show "block #0" and nothing moving.
I need your help in changing the firmware to linksys orginal or installing the web interface.
Topic: Linksys WRT54G missing web interface
The content of this topic has been archived on 17 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.
Kamikaze doesn't come with web interface. If you had searched into forum posts, you would have found out this information
So:
If you intend to use Kamikaze with web interface upload this file: http://downloads.x-wrt.org/xwrt/kamikaz … uashfs.trx. http://x-wrt.org is the web site dedicated to the OpenWrt web interface project.
If you intend to restore Linksys firmware:
New OpenWrt doesn't support .bin files, so you have to tftp an intermediate .trx file. My advice is to try with a WhiteRussian trx image.
(Last edited by ggp81 on 18 Feb 2008, 14:59)
From my local FAQ:
====== Does OpenWrt Kamikaze have a web GUI? ======
Short answer: no.\\
X-Wrt (http://www.x-wrt.org/) has a package which you can install ontop of OpenWrt Kamikaze and provides a web GUI called webif^2.
Thanks ggp81 and forum2008 for your reply.
I will try the soultion and get a feedbak.
I too find my self in a similar place.
I have another wrt linksys V3 running DDWRT.
On a spare wrt54g version 3, I was fiddling about with different versions of firmware, installed tomato and then after reading around I saw some features that may have suited a project I was working on in the openwrt firmware.
Sadly before starting I did not read closly enough to see no GUI...
So now begins my interest and fiddle with CLI
Perhaps a little about my computer knowledge, CPM with a Z80. (so long ago, forgotten it mostly by now.. Then Amiga then Dos and various Windows to XP
I have reasonable network configuration abilities, hard setting ip addresses, gateways, etc. Can handle dos command prompts OK.
Have had a little fiddle with Ubuntu but do not know too much about Linux architecture.
I installed Kamikaze 7.09 without fully understanding what I was doing.
Much reading, trial and error enabled a ping to 192.168.1.1 but no web page. telnet 192.168.1.1 produces
=== IMPORTANT ============================
Use 'passwd' to set your login password
this will disable telnet and enable SSH
------------------------------------------
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@(none)hmm#
I did try passwd and then found I could no longer telnet.
Ping still worked OK.
Tried an SSH client and also TFTP
Manged to get it back to telnet state.
IPKG command
root@(none)hmm# ipkg update
ipkg: cannot create directory '/usr/lib/ipkg/lists': Read-only file system
ipkg: cannot create directory '/usr/lib/ipkg/lists': Read-only file system
ipkg: cannot create directory '/usr/lib/ipkg/lists': Read-only file system
An error ocurred, return value: 22.
Collected errors:
ipkg_update_cmd: ERROR: failed to make directory /usr/lib/ipkg/lists: Read-only
file system
root@(none)hmm#
and then
root@(none)hmm# ipkg list
ipkg: cannot create directory '/usr/lib/ipkg/lists': Read-only file system
ipkg: cannot create directory '/usr/lib/ipkg/lists': Read-only file system
base-files-brcm47xx-2.6 - 10-9078 -
bridge - 1.0.6-1 -
busybox - 1.4.2-2 -
dnsmasq - 2.39-1 -
dropbear - 0.50-2 -
hotplug2 - 0.9+r102-2 -
iptables - 1.3.7-1 -
kernel - 2.6.22-brcm47xx-1 -
kmod-diag - 2+2.6.22-brcm47xx-1 -
kmod-madwifi - 2.6.22+r2568-20070710-brcm47xx-2 -
kmod-ppp - 2.6.22-brcm47xx-1 -
kmod-pppoe - 2.6.22-brcm47xx-1 -
kmod-switch - 2.6.22-brcm47xx-1 -
libgcc - 4.1.2-10 -
mtd - 5 -
ppp - 2.4.3-8 -
ppp-mod-pppoe - 2.4.3-8 -
uclibc - 0.9.28-10 -
udevtrigger - 106-1 -
wireless-tools - 29-1 -
Done.
I have tried
http://x-wrt.org/
and their suggestions
Method #2
Flash OpenWrt White Russian then install X-Wrt packages
If you do not already have OpenWrt White Russian on your router, download an appropriate OpenWrt White Russian image and flash it (follow instructions in OpenWrt's wiki). We recommend White Russian RC5, RC6, or 0.9. Kamikaze support is a work in progress, but many functions are supported already.
WARNING: Do not install webif² on the micro images OpenWrt distributes. They lack the 'ipkg' package, which is currently critical to the proper operation of webif²
Installation:
1. SSH to your router, or telnet if you've not set a password yet.
2. Add the X-Wrt package repository with this command:
echo "src X-Wrt http://download2.berlios.de/pub/xwrt/packages" >> /etc/ipkg.conf
3. Refresh the package lists this command:
ipkg update
4. Finally, install webif^2 via:
ipkg install http://ftp.berlios.de/pub/xwrt/webif_latest_stable.ipk
On trying the
root@(none):/# echo "src X-Wrt http://download2.berliosde/pub/xwrt/packages" >> /etc/ipkg.conf
/bin/ash: cannot create /etc/ipkg.conf: Read-only file system
root@(none):/#
Seems I have to change my file system to writable? But how?
I have tried to TFTP original firmware.BIN but get timeouts. seems only TRX is supported? Tried that too..
I am now well sure I am in past my abilities and am unsure if I should try the passwd and SSH options again as suggested by http://martybugs.net/wireless/openwrt/flash.cgi
Now to other things tried.
looked at
3.5. via the OpenWrt commandline
mtd -r write firmware.trx linux
Have tried it from within the telnet 192.168.1.1
No matter what I try I can seem to direct the system to any of the windows directories that I place the firmware.trx file into.
root@(none):/# mtd -r write p:openwrt.trx linux
Couldn't open image file: p:openwrt.trx!
root@(none):/# mtd -r write p:\openwrt.trx linux
Couldn't open image file: p:openwrt.trx!
root@(none):/# mtd -r write p:\\openwrt.trx linux
Couldn't open image file: p:\openwrt.trx!
root@(none):/# mtd -r write p:/openwrt.trx linux
Couldn't open image file: p:/openwrt.trx!
root@(none):/# mtd -r write p://openwrt.trx linux
Couldn't open image file: p://openwrt.trx!
root@(none):/# mtd -r write p openwrt.trx linux
Tried to update password
root@(none):/# passwd
Changing password for root
New password:
Retype password:
passwd: cannot update password file /etc/passwd
Grr I feel like a rite wally!!!!
Any help would be greatly appreciated.........
(Last edited by grunthos on 12 Mar 2008, 20:45)
Squashfs is a read-only file system, so you cannot modify it.
In order to tftp your new firmware look here: http://wiki.openwrt.org/OpenWrtDocs/Installing/.
You can of course update your firmware also using mtd.
Log into the shell, then type
root@OpenWrt# cd
root@OpenWrt# wget http://downloads.x-wrt.org/xwrt/kamikaze/7.09/brcm-2.4/openwrt-brcm-2.4-squashfs.trx
root@OpenWrt# mtd -r write openwrt-brcm-2.4-squashfs.trx linux
If your router is not directly plugged to the Internet, download that file from your PC, then copy it into the /tmp/ directory in the router (use WinSCP if you are using Windows, or SCP command if you are under Unix/Linux) and use the mtd command as I mentioned above.
(Last edited by ggp81 on 20 Mar 2008, 10:10)
The discussion might have continued from here.