OpenWrt Kamikaze 7.06 Released

Discussion in 'X-WRT - OpenWRT Firmware' started by thepeople, Jun 5, 2007.

  1. thepeople

    thepeople LI Guru Member

    Copied from the release notes:

    Kamikaze 7.06, June 2007

    This marks the first 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.

    There are 8 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.

    We've made a radical change and tossed away NVRAM based configuration
    in favor of a much more robust set of config files.


    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)

    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

    magicbox-2.6 - Magicbox v1.1 / v2.0

    rb532-2.6 - Mikrotik RouterBoard 532

    x86-2.6 - x86 based devices (eg. WRAP)


    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.

    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 <type> <name>
    option <name> <value>
    option <name> <value>

    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 <config file>
    uci show <config file>.<config name>
    uci get <file>.<config>.<option>
    uci set <file>.<config>.<option>=<value>
    uci del <file>.<config>.<option>
    uci commit


    root@OpenWrt:~# uci show network.lan

    root@OpenWrt:~# uci set network.lan.ipaddr=""

    root@OpenWrt:~# uci get network.lan.ipaddr

    root@OpenWrt:~# uci commit

    root@OpenWrt:~# /etc/init.d/network restart


    Additional features or utilities can be added via the ipkg system.

    ipkg update
    ipkg list
    ipkg install <package>
    ipkg remove <package>

    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.



    Bug reports: (New Ticket/View Ticket)
    (Please try support first)
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice