home 
wiki
wiki
Spelling: MWRPSoftware
MWRP SOFTWARE
This page is currently a scratch area for evolving the software model
for the MWRP.
Previous thinking was based on developing/modifying add-on packages
(ipkg) to create the basic set of software we think is needed on the
router. The problem was/is that there still needs to be some
customization and configuration and that it woul dbe better to
generate a pre-configured firmware image using something like the
freifunk tools.
WRT54GS PACKAGE DEVELOPMENT
* Basic package that installs and configures these packages:
* quagga,
* wl,
* dropbear, _think this is included in even the thinnest base
package_
* ip,
* frottle,
* chillispot, _ replace with_ MWRPHotspot
* interface-wrt.
* Firewall/NAT script suitable for two public wireless interfaces
and one private wired-LAN interface _Done - included as part of_
MWRPHotspot
* Basic web-interface - network interfaces, wireless setup. Based on
either the interface-wrt OpenWRT [1] package or the freifunk-webadmin
component of the excellent German _Freifunk Firmware [2] project for
OpenWRT [3]
* DHCP client and DHCP server settings Changing this from using the
NVRAM settings means configuration can easily be done through the
config file - a better approach_
* Firewall/NAT web-interface
* Routing (Quagga) web-interface
* Captive-portal web-interface
* Automatic activiation of Frottle on wireless interfaces - Frottle
mode (master, client) corresponding to wireless mode selected (AP,
client)
CURRENT MWRP STATUS
MWRP is available via CVS using:
$ export CVSROOT=:pserver:wireless.org.au:/var/cvs $ cvs checkout
mwrp
Currently, it builds a .ipkg file that can be loaded directly onto
any OpenWRT [4] based device. There are some pre-requisites. Make sure
you read the INSTALL file to get the whole story. If you have any
contributions to make, add features, fix bugs etc, then patches are
accepted by CRC. His address is in the AUTHORS file.
OPEN QUESTIONS
* Do we still want a master package?
* Is the list of packages the extent of what we think should go in
the router?
* Do we need to do any web-admin construction or can we use a
package? If there is a package how do we add our own application admin
stuff to it?
* Is there anyone out there who gives a toss?
WHO DO WHAT?
I (dna) can do any package creation and shell scripting we need. I
have created some simple sript based menus for the Hotspot package
that shouldbe easy to turn into web forms. Any volunteers?
Dan, can you get us up to speed on how the freifunk packaging works (
like what the parameters for running the script are and how we can
extend the web interface?
Links:
------
[1] http://melbournewireless.org.au/?OpenWRT
[2] http://ff-firmware.sourceforge.net/
[3] http://melbournewireless.org.au/?OpenWRT
[4] http://melbournewireless.org.au/?OpenWRT
[EditText] [Spelling] [Current] [Raw] [Code] [Diff] [Subscribe] [VersionHistory] [Revert] [Delete] [RecentChanges]