1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

What we need is a modulare firmware system for the wrt54g/gs

Discussion in 'Other Firmware Projects' started by Gheimposse, Jan 4, 2005.

  1. Gheimposse

    Gheimposse Network Guru Member

    I bought a wrt54gs some days ago and I´ll have to say that each firmware from hyperwrt over openwrt and sveasoft to wifi-box offers its own goodies which are interesting enough to run this or that firmware.

    But what I´m still missing is a way to choose modules as needed, put them together an creat via a windows based gui the corresponding .bin firmware having a tftp client included to push it up to the router.

    And pleas don´tell me that this is impossible!!! Years ago the guys from FLI4L startet their projekt to use 486 computers via a 1,44MB flloppy drive to bring up small linux firwall system using the computers internal ram.
    The minmal system size was 4mb and was still huge enough to have a web based gui included as well as dyndns, dhcp, etc. modules still included.
    Fli4l (for each who still doesn´t know this piece this project) check out http://www.fli4l.de.
    Fli4l is a german project still be adapted for dsl usage supplying a core code binary as well as a windows based gui.
    You just need to download the needed modules, unzipping them, putting them in the directory to the core code, starting the gui, entering the needed information (ip of wan address, etc.) and press the "go" button so the tools starts to creat the 1,44" floppy disc.
    Also possible there´s a windows client utility with which you´re able to control the router (uptime, connect, disconnect, etc.) as well as doing a update by pushing the new binaries via tftp onto the router.

    Going this way not each and everyone (sorry for Sveasoft) need to invest many time on evaluating and supporting their own firmware ... no each developer may focus on his needs ... one can evaluate a vpn-server another a radius server, the next one the vlan support , etc. pp.
    So the programmers of a module just need to hand out infos for which original firmware the module is written for. If a new firmware comes out he just need to verify whether his module still works with the new firmware or to reprogramm his module for the new release.
    This way not each programmer needs to hack the whole sorcecode in its own.

    Regarding the fact that this is a GPL based code I hope I can interest enough programmers from sveasoft, wifi-box, HyperWRT, TinyPEAP, etc. to work togehter instead of side by side each on its own creating own releases.


    With this idea you have more time on your own by investing less support for a whole firmware instead just bringing out the best out of your modules. You also just need to support your own modules!
    "Wish list" are up to this date a thing of yesterday cause each and everyone can choose their modules, put them together on the current, official linksys firmware to have their own idea.
    Also improved firewall scripts, or telnet functions are able to be implemented ... you just overwrite the current source code.


    For all programmers ... please let me know if you´re interested!

  2. Disman_ca

    Disman_ca Super Moderator Staff Member Member

    You use the word "module" but the term should probably be "package" as that is what it is being called. Sveasoft will be offering this as a feature of Talisman. Load a package to the router instead of it being in the core firmware. I can't remember off hand but there is a least 1 other WRT54G/GS dev group who currently supports packages. The same thing is being done on the NSLU2. Core firmware and opensource packages are being compiled to run on the target processor system. The idea I think is still there in the current firmware. It is decided right now whether or not to put it in the core firmware. In Sveasoft's case PPTP and SNMP just to name 2 additions. It is a great idea and it will spawn more once the dev community begins to model the core firmware after this idea. I think there is general consensus to move to this approach.
  3. __nbd

    __nbd Network Guru Member

    Well... Sveasoft announced some 'modular' stuff, but so far, they haven't implemented anything at all in that area.

    About OpenWrt: We already have the kind of modularity you're talking about, we even had the standard package stuff for a long time now, but it's not implemented for Windows yet. Our source code builds two extra packages (currently Linux only) for that purpose:
    1) The OpenWrt SDK - This is a precompiled toolchain together with our core makefile code for building packages - you can use that to create your own packages in a format that can be added to our source code later
    2) The OpenWrt ImageBuilder - You can use it to make your own custom firmware image containing only the packages that you want. Just add your .ipk files to the package directory, run make and you'll get a firmware bin containing those packages that can be uploaded with the standard TFTP method.

    Maybe we'll add a web frontend for the Image Builder later, so that even windows users can configure their own custom firmware image.
  4. zgamer

    zgamer Network Guru Member

    OpenWRT is great in that way but what I would like to see would be a standardized web-interface for it where when you install addon modules, there would be a web-addon for managing it....much like webmin for regular linux/unix based boxes.
  5. __nbd

    __nbd Network Guru Member

    We're working on it, and a web interface that implements will be added soon (probably in the next few days).
    The thing already works, the developer just wants to clean up its code, before things get merged into our CVS
  6. zgamer

    zgamer Network Guru Member


Share This Page