Kamikaze 7.07, July 2007
========================
This marks the second official release of Kamikaze.
What's new in Kamikaze?
Build system.
Our build system (aka buildroot) has been completely rewritten since the
whiterussian releases. There's tons of new packages, and adding support
for new packages has never been easier.
Platforms.
There are 10 supported architectures listed below, with support for many
more in progress. Almost all of these platforms are based on 2.6 kernels
with the exception of Broadcom -- Sorry; we couldn't get a stable wifi
connection on 2.6.
Configuration.
We've made a radical change and tossed away NVRAM based configuration
in favor of a much more robust set of config files.
Changes since Kamikaze 7.06
---------------------------
- PPPoE support fixed
- Failsafe on Broadcom fixed
- Failsafe mode on Atheros AR2315+
- Improved system boot time
- New 2.6 kernel with stability fixes for Broadcom
- Improved qos-scripts rate calculation
- Improved wireless-tools compatibility on Broadcom with Linux 2.4
- New version of MadWiFi with improved stability and performance
- New platforms: AMCC, AVR32
- WPA related bugfixes in the wifi scripts for Broadcom and Atheros
- RouterBoard 500 NAND flash fixes
Platforms
---------
amcc-2.6 - AMCC Taishan
atheros-2.6 - Fon Fonera, Ubiquiti LiteStation 2/5, Ubiquiti PowerStation2
Atheros AR231x/AR5312 based devices.
au1000-2.6 - Access/Meshcube (aka 4G Systems MTX-1)
avr32-2.6 - Atmel AVR32
brcm-2.4 - Broadcom devices requiring Broadcom wifi
(everyone migrating from Whiterussian)
brcm47xx-2.6 - Netgear WGT634U, Broadcom Devices without Broadcom wifi
(you can use this instead of brcm-2.4 but wifi won't work)
ixp4xx-2.6 - Adi Engineering Pronghorn Metro, Compex NP18A, Compex WP18,
Gateworks Avila, Iomega StorCenter, Linksys NSLU2*
(NSLU2 avaiable via http://www.slug-firmware.net/)
magicbox-2.6 - Magicbox v1.1 / v2.0
rb532-2.6 - Mikrotik RouterBoard 532
x86-2.6 - x86 based devices (eg. WRAP)
Configuration
-------------
All of the configuration data is now kept within the filesystem, under the
/etc/config directory. This means that when installing or reflashing, the
configuration will be reset to default values as the filesystem is replaced.
LAN: 192.168.1.1/24
WAN: DHCP
WIFI: Disabled
Telnet: Enabled until root password set
SSH: Used after setting root password
The new configuration files are built in sections, each section begins with
a "config" keyword defining the section, followed by one or more "option"
keywords defining values for that section.
config
option
option
...
Configuration can be done either by editing the configuration files directly
or by using the "uci" tool in a manner similar to the previous nvram util.
uci show
uci show
uci show .
uci get ..

uci set ..

=
uci del ..

uci commit
Example:
root@OpenWrt:~# uci show network.lan
network.lan=interface
network.lan.ifname=eth0.0
network.lan.proto=static
network.lan.ipaddr=192.168.1.1
network.lan.netmask=255.255.255.0
root@OpenWrt:~# uci set network.lan.ipaddr="192.168.1.20"
root@OpenWrt:~# uci get network.lan.ipaddr
192.168.1.20
root@OpenWrt:~# uci commit
root@OpenWrt:~# /etc/init.d/network restart
Packages
--------
Additional features or utilities can be added via the ipkg system.
ipkg update
ipkg list
ipkg install
ipkg remove
Note, there are two compressed filesystems, squashfs and jffs2. The squashfs
partition is readonly and contains all the files shipped with the firmware.
The jffs2 partition is writable, and stores changes to squashfs.
- Reinstalling or upgrading packages contained on squashfs is not recommend;
the old package will simply be hidden, not deleted.
- Because the filesystems are compressed, ipkg cannot determine if you have
enough free space, and consequently may run out. If this happens you should
try to manually delete files.
Misc.
-----
Support: http://forum.openwrt.org/
http://irc.openwrt.org/
Bug reports: https://dev.openwrt.org/ (New Ticket/View Ticket)
(Please try support first)