WirelessAfrica - User contributions [en]

WISPiab specifications

2009-02-16T12:28:36Z

Sebastian:

[[Category: WISP in a box]]

=Introduction=

The following is our work copy of a specification / feature wish list for the WISP-in-a-box product.

It is meant to be commented and refined.

Please also note the related document, specifying concrete tasks and job profiles:
[[Image:WISP task specifications.pdf]]

=Business models=

Discussion of business models: [[WISPiab_business_models]]

=High level architecture=

Our currently suggested architecture splits the WISPiab hardware package into two components plus an option:

#Front Access Node
##
# Back end server (with or without screen, depending on existing ...)
##
#(Sub)Laptop as GUI admin (optional)

This seems appropriate based on the analysis of the SW specs in detail.

However, if test implementations seem to suggest reuniting the two tiers on one box, this is an open option, which might bring manageability benefits.

[[Image:WISPiab elements horizontal with net small.png|thumb|left]]

=Software Specification / Feature list for the WISP-in-a-box product=

==Shared functionality==

* All configuration etc to be accessible via browser based GUI
* ssh access

* Routing Protocols
** OLSR
** b.a.t.m.a.n.

==Front access node==

* CoovaAP
** Authentication potentially with 2 options
*** Against itself / on acces node
*** Against back end server Radius

CoovaAP will bring most of the following mandatory features for the front access node.

* OpenSER

==Back end server==

* apache
* php
* mediawiki
* mysql

* ispconfig
** webmin?

* DNS server (DDNS, DynDNS)

* Proxy / Cache
** Squid

===Mail===

* Postfix / Courier
* Webmail: squirrelmail
* gmail syncing desirable
* Google server local? (--> talk to gmail, Kobus)

* Spam/Virus control
** amavis
** spamassassin

===Network management===

* Nagios
* Cacti

* Statistics
** awstats or similar

===Auth, Access, Security, Billing===

* Radius
**FreeRadius
* OpenLDAP
* OpenID

* OpenVPN
* GnuPG

===QoS===

* QoS - details of this not clear yet - what layer? what tools?
** iproute2
** MasterShaper?
** Wondershaper

===Storage, FS===

* NAS – iSCSI

* File servers
** SMB
** NFS
** rsyncing cron'd

* Redundancy - to be specified in more detail
** Would like to build distributed storage - “graded distributed system”

===Voice over IP===

* Asterisk
* OpenSER
* billing integration
** a2billing

===Miscellaneous===

* Local Library of SW
** Documentation
** Integrated Skilling / Education
* patch management
* IpCOP
* wikipedia local copy

* Content filtering ? - discussion!

* Virtualization (XenSource)
** to be discussed - not deemed mandatory

=Hardware Specification / Feature list for the WISP-in-a-box product=

To be spec'ed after completion of SW specs.

==Minimum requirements==

===General requirements for all elements===

* Input: 12 V_dc
* Fanless
* Low power (< 8 W)

===Front access node===

Network interfaces
2 minimum, maybe more

===Back end server===
external switch

==Hardware candidates==

{| rules="rows" frame="hsides" align="left" width="100%" cellpadding=10
|- align="left" valign="top"
!'''Table 1''': Table title
|- bgcolor="lightgrey" align="left" valign="top"
! Name !! candidate for !! CPU Memory Storage !! Power !! Wireless !! Cost !! Comments

|- align="left" valign="top"
| ASUS EEE PC || server? ||
ASUS® EEE PC 700-W - Intel® 900Mhz Pentium®M ULV, 512MB DDR2 Memory, Internal 2GB SSD Based Hard Drive, Intel® 910GML Chipset, 7" 800x480 LCD, 10/100 LAN, WiFi b/g, SD Card Slot, 3xUSB 2.0 / ASUS EEE PC 4g with 4 GB SSD / ASUS EEE 900 with 1 GB RAM, 12 GB SSD
|| power: ? ||- || ? || comments

|- align="left" valign="top"
| dataevolution.com decTOP etc || server? ||
Memory
128MB SDRAM
10GB HDD
|| power: ? ||- || ? || comments

|- align="left" valign="top"
| FON(ERA) || access node ||
CPU: MIPS 180 MHz
Memory: 16 MB ram
|| power || wireless || EUR 40 || comments

|- align="left" valign="top"
| Inveneo Outdoor WiFi Access Point|| access node, server (?) || ??? ask Inveneo || power || 802.11 b/g
Athenos chipset
Peak power: +24dBm (250mW) || Single Radio: $469 USD* Dual Radio: $659 USD* || incl antennas, install kits, outdoor ready

|- align="left" valign="top"
| Inveneo Hub server|| server ||
1.2GHz VIA C7 nanoBGA2 Fanless
VIA CN700 North Bridge
VIA VT8237RP High-bandwidth Vlink Client South Bridge
51MB standard, 1GB optional
One RS-232C serial port (DB-9)
Four USB 2.0 ports (two in front, two in back)
|| < 20 W || -|| Price: starting at $$785 USD* || incl many things, see site :)

|- align="left" valign="top"
| Linksys WRT54G(L) || access node ||
System-On-Chip: Broadcom 5352EKPB

CPU Speed:200 Mhz

Flash size: 4 MiB

RAM: 16 MiB

Wireless: Broadcom BCM43xx 802.11b/g Wireless LAN (integrated) || < 5 W (3.8 if optimized) || wireless || USD 45 || comments

|- align="left" valign="top"
| Accton / Open-Mesh || access node ||
(Atheros AR2315 chipset, 32MB DRAM, 8MB Flash, 1 ethernet port) = Meraki
|| power: ?, 5 V || wireless_ 60 dBm max || USD 45 || comments

|- align="left" valign="top"
| Meraki outdoor || access node ||
Bootloader: RedBoot
CPU: Atheros AR2315
CPU Speed: 180 Mhz
Flash size: 8 MB
RAM: 32 MB
|| Power consumption: 12W max; 3W typical ||
* 200 mW (23dBm) peak transmission power*
* Enhanced receive sensitivity
* External RP-SMA connector
* 802.11 b/g (1-54 Mbps)
* 2dBi omni directional antenna included
|| USD 49/99 || note EULA issues!

http://www.mini-itx.com/

|- align="left" valign="top"
| Mini-ITX / VIA / LEX / Jetway etc || access node, server || varies || power || wireless || cost || see [http://www.mini-itx.com/ http://www.mini-itx.com/] [http://www.via.com.tw/en/products/mainboards/ http://www.via.com.tw/en/products/mainboards/]

|- align="left" valign="top"
| Soekris boards || access node, server (?) || cpu memory storage etc || power || wireless || cost || comments

|- align="left" valign="top"
| Ultra Mobile PCs / sub laptops || becoming a valid candidate as ''Backend/server'' component? ||
many candidates with differing specs, need to check out and test:

* OLPC
* eMate 300
* Classmate PC
* Linutop, Geode LX -based computer
* Longmeng or Dragon Dream, China
* Tianhua GX-1C, Sinomanic in China
* VIA pc-1 Initiative, VIA Technologies digital divide program.
* Zonbu, a low-cost desktop computer
* Eee PC, ASUS and Intel - watch!
* Clio NXT.
* InkMedia MC, another low-cost subnotebook
* Elonex_ONE, subnotebook, expected to be £99

|| ??? - typically low, 3 Watts for OLPC-X01 || typically built in

||

EUR 250 - 400

* OLPC
* eMate 300
* Classmate PC
* Linutop, Geode LX -based computer EUR 280
* Longmeng or Dragon Dream, China
* Tianhua GX-1C, Sinomanic in China
* VIA pc-1 Initiative, VIA Technologies digital divide program.
* Zonbu, a low-cost desktop computer
* Eee PC, model900 = EUR 400, model 4g = EUR 300
* Acer, Q2 2008, approx EUR 250 ?
* Clio NXT.
* InkMedia MC, another low-cost subnotebook
* Elonex_ONE, subnotebook, expected to be £99

|| needs testing and verification as candidates

|- align="left" valign="top"
| WRAP boards || access node, server (?) || cpu memory storage etc || power || wireless || cost || comments

|}

----

==Solar part==

Solar Kit to be spe'ed after HW power is known

File:WISP task specifications.pdf

2009-02-16T11:32:00Z

Sebastian: WISPiab task specifications, Status September 2008

WISPiab task specifications, Status September 2008

WISPiab specifications

2009-02-16T11:25:02Z

Sebastian:

[[Category: WISP in a box]]

=Introduction=

The following is our work copy of a specification / feature wish list for the WISP-in-a-box product.

It is meant to be commented and refined.

Please also note the related document, specifying concrete tasks and job profiles.

=Business models=

Discussion of business models: [[WISPiab_business_models]]

=High level architecture=

Our currently suggested architecture splits the WISPiab hardware package into two components plus an option:

#Front Access Node
##
# Back end server (with or without screen, depending on existing ...)
##
#(Sub)Laptop as GUI admin (optional)

This seems appropriate based on the analysis of the SW specs in detail.

However, if test implementations seem to suggest reuniting the two tiers on one box, this is an open option, which might bring manageability benefits.

[[Image:WISPiab elements horizontal with net small.png|thumb|left]]

=Software Specification / Feature list for the WISP-in-a-box product=

==Shared functionality==

* All configuration etc to be accessible via browser based GUI
* ssh access

* Routing Protocols
** OLSR
** b.a.t.m.a.n.

==Front access node==

* CoovaAP
** Authentication potentially with 2 options
*** Against itself / on acces node
*** Against back end server Radius

CoovaAP will bring most of the following mandatory features for the front access node.

* OpenSER

==Back end server==

* apache
* php
* mediawiki
* mysql

* ispconfig
** webmin?

* DNS server (DDNS, DynDNS)

* Proxy / Cache
** Squid

===Mail===

* Postfix / Courier
* Webmail: squirrelmail
* gmail syncing desirable
* Google server local? (--> talk to gmail, Kobus)

* Spam/Virus control
** amavis
** spamassassin

===Network management===

* Nagios
* Cacti

* Statistics
** awstats or similar

===Auth, Access, Security, Billing===

* Radius
**FreeRadius
* OpenLDAP
* OpenID

* OpenVPN
* GnuPG

===QoS===

* QoS - details of this not clear yet - what layer? what tools?
** iproute2
** MasterShaper?
** Wondershaper

===Storage, FS===

* NAS – iSCSI

* File servers
** SMB
** NFS
** rsyncing cron'd

* Redundancy - to be specified in more detail
** Would like to build distributed storage - “graded distributed system”

===Voice over IP===

* Asterisk
* OpenSER
* billing integration
** a2billing

===Miscellaneous===

* Local Library of SW
** Documentation
** Integrated Skilling / Education
* patch management
* IpCOP
* wikipedia local copy

* Content filtering ? - discussion!

* Virtualization (XenSource)
** to be discussed - not deemed mandatory

=Hardware Specification / Feature list for the WISP-in-a-box product=

To be spec'ed after completion of SW specs.

==Minimum requirements==

===General requirements for all elements===

* Input: 12 V_dc
* Fanless
* Low power (< 8 W)

===Front access node===

Network interfaces
2 minimum, maybe more

===Back end server===
external switch

==Hardware candidates==

{| rules="rows" frame="hsides" align="left" width="100%" cellpadding=10
|- align="left" valign="top"
!'''Table 1''': Table title
|- bgcolor="lightgrey" align="left" valign="top"
! Name !! candidate for !! CPU Memory Storage !! Power !! Wireless !! Cost !! Comments

|- align="left" valign="top"
| ASUS EEE PC || server? ||
ASUS® EEE PC 700-W - Intel® 900Mhz Pentium®M ULV, 512MB DDR2 Memory, Internal 2GB SSD Based Hard Drive, Intel® 910GML Chipset, 7" 800x480 LCD, 10/100 LAN, WiFi b/g, SD Card Slot, 3xUSB 2.0 / ASUS EEE PC 4g with 4 GB SSD / ASUS EEE 900 with 1 GB RAM, 12 GB SSD
|| power: ? ||- || ? || comments

|- align="left" valign="top"
| dataevolution.com decTOP etc || server? ||
Memory
128MB SDRAM
10GB HDD
|| power: ? ||- || ? || comments

|- align="left" valign="top"
| FON(ERA) || access node ||
CPU: MIPS 180 MHz
Memory: 16 MB ram
|| power || wireless || EUR 40 || comments

|- align="left" valign="top"
| Inveneo Outdoor WiFi Access Point|| access node, server (?) || ??? ask Inveneo || power || 802.11 b/g
Athenos chipset
Peak power: +24dBm (250mW) || Single Radio: $469 USD* Dual Radio: $659 USD* || incl antennas, install kits, outdoor ready

|- align="left" valign="top"
| Inveneo Hub server|| server ||
1.2GHz VIA C7 nanoBGA2 Fanless
VIA CN700 North Bridge
VIA VT8237RP High-bandwidth Vlink Client South Bridge
51MB standard, 1GB optional
One RS-232C serial port (DB-9)
Four USB 2.0 ports (two in front, two in back)
|| < 20 W || -|| Price: starting at $$785 USD* || incl many things, see site :)

|- align="left" valign="top"
| Linksys WRT54G(L) || access node ||
System-On-Chip: Broadcom 5352EKPB

CPU Speed:200 Mhz

Flash size: 4 MiB

RAM: 16 MiB

Wireless: Broadcom BCM43xx 802.11b/g Wireless LAN (integrated) || < 5 W (3.8 if optimized) || wireless || USD 45 || comments

|- align="left" valign="top"
| Accton / Open-Mesh || access node ||
(Atheros AR2315 chipset, 32MB DRAM, 8MB Flash, 1 ethernet port) = Meraki
|| power: ?, 5 V || wireless_ 60 dBm max || USD 45 || comments

|- align="left" valign="top"
| Meraki outdoor || access node ||
Bootloader: RedBoot
CPU: Atheros AR2315
CPU Speed: 180 Mhz
Flash size: 8 MB
RAM: 32 MB
|| Power consumption: 12W max; 3W typical ||
* 200 mW (23dBm) peak transmission power*
* Enhanced receive sensitivity
* External RP-SMA connector
* 802.11 b/g (1-54 Mbps)
* 2dBi omni directional antenna included
|| USD 49/99 || note EULA issues!

http://www.mini-itx.com/

|- align="left" valign="top"
| Mini-ITX / VIA / LEX / Jetway etc || access node, server || varies || power || wireless || cost || see [http://www.mini-itx.com/ http://www.mini-itx.com/] [http://www.via.com.tw/en/products/mainboards/ http://www.via.com.tw/en/products/mainboards/]

|- align="left" valign="top"
| Soekris boards || access node, server (?) || cpu memory storage etc || power || wireless || cost || comments

|- align="left" valign="top"
| Ultra Mobile PCs / sub laptops || becoming a valid candidate as ''Backend/server'' component? ||
many candidates with differing specs, need to check out and test:

* OLPC
* eMate 300
* Classmate PC
* Linutop, Geode LX -based computer
* Longmeng or Dragon Dream, China
* Tianhua GX-1C, Sinomanic in China
* VIA pc-1 Initiative, VIA Technologies digital divide program.
* Zonbu, a low-cost desktop computer
* Eee PC, ASUS and Intel - watch!
* Clio NXT.
* InkMedia MC, another low-cost subnotebook
* Elonex_ONE, subnotebook, expected to be £99

|| ??? - typically low, 3 Watts for OLPC-X01 || typically built in

||

EUR 250 - 400

* OLPC
* eMate 300
* Classmate PC
* Linutop, Geode LX -based computer EUR 280
* Longmeng or Dragon Dream, China
* Tianhua GX-1C, Sinomanic in China
* VIA pc-1 Initiative, VIA Technologies digital divide program.
* Zonbu, a low-cost desktop computer
* Eee PC, model900 = EUR 400, model 4g = EUR 300
* Acer, Q2 2008, approx EUR 250 ?
* Clio NXT.
* InkMedia MC, another low-cost subnotebook
* Elonex_ONE, subnotebook, expected to be £99

|| needs testing and verification as candidates

|- align="left" valign="top"
| WRAP boards || access node, server (?) || cpu memory storage etc || power || wireless || cost || comments

|}

----

==Solar part==

Solar Kit to be spe'ed after HW power is known

AfrimeshToDo

2009-01-31T19:58:31Z

Sebastian:

[[Category: WISP in a box]]

= ALPHA - End January =

== Dashboard ==
* Customers
** Recharge -> Solicit feedback
** Manage -> How to make MAC/IP auth obvious from interface ?
** Manage -> Implement seconds left field
** Manage -> Fix New/Modify/Delete/Password
** Manage -> Paginate when > 'x' users
** Prices -> Implement
*** Add or delete a plan
*** Set price & seconds
* Network
** Map -> Refactor
** Map -> Populate popups
** Map -> Cache map data
** Map -> Satellite overlay ?
** Health -> Health monitors
** Health -> Mesh congestion
** Health -> Messages
** Health -> Use case -> Spot misbehaving doze boxes
** Health -> Manage cap
** Health -> Query router settings, firmware versions?
** Activity -> Show seconds left
** Activity -> Show router name/address
** Activity -> Traffic info
* Settings
** Link to webmin
** Mesh -> Provisioning
*** use cases for: flashing firmware, installing packages, changing settings ?
** Mesh -> Set throttling on coova's
** Mesh -> Bandwidth/QOS
*** Manage cap
*** So start off with small allocation
*** Track use
*** Speak to David Johnson
*** Release buffer into the system
** Internet -> Webmin
** Internet -> Drop assumption that we control the gateway and rethink
** Internet -> Bandwidth/QOS
** Internet -> Configure
* Install
** On first run, default to settings pages
** Map -> Configure map: location, size, source (remote/local)

== Routers ==
* Authentication
** coova -> finish packaging config
** a2billing -> write bridge
* Mini Dash
** coova -> Make splash pretty
** coova -> Fix time left fields
** Diagnostics on splash!
** Signals strength indicator
* Install
** On first run, default to settings page
** Zoomed to max extent

== Deployment ==
* Start doing daily builds
* Dashboard Installation
** Ubuntu packages
** ISO
** Download/Generate map data
** phpMyPrepaid package
* Router Installation
** OpenWRT Packages -> broadcom, atheros
*** Firewall configs
*** Auto-configuration
** Pre-installed firmware image
* Documentation
** Dashboard installation
** Router installation
** Instructions for using with other firmwares

== Security ==
* Implement auth

== Logging ==
* Set up some guidelines

== Dev Docs ==
* Document LQ colour coding

== Map Biz Process ==
* For docs

== Reporting Interface ==
* Expose the program tree to plugin / report authors
* Read only
** What are my router channels ?
** etc.

WISP-in-a-box Way Forward

2008-09-09T04:45:38Z

Sebastian: /* Our Approach */

This document remains very much a draft, but is the evolving specification for the WISP-in-a-box project.

=== Overview ===

[[Image:Grafic_(Modified).png|thumb|400px]]

[[Image:Grafic-telco_(Modified).png|thumb|400px|Icon sources: http://villagetelco.org/, http://www.ubnt.com/products/ns2.php]]

The entire WISP-in-a-box system consists of:

* A central dashboard, running on the gateway server, from which:
** the network can be monitored and all nodes can be configured
** prepaid vouchers can be administered
** software running on the server (web & mail services, upstream connection QoS software, etc) can be administered
** all functionality will work without upstream Internet access
* Mesh nodes which:
** receive configuration updates from the central dashboard
** run a captive portal that interacts with clients and authenticates against the gateway server
** run intra-mesh QoS software
** route themselves intelligently using BATMAN

=== Component Diagram ===

The basic setup looks like the digram to the right. For the Village Telco project, many components are the same. There is some additional functionality that's desired, however, that can reside on top of the base WISP-in-a-box system.

This document is going to mainly focus on specifying the needs of the mesh & networking side of things, with an eye towards exactly how voice-related services will be integrated (but not an elaborate discussion of the technologies themselves).

=== Dashboard & Server ===
==== Existing Dashboard Projects ====
The OrangeMesh and Open-Mesh dashboards provide almost exactly the functionality we require. However, they have a number of problems:

* Both dashboards require the nodes to be running ROBIN firmware to receive configuration updates. ROBIN, as it is now, only runs on Atheros-based devices, not Broadcom devices (like the Linksys WRT). Some semi-serious hacking will be required to add support for Broadcom devices into ROBIN, since right now it assumes the use of the Atheros-only MadWifi drivers.
* With an eye towards localization & modularity, the OrangeMesh sources aren't quite what we'd like them to be.

Because of these limitations, we may not want to use the OrangeMesh/Open-Mesh dashboard. We still want to imitate the same basic style of system, however, while adding some functionality to meet the additional needs of our dashboard (e.g. ability to administer vouchers and server services, things that the OrangeMesh/Open-Mesh dashboards don't cover).

==== Our Approach ====
We will start essentially from scratch on the dashboard, with the OrangeMesh dashboard as an example to work off of and borrow heavily from.

The dashboard we will design will be highly modular, with a high-level menu in which the user can select a module to work with. A module might be an existing software component or a new one we've written. In the case of Network Status and Network Configuration, we can use the Orangemesh-Openmesh/ROBIN setup as a reference, and where appropriate can adapt their code to suit our needs. Other tools to borrow from include Zeroshell for network QoS configuration. Essential modules include:

* Server Administration -- brings up Webmin
** This will not only allow us to configure the server, but also execute arbitrary commands on all the mesh nodes using Webmin's cluster functionality. We will strip down a version of Webmin to run on the client nodes and use Webmin's cluster modules on the server to communicate with them. ''Comment: Running stripped down webmin on the nodes might neither be feasible nor needed - instead, we will copy the functionality of such a cluster control, howwever implement it using generic remote commands rather than webmin instances.''
* Vouchers -- brings up phpMyPrepaid, our data billing control system
** phpMyPrepaid additionally controls the CoovaChilli instances running on all routers, including the ability to restrict or permit free access to the rest of the mesh network
** We need to also design in some way of dumping the user usage data that FreeRADIUS stores so that researchers can do usage studies on it. The local user needs to be able to easily dump this data and send it back to the CSIR for study.
* Network Status -- new custom dashboard component with following features:
** A semi-detailed list of all the nodes in the mesh, including:
*** the node's IP and MAC addresses
*** the node's current status (simple up or down)
*** when they were last heard from (when an update from that node was last received)
*** how many hops and/or what route the node currently has to the gateway
** Basic network usage statistics, data taken from RADIUS:
*** Total bandwidth going out of the gateway in the last X amount of time
*** Heaviest users of the network to monitor abuse (further information on individual users is available already in phpMyPrepaid)
** Ability to test network throughput, either through:
*** Simple interface to run iperf between any two nodes, or:
*** Visual display of metrics & signal strengths of every link, data reported from clients' BATMAN daemons and network tools

* Mesh Network Configuration -- new custom dashboard component with following features (note this is designed to be minimal for ease of use):
** Change SSID of mesh network
** Change channel of mesh network
** Other features? Open to discussion.
** Note - It might be necessary to have multiple classes of mesh devices on the network, to accommodate a combination of different hardwares, different channels, etc.
* QoS Network Configuration – new custom dashboard component for adjusting QoS settings both:
** On the server, for outgoing traffic going to the upstream connection
** On the various nodes in the mesh, for intra-mesh network bandwidth management.
* AP-only node configuration – new custom dashboard component that configures node that are only AP's, not part of the mesh. Configures:
** SSID of AP
** Channel of AP
** Any kind of WPA authentication a user might want to run on the AP

Possible other voice-related modules include Asterisk and A2billing modules or pages.

The dashboard will send out all configuration updates using a standardized API; any mesh node in the network will have to run a client implementing this API that receives configuration messages from the dashboard and makes the necessary changes to files on its system. The API will be just as modular as the dashboard, so if a user wants to only implement certain features (say, add billing to an existing network) she would only need to implement a client for the platform her nodes are running (or, ideally, there will already be a client for that platform). Through the dashboard the user could then disable the unwanted modules. The dashboard will only send out updates for the components that are enabled, and the client will only modify configuration files for the components it receives.

All of the components of the larger dashboard will be skinned in a unified CSS style, with the potential for branding built in.

=== Mesh Nodes ===
The mesh nodes themselves will run OpenWRT. Node software includes:

* Batman for routing
* CoovaChilli as a local captive portal
* Intra-mesh QoS software, configurable from the dashboard. Uncertain as to what tools exactly to use here, however borrowing from Zeroshell it may be possible to simply use netfilter/iptables & l7-filter. Using an existing tool here would be very nice, as this is a complex task.
* A client daemon modeled on the ROBIN scripts that receives updates from the dashboard and sends any necessary information back to the dashboard. The client daemon will have to be co-developed with the dashboard.
* Stripped-down Webmin server component so we can run remote Webmin commands on the node through the server's Webmin installation.
* In addition to configuration through the dashboard, we will include a minimal web interface for configuring each individual node. This interface will run on the nodes, and can be a stripped-down version of X-WRT's webif^2 or FFLuCI. It would be useful if the interface could be designed such that it would run on any device regardless of that device's platform. This may be easy to do with existing abstractions in OpenWRT, but an alternative method would be for this interface to change the configuration of the local node via the update API, which is guaranteed to be fully abstracted, and let the update client for that device take care of making the actual changes.

=== AP-only Nodes ===
The mesh nodes will use their radios exclusively for the mesh network ('backhaul'). Clients can be attached directly to the Ethernet ports of these nodes, however it may be useful to have wireless client access as well. In this case, a second device can be attached to the mesh node to act as an access point. These devices can also be Linksys WRTs or similar, running OpenWRT with:

* CoovaChilli
* Dashboard Client with:
** AP-only node configuration module
** CoovaChilli configuration module

=== Task Breakdown ===
Once the specification is agreed upon work can begin. At that time further task breakdowns may be useful, but at a high level the expectation currently is as follows (refer to above for details on what individual software piece entail):

# Dashboard & first client development: Meraka
## Further examination of ROBIN to see which parts of it can be modified for our purposes
## Adaptation of Webmin's cluster tools for use on the mesh
## Determine appropriate tools for QoS [starting point: Zeroshell]
## Update API design & specification
## Dashboard framework design and implementation
## Mesh update client framework design and implementation
## Dashboard module implementation
### Network Monitoring
### Network Configuration – basics (Channel, SSID, etc)
### Network Configuration – QoS settings
### Network Configuration – AP-only settings
### Adapt phpMyPrepaid's CoovaChilli configuration to send out updates via standardized API rather than only changing local configuration file.
## Co-development with dashboard modules: mesh client update modules for each dashboard component, designed initially for the WRT but as portable as possible (for most modules portability should be trivial, as the software on the node the update client is configuring will be the same).
## CSS skinning for all dashboard components (including pre-existing ones such as Webmin and phpMyPrepaid).

# Minimal interface development for starter devices (at least the WRT, Mesh Potato, and Ubiquity nodes): Inveneo
# Porting of mesh client to Ubiquity and Mesh Potato (most modules should be identical, but basic network configuration settings may be device-specific): Inveneo

[[Category:WISP in a box]]

WISP-in-a-box Way Forward

2008-09-09T04:45:11Z

Sebastian: /* Our Approach */ webmin on nodes?

This document remains very much a draft, but is the evolving specification for the WISP-in-a-box project.

=== Overview ===

[[Image:Grafic_(Modified).png|thumb|400px]]

[[Image:Grafic-telco_(Modified).png|thumb|400px|Icon sources: http://villagetelco.org/, http://www.ubnt.com/products/ns2.php]]

The entire WISP-in-a-box system consists of:

* A central dashboard, running on the gateway server, from which:
** the network can be monitored and all nodes can be configured
** prepaid vouchers can be administered
** software running on the server (web & mail services, upstream connection QoS software, etc) can be administered
** all functionality will work without upstream Internet access
* Mesh nodes which:
** receive configuration updates from the central dashboard
** run a captive portal that interacts with clients and authenticates against the gateway server
** run intra-mesh QoS software
** route themselves intelligently using BATMAN

=== Component Diagram ===

The basic setup looks like the digram to the right. For the Village Telco project, many components are the same. There is some additional functionality that's desired, however, that can reside on top of the base WISP-in-a-box system.

This document is going to mainly focus on specifying the needs of the mesh & networking side of things, with an eye towards exactly how voice-related services will be integrated (but not an elaborate discussion of the technologies themselves).

=== Dashboard & Server ===
==== Existing Dashboard Projects ====
The OrangeMesh and Open-Mesh dashboards provide almost exactly the functionality we require. However, they have a number of problems:

* Both dashboards require the nodes to be running ROBIN firmware to receive configuration updates. ROBIN, as it is now, only runs on Atheros-based devices, not Broadcom devices (like the Linksys WRT). Some semi-serious hacking will be required to add support for Broadcom devices into ROBIN, since right now it assumes the use of the Atheros-only MadWifi drivers.
* With an eye towards localization & modularity, the OrangeMesh sources aren't quite what we'd like them to be.

Because of these limitations, we may not want to use the OrangeMesh/Open-Mesh dashboard. We still want to imitate the same basic style of system, however, while adding some functionality to meet the additional needs of our dashboard (e.g. ability to administer vouchers and server services, things that the OrangeMesh/Open-Mesh dashboards don't cover).

==== Our Approach ====
We will start essentially from scratch on the dashboard, with the OrangeMesh dashboard as an example to work off of and borrow heavily from.

The dashboard we will design will be highly modular, with a high-level menu in which the user can select a module to work with. A module might be an existing software component or a new one we've written. In the case of Network Status and Network Configuration, we can use the Orangemesh-Openmesh/ROBIN setup as a reference, and where appropriate can adapt their code to suit our needs. Other tools to borrow from include Zeroshell for network QoS configuration. Essential modules include:

* Server Administration -- brings up Webmin
** This will not only allow us to configure the server, but also execute arbitrary commands on all the mesh nodes using Webmin's cluster functionality. We will strip down a version of Webmin to run on the client nodes and use Webmin's cluster modules on the server to communicate with them. ''Comment: Running stripped down webmin on the nodes might neither be feasible nor needed - instead, we will copy the functionality of such a cluster control, hwowever implement it using generic remote commands rather than webmin instances.''
* Vouchers -- brings up phpMyPrepaid, our data billing control system
** phpMyPrepaid additionally controls the CoovaChilli instances running on all routers, including the ability to restrict or permit free access to the rest of the mesh network
** We need to also design in some way of dumping the user usage data that FreeRADIUS stores so that researchers can do usage studies on it. The local user needs to be able to easily dump this data and send it back to the CSIR for study.
* Network Status -- new custom dashboard component with following features:
** A semi-detailed list of all the nodes in the mesh, including:
*** the node's IP and MAC addresses
*** the node's current status (simple up or down)
*** when they were last heard from (when an update from that node was last received)
*** how many hops and/or what route the node currently has to the gateway
** Basic network usage statistics, data taken from RADIUS:
*** Total bandwidth going out of the gateway in the last X amount of time
*** Heaviest users of the network to monitor abuse (further information on individual users is available already in phpMyPrepaid)
** Ability to test network throughput, either through:
*** Simple interface to run iperf between any two nodes, or:
*** Visual display of metrics & signal strengths of every link, data reported from clients' BATMAN daemons and network tools

* Mesh Network Configuration -- new custom dashboard component with following features (note this is designed to be minimal for ease of use):
** Change SSID of mesh network
** Change channel of mesh network
** Other features? Open to discussion.
** Note - It might be necessary to have multiple classes of mesh devices on the network, to accommodate a combination of different hardwares, different channels, etc.
* QoS Network Configuration – new custom dashboard component for adjusting QoS settings both:
** On the server, for outgoing traffic going to the upstream connection
** On the various nodes in the mesh, for intra-mesh network bandwidth management.
* AP-only node configuration – new custom dashboard component that configures node that are only AP's, not part of the mesh. Configures:
** SSID of AP
** Channel of AP
** Any kind of WPA authentication a user might want to run on the AP

Possible other voice-related modules include Asterisk and A2billing modules or pages.

The dashboard will send out all configuration updates using a standardized API; any mesh node in the network will have to run a client implementing this API that receives configuration messages from the dashboard and makes the necessary changes to files on its system. The API will be just as modular as the dashboard, so if a user wants to only implement certain features (say, add billing to an existing network) she would only need to implement a client for the platform her nodes are running (or, ideally, there will already be a client for that platform). Through the dashboard the user could then disable the unwanted modules. The dashboard will only send out updates for the components that are enabled, and the client will only modify configuration files for the components it receives.

All of the components of the larger dashboard will be skinned in a unified CSS style, with the potential for branding built in.

=== Mesh Nodes ===
The mesh nodes themselves will run OpenWRT. Node software includes:

* Batman for routing
* CoovaChilli as a local captive portal
* Intra-mesh QoS software, configurable from the dashboard. Uncertain as to what tools exactly to use here, however borrowing from Zeroshell it may be possible to simply use netfilter/iptables & l7-filter. Using an existing tool here would be very nice, as this is a complex task.
* A client daemon modeled on the ROBIN scripts that receives updates from the dashboard and sends any necessary information back to the dashboard. The client daemon will have to be co-developed with the dashboard.
* Stripped-down Webmin server component so we can run remote Webmin commands on the node through the server's Webmin installation.
* In addition to configuration through the dashboard, we will include a minimal web interface for configuring each individual node. This interface will run on the nodes, and can be a stripped-down version of X-WRT's webif^2 or FFLuCI. It would be useful if the interface could be designed such that it would run on any device regardless of that device's platform. This may be easy to do with existing abstractions in OpenWRT, but an alternative method would be for this interface to change the configuration of the local node via the update API, which is guaranteed to be fully abstracted, and let the update client for that device take care of making the actual changes.

=== AP-only Nodes ===
The mesh nodes will use their radios exclusively for the mesh network ('backhaul'). Clients can be attached directly to the Ethernet ports of these nodes, however it may be useful to have wireless client access as well. In this case, a second device can be attached to the mesh node to act as an access point. These devices can also be Linksys WRTs or similar, running OpenWRT with:

* CoovaChilli
* Dashboard Client with:
** AP-only node configuration module
** CoovaChilli configuration module

=== Task Breakdown ===
Once the specification is agreed upon work can begin. At that time further task breakdowns may be useful, but at a high level the expectation currently is as follows (refer to above for details on what individual software piece entail):

# Dashboard & first client development: Meraka
## Further examination of ROBIN to see which parts of it can be modified for our purposes
## Adaptation of Webmin's cluster tools for use on the mesh
## Determine appropriate tools for QoS [starting point: Zeroshell]
## Update API design & specification
## Dashboard framework design and implementation
## Mesh update client framework design and implementation
## Dashboard module implementation
### Network Monitoring
### Network Configuration – basics (Channel, SSID, etc)
### Network Configuration – QoS settings
### Network Configuration – AP-only settings
### Adapt phpMyPrepaid's CoovaChilli configuration to send out updates via standardized API rather than only changing local configuration file.
## Co-development with dashboard modules: mesh client update modules for each dashboard component, designed initially for the WRT but as portable as possible (for most modules portability should be trivial, as the software on the node the update client is configuring will be the same).
## CSS skinning for all dashboard components (including pre-existing ones such as Webmin and phpMyPrepaid).

# Minimal interface development for starter devices (at least the WRT, Mesh Potato, and Ubiquity nodes): Inveneo
# Porting of mesh client to Ubiquity and Mesh Potato (most modules should be identical, but basic network configuration settings may be device-specific): Inveneo

[[Category:WISP in a box]]

WISPiab brainstorm on way forward 200806

2008-06-24T12:37:11Z

Sebastian: /* Create hardware demo */

[[Category: WISP in a box]]

==detailed software development plan==

===Finish test of central SW ingredients and their interplay===

'''Deadline: approx. end of July'''

on server:

* priority 1
** FreeRadius
** mysql (or smaller allternative)
** radius/billing admin: phpmyprepaid or ISPbill or daloRadius or phpRADmin
** nagios (or alternatives: Osmius?)
** apache /
** webmin

* priority 2
** squid
** statistics (awstats)
** mail / webmail

===Create hardware demo===

'''Deadline: August'''

Install set of components on

* AMD Geode box
** on Ubuntu 8.04 (Ubuntu w Fluxbox)
* Linksys(es)

* Solar power part

===Analyze code architecture, UI===

For each component, analyze:

* language / environment used (e.g. PHP for many if not all)
* code organisation, i.e.
** use of include libraries,
** object orientation?
** design layer, i.e. use of css
** session management

goal: develop plan how to integrate these central components, by. e.g.

shared sessions, shared libraries, obviouslt shared GUI

==detailed (human) resource plan==

==collab server, svn, etc==

==hardware: build solar powered prototype==

==outreach: conferences and papers==

==ndlovu tests==

visit june 24?

WISPiab brainstorm on way forward 200806

2008-06-24T12:36:46Z

Sebastian: /* Finish test of central SW ingredients and their interplay */

[[Category: WISP in a box]]

==detailed software development plan==

===Finish test of central SW ingredients and their interplay===

'''Deadline: approx. end of July'''

on server:

* priority 1
** FreeRadius
** mysql (or smaller allternative)
** radius/billing admin: phpmyprepaid or ISPbill or daloRadius or phpRADmin
** nagios (or alternatives: Osmius?)
** apache /
** webmin

* priority 2
** squid
** statistics (awstats)
** mail / webmail

===Create hardware demo===

Install set of components on

* AMD Geode box
** on Ubuntu 8.04 (Ubuntu w Fluxbox)
* Linksys(es)

* Solar power part

===Analyze code architecture, UI===

For each component, analyze:

* language / environment used (e.g. PHP for many if not all)
* code organisation, i.e.
** use of include libraries,
** object orientation?
** design layer, i.e. use of css
** session management

goal: develop plan how to integrate these central components, by. e.g.

shared sessions, shared libraries, obviouslt shared GUI

==detailed (human) resource plan==

==collab server, svn, etc==

==hardware: build solar powered prototype==

==outreach: conferences and papers==

==ndlovu tests==

visit june 24?

WISPiab brainstorm on way forward 200806

2008-06-24T12:32:58Z

Sebastian: /* Create hardware demo */

[[Category: WISP in a box]]

==detailed software development plan==

===Finish test of central SW ingredients and their interplay===

on server:

* priority 1
** FreeRadius
** mysql (or smaller allternative)
** radius/billing admin: phpmyprepaid or ISPbill or daloRadius or phpRADmin
** nagios (or alternatives: Osmius?)
** apache /
** webmin

* priority 2
** squid
** statistics (awstats)
** mail / webmail

===Create hardware demo===

Install set of components on

* AMD Geode box
** on Ubuntu 8.04 (Ubuntu w Fluxbox)
* Linksys(es)

* Solar power part

===Analyze code architecture, UI===

For each component, analyze:

* language / environment used (e.g. PHP for many if not all)
* code organisation, i.e.
** use of include libraries,
** object orientation?
** design layer, i.e. use of css
** session management

goal: develop plan how to integrate these central components, by. e.g.

shared sessions, shared libraries, obviouslt shared GUI

==detailed (human) resource plan==

==collab server, svn, etc==

==hardware: build solar powered prototype==

==outreach: conferences and papers==

==ndlovu tests==

visit june 24?

WISPiab brainstorm on way forward 200806

2008-06-24T12:30:27Z

Sebastian: /* Analyze code architecture, UI */

[[Category: WISP in a box]]

==detailed software development plan==

===Finish test of central SW ingredients and their interplay===

on server:

* priority 1
** FreeRadius
** mysql (or smaller allternative)
** radius/billing admin: phpmyprepaid or ISPbill or daloRadius or phpRADmin
** nagios (or alternatives: Osmius?)
** apache /
** webmin

* priority 2
** squid
** statistics (awstats)
** mail / webmail

===Create hardware demo===

Install set of components on

* A

===Analyze code architecture, UI===

For each component, analyze:

* language / environment used (e.g. PHP for many if not all)
* code organisation, i.e.
** use of include libraries,
** object orientation?
** design layer, i.e. use of css
** session management

goal: develop plan how to integrate these central components, by. e.g.

shared sessions, shared libraries, obviouslt shared GUI

==detailed (human) resource plan==

==collab server, svn, etc==

==hardware: build solar powered prototype==

==outreach: conferences and papers==

==ndlovu tests==

visit june 24?

WISPiab brainstorm on way forward 200806

2008-06-24T12:27:20Z

Sebastian:

[[Category: WISP in a box]]

==detailed software development plan==

===Finish test of central SW ingredients and their interplay===

on server:

* priority 1
** FreeRadius
** mysql (or smaller allternative)
** radius/billing admin: phpmyprepaid or ISPbill or daloRadius or phpRADmin
** nagios (or alternatives: Osmius?)
** apache /
** webmin

* priority 2
** squid
** statistics (awstats)
** mail / webmail

===Analyze code architecture, UI===

For each component, analyze:

* language / environment used (e.g. PHP for many if not all)
* code organisation, i.e.
** use of include libraries,
** object orientation?
** design layer, i.e. use of css
** session management

goal: develop plan how to integrate these central components, by. e.g.

shared sessions, shared libraries, obviouslt shared GUI

==detailed (human) resource plan==

==collab server, svn, etc==

==hardware: build solar powered prototype==

==outreach: conferences and papers==

==ndlovu tests==

visit june 24?

WISPiab brainstorm on way forward 200806

2008-06-19T10:20:28Z

Sebastian: /* detailed software development plan */

[[Category: WISP in a box]]

==detailed software development plan==

===Finish test of central SW ingredients and their interplay===

* on server:
** FreeRadius
** mysql (or smaller allternative)
** radius/billing admin: phpmyprepaid or ISPbill or daloRadius or phpRADmin
** nagios (or alternatives: Osmius?)

===Analyze code architecture, UI===

For each component, analyze:

* language / environment used (e.g. PHP for many if not all)
* code organisation, i.e.
** use of include libraries,
** object orientation?
** design layer, i.e. use of css
** session management

goal: develop plan how to integrate these central components, by. e.g.

shared sessions, shared libraries, obviouslt shared GUI

==detailed (human) resource plan==

==collab server, svn, etc==

==hardware: build solar powered prototype==

==outreach: conferences and papers==

==ndlovu tests==

visit june 24?

The WISP-in-a-box project

2008-06-19T06:23:16Z

Sebastian: /* LessNetworks */

[[Category: WISP in a box]]

=What is it? The 30 second summary =

The ''WISP in a box'' project will

* take the best known ingredients from the open source / free software world
* bundle them and make them easy to use
* put them on low cost, low power hardware (which will be solar powered)

to create a

* easy-to use-and-run wireless ISP box

and make this product available to

* entrepreneurs, activists, movers of all kinds

in order to help bringing

* connectivity to underserviced, underprivileged and overcharged communities in Africa.

Click here to see [http://wirelessafrica.meraka.org.za/wiki/index.php/Category:WISP_in_a_box all documents related to the project]

=Contacts & how to get involved?=

The WISP in a box project is hosted and coordinated at

'''The Meraka Institute, CSIR, South Africa.'''

Project coordination: Sebastian Büttrich, http://wire.less.dk, mail: sebastian_at_less.dk

Click here to see [http://wirelessafrica.meraka.org.za/wiki/index.php/Category:WISP_in_a_box all documents related to the project]

The WISP in a box project is '''completely open''' in that

* We are highly interested in working with everybody with an interest in the project - just talk to us!
* All project communications and results will be fully open.
* Contributions to the project will be respected, attributed and credited for.
* We are aiming at actively making our resources available to the community as best we can.

All parts of this and other project '''documents are open for editing and commenting'''.

Best starting points might be ...

* the list of existing and related projects - we are interested in your input, * We are open to any dialogue about cooperation.experiences, additions.
* the specifications
* use cases and business cases

=Background and Goals=

The Wireless ISP in a box (short: WISPiab, final name pending) project has been suggested and discussed over a period of time,
a.o. it has been suggested at the London meeting, December 2006.

==Time for action==

Without discussing the connectivity situation in Africa in great depth,
there is no doubt that 2008 is the year that new business and non-business connectivity initiatives need to be put into action, gain in speed and be scaled up.

The WISPiab project wants enable the implementation speed needed,
by

* lowering the technology skils barrier
* offering a technology match to emerging business models
* creating an open platform for others to build on

Pragmatically speaking,

<pre>
we seek to address a dilemma that many wireless practicioners, activists and entrepreneurs are facing constantly:

When asked if all technology ingredients needed for starting a wireless project also is freely available, we answer 'yes'.
However, when asked ''how'' to get started, we have to admit that

* it is not quite so easy (yet),
* it will take a bit of fumbling and skills,
* while 80% of all needed parts are there, 20% and the finished bundle are still missing

and so forth.

Thus, successful startups - and we have seen a few of those - still largely depend on the "one skilled enthusiast" approach.
While this approach produces admirable case stories,
it is not a path the vast majority of people can take.
</pre>

==Openness and reusability==

We are in the lucky situation that many people have invested tremendous work over the last few years.

The project does not intend to reinvent any wheels, but to identify the best ingredients and components,
bring them together and make them more manageable.

It is time to get up to speed and scale.

We intend to work with everybody who is willing to share, and willing to benefit from what Meraka can bring to the table:

* capacity for the improvement of existing solutions
* capacity for testing and rollout
* capacity for documenting

All discussions, documents and results of the WISPiab project will be open throughout.

Software developed as aprt of this project will be licensed under a GPL license.
Harware specifications will be open,
and all documentation and educational materials will be published under an open license, e.g Creative Commons Licenses, GNU Free Documentation License, or such.

==Wireless vs. Wired?==

Wireless technology is not seen as competing with wires (fiber) connectivity. On the contrary, we feel that

wireless first meters will be essential in turning wired miles into successes.

Suppliers of wired connectivity need to be able to work with markets of well connected users and customers, businesses as well as non-profit,
which currently can only be created through the use of wireless technologies.

Thus, wireless technology is seen as an enabler of wired connectivity.

==Data or Voice? Infrastructure or Application?==

Two questions need a short comment:

# Is Data or Voice the most urgent field to address?
# Should the focus be on Infrastructure or Applications?

need a short comment.

As far as the WISPiab is concerned, none of these questions is of explicit relevance.
The WISPiab needs to support and match any business case that is identified as valid.

Technology follows need, and the need is identified by careful study of emerging business models.

Most business models will need

* infrastructure to transport applications,
and
* applications to make infrastructure attractive.

=Pillars of the project=

As indicated by the name, the project focusses on wireless technology,
however the project is based on a wider set of pillars.

# Free Software / Open Source
# License exempt wireless (802.11_)
# Local ownership
# Solar power (and thus low power)
# Low cost

These pillars indicate that

# Proprietary and closed source elements will not be allowed into the product. Where they are inevitable (e.g. drivers), they have to be clearly marked as such.
# Licensed frequencies and proprietary implentations with license exemt spectrum will not be allowed into the product. Backhaul connectivity, being outside of the product scope, is not touched by this.
# Centralized and non-lcoal business and technology models, e.g. models that require a sign up to a central corporate server (see for example the Meraki model), will not be considered.
# Any hardware solution will only be deemed complete if delivered bundled with a non-grid power supply. The default version of any WISPian project will be solar powered. Users with stable grid electricity have the freedom to deselect this option.
# Hardware and Software cost must be kept to an absolute minimum.

=Business models=

The WISPiab project takes its point of departure in feasible business models, not in technology.

Business models here will include for-profit as well as not-for-profit and completely free models, e.g. open networks.

Among the models and names recently discussed are

* VT: Village Telco
* VOT: Village Own/Operated Telco
* VOOT: Village Own and Operated Telco
* CON: Community owned network
* COF: Community owned Fibre

See e.g. the list [http://groups.google.com/group/wireless-africa/browse_thread/thread/efddf11a456b33cc Wireless Africa] for a recent discussion thread.

From its first phase on, the project seeks to

* collect user and business needs and feedback
* adjust technology to business and user needs

=The WISPiab product=

==Scope==

The WISPiab project aims at creating a bundled product, seen as consisting of

* Hardware
* Software
* Documentation

with the related out-of-scope side aspects of

* Education, Skills and Support
* Backhaul/Uplink connectivity

===Language/Localization===

For the time being, all Software and Docs will be in

* English

Localization and translation will be welcome, but the project team will currently not dedicate its own resources to this.

==Requirements / Specification==

Please see: [[WISPiab specifications]]

=Existing/related projects & products=

'''NOTE BEFORE YOU READ: At this point we have not broken down the list into sublists for Hardware / Software / Projects - etc!'''
'''Most items in the list incorporate aspects of all of these, so we keep them in one list. When this becomes to chaotic, we will divide it.'''

This list includes a.o.

* projects / approaches, commercial as well as non-commercial
* software, software platforms
* (almost) pure hardware vendors, integrated hardware/software, etc

'''We have now removed into archive - [[WISPiab ingredients - research archive]] - all the items that have been identified as NOT relevant.'''
In case you feel something is missing here, please check that archive first.

Please find a template at the top of the list, in case you would like to add to the list! You are very welcome to!

==Template for new entries==

* Type: (e.g. Community project, Company, Hardware vendor, Software Vendor, ISP, Telco, ...)
* Description:
* URL: [http://URL URL]
* Contacts:
* Relevance:

==aerospace software==

* Type: Software
* Description: Pre-paid cards for Radius
* URL: [http://www.aerospacesoftware.com/prepaid.html http://www.aerospacesoftware.com/prepaid.html]
* Contacts:
* Relevance: possibly, as element in billing handling

==A2Billing==

* Type: Hardware + Software platform
* Description: "full featured telecom platform and softswitch providing converged services, with self contained billing (pre or post-paid), reporting and statistics for IP and TDM based voice networks"
* URL: [http://trac.asterisk2billing.org/cgi-bin/trac.cgi http://trac.asterisk2billing.org/cgi-bin/trac.cgi]
* Contacts:
* Relevance: '''YES''' - see a.o. connections to Dabba and Trixbox

==Chillispot==

* Type: SW
* Description: Chilispot captive portal, standard in FLOSS captive portal world - "ChilliSpot is an open source captive portal or wireless LAN access point controller. It is used for authenticating users of a wireless LAN. It supports web based login, which is today's standard for public HotSpots, WISP "smart-client" authentication, and it supports Wi-Fi Protected Access (WPA and WPA2). Authentication, authorization and accounting (AAA protocol) is handled via RADIUS (on board or remote).

Development on the original project continues, but slowly for some. The Coova-Chilli is an active project and has since added many new features and is an integral part of the CoovaAP firmware.

As of mid 2007, ChilliSpot appears to be dead. The developer Jens Jacobsen has vanished, and the chillispot.org domain has lapsed. Fortunately CoovaChilli has forked from ChilliSpot 1.0 and development continues with an active user-base." See Coova instead.
* URL: [http://en.wikipedia.org/wiki/ChilliSpot http://en.wikipedia.org/wiki/ChilliSpot]
* Contacts:
* Relevance: '''YES - in its Coova form''' - probably an ingredient

==Colubris==

* Type: HW, SW, solutions
* Description: Colubris SW covers the whole rnage of wireless operations. Fantsuam used their billing module, with mixed experience.
* URL: [http://www.colubris.com/ http://www.colubris.com/] partners: [http://www.colubris.com/partners/service-partners.asp http://www.colubris.com/partners/service-partners.asp] --> HookMeUp system
* Contacts:
* Relevance: '''Probably low.''' license, price, opennness, ... interesting to study though

==Coova==

* Type: Software: Firmware for WRT54G etc
* Description: "Hotspot setup and management software .... includes firmware, authentication and management services, and captive portal solutions.... . .. Builds on OpenWrt, ChilliSpot, WifiDog, OpenVPN ...web interfaces for wifidog.conf and other conf files"
* URL: [http://URL URL]
* Contacts:
* Relevance: '''YES''' relevant! test and evaluate

==Cuwin==

* Type: Software, community project
* Description: "The CUWiN Foundation develops decentralized, community-owned networks that foster democratic cultures and local content. Through advocacy and through our commitment to open source technology, we support organic networks that grow to meet the needs of their community."
* URL: [http://www.cuwin.net/ http://www.cuwin.net/]
* Contacts:
* Relevance: '''yes'''- explore overlaps and cooperation

==Dabba / Orange Farm==

* Type: Village telco and ISP (e.g. Community project, Company, Hardware vendor, Software Vendor, ISP, Telco, ...)
* Description: SW based off openWRT, OpenSER, coova,
* URL: [http://dabba.co.za dabba.co.za]
* Contacts:
* Relevance: '''yes'''! uses and brings together best-of-breed usual suspects. working business model. cooperation.

==daloRadius==

* Type: Software
* Description: "daloRADIUS is an advanced RADIUS web management application aimed at managing hotspots and general-purpose ISP deployments. It features user management, graphical reporting, accounting, a billing engine and integrates with GoogleMaps for geo-locating."
* URL: [http://sourceforge.net/projects/daloradius http://sourceforge.net/projects/daloradius]
* Contacts:
* Relevance: '''evaluate!'''

==Fadeco==

* Type: Community project
* Description: an impressive example of an organically grown bootstrapped
network project. Ian Howard interview: "a true social entrepreneur at work." [http://www.youtube.com/watch?v=ErXK29u4Pf8 http://www.youtube.com/watch?v=ErXK29u4Pf8]
* URL: [http://fadeco.org URL]
* Contacts: Josepg Sekiku
* Relevance: '''high'''. interview and study business model.

==Fantsuam Foundation==

* Type: Community project, network
* Description: Fantsuam has implemented a communtiy network, including interesting experiences with voucher based billing
* URL: [http://www.fantsuam.org/ fantsuam.org ]
* Contacts: Alberto and Ochuoko through Sebastian
* Relevance: '''yes'''. Analyse experience with Billing implementation

==Firkant.net==

* Type: Communtiy owned fiber network
* Description: Though outside region (Denmark), an interesting case story of successful CON (fiber).
* URL: [http://firkant.net firkant.net]
* Contacts: through Sebastian
* Relevance: '''low in this phase''', but interesting re: community owned fiber. to learn from. interview!

==Freifunk==

* Type: Community project, Software
* Description: Freifunk is arguably the most succesful mesh movement and source of one of the best GUI integrated firmwares for the Linksys WRT54G and other boxes
* URL: [http://freifunk.net freifunk.net]
* Contacts: see URL
* Relevance: '''high'''

==Green-Wifi==

* Type: Community project, Hardware
* Description: "Green WiFi has developed a low cost, solar-powered, standardized WiFi access solution that runs out-of-the-box with no systems integration or power requirements. All that is required is a single source of broadband access. "
* URL: [http://green-wifi.org/ http://green-wifi.org/]
* Contacts: see URL
* Relevance: '''high''' - hardware experience, sw aspects (?), rollout coop?

==Inveneo==

* Type: Hardware/Software solutions, Implementer
* Description: "The Inveneo WiFi Outdoor Access Point is a rugged wireless router that can be used in multiple network configurations, for long-distance point-to-point links or to connect multiple locations. The WiFi Access Point requires very little network and device setup, as the integrated software has an internal webserver with easy-to-use interface accessible from any standard web browser. - The Computing Station is an ultra-low-power, affordable and fully functional desktop computer designed for use in rural locations such as schools, clinics, field offices, community centers and Internet cafes. - The Inveneo Hub Server|| "
* URL: [http://www.inveneo.org http://www.inveneo.org]
* Contacts:
* Relevance: '''high. Low power focus extremely relevant'''.

==ISPBill==

* Type: Software
* Description: "ISPBill is an ISP billing and management system. It features automatic generation and emailing of invoices, receipts and statements, a customer interface, a ticket system, and much more. ISPBill is intended to continue where cwispy left off"
* URL: [http://sourceforge.net/projects/ispbill/ http://sourceforge.net/projects/ispbill/]
* Contacts:
* Relevance: '''yes''' - test it

==ISPConfig==

* Type: Software
* Description: "ISPConfig is an open source hosting control panel for Linux. ISPConfig is licensed under BSD license."
* URL: [http://www.ispconfig.org/ http://www.ispconfig.org/]
* Contacts:
* Relevance:'''yes'' - check against webmin

==it46 - VoIP for Development project - Free Telephony Project==

* Type: Software
* Description: "free hardware designs for telephone systems. Both the hardware and software are open ... free to copy, modify and re-use the hardware designs. The hardware for a complete embedded Asterisk IP PBX (including multiple analog ports or a T1/E1) can be built for a few hundred dollars. ... first product is the IP04. The IP04 is a low cost phone system that can switch phone calls from analog phones or phone lines over the Internet using VoIP. The IP04 is a professionally designed product that is in volume production today"
* URL: [https://www.it46.se/entry/310 https://www.it46.se/entry/310] [http://www.rowetel.com/ucasterisk/ip04.html http://www.rowetel.com/ucasterisk/ip04.html]
* Contacts:
* Relevance:'''yes'''

==LessNetworks==

* Type: Software, SW/HW bundles
* Description: "This Austin Texas based group, part of the Free WiFi Movement, offers the Hotspot Server open source software that you can use to create your own free hotspot. When you run their software installation it creates a Linux system with the appropriate settings. Lessnetworks provides downloads of the software, sells their software on disk for a nominal cost, and even sells some preconfigured wireless servers on eBay that you can purchase as a package."
* URL: [http://www.lessnetworks.com/index.php http://www.lessnetworks.com/index.php]
* Contacts:
* Relevance: '''yes'''. check out!

==Meshlium, Mesh-Networks.org==

* Type: SW/HW
* Description: dual frequency mesh nodes, high power - mesh management software - power modules
* URL: [http://www.meshlium.com/ http://www.meshlium.com/] [http://www.mesh-networks.org http://www.mesh-networks.org]
* Contacts: participates in sensor networks group at ICTP
* Relevance: '''yes - evaluate!'''.

==Musimi==

* Type: Village Telco of sorts
* Description: Though outside region (Denmark), an interesting case story of successful (but also problematic?) Asterisk based Telco startup -
* URL: [http://musimi.dk msuimi.dk]
* Contacts: through Sebastian
* Relevance: '''to learn from. interview! Sebastian'''

==open-mesh==

* Type: Hardware vendor, Software Vendor
* Description: "Our Mission - To support WiFi mesh networks for community wireless, education, and the developing world."
* URL: [http://www.open-mesh.com/ open-mesh.com] see e.g. the roadmap [http://www.open-mesh.com/activekb/questions/4/Open-Mesh+Roadmap http://www.open-mesh.com/activekb/questions/4/Open-Mesh+Roadmap]
* Contacts:
* Relevance: very high! esp. when looking at development roadmap.

==Orangemesh==

* Type: Software Project
* Description: "OrangeMesh is a simple, open source network management dashboard for ROBIN based networks. OrangeMesh is jointly developed by Orange Networking, Open-Mesh, Inc, and students at UNC Chapel Hill.
Features

Seamless Integration with Open-Mesh: You can use Orangemesh together with your existing control at Open-Mesh.com. Soon, you'll be able to migrate all your network settings and infromation from Open-Mesh to an Orangemesh server with just a click of a button.

Completely Open Source: Change anything you want. Help build the final piece necessary for a completely open-source and affordable mesh network.

Customizable checkin script: Have access to every configuration option available in ROBIN. Make those pesky custom /config changes outlast the next firmware update.

Advanced Community Features: Grow an organic mesh network. Empower non-administrators and give your users a stake in the network and simplify the deployment of large community networks.

Much more: Improved Google Maps status view, custom CSS skins, user management, captive portal support, and more!"
* URL: [http://orangemesh.sourceforge.net/ http://orangemesh.sourceforge.net/]
* Contacts: through Open-Mesh
* Relevance: high

==Osmius==

* Type: Software Project
* Description: "Osmius allow us to monitor and supervise anything connected to our network. These elements could be attached to:

-Server Network : Linux, Windows, Solaris, HP-UX, AIX, VxWorks, OpenVMS, ...

-Services : Databases, Web Services, App. Services, SAP, ...

-Sensors : Pressure, Temperature, Industrial,SCADA,Solar Pannels, ...

-Domotic Networks : Fire detectors, surveillance elements and access control, ...

-Other types : To develop a new Osmius agent is extremely easy, fast and robust.

Osmius: Distinctive Features

-Open Source : Osmius exhibits its quality difference.

-Open Analysis : Access to documentation generated during the Analysis Phases as well as articles, architectural diagrams,...

-Osmius leverages ACE : Reusability applied with this extraordinary framework with decades of knowledge and very robust code.

-Multi-Platform : Hardware and operative system independence.

-Architecture Oriented : Osmius is a solution to a set of systems and problems, it is not just a product.

-Market Oriented : Osmius has a Business Plan and an Open Source Business Model with Peopleware.es."
* URL: [http://www.osmius.net/en/ http://www.osmius.net/en/]
* Contacts: -> mesh-networks, libelium
* Relevance: evaluate!

http://www.osmius.net/en/

==phpMyPrepaid==

* Type: Software
* Description: An interface for the creation and managment of prepaid cards and accounts designed to work with a MySQL database and FreeRadius.
* URL: [http://sourceforge.net/projects/phpmyprepaid/ http://sourceforge.net/projects/phpmyprepaid/]
* Contacts:
* Relevance:'''Yes''' - possible candidate for billing integration

==phpRADmin==

* Type: Software
* Description: "phpRADmin is a tool written in PHP intended to handle the administration and provisioning of FreeRADIUS over the Web with MySQL as backend. This interface (including dialup_admin) allows the administrator to config, find, create, edit, delete, and test users on an SQL (MySQL) database, create SQL groups, gather accounting information for a user, do complicated queries on the SQL accounting database, check RADIUS server availability, and produce dialup usage statistics, manage (create, update, revoke) PKI Certificates, Dictionary management, invoice management and system monitoring. Really, a system to manage FreeRADIUS with WPA, EAP (802.1X), PPP, PPPoE, Captive Portal, VoIP systems and other authentication methods. phpRADmin show pies and graphs of your network status, usage audits, administration profiles with 3 levels. phpRADmin is Chillispot and WISP ready."
* URL: [http://www.phpradmin.org/ http://www.phpradmin.org/]
* Contacts:
* Relevance:'''evaluate!'''

http://www.phpradmin.org/

==Robin==

* Type: Software
* Description: "ROBIN stands for ROuting Batman INside: a mesh network firmware using BATMAN routing algorithm
ROBIN is a firmware deployed on OpenWRT kamikaze 7.07 and is intended for Atheros AP51 devices such as Meraki Mini or Fonera; when flashed, your mini-routers act as comfortable and 0-config mesh-network appliances."
* URL: [http://www.blogin.it/howtorobin/index.html http://www.blogin.it/howtorobin/index.html]
* Contacts:
* Relevance: yes - study Mesh/Captive implementation

==Soekris==

* Type: Hardware
* Description: Low cost, low poer comms boards, e.g. net4521 - This compact, low-power, low-cost, advanced communication computer is based on a 133 Mhz 486 class processor. It has two 10/100 Mbit ethernet ports, up to 64 Mbyte SDRAM main memory and uses a CompactFlash module for program and data storage. It can be expanded using a MiniPCI type III board and up to two PC-Card/Cardbus adapters.

It has been optimized for use as wireless router using PC-Card wireless adapters, but has the flexibility to take on a whole range of different functions as a communication appliance. The board is designed for long life and low power.

It is available in any volume in the standard version, and as board only or with a small metal box and various power supplies. The board can be customized according to requirements when ordering higher volume."
* URL: [http://soekris.com http://soekris.com]
* Contacts:
* Relevance: '''maybe''' - potential hardware ingredient

==Tranzeo==

* Type: Hardware vendor
* Description: Interesting wireless hardware
* URL: [http://tranzeo.comL tranzeo.com]
* Contacts:
* Relevance: '''possibly?'''.

==Trixbox==

* Type: SW, distro
* Description: formerly known as Asterisk@Home, is an Asterisk distro aimed at ease of use. It is used by e.g. Uninet to provide community Voip. Their intgrated HW/SW product "Trixbox in a box" ... "... makes it even easier for business to get trixbox phone systems up and running. Why buy separate hardware, download and install software, configure the hardware, and test it all yourself?"
* URL: [http://URL URL]
* Contacts:
* Relevance: '''medium''' - probably covered already or integrated elsewhere

==Ubiquiti==

* Type: Hardware vendor, solutions
* Description: Vendors of WISP targetted high quality, low budget gear
* URL: [http://ubnt.com/ http://ubnt.com/]
* Contacts:
* Relevance:'''yes'''

==Webmin==

* Type: SW management, GUI based admin, etc
* Description: "Webmin is a web-based interface for system administration for Unix. Using any modern web browser, you can setup user accounts, Apache, DNS, file sharing and much more. Webmin removes the need to manually edit Unix configuration files like /etc/passwd, and lets you manage a system from the console or remotely."
* URL: [http://www.webmin.com/ http://www.webmin.com]
* Contacts:
* Relevance: '''yes'''

==Worldspot==

* Type: WISP management, hotspot manegement
* Description: builds on DD-WRT, Coova. Adds billing, multiple schemes and models.
* URL: [http://worldspot.net/ http://worldspot.net]
* Contacts:
* Relevance: '''medium.''' tech ingredients are coova and dd-wrt. better go direct, '''Billing part might be interesting to look at,''' though business models might be incompatible.

=Appendices=

==Appendix 1: Suggested product names==

* WIAB
* Wimbo - WIreless Mover BOx (Wimbo = Kiswahili for Song, Anthem, Hymn)

The WISP-in-a-box project

2008-06-19T06:16:58Z

Sebastian: /* Orangemesh */

[[Category: WISP in a box]]

=What is it? The 30 second summary =

The ''WISP in a box'' project will

* take the best known ingredients from the open source / free software world
* bundle them and make them easy to use
* put them on low cost, low power hardware (which will be solar powered)

to create a

* easy-to use-and-run wireless ISP box

and make this product available to

* entrepreneurs, activists, movers of all kinds

in order to help bringing

* connectivity to underserviced, underprivileged and overcharged communities in Africa.

Click here to see [http://wirelessafrica.meraka.org.za/wiki/index.php/Category:WISP_in_a_box all documents related to the project]

=Contacts & how to get involved?=

The WISP in a box project is hosted and coordinated at

'''The Meraka Institute, CSIR, South Africa.'''

Project coordination: Sebastian Büttrich, http://wire.less.dk, mail: sebastian_at_less.dk

Click here to see [http://wirelessafrica.meraka.org.za/wiki/index.php/Category:WISP_in_a_box all documents related to the project]

The WISP in a box project is '''completely open''' in that

* We are highly interested in working with everybody with an interest in the project - just talk to us!
* All project communications and results will be fully open.
* Contributions to the project will be respected, attributed and credited for.
* We are aiming at actively making our resources available to the community as best we can.

All parts of this and other project '''documents are open for editing and commenting'''.

Best starting points might be ...

* the list of existing and related projects - we are interested in your input, * We are open to any dialogue about cooperation.experiences, additions.
* the specifications
* use cases and business cases

=Background and Goals=

The Wireless ISP in a box (short: WISPiab, final name pending) project has been suggested and discussed over a period of time,
a.o. it has been suggested at the London meeting, December 2006.

==Time for action==

Without discussing the connectivity situation in Africa in great depth,
there is no doubt that 2008 is the year that new business and non-business connectivity initiatives need to be put into action, gain in speed and be scaled up.

The WISPiab project wants enable the implementation speed needed,
by

* lowering the technology skils barrier
* offering a technology match to emerging business models
* creating an open platform for others to build on

Pragmatically speaking,

<pre>
we seek to address a dilemma that many wireless practicioners, activists and entrepreneurs are facing constantly:

When asked if all technology ingredients needed for starting a wireless project also is freely available, we answer 'yes'.
However, when asked ''how'' to get started, we have to admit that

* it is not quite so easy (yet),
* it will take a bit of fumbling and skills,
* while 80% of all needed parts are there, 20% and the finished bundle are still missing

and so forth.

Thus, successful startups - and we have seen a few of those - still largely depend on the "one skilled enthusiast" approach.
While this approach produces admirable case stories,
it is not a path the vast majority of people can take.
</pre>

==Openness and reusability==

We are in the lucky situation that many people have invested tremendous work over the last few years.

The project does not intend to reinvent any wheels, but to identify the best ingredients and components,
bring them together and make them more manageable.

It is time to get up to speed and scale.

We intend to work with everybody who is willing to share, and willing to benefit from what Meraka can bring to the table:

* capacity for the improvement of existing solutions
* capacity for testing and rollout
* capacity for documenting

All discussions, documents and results of the WISPiab project will be open throughout.

Software developed as aprt of this project will be licensed under a GPL license.
Harware specifications will be open,
and all documentation and educational materials will be published under an open license, e.g Creative Commons Licenses, GNU Free Documentation License, or such.

==Wireless vs. Wired?==

Wireless technology is not seen as competing with wires (fiber) connectivity. On the contrary, we feel that

wireless first meters will be essential in turning wired miles into successes.

Suppliers of wired connectivity need to be able to work with markets of well connected users and customers, businesses as well as non-profit,
which currently can only be created through the use of wireless technologies.

Thus, wireless technology is seen as an enabler of wired connectivity.

==Data or Voice? Infrastructure or Application?==

Two questions need a short comment:

# Is Data or Voice the most urgent field to address?
# Should the focus be on Infrastructure or Applications?

need a short comment.

As far as the WISPiab is concerned, none of these questions is of explicit relevance.
The WISPiab needs to support and match any business case that is identified as valid.

Technology follows need, and the need is identified by careful study of emerging business models.

Most business models will need

* infrastructure to transport applications,
and
* applications to make infrastructure attractive.

=Pillars of the project=

As indicated by the name, the project focusses on wireless technology,
however the project is based on a wider set of pillars.

# Free Software / Open Source
# License exempt wireless (802.11_)
# Local ownership
# Solar power (and thus low power)
# Low cost

These pillars indicate that

# Proprietary and closed source elements will not be allowed into the product. Where they are inevitable (e.g. drivers), they have to be clearly marked as such.
# Licensed frequencies and proprietary implentations with license exemt spectrum will not be allowed into the product. Backhaul connectivity, being outside of the product scope, is not touched by this.
# Centralized and non-lcoal business and technology models, e.g. models that require a sign up to a central corporate server (see for example the Meraki model), will not be considered.
# Any hardware solution will only be deemed complete if delivered bundled with a non-grid power supply. The default version of any WISPian project will be solar powered. Users with stable grid electricity have the freedom to deselect this option.
# Hardware and Software cost must be kept to an absolute minimum.

=Business models=

The WISPiab project takes its point of departure in feasible business models, not in technology.

Business models here will include for-profit as well as not-for-profit and completely free models, e.g. open networks.

Among the models and names recently discussed are

* VT: Village Telco
* VOT: Village Own/Operated Telco
* VOOT: Village Own and Operated Telco
* CON: Community owned network
* COF: Community owned Fibre

See e.g. the list [http://groups.google.com/group/wireless-africa/browse_thread/thread/efddf11a456b33cc Wireless Africa] for a recent discussion thread.

From its first phase on, the project seeks to

* collect user and business needs and feedback
* adjust technology to business and user needs

=The WISPiab product=

==Scope==

The WISPiab project aims at creating a bundled product, seen as consisting of

* Hardware
* Software
* Documentation

with the related out-of-scope side aspects of

* Education, Skills and Support
* Backhaul/Uplink connectivity

===Language/Localization===

For the time being, all Software and Docs will be in

* English

Localization and translation will be welcome, but the project team will currently not dedicate its own resources to this.

==Requirements / Specification==

Please see: [[WISPiab specifications]]

=Existing/related projects & products=

'''NOTE BEFORE YOU READ: At this point we have not broken down the list into sublists for Hardware / Software / Projects - etc!'''
'''Most items in the list incorporate aspects of all of these, so we keep them in one list. When this becomes to chaotic, we will divide it.'''

This list includes a.o.

* projects / approaches, commercial as well as non-commercial
* software, software platforms
* (almost) pure hardware vendors, integrated hardware/software, etc

'''We have now removed into archive - [[WISPiab ingredients - research archive]] - all the items that have been identified as NOT relevant.'''
In case you feel something is missing here, please check that archive first.

Please find a template at the top of the list, in case you would like to add to the list! You are very welcome to!

==Template for new entries==

* Type: (e.g. Community project, Company, Hardware vendor, Software Vendor, ISP, Telco, ...)
* Description:
* URL: [http://URL URL]
* Contacts:
* Relevance:

==aerospace software==

* Type: Software
* Description: Pre-paid cards for Radius
* URL: [http://www.aerospacesoftware.com/prepaid.html http://www.aerospacesoftware.com/prepaid.html]
* Contacts:
* Relevance: possibly, as element in billing handling

==A2Billing==

* Type: Hardware + Software platform
* Description: "full featured telecom platform and softswitch providing converged services, with self contained billing (pre or post-paid), reporting and statistics for IP and TDM based voice networks"
* URL: [http://trac.asterisk2billing.org/cgi-bin/trac.cgi http://trac.asterisk2billing.org/cgi-bin/trac.cgi]
* Contacts:
* Relevance: '''YES''' - see a.o. connections to Dabba and Trixbox

==Chillispot==

* Type: SW
* Description: Chilispot captive portal, standard in FLOSS captive portal world - "ChilliSpot is an open source captive portal or wireless LAN access point controller. It is used for authenticating users of a wireless LAN. It supports web based login, which is today's standard for public HotSpots, WISP "smart-client" authentication, and it supports Wi-Fi Protected Access (WPA and WPA2). Authentication, authorization and accounting (AAA protocol) is handled via RADIUS (on board or remote).

Development on the original project continues, but slowly for some. The Coova-Chilli is an active project and has since added many new features and is an integral part of the CoovaAP firmware.

As of mid 2007, ChilliSpot appears to be dead. The developer Jens Jacobsen has vanished, and the chillispot.org domain has lapsed. Fortunately CoovaChilli has forked from ChilliSpot 1.0 and development continues with an active user-base." See Coova instead.
* URL: [http://en.wikipedia.org/wiki/ChilliSpot http://en.wikipedia.org/wiki/ChilliSpot]
* Contacts:
* Relevance: '''YES - in its Coova form''' - probably an ingredient

==Colubris==

* Type: HW, SW, solutions
* Description: Colubris SW covers the whole rnage of wireless operations. Fantsuam used their billing module, with mixed experience.
* URL: [http://www.colubris.com/ http://www.colubris.com/] partners: [http://www.colubris.com/partners/service-partners.asp http://www.colubris.com/partners/service-partners.asp] --> HookMeUp system
* Contacts:
* Relevance: '''Probably low.''' license, price, opennness, ... interesting to study though

==Coova==

* Type: Software: Firmware for WRT54G etc
* Description: "Hotspot setup and management software .... includes firmware, authentication and management services, and captive portal solutions.... . .. Builds on OpenWrt, ChilliSpot, WifiDog, OpenVPN ...web interfaces for wifidog.conf and other conf files"
* URL: [http://URL URL]
* Contacts:
* Relevance: '''YES''' relevant! test and evaluate

==Cuwin==

* Type: Software, community project
* Description: "The CUWiN Foundation develops decentralized, community-owned networks that foster democratic cultures and local content. Through advocacy and through our commitment to open source technology, we support organic networks that grow to meet the needs of their community."
* URL: [http://www.cuwin.net/ http://www.cuwin.net/]
* Contacts:
* Relevance: '''yes'''- explore overlaps and cooperation

==Dabba / Orange Farm==

* Type: Village telco and ISP (e.g. Community project, Company, Hardware vendor, Software Vendor, ISP, Telco, ...)
* Description: SW based off openWRT, OpenSER, coova,
* URL: [http://dabba.co.za dabba.co.za]
* Contacts:
* Relevance: '''yes'''! uses and brings together best-of-breed usual suspects. working business model. cooperation.

==daloRadius==

* Type: Software
* Description: "daloRADIUS is an advanced RADIUS web management application aimed at managing hotspots and general-purpose ISP deployments. It features user management, graphical reporting, accounting, a billing engine and integrates with GoogleMaps for geo-locating."
* URL: [http://sourceforge.net/projects/daloradius http://sourceforge.net/projects/daloradius]
* Contacts:
* Relevance: '''evaluate!'''

==Fadeco==

* Type: Community project
* Description: an impressive example of an organically grown bootstrapped
network project. Ian Howard interview: "a true social entrepreneur at work." [http://www.youtube.com/watch?v=ErXK29u4Pf8 http://www.youtube.com/watch?v=ErXK29u4Pf8]
* URL: [http://fadeco.org URL]
* Contacts: Josepg Sekiku
* Relevance: '''high'''. interview and study business model.

==Fantsuam Foundation==

* Type: Community project, network
* Description: Fantsuam has implemented a communtiy network, including interesting experiences with voucher based billing
* URL: [http://www.fantsuam.org/ fantsuam.org ]
* Contacts: Alberto and Ochuoko through Sebastian
* Relevance: '''yes'''. Analyse experience with Billing implementation

==Firkant.net==

* Type: Communtiy owned fiber network
* Description: Though outside region (Denmark), an interesting case story of successful CON (fiber).
* URL: [http://firkant.net firkant.net]
* Contacts: through Sebastian
* Relevance: '''low in this phase''', but interesting re: community owned fiber. to learn from. interview!

==Freifunk==

* Type: Community project, Software
* Description: Freifunk is arguably the most succesful mesh movement and source of one of the best GUI integrated firmwares for the Linksys WRT54G and other boxes
* URL: [http://freifunk.net freifunk.net]
* Contacts: see URL
* Relevance: '''high'''

==Green-Wifi==

* Type: Community project, Hardware
* Description: "Green WiFi has developed a low cost, solar-powered, standardized WiFi access solution that runs out-of-the-box with no systems integration or power requirements. All that is required is a single source of broadband access. "
* URL: [http://green-wifi.org/ http://green-wifi.org/]
* Contacts: see URL
* Relevance: '''high''' - hardware experience, sw aspects (?), rollout coop?

==Inveneo==

* Type: Hardware/Software solutions, Implementer
* Description: "The Inveneo WiFi Outdoor Access Point is a rugged wireless router that can be used in multiple network configurations, for long-distance point-to-point links or to connect multiple locations. The WiFi Access Point requires very little network and device setup, as the integrated software has an internal webserver with easy-to-use interface accessible from any standard web browser. - The Computing Station is an ultra-low-power, affordable and fully functional desktop computer designed for use in rural locations such as schools, clinics, field offices, community centers and Internet cafes. - The Inveneo Hub Server|| "
* URL: [http://www.inveneo.org http://www.inveneo.org]
* Contacts:
* Relevance: '''high. Low power focus extremely relevant'''.

==ISPBill==

* Type: Software
* Description: "ISPBill is an ISP billing and management system. It features automatic generation and emailing of invoices, receipts and statements, a customer interface, a ticket system, and much more. ISPBill is intended to continue where cwispy left off"
* URL: [http://sourceforge.net/projects/ispbill/ http://sourceforge.net/projects/ispbill/]
* Contacts:
* Relevance: '''yes''' - test it

==ISPConfig==

* Type: Software
* Description: "ISPConfig is an open source hosting control panel for Linux. ISPConfig is licensed under BSD license."
* URL: [http://www.ispconfig.org/ http://www.ispconfig.org/]
* Contacts:
* Relevance:'''yes'' - check against webmin

==it46 - VoIP for Development project - Free Telephony Project==

* Type: Software
* Description: "free hardware designs for telephone systems. Both the hardware and software are open ... free to copy, modify and re-use the hardware designs. The hardware for a complete embedded Asterisk IP PBX (including multiple analog ports or a T1/E1) can be built for a few hundred dollars. ... first product is the IP04. The IP04 is a low cost phone system that can switch phone calls from analog phones or phone lines over the Internet using VoIP. The IP04 is a professionally designed product that is in volume production today"
* URL: [https://www.it46.se/entry/310 https://www.it46.se/entry/310] [http://www.rowetel.com/ucasterisk/ip04.html http://www.rowetel.com/ucasterisk/ip04.html]
* Contacts:
* Relevance:'''yes'''

==LessNetworks==

* Type: Software, SW/HW bundles
* Description: "This Austin Texas based group, part of the Free WiFi Movement, offers the Hotspot Server open source software that you can use to create your own free hotspot. When you run their software installation it creates a Linux system with the appropriate settings. Lessnetworks provides downloads of the software, sells their software on disk for a nominal cost, and even sells some preconfigured wireless servers on eBay that you can purchase as a package."
* URL: [http://www.lessnetworks.com/index.php http://www.lessnetworks.com/index.php]
* Contacts:
* Relevance: '''yes'''. check out!

==Musimi==

* Type: Village Telco of sorts
* Description: Though outside region (Denmark), an interesting case story of successful (but also problematic?) Asterisk based Telco startup -
* URL: [http://musimi.dk msuimi.dk]
* Contacts: through Sebastian
* Relevance: '''to learn from. interview! Sebastian'''

==open-mesh==

* Type: Hardware vendor, Software Vendor
* Description: "Our Mission - To support WiFi mesh networks for community wireless, education, and the developing world."
* URL: [http://www.open-mesh.com/ open-mesh.com] see e.g. the roadmap [http://www.open-mesh.com/activekb/questions/4/Open-Mesh+Roadmap http://www.open-mesh.com/activekb/questions/4/Open-Mesh+Roadmap]
* Contacts:
* Relevance: very high! esp. when looking at development roadmap.

==Orangemesh==

* Type: Software Project
* Description: "OrangeMesh is a simple, open source network management dashboard for ROBIN based networks. OrangeMesh is jointly developed by Orange Networking, Open-Mesh, Inc, and students at UNC Chapel Hill.
Features

Seamless Integration with Open-Mesh: You can use Orangemesh together with your existing control at Open-Mesh.com. Soon, you'll be able to migrate all your network settings and infromation from Open-Mesh to an Orangemesh server with just a click of a button.

Completely Open Source: Change anything you want. Help build the final piece necessary for a completely open-source and affordable mesh network.

Customizable checkin script: Have access to every configuration option available in ROBIN. Make those pesky custom /config changes outlast the next firmware update.

Advanced Community Features: Grow an organic mesh network. Empower non-administrators and give your users a stake in the network and simplify the deployment of large community networks.

Much more: Improved Google Maps status view, custom CSS skins, user management, captive portal support, and more!"
* URL: [http://orangemesh.sourceforge.net/ http://orangemesh.sourceforge.net/]
* Contacts: through Open-Mesh
* Relevance: high

==Osmius==

* Type: Software Project
* Description: "Osmius allow us to monitor and supervise anything connected to our network. These elements could be attached to:

-Server Network : Linux, Windows, Solaris, HP-UX, AIX, VxWorks, OpenVMS, ...

-Services : Databases, Web Services, App. Services, SAP, ...

-Sensors : Pressure, Temperature, Industrial,SCADA,Solar Pannels, ...

-Domotic Networks : Fire detectors, surveillance elements and access control, ...

-Other types : To develop a new Osmius agent is extremely easy, fast and robust.

Osmius: Distinctive Features

-Open Source : Osmius exhibits its quality difference.

-Open Analysis : Access to documentation generated during the Analysis Phases as well as articles, architectural diagrams,...

-Osmius leverages ACE : Reusability applied with this extraordinary framework with decades of knowledge and very robust code.

-Multi-Platform : Hardware and operative system independence.

-Architecture Oriented : Osmius is a solution to a set of systems and problems, it is not just a product.

-Market Oriented : Osmius has a Business Plan and an Open Source Business Model with Peopleware.es."
* URL: [http://www.osmius.net/en/ http://www.osmius.net/en/]
* Contacts: -> mesh-networks, libelium
* Relevance: evaluate!

http://www.osmius.net/en/

==phpMyPrepaid==

* Type: Software
* Description: An interface for the creation and managment of prepaid cards and accounts designed to work with a MySQL database and FreeRadius.
* URL: [http://sourceforge.net/projects/phpmyprepaid/ http://sourceforge.net/projects/phpmyprepaid/]
* Contacts:
* Relevance:'''Yes''' - possible candidate for billing integration

==phpRADmin==

* Type: Software
* Description: "phpRADmin is a tool written in PHP intended to handle the administration and provisioning of FreeRADIUS over the Web with MySQL as backend. This interface (including dialup_admin) allows the administrator to config, find, create, edit, delete, and test users on an SQL (MySQL) database, create SQL groups, gather accounting information for a user, do complicated queries on the SQL accounting database, check RADIUS server availability, and produce dialup usage statistics, manage (create, update, revoke) PKI Certificates, Dictionary management, invoice management and system monitoring. Really, a system to manage FreeRADIUS with WPA, EAP (802.1X), PPP, PPPoE, Captive Portal, VoIP systems and other authentication methods. phpRADmin show pies and graphs of your network status, usage audits, administration profiles with 3 levels. phpRADmin is Chillispot and WISP ready."
* URL: [http://www.phpradmin.org/ http://www.phpradmin.org/]
* Contacts:
* Relevance:'''evaluate!'''

http://www.phpradmin.org/

==Robin==

* Type: Software
* Description: "ROBIN stands for ROuting Batman INside: a mesh network firmware using BATMAN routing algorithm
ROBIN is a firmware deployed on OpenWRT kamikaze 7.07 and is intended for Atheros AP51 devices such as Meraki Mini or Fonera; when flashed, your mini-routers act as comfortable and 0-config mesh-network appliances."
* URL: [http://www.blogin.it/howtorobin/index.html http://www.blogin.it/howtorobin/index.html]
* Contacts:
* Relevance: yes - study Mesh/Captive implementation

==Soekris==

* Type: Hardware
* Description: Low cost, low poer comms boards, e.g. net4521 - This compact, low-power, low-cost, advanced communication computer is based on a 133 Mhz 486 class processor. It has two 10/100 Mbit ethernet ports, up to 64 Mbyte SDRAM main memory and uses a CompactFlash module for program and data storage. It can be expanded using a MiniPCI type III board and up to two PC-Card/Cardbus adapters.

It has been optimized for use as wireless router using PC-Card wireless adapters, but has the flexibility to take on a whole range of different functions as a communication appliance. The board is designed for long life and low power.

It is available in any volume in the standard version, and as board only or with a small metal box and various power supplies. The board can be customized according to requirements when ordering higher volume."
* URL: [http://soekris.com http://soekris.com]
* Contacts:
* Relevance: '''maybe''' - potential hardware ingredient

==Tranzeo==

* Type: Hardware vendor
* Description: Interesting wireless hardware
* URL: [http://tranzeo.comL tranzeo.com]
* Contacts:
* Relevance: '''possibly?'''.

==Trixbox==

* Type: SW, distro
* Description: formerly known as Asterisk@Home, is an Asterisk distro aimed at ease of use. It is used by e.g. Uninet to provide community Voip. Their intgrated HW/SW product "Trixbox in a box" ... "... makes it even easier for business to get trixbox phone systems up and running. Why buy separate hardware, download and install software, configure the hardware, and test it all yourself?"
* URL: [http://URL URL]
* Contacts:
* Relevance: '''medium''' - probably covered already or integrated elsewhere

==Ubiquiti==

* Type: Hardware vendor, solutions
* Description: Vendors of WISP targetted high quality, low budget gear
* URL: [http://ubnt.com/ http://ubnt.com/]
* Contacts:
* Relevance:'''yes'''

==Webmin==

* Type: SW management, GUI based admin, etc
* Description: "Webmin is a web-based interface for system administration for Unix. Using any modern web browser, you can setup user accounts, Apache, DNS, file sharing and much more. Webmin removes the need to manually edit Unix configuration files like /etc/passwd, and lets you manage a system from the console or remotely."
* URL: [http://www.webmin.com/ http://www.webmin.com]
* Contacts:
* Relevance: '''yes'''

==Worldspot==

* Type: WISP management, hotspot manegement
* Description: builds on DD-WRT, Coova. Adds billing, multiple schemes and models.
* URL: [http://worldspot.net/ http://worldspot.net]
* Contacts:
* Relevance: '''medium.''' tech ingredients are coova and dd-wrt. better go direct, '''Billing part might be interesting to look at,''' though business models might be incompatible.

=Appendices=

==Appendix 1: Suggested product names==

* WIAB
* Wimbo - WIreless Mover BOx (Wimbo = Kiswahili for Song, Anthem, Hymn)

The WISP-in-a-box project

2008-06-19T06:12:15Z

Sebastian: /* phpMyPrepaid */

[[Category: WISP in a box]]

=What is it? The 30 second summary =

The ''WISP in a box'' project will

* take the best known ingredients from the open source / free software world
* bundle them and make them easy to use
* put them on low cost, low power hardware (which will be solar powered)

to create a

* easy-to use-and-run wireless ISP box

and make this product available to

* entrepreneurs, activists, movers of all kinds

in order to help bringing

* connectivity to underserviced, underprivileged and overcharged communities in Africa.

Click here to see [http://wirelessafrica.meraka.org.za/wiki/index.php/Category:WISP_in_a_box all documents related to the project]

=Contacts & how to get involved?=

The WISP in a box project is hosted and coordinated at

'''The Meraka Institute, CSIR, South Africa.'''

Project coordination: Sebastian Büttrich, http://wire.less.dk, mail: sebastian_at_less.dk

Click here to see [http://wirelessafrica.meraka.org.za/wiki/index.php/Category:WISP_in_a_box all documents related to the project]

The WISP in a box project is '''completely open''' in that

* We are highly interested in working with everybody with an interest in the project - just talk to us!
* All project communications and results will be fully open.
* Contributions to the project will be respected, attributed and credited for.
* We are aiming at actively making our resources available to the community as best we can.

All parts of this and other project '''documents are open for editing and commenting'''.

Best starting points might be ...

* the list of existing and related projects - we are interested in your input, * We are open to any dialogue about cooperation.experiences, additions.
* the specifications
* use cases and business cases

=Background and Goals=

The Wireless ISP in a box (short: WISPiab, final name pending) project has been suggested and discussed over a period of time,
a.o. it has been suggested at the London meeting, December 2006.

==Time for action==

Without discussing the connectivity situation in Africa in great depth,
there is no doubt that 2008 is the year that new business and non-business connectivity initiatives need to be put into action, gain in speed and be scaled up.

The WISPiab project wants enable the implementation speed needed,
by

* lowering the technology skils barrier
* offering a technology match to emerging business models
* creating an open platform for others to build on

Pragmatically speaking,

<pre>
we seek to address a dilemma that many wireless practicioners, activists and entrepreneurs are facing constantly:

When asked if all technology ingredients needed for starting a wireless project also is freely available, we answer 'yes'.
However, when asked ''how'' to get started, we have to admit that

* it is not quite so easy (yet),
* it will take a bit of fumbling and skills,
* while 80% of all needed parts are there, 20% and the finished bundle are still missing

and so forth.

Thus, successful startups - and we have seen a few of those - still largely depend on the "one skilled enthusiast" approach.
While this approach produces admirable case stories,
it is not a path the vast majority of people can take.
</pre>

==Openness and reusability==

We are in the lucky situation that many people have invested tremendous work over the last few years.

The project does not intend to reinvent any wheels, but to identify the best ingredients and components,
bring them together and make them more manageable.

It is time to get up to speed and scale.

We intend to work with everybody who is willing to share, and willing to benefit from what Meraka can bring to the table:

* capacity for the improvement of existing solutions
* capacity for testing and rollout
* capacity for documenting

All discussions, documents and results of the WISPiab project will be open throughout.

Software developed as aprt of this project will be licensed under a GPL license.
Harware specifications will be open,
and all documentation and educational materials will be published under an open license, e.g Creative Commons Licenses, GNU Free Documentation License, or such.

==Wireless vs. Wired?==

Wireless technology is not seen as competing with wires (fiber) connectivity. On the contrary, we feel that

wireless first meters will be essential in turning wired miles into successes.

Suppliers of wired connectivity need to be able to work with markets of well connected users and customers, businesses as well as non-profit,
which currently can only be created through the use of wireless technologies.

Thus, wireless technology is seen as an enabler of wired connectivity.

==Data or Voice? Infrastructure or Application?==

Two questions need a short comment:

# Is Data or Voice the most urgent field to address?
# Should the focus be on Infrastructure or Applications?

need a short comment.

As far as the WISPiab is concerned, none of these questions is of explicit relevance.
The WISPiab needs to support and match any business case that is identified as valid.

Technology follows need, and the need is identified by careful study of emerging business models.

Most business models will need

* infrastructure to transport applications,
and
* applications to make infrastructure attractive.

=Pillars of the project=

As indicated by the name, the project focusses on wireless technology,
however the project is based on a wider set of pillars.

# Free Software / Open Source
# License exempt wireless (802.11_)
# Local ownership
# Solar power (and thus low power)
# Low cost

These pillars indicate that

# Proprietary and closed source elements will not be allowed into the product. Where they are inevitable (e.g. drivers), they have to be clearly marked as such.
# Licensed frequencies and proprietary implentations with license exemt spectrum will not be allowed into the product. Backhaul connectivity, being outside of the product scope, is not touched by this.
# Centralized and non-lcoal business and technology models, e.g. models that require a sign up to a central corporate server (see for example the Meraki model), will not be considered.
# Any hardware solution will only be deemed complete if delivered bundled with a non-grid power supply. The default version of any WISPian project will be solar powered. Users with stable grid electricity have the freedom to deselect this option.
# Hardware and Software cost must be kept to an absolute minimum.

=Business models=

The WISPiab project takes its point of departure in feasible business models, not in technology.

Business models here will include for-profit as well as not-for-profit and completely free models, e.g. open networks.

Among the models and names recently discussed are

* VT: Village Telco
* VOT: Village Own/Operated Telco
* VOOT: Village Own and Operated Telco
* CON: Community owned network
* COF: Community owned Fibre

See e.g. the list [http://groups.google.com/group/wireless-africa/browse_thread/thread/efddf11a456b33cc Wireless Africa] for a recent discussion thread.

From its first phase on, the project seeks to

* collect user and business needs and feedback
* adjust technology to business and user needs

=The WISPiab product=

==Scope==

The WISPiab project aims at creating a bundled product, seen as consisting of

* Hardware
* Software
* Documentation

with the related out-of-scope side aspects of

* Education, Skills and Support
* Backhaul/Uplink connectivity

===Language/Localization===

For the time being, all Software and Docs will be in

* English

Localization and translation will be welcome, but the project team will currently not dedicate its own resources to this.

==Requirements / Specification==

Please see: [[WISPiab specifications]]

=Existing/related projects & products=

'''NOTE BEFORE YOU READ: At this point we have not broken down the list into sublists for Hardware / Software / Projects - etc!'''
'''Most items in the list incorporate aspects of all of these, so we keep them in one list. When this becomes to chaotic, we will divide it.'''

This list includes a.o.

* projects / approaches, commercial as well as non-commercial
* software, software platforms
* (almost) pure hardware vendors, integrated hardware/software, etc

'''We have now removed into archive - [[WISPiab ingredients - research archive]] - all the items that have been identified as NOT relevant.'''
In case you feel something is missing here, please check that archive first.

Please find a template at the top of the list, in case you would like to add to the list! You are very welcome to!

==Template for new entries==

* Type: (e.g. Community project, Company, Hardware vendor, Software Vendor, ISP, Telco, ...)
* Description:
* URL: [http://URL URL]
* Contacts:
* Relevance:

==aerospace software==

* Type: Software
* Description: Pre-paid cards for Radius
* URL: [http://www.aerospacesoftware.com/prepaid.html http://www.aerospacesoftware.com/prepaid.html]
* Contacts:
* Relevance: possibly, as element in billing handling

==A2Billing==

* Type: Hardware + Software platform
* Description: "full featured telecom platform and softswitch providing converged services, with self contained billing (pre or post-paid), reporting and statistics for IP and TDM based voice networks"
* URL: [http://trac.asterisk2billing.org/cgi-bin/trac.cgi http://trac.asterisk2billing.org/cgi-bin/trac.cgi]
* Contacts:
* Relevance: '''YES''' - see a.o. connections to Dabba and Trixbox

==Chillispot==

* Type: SW
* Description: Chilispot captive portal, standard in FLOSS captive portal world - "ChilliSpot is an open source captive portal or wireless LAN access point controller. It is used for authenticating users of a wireless LAN. It supports web based login, which is today's standard for public HotSpots, WISP "smart-client" authentication, and it supports Wi-Fi Protected Access (WPA and WPA2). Authentication, authorization and accounting (AAA protocol) is handled via RADIUS (on board or remote).

Development on the original project continues, but slowly for some. The Coova-Chilli is an active project and has since added many new features and is an integral part of the CoovaAP firmware.

As of mid 2007, ChilliSpot appears to be dead. The developer Jens Jacobsen has vanished, and the chillispot.org domain has lapsed. Fortunately CoovaChilli has forked from ChilliSpot 1.0 and development continues with an active user-base." See Coova instead.
* URL: [http://en.wikipedia.org/wiki/ChilliSpot http://en.wikipedia.org/wiki/ChilliSpot]
* Contacts:
* Relevance: '''YES - in its Coova form''' - probably an ingredient

==Colubris==

* Type: HW, SW, solutions
* Description: Colubris SW covers the whole rnage of wireless operations. Fantsuam used their billing module, with mixed experience.
* URL: [http://www.colubris.com/ http://www.colubris.com/] partners: [http://www.colubris.com/partners/service-partners.asp http://www.colubris.com/partners/service-partners.asp] --> HookMeUp system
* Contacts:
* Relevance: '''Probably low.''' license, price, opennness, ... interesting to study though

==Coova==

* Type: Software: Firmware for WRT54G etc
* Description: "Hotspot setup and management software .... includes firmware, authentication and management services, and captive portal solutions.... . .. Builds on OpenWrt, ChilliSpot, WifiDog, OpenVPN ...web interfaces for wifidog.conf and other conf files"
* URL: [http://URL URL]
* Contacts:
* Relevance: '''YES''' relevant! test and evaluate

==Cuwin==

* Type: Software, community project
* Description: "The CUWiN Foundation develops decentralized, community-owned networks that foster democratic cultures and local content. Through advocacy and through our commitment to open source technology, we support organic networks that grow to meet the needs of their community."
* URL: [http://www.cuwin.net/ http://www.cuwin.net/]
* Contacts:
* Relevance: '''yes'''- explore overlaps and cooperation

==Dabba / Orange Farm==

* Type: Village telco and ISP (e.g. Community project, Company, Hardware vendor, Software Vendor, ISP, Telco, ...)
* Description: SW based off openWRT, OpenSER, coova,
* URL: [http://dabba.co.za dabba.co.za]
* Contacts:
* Relevance: '''yes'''! uses and brings together best-of-breed usual suspects. working business model. cooperation.

==daloRadius==

* Type: Software
* Description: "daloRADIUS is an advanced RADIUS web management application aimed at managing hotspots and general-purpose ISP deployments. It features user management, graphical reporting, accounting, a billing engine and integrates with GoogleMaps for geo-locating."
* URL: [http://sourceforge.net/projects/daloradius http://sourceforge.net/projects/daloradius]
* Contacts:
* Relevance: '''evaluate!'''

==Fadeco==

* Type: Community project
* Description: an impressive example of an organically grown bootstrapped
network project. Ian Howard interview: "a true social entrepreneur at work." [http://www.youtube.com/watch?v=ErXK29u4Pf8 http://www.youtube.com/watch?v=ErXK29u4Pf8]
* URL: [http://fadeco.org URL]
* Contacts: Josepg Sekiku
* Relevance: '''high'''. interview and study business model.

==Fantsuam Foundation==

* Type: Community project, network
* Description: Fantsuam has implemented a communtiy network, including interesting experiences with voucher based billing
* URL: [http://www.fantsuam.org/ fantsuam.org ]
* Contacts: Alberto and Ochuoko through Sebastian
* Relevance: '''yes'''. Analyse experience with Billing implementation

==Firkant.net==

* Type: Communtiy owned fiber network
* Description: Though outside region (Denmark), an interesting case story of successful CON (fiber).
* URL: [http://firkant.net firkant.net]
* Contacts: through Sebastian
* Relevance: '''low in this phase''', but interesting re: community owned fiber. to learn from. interview!

==Freifunk==

* Type: Community project, Software
* Description: Freifunk is arguably the most succesful mesh movement and source of one of the best GUI integrated firmwares for the Linksys WRT54G and other boxes
* URL: [http://freifunk.net freifunk.net]
* Contacts: see URL
* Relevance: '''high'''

==Green-Wifi==

* Type: Community project, Hardware
* Description: "Green WiFi has developed a low cost, solar-powered, standardized WiFi access solution that runs out-of-the-box with no systems integration or power requirements. All that is required is a single source of broadband access. "
* URL: [http://green-wifi.org/ http://green-wifi.org/]
* Contacts: see URL
* Relevance: '''high''' - hardware experience, sw aspects (?), rollout coop?

==Inveneo==

* Type: Hardware/Software solutions, Implementer
* Description: "The Inveneo WiFi Outdoor Access Point is a rugged wireless router that can be used in multiple network configurations, for long-distance point-to-point links or to connect multiple locations. The WiFi Access Point requires very little network and device setup, as the integrated software has an internal webserver with easy-to-use interface accessible from any standard web browser. - The Computing Station is an ultra-low-power, affordable and fully functional desktop computer designed for use in rural locations such as schools, clinics, field offices, community centers and Internet cafes. - The Inveneo Hub Server|| "
* URL: [http://www.inveneo.org http://www.inveneo.org]
* Contacts:
* Relevance: '''high. Low power focus extremely relevant'''.

==ISPBill==

* Type: Software
* Description: "ISPBill is an ISP billing and management system. It features automatic generation and emailing of invoices, receipts and statements, a customer interface, a ticket system, and much more. ISPBill is intended to continue where cwispy left off"
* URL: [http://sourceforge.net/projects/ispbill/ http://sourceforge.net/projects/ispbill/]
* Contacts:
* Relevance: '''yes''' - test it

==ISPConfig==

* Type: Software
* Description: "ISPConfig is an open source hosting control panel for Linux. ISPConfig is licensed under BSD license."
* URL: [http://www.ispconfig.org/ http://www.ispconfig.org/]
* Contacts:
* Relevance:'''yes'' - check against webmin

==it46 - VoIP for Development project - Free Telephony Project==

* Type: Software
* Description: "free hardware designs for telephone systems. Both the hardware and software are open ... free to copy, modify and re-use the hardware designs. The hardware for a complete embedded Asterisk IP PBX (including multiple analog ports or a T1/E1) can be built for a few hundred dollars. ... first product is the IP04. The IP04 is a low cost phone system that can switch phone calls from analog phones or phone lines over the Internet using VoIP. The IP04 is a professionally designed product that is in volume production today"
* URL: [https://www.it46.se/entry/310 https://www.it46.se/entry/310] [http://www.rowetel.com/ucasterisk/ip04.html http://www.rowetel.com/ucasterisk/ip04.html]
* Contacts:
* Relevance:'''yes'''

==LessNetworks==

* Type: Software, SW/HW bundles
* Description: "This Austin Texas based group, part of the Free WiFi Movement, offers the Hotspot Server open source software that you can use to create your own free hotspot. When you run their software installation it creates a Linux system with the appropriate settings. Lessnetworks provides downloads of the software, sells their software on disk for a nominal cost, and even sells some preconfigured wireless servers on eBay that you can purchase as a package."
* URL: [http://www.lessnetworks.com/index.php http://www.lessnetworks.com/index.php]
* Contacts:
* Relevance: '''yes'''. check out!

==Musimi==

* Type: Village Telco of sorts
* Description: Though outside region (Denmark), an interesting case story of successful (but also problematic?) Asterisk based Telco startup -
* URL: [http://musimi.dk msuimi.dk]
* Contacts: through Sebastian
* Relevance: '''to learn from. interview! Sebastian'''

==open-mesh==

* Type: Hardware vendor, Software Vendor
* Description: "Our Mission - To support WiFi mesh networks for community wireless, education, and the developing world."
* URL: [http://www.open-mesh.com/ open-mesh.com] see e.g. the roadmap [http://www.open-mesh.com/activekb/questions/4/Open-Mesh+Roadmap http://www.open-mesh.com/activekb/questions/4/Open-Mesh+Roadmap]
* Contacts:
* Relevance: very high! esp. when looking at development roadmap.

==Orangemesh==

* Type: Software Project
* Description: "OrangeMesh is a simple, open source network management dashboard for ROBIN based networks. OrangeMesh is jointly developed by Orange Networking, Open-Mesh, Inc, and students at UNC Chapel Hill.
Features

Seamless Integration with Open-Mesh: You can use Orangemesh together with your existing control at Open-Mesh.com. Soon, you'll be able to migrate all your network settings and infromation from Open-Mesh to an Orangemesh server with just a click of a button.

Completely Open Source: Change anything you want. Help build the final piece necessary for a completely open-source and affordable mesh network.

Customizable checkin script: Have access to every configuration option available in ROBIN. Make those pesky custom /config changes outlast the next firmware update.

Advanced Community Features: Grow an organic mesh network. Empower non-administrators and give your users a stake in the network and simplify the deployment of large community networks.

Much more: Improved Google Maps status view, custom CSS skins, user management, captive portal support, and more!"
* URL: [http://orangemesh.sourceforge.net/ http://orangemesh.sourceforge.net/]
* Contacts: through Open-Mesh
* Relevance: high

==phpMyPrepaid==

* Type: Software
* Description: An interface for the creation and managment of prepaid cards and accounts designed to work with a MySQL database and FreeRadius.
* URL: [http://sourceforge.net/projects/phpmyprepaid/ http://sourceforge.net/projects/phpmyprepaid/]
* Contacts:
* Relevance:'''Yes''' - possible candidate for billing integration

==phpRADmin==

* Type: Software
* Description: "phpRADmin is a tool written in PHP intended to handle the administration and provisioning of FreeRADIUS over the Web with MySQL as backend. This interface (including dialup_admin) allows the administrator to config, find, create, edit, delete, and test users on an SQL (MySQL) database, create SQL groups, gather accounting information for a user, do complicated queries on the SQL accounting database, check RADIUS server availability, and produce dialup usage statistics, manage (create, update, revoke) PKI Certificates, Dictionary management, invoice management and system monitoring. Really, a system to manage FreeRADIUS with WPA, EAP (802.1X), PPP, PPPoE, Captive Portal, VoIP systems and other authentication methods. phpRADmin show pies and graphs of your network status, usage audits, administration profiles with 3 levels. phpRADmin is Chillispot and WISP ready."
* URL: [http://www.phpradmin.org/ http://www.phpradmin.org/]
* Contacts:
* Relevance:'''evaluate!'''

http://www.phpradmin.org/

==Robin==

* Type: Software
* Description: "ROBIN stands for ROuting Batman INside: a mesh network firmware using BATMAN routing algorithm
ROBIN is a firmware deployed on OpenWRT kamikaze 7.07 and is intended for Atheros AP51 devices such as Meraki Mini or Fonera; when flashed, your mini-routers act as comfortable and 0-config mesh-network appliances."
* URL: [http://www.blogin.it/howtorobin/index.html http://www.blogin.it/howtorobin/index.html]
* Contacts:
* Relevance: yes - study Mesh/Captive implementation

==Soekris==

* Type: Hardware
* Description: Low cost, low poer comms boards, e.g. net4521 - This compact, low-power, low-cost, advanced communication computer is based on a 133 Mhz 486 class processor. It has two 10/100 Mbit ethernet ports, up to 64 Mbyte SDRAM main memory and uses a CompactFlash module for program and data storage. It can be expanded using a MiniPCI type III board and up to two PC-Card/Cardbus adapters.

It has been optimized for use as wireless router using PC-Card wireless adapters, but has the flexibility to take on a whole range of different functions as a communication appliance. The board is designed for long life and low power.

It is available in any volume in the standard version, and as board only or with a small metal box and various power supplies. The board can be customized according to requirements when ordering higher volume."
* URL: [http://soekris.com http://soekris.com]
* Contacts:
* Relevance: '''maybe''' - potential hardware ingredient

==Tranzeo==

* Type: Hardware vendor
* Description: Interesting wireless hardware
* URL: [http://tranzeo.comL tranzeo.com]
* Contacts:
* Relevance: '''possibly?'''.

==Trixbox==

* Type: SW, distro
* Description: formerly known as Asterisk@Home, is an Asterisk distro aimed at ease of use. It is used by e.g. Uninet to provide community Voip. Their intgrated HW/SW product "Trixbox in a box" ... "... makes it even easier for business to get trixbox phone systems up and running. Why buy separate hardware, download and install software, configure the hardware, and test it all yourself?"
* URL: [http://URL URL]
* Contacts:
* Relevance: '''medium''' - probably covered already or integrated elsewhere

==Ubiquiti==

* Type: Hardware vendor, solutions
* Description: Vendors of WISP targetted high quality, low budget gear
* URL: [http://ubnt.com/ http://ubnt.com/]
* Contacts:
* Relevance:'''yes'''

==Webmin==

* Type: SW management, GUI based admin, etc
* Description: "Webmin is a web-based interface for system administration for Unix. Using any modern web browser, you can setup user accounts, Apache, DNS, file sharing and much more. Webmin removes the need to manually edit Unix configuration files like /etc/passwd, and lets you manage a system from the console or remotely."
* URL: [http://www.webmin.com/ http://www.webmin.com]
* Contacts:
* Relevance: '''yes'''

==Worldspot==

* Type: WISP management, hotspot manegement
* Description: builds on DD-WRT, Coova. Adds billing, multiple schemes and models.
* URL: [http://worldspot.net/ http://worldspot.net]
* Contacts:
* Relevance: '''medium.''' tech ingredients are coova and dd-wrt. better go direct, '''Billing part might be interesting to look at,''' though business models might be incompatible.

=Appendices=

==Appendix 1: Suggested product names==

* WIAB
* Wimbo - WIreless Mover BOx (Wimbo = Kiswahili for Song, Anthem, Hymn)

The WISP-in-a-box project

2008-06-19T06:10:43Z

Sebastian: /* Dabba / Orange Farm */

[[Category: WISP in a box]]

=What is it? The 30 second summary =

The ''WISP in a box'' project will

* take the best known ingredients from the open source / free software world
* bundle them and make them easy to use
* put them on low cost, low power hardware (which will be solar powered)

to create a

* easy-to use-and-run wireless ISP box

and make this product available to

* entrepreneurs, activists, movers of all kinds

in order to help bringing

* connectivity to underserviced, underprivileged and overcharged communities in Africa.

Click here to see [http://wirelessafrica.meraka.org.za/wiki/index.php/Category:WISP_in_a_box all documents related to the project]

=Contacts & how to get involved?=

The WISP in a box project is hosted and coordinated at

'''The Meraka Institute, CSIR, South Africa.'''

Project coordination: Sebastian Büttrich, http://wire.less.dk, mail: sebastian_at_less.dk

Click here to see [http://wirelessafrica.meraka.org.za/wiki/index.php/Category:WISP_in_a_box all documents related to the project]

The WISP in a box project is '''completely open''' in that

* We are highly interested in working with everybody with an interest in the project - just talk to us!
* All project communications and results will be fully open.
* Contributions to the project will be respected, attributed and credited for.
* We are aiming at actively making our resources available to the community as best we can.

All parts of this and other project '''documents are open for editing and commenting'''.

Best starting points might be ...

* the list of existing and related projects - we are interested in your input, * We are open to any dialogue about cooperation.experiences, additions.
* the specifications
* use cases and business cases

=Background and Goals=

The Wireless ISP in a box (short: WISPiab, final name pending) project has been suggested and discussed over a period of time,
a.o. it has been suggested at the London meeting, December 2006.

==Time for action==

Without discussing the connectivity situation in Africa in great depth,
there is no doubt that 2008 is the year that new business and non-business connectivity initiatives need to be put into action, gain in speed and be scaled up.

The WISPiab project wants enable the implementation speed needed,
by

* lowering the technology skils barrier
* offering a technology match to emerging business models
* creating an open platform for others to build on

Pragmatically speaking,

<pre>
we seek to address a dilemma that many wireless practicioners, activists and entrepreneurs are facing constantly:

When asked if all technology ingredients needed for starting a wireless project also is freely available, we answer 'yes'.
However, when asked ''how'' to get started, we have to admit that

* it is not quite so easy (yet),
* it will take a bit of fumbling and skills,
* while 80% of all needed parts are there, 20% and the finished bundle are still missing

and so forth.

Thus, successful startups - and we have seen a few of those - still largely depend on the "one skilled enthusiast" approach.
While this approach produces admirable case stories,
it is not a path the vast majority of people can take.
</pre>

==Openness and reusability==

We are in the lucky situation that many people have invested tremendous work over the last few years.

The project does not intend to reinvent any wheels, but to identify the best ingredients and components,
bring them together and make them more manageable.

It is time to get up to speed and scale.

We intend to work with everybody who is willing to share, and willing to benefit from what Meraka can bring to the table:

* capacity for the improvement of existing solutions
* capacity for testing and rollout
* capacity for documenting

All discussions, documents and results of the WISPiab project will be open throughout.

Software developed as aprt of this project will be licensed under a GPL license.
Harware specifications will be open,
and all documentation and educational materials will be published under an open license, e.g Creative Commons Licenses, GNU Free Documentation License, or such.

==Wireless vs. Wired?==

Wireless technology is not seen as competing with wires (fiber) connectivity. On the contrary, we feel that

wireless first meters will be essential in turning wired miles into successes.

Suppliers of wired connectivity need to be able to work with markets of well connected users and customers, businesses as well as non-profit,
which currently can only be created through the use of wireless technologies.

Thus, wireless technology is seen as an enabler of wired connectivity.

==Data or Voice? Infrastructure or Application?==

Two questions need a short comment:

# Is Data or Voice the most urgent field to address?
# Should the focus be on Infrastructure or Applications?

need a short comment.

As far as the WISPiab is concerned, none of these questions is of explicit relevance.
The WISPiab needs to support and match any business case that is identified as valid.

Technology follows need, and the need is identified by careful study of emerging business models.

Most business models will need

* infrastructure to transport applications,
and
* applications to make infrastructure attractive.

=Pillars of the project=

As indicated by the name, the project focusses on wireless technology,
however the project is based on a wider set of pillars.

# Free Software / Open Source
# License exempt wireless (802.11_)
# Local ownership
# Solar power (and thus low power)
# Low cost

These pillars indicate that

# Proprietary and closed source elements will not be allowed into the product. Where they are inevitable (e.g. drivers), they have to be clearly marked as such.
# Licensed frequencies and proprietary implentations with license exemt spectrum will not be allowed into the product. Backhaul connectivity, being outside of the product scope, is not touched by this.
# Centralized and non-lcoal business and technology models, e.g. models that require a sign up to a central corporate server (see for example the Meraki model), will not be considered.
# Any hardware solution will only be deemed complete if delivered bundled with a non-grid power supply. The default version of any WISPian project will be solar powered. Users with stable grid electricity have the freedom to deselect this option.
# Hardware and Software cost must be kept to an absolute minimum.

=Business models=

The WISPiab project takes its point of departure in feasible business models, not in technology.

Business models here will include for-profit as well as not-for-profit and completely free models, e.g. open networks.

Among the models and names recently discussed are

* VT: Village Telco
* VOT: Village Own/Operated Telco
* VOOT: Village Own and Operated Telco
* CON: Community owned network
* COF: Community owned Fibre

See e.g. the list [http://groups.google.com/group/wireless-africa/browse_thread/thread/efddf11a456b33cc Wireless Africa] for a recent discussion thread.

From its first phase on, the project seeks to

* collect user and business needs and feedback
* adjust technology to business and user needs

=The WISPiab product=

==Scope==

The WISPiab project aims at creating a bundled product, seen as consisting of

* Hardware
* Software
* Documentation

with the related out-of-scope side aspects of

* Education, Skills and Support
* Backhaul/Uplink connectivity

===Language/Localization===

For the time being, all Software and Docs will be in

* English

Localization and translation will be welcome, but the project team will currently not dedicate its own resources to this.

==Requirements / Specification==

Please see: [[WISPiab specifications]]

=Existing/related projects & products=

'''NOTE BEFORE YOU READ: At this point we have not broken down the list into sublists for Hardware / Software / Projects - etc!'''
'''Most items in the list incorporate aspects of all of these, so we keep them in one list. When this becomes to chaotic, we will divide it.'''

This list includes a.o.

* projects / approaches, commercial as well as non-commercial
* software, software platforms
* (almost) pure hardware vendors, integrated hardware/software, etc

'''We have now removed into archive - [[WISPiab ingredients - research archive]] - all the items that have been identified as NOT relevant.'''
In case you feel something is missing here, please check that archive first.

Please find a template at the top of the list, in case you would like to add to the list! You are very welcome to!

==Template for new entries==

* Type: (e.g. Community project, Company, Hardware vendor, Software Vendor, ISP, Telco, ...)
* Description:
* URL: [http://URL URL]
* Contacts:
* Relevance:

==aerospace software==

* Type: Software
* Description: Pre-paid cards for Radius
* URL: [http://www.aerospacesoftware.com/prepaid.html http://www.aerospacesoftware.com/prepaid.html]
* Contacts:
* Relevance: possibly, as element in billing handling

==A2Billing==

* Type: Hardware + Software platform
* Description: "full featured telecom platform and softswitch providing converged services, with self contained billing (pre or post-paid), reporting and statistics for IP and TDM based voice networks"
* URL: [http://trac.asterisk2billing.org/cgi-bin/trac.cgi http://trac.asterisk2billing.org/cgi-bin/trac.cgi]
* Contacts:
* Relevance: '''YES''' - see a.o. connections to Dabba and Trixbox

==Chillispot==

* Type: SW
* Description: Chilispot captive portal, standard in FLOSS captive portal world - "ChilliSpot is an open source captive portal or wireless LAN access point controller. It is used for authenticating users of a wireless LAN. It supports web based login, which is today's standard for public HotSpots, WISP "smart-client" authentication, and it supports Wi-Fi Protected Access (WPA and WPA2). Authentication, authorization and accounting (AAA protocol) is handled via RADIUS (on board or remote).

Development on the original project continues, but slowly for some. The Coova-Chilli is an active project and has since added many new features and is an integral part of the CoovaAP firmware.

As of mid 2007, ChilliSpot appears to be dead. The developer Jens Jacobsen has vanished, and the chillispot.org domain has lapsed. Fortunately CoovaChilli has forked from ChilliSpot 1.0 and development continues with an active user-base." See Coova instead.
* URL: [http://en.wikipedia.org/wiki/ChilliSpot http://en.wikipedia.org/wiki/ChilliSpot]
* Contacts:
* Relevance: '''YES - in its Coova form''' - probably an ingredient

==Colubris==

* Type: HW, SW, solutions
* Description: Colubris SW covers the whole rnage of wireless operations. Fantsuam used their billing module, with mixed experience.
* URL: [http://www.colubris.com/ http://www.colubris.com/] partners: [http://www.colubris.com/partners/service-partners.asp http://www.colubris.com/partners/service-partners.asp] --> HookMeUp system
* Contacts:
* Relevance: '''Probably low.''' license, price, opennness, ... interesting to study though

==Coova==

* Type: Software: Firmware for WRT54G etc
* Description: "Hotspot setup and management software .... includes firmware, authentication and management services, and captive portal solutions.... . .. Builds on OpenWrt, ChilliSpot, WifiDog, OpenVPN ...web interfaces for wifidog.conf and other conf files"
* URL: [http://URL URL]
* Contacts:
* Relevance: '''YES''' relevant! test and evaluate

==Cuwin==

* Type: Software, community project
* Description: "The CUWiN Foundation develops decentralized, community-owned networks that foster democratic cultures and local content. Through advocacy and through our commitment to open source technology, we support organic networks that grow to meet the needs of their community."
* URL: [http://www.cuwin.net/ http://www.cuwin.net/]
* Contacts:
* Relevance: '''yes'''- explore overlaps and cooperation

==Dabba / Orange Farm==

* Type: Village telco and ISP (e.g. Community project, Company, Hardware vendor, Software Vendor, ISP, Telco, ...)
* Description: SW based off openWRT, OpenSER, coova,
* URL: [http://dabba.co.za dabba.co.za]
* Contacts:
* Relevance: '''yes'''! uses and brings together best-of-breed usual suspects. working business model. cooperation.

==daloRadius==

* Type: Software
* Description: "daloRADIUS is an advanced RADIUS web management application aimed at managing hotspots and general-purpose ISP deployments. It features user management, graphical reporting, accounting, a billing engine and integrates with GoogleMaps for geo-locating."
* URL: [http://sourceforge.net/projects/daloradius http://sourceforge.net/projects/daloradius]
* Contacts:
* Relevance: '''evaluate!'''

==Fadeco==

* Type: Community project
* Description: an impressive example of an organically grown bootstrapped
network project. Ian Howard interview: "a true social entrepreneur at work." [http://www.youtube.com/watch?v=ErXK29u4Pf8 http://www.youtube.com/watch?v=ErXK29u4Pf8]
* URL: [http://fadeco.org URL]
* Contacts: Josepg Sekiku
* Relevance: '''high'''. interview and study business model.

==Fantsuam Foundation==

* Type: Community project, network
* Description: Fantsuam has implemented a communtiy network, including interesting experiences with voucher based billing
* URL: [http://www.fantsuam.org/ fantsuam.org ]
* Contacts: Alberto and Ochuoko through Sebastian
* Relevance: '''yes'''. Analyse experience with Billing implementation

==Firkant.net==

* Type: Communtiy owned fiber network
* Description: Though outside region (Denmark), an interesting case story of successful CON (fiber).
* URL: [http://firkant.net firkant.net]
* Contacts: through Sebastian
* Relevance: '''low in this phase''', but interesting re: community owned fiber. to learn from. interview!

==Freifunk==

* Type: Community project, Software
* Description: Freifunk is arguably the most succesful mesh movement and source of one of the best GUI integrated firmwares for the Linksys WRT54G and other boxes
* URL: [http://freifunk.net freifunk.net]
* Contacts: see URL
* Relevance: '''high'''

==Green-Wifi==

* Type: Community project, Hardware
* Description: "Green WiFi has developed a low cost, solar-powered, standardized WiFi access solution that runs out-of-the-box with no systems integration or power requirements. All that is required is a single source of broadband access. "
* URL: [http://green-wifi.org/ http://green-wifi.org/]
* Contacts: see URL
* Relevance: '''high''' - hardware experience, sw aspects (?), rollout coop?

==Inveneo==

* Type: Hardware/Software solutions, Implementer
* Description: "The Inveneo WiFi Outdoor Access Point is a rugged wireless router that can be used in multiple network configurations, for long-distance point-to-point links or to connect multiple locations. The WiFi Access Point requires very little network and device setup, as the integrated software has an internal webserver with easy-to-use interface accessible from any standard web browser. - The Computing Station is an ultra-low-power, affordable and fully functional desktop computer designed for use in rural locations such as schools, clinics, field offices, community centers and Internet cafes. - The Inveneo Hub Server|| "
* URL: [http://www.inveneo.org http://www.inveneo.org]
* Contacts:
* Relevance: '''high. Low power focus extremely relevant'''.

==ISPBill==

* Type: Software
* Description: "ISPBill is an ISP billing and management system. It features automatic generation and emailing of invoices, receipts and statements, a customer interface, a ticket system, and much more. ISPBill is intended to continue where cwispy left off"
* URL: [http://sourceforge.net/projects/ispbill/ http://sourceforge.net/projects/ispbill/]
* Contacts:
* Relevance: '''yes''' - test it

==ISPConfig==

* Type: Software
* Description: "ISPConfig is an open source hosting control panel for Linux. ISPConfig is licensed under BSD license."
* URL: [http://www.ispconfig.org/ http://www.ispconfig.org/]
* Contacts:
* Relevance:'''yes'' - check against webmin

==it46 - VoIP for Development project - Free Telephony Project==

* Type: Software
* Description: "free hardware designs for telephone systems. Both the hardware and software are open ... free to copy, modify and re-use the hardware designs. The hardware for a complete embedded Asterisk IP PBX (including multiple analog ports or a T1/E1) can be built for a few hundred dollars. ... first product is the IP04. The IP04 is a low cost phone system that can switch phone calls from analog phones or phone lines over the Internet using VoIP. The IP04 is a professionally designed product that is in volume production today"
* URL: [https://www.it46.se/entry/310 https://www.it46.se/entry/310] [http://www.rowetel.com/ucasterisk/ip04.html http://www.rowetel.com/ucasterisk/ip04.html]
* Contacts:
* Relevance:'''yes'''

==LessNetworks==

* Type: Software, SW/HW bundles
* Description: "This Austin Texas based group, part of the Free WiFi Movement, offers the Hotspot Server open source software that you can use to create your own free hotspot. When you run their software installation it creates a Linux system with the appropriate settings. Lessnetworks provides downloads of the software, sells their software on disk for a nominal cost, and even sells some preconfigured wireless servers on eBay that you can purchase as a package."
* URL: [http://www.lessnetworks.com/index.php http://www.lessnetworks.com/index.php]
* Contacts:
* Relevance: '''yes'''. check out!

==Musimi==

* Type: Village Telco of sorts
* Description: Though outside region (Denmark), an interesting case story of successful (but also problematic?) Asterisk based Telco startup -
* URL: [http://musimi.dk msuimi.dk]
* Contacts: through Sebastian
* Relevance: '''to learn from. interview! Sebastian'''

==open-mesh==

* Type: Hardware vendor, Software Vendor
* Description: "Our Mission - To support WiFi mesh networks for community wireless, education, and the developing world."
* URL: [http://www.open-mesh.com/ open-mesh.com] see e.g. the roadmap [http://www.open-mesh.com/activekb/questions/4/Open-Mesh+Roadmap http://www.open-mesh.com/activekb/questions/4/Open-Mesh+Roadmap]
* Contacts:
* Relevance: very high! esp. when looking at development roadmap.

==Orangemesh==

* Type: Software Project
* Description: "OrangeMesh is a simple, open source network management dashboard for ROBIN based networks. OrangeMesh is jointly developed by Orange Networking, Open-Mesh, Inc, and students at UNC Chapel Hill.
Features

Seamless Integration with Open-Mesh: You can use Orangemesh together with your existing control at Open-Mesh.com. Soon, you'll be able to migrate all your network settings and infromation from Open-Mesh to an Orangemesh server with just a click of a button.

Completely Open Source: Change anything you want. Help build the final piece necessary for a completely open-source and affordable mesh network.

Customizable checkin script: Have access to every configuration option available in ROBIN. Make those pesky custom /config changes outlast the next firmware update.

Advanced Community Features: Grow an organic mesh network. Empower non-administrators and give your users a stake in the network and simplify the deployment of large community networks.

Much more: Improved Google Maps status view, custom CSS skins, user management, captive portal support, and more!"
* URL: [http://orangemesh.sourceforge.net/ http://orangemesh.sourceforge.net/]
* Contacts: through Open-Mesh
* Relevance: high

==phpMyPrepaid==

* Type: Software
* Description: An interface for the creation and managment of prepaid cards and accounts designed to work with a MySQL database and FreeRadius.
* URL: [http://sourceforge.net/projects/phpmyprepaid/ http://sourceforge.net/projects/phpmyprepaid/]
* Contacts:
* Relevance:'''Yes''' - possible candidate for billing integration

==Robin==

* Type: Software
* Description: "ROBIN stands for ROuting Batman INside: a mesh network firmware using BATMAN routing algorithm
ROBIN is a firmware deployed on OpenWRT kamikaze 7.07 and is intended for Atheros AP51 devices such as Meraki Mini or Fonera; when flashed, your mini-routers act as comfortable and 0-config mesh-network appliances."
* URL: [http://www.blogin.it/howtorobin/index.html http://www.blogin.it/howtorobin/index.html]
* Contacts:
* Relevance: yes - study Mesh/Captive implementation

==Soekris==

* Type: Hardware
* Description: Low cost, low poer comms boards, e.g. net4521 - This compact, low-power, low-cost, advanced communication computer is based on a 133 Mhz 486 class processor. It has two 10/100 Mbit ethernet ports, up to 64 Mbyte SDRAM main memory and uses a CompactFlash module for program and data storage. It can be expanded using a MiniPCI type III board and up to two PC-Card/Cardbus adapters.

It has been optimized for use as wireless router using PC-Card wireless adapters, but has the flexibility to take on a whole range of different functions as a communication appliance. The board is designed for long life and low power.

It is available in any volume in the standard version, and as board only or with a small metal box and various power supplies. The board can be customized according to requirements when ordering higher volume."
* URL: [http://soekris.com http://soekris.com]
* Contacts:
* Relevance: '''maybe''' - potential hardware ingredient

==Tranzeo==

* Type: Hardware vendor
* Description: Interesting wireless hardware
* URL: [http://tranzeo.comL tranzeo.com]
* Contacts:
* Relevance: '''possibly?'''.

==Trixbox==

* Type: SW, distro
* Description: formerly known as Asterisk@Home, is an Asterisk distro aimed at ease of use. It is used by e.g. Uninet to provide community Voip. Their intgrated HW/SW product "Trixbox in a box" ... "... makes it even easier for business to get trixbox phone systems up and running. Why buy separate hardware, download and install software, configure the hardware, and test it all yourself?"
* URL: [http://URL URL]
* Contacts:
* Relevance: '''medium''' - probably covered already or integrated elsewhere

==Ubiquiti==

* Type: Hardware vendor, solutions
* Description: Vendors of WISP targetted high quality, low budget gear
* URL: [http://ubnt.com/ http://ubnt.com/]
* Contacts:
* Relevance:'''yes'''

==Webmin==

* Type: SW management, GUI based admin, etc
* Description: "Webmin is a web-based interface for system administration for Unix. Using any modern web browser, you can setup user accounts, Apache, DNS, file sharing and much more. Webmin removes the need to manually edit Unix configuration files like /etc/passwd, and lets you manage a system from the console or remotely."
* URL: [http://www.webmin.com/ http://www.webmin.com]
* Contacts:
* Relevance: '''yes'''

==Worldspot==

* Type: WISP management, hotspot manegement
* Description: builds on DD-WRT, Coova. Adds billing, multiple schemes and models.
* URL: [http://worldspot.net/ http://worldspot.net]
* Contacts:
* Relevance: '''medium.''' tech ingredients are coova and dd-wrt. better go direct, '''Billing part might be interesting to look at,''' though business models might be incompatible.

=Appendices=

==Appendix 1: Suggested product names==

* WIAB
* Wimbo - WIreless Mover BOx (Wimbo = Kiswahili for Song, Anthem, Hymn)

WISPiab work meeting 200806

2008-06-12T11:18:04Z

Sebastian: /* Requirements, Specifications, Wishlist */

[[Category: WISP in a box]]

=Work meeting of the WISP-in-a-box project=

[[The WISP-in-a-box project]]

=Date=

June 2-3-4, 2008

9-17 h

=Location=

Meraka Institute,
Building 43 C,
Hummingbird Room (C128, ground floor)

Pretoria

=Invitation List=

People and organisations with an active interest in building a concrete product that
helps bringing

connectivity to underserviced, underprivileged and overcharged communities in Africa.

Invitation list:

* Steve Song / Shuttleworth Foundation (monday only)
* Rael Lissoos / Dabba
* Henry Marnitz / Ndlovu Medical Centre (wednesday only)
* Mark Summer, Inveneo (with request to forward to Ubiquiti)
* Elektra
* Mike Jensen (not confirmed)
* Kobus Roux, Meraka (NOT monday)
* Karel Matthee, Meraka
* Kim Gush, Meraka
* David Johnson, Meraka
* Chris Morris, Meraka
* Grant Cambridge, Meraka
* Shela Boshomane, Meraka (monday and wednesday)
* George James, Meraka
* Johann Hugo, Meraka
* John Hay, Meraka
* Ajay Makan, Meraka
* Sebastian Buettrich

More proposals are welcome!

Budgets for travel, if needed: Please contact us!

=Contact=

Sebastian

mail: sebastian@less.dk

skype: sebastian_buettrich

cell: (+27) (0) 79 915 32 92

=Timeplan=

The timeplan is draft level and will be adjusted to people's ability to join for limited periods.

'''The first day''' will be dedicated to the '''organizational layer''',

introducing the various projects and teams,
discussing the business models,
identifying overlap of work agendas as well as the main challenges each of the projects are seeing.

'''The second day''' will move down to detail level,
moving from business and organizational models to technology requirements/specifications.

The third day

==Day 1 - Monday, June 2==

===Morning===

====Creating Context====

Introductions, Presentations of participants

(Short 10 mns, informal project introductions)

* Introduction and WISPiab Project (Sebastian Buettrich)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Ndlovu Medical Centre (Henry Marnitz) (moved to Wednesday, June 4)
* Peeble's Valley Mesh (David Johnson)
* Digital Doorway (tba)
* Inveneo platform (Mark Summer)
* WISPiab work status (George James)
* Wireless Africa project (Chris Morris)
* Freifunk, B.a.t.m.a.n. & Meraka Mesh Testbed (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* IP04 (it46, rowetel) (on behalf of the project: Sebastian Buettrich)

===Afternoon===

====Business models====

Introduction: Sebastian

Business models may be classified according to a number of different dimensions -

e.g. financial/economic layer, tech/network topology layer, applications layer, social layer, -

Based on the experience of the participants and projects,
business models should be reviewed with the goal of reaching a downselection of models that should be implemented/supported
in the first iteration of the WISPiab project.

Classical examples:

* Voice services - The Village Telco
* "Line sharing" - sharing internet access between organizations
* Telecentre / Internet Cafe
* Campus / School network

'''The goal''' is to go through all our relevant models, to classify them on all layers,

and to identify the technology implications (such that technology follows business models, and not vice versa), producing a clear results list.

====Cooperations and Resources====

There is significant overlap between projects on the technology layer.
All projects are subscribing to free software models (GPL / CC, etc).

We are operating against a backdrop of

* challenged (human) resource situation
* brain drain / skills exodus
* wanting to build local (i.e. african? ... southern african? .... south african?) capacity

Cooperation between projects seems appropriate and possible.

'''The goal''' is to conclude this meeting with a clear picture of modes of cooperation.

====Advisory Group====

We wish to form an advisory group / peer group, including partly the invitees of this meeting, but not limited to these.

==Day 2 - Tuesday, June 3==

===Morning===

====Technical Requirements / Specifications - detail level====

Examples of concrete detail issues:

* Authentication - where and how
* Billing in mesh networks
* VoIP in mesh networks

'''The goal''' of this session is to fill the matrix of

''technology requirements x project/business model''

and then check this matrix against the various existing hardware/software platforms.

====Hardware platforms aspects====

A number of different hardware/software platforms are fulfilling subsets of our requirements.

The available platforms need to be discussed and evaluated, towards a decision on what to choose.

The platforms that our projects are currently working with are:

* Linksys WRT54, with firmwares OpenWRT, DD-WRT, Freifunk, CoovaAP, and similar
* Open-Mesh, Accton - with Open Mesh Firmware (new firmware anoounced for summer 2008, with: RO.B.IN, orangemesh, COOVA, etc)
* Inveneo platform
* Ubiquti NS, PS
* Meraka Bokkie routers
* pls add!

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Productification / Dissemination / Rollout strategies====

* Strategies for the productification of software packages
** Sourceforge platform plans (Steve?)
** Ubuntu / UCK (Sebastian, Mark, Elektra)
* Rollout capacity

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

==Day 3 - Wednesday, June 4==

===Morning===

==== Ndlovu Medical Center====

Status and Agenda of network at Ndlovu Medical Center

* How can the various projects benefit Ndlovu Medical Center?

====Status, gaps and planning of implementations====

* WISPiab status and work plan
* Dabba / Village Telco work sprint, June 16-20
** prepare and support that workshop

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Conclusions & Next steps====

* Dabba Worksprint
* WISPiab work plan
* Digital Doorway work
* Wireless Africa, June meeting

etc

= Notes from the meeting - Day 1=

==People & Project introductions==

* Introduction and WISPiab Project (Sebastian Buettrich)
* Peeble's Valley Mesh (David Johnson)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Inveneo platform (Mark Summer)
* Freifunk (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* WISPiab work status (George James)
* Two radio mesh router (Johann Hugo)
* Wireless Africa project (Chris Morris)

==Forming an Alliance?==

to be edited

= Notes from the meeting - Day 2=
[[Image:Day2 - WISPiab_Wkshop.jpg|left|thumb|350px|Day2 (L-R) Mark Summer, Johann Hugo, Mike Jensen, Elektra, Sebastian Buettrich, Kobus Roux, George James, Ajay Makan, Karel Matthee
]]

 

==Requirements, Specifications, Wishlist==

We chose the GUI [http://dabba.co.za/wispgui wishlist by Dabba] as an entry to discussing our current specifications set, identifying how we cover the single elements today, identifying dependencies, etc

[[Image:WISPiab meeting 20080603 whiteboard 1.jpg|thumb|left| Whiteboard Day 2]]
[[Image:Working_Logo.jpg|thumb|left|Table context]]

{| border="1" cellpadding="7" cellspacing="0"
!align="left" |What?
!align="left" |Which element
!align="left" |Existing
!align="left" |Who/how
!align="left" |Alternate names/terms
!align="left" |Task
|-
|Network Settings
|core
|FF, IHL, Coova (wifidog) + alternatives, Linksys & Netgear interfaces, webmin/ISPconfig
|
|Network Management, Setup,
|
|-
|ISP settings
|core
|Coova, phpMyPrepaid, OpenWRT (QoS script), master-/wondershaper, webmin/ISPconfig
|
|user/service profiles – provisioning (some of it -> QoS)
|
|-
|VoIP Settings Users, tarriffs
|voice
|AsteriskNow, IP04 HW, Trixbox, A2billing, (Open)SER
|
| -->user profiles, --> VoIP settings
|
|-
|Prepaid Card System (print cards) (ops), ->web, ->voice
|web,voice
|phpMyPrepaid / ISPBill, A2billing
|
|“usage”
|
|-
|CRM
|core
|[http://compiere.com compiere] - explore!
|
|
|
|-
|Accounting -->logs
|core
|phpMyPrepaid/ISPBill, a2billing
|
| ->(if bill) ->ERP
|
|-
|Logo/Company
|core, feeding into the various channels
|(all components have some of it)
|
|themes/skins/ customisation
|
|-
|Network Monitoring
|core
|Nagios/Cacti, Open-Mesh, Open NMS, FF (some), MRTG/rrdtool
|
|Network management
|
|-
|'''Items not contained in Dabba GUI'''
|
|
|
|
|
|-
|Content repository (SW, media, ...), Video Server
|(various, different contents for different channels)
|
|
|
|
|-
|Cache\Proxy with stats
|web
|squid with awstats
|
|
|
|-
|Mail
|core
|Postfix, Courier, webmail: squirrelmail
|
|
|
|-
|Security & encryption
|core
|OpenVPN, GnuPG
|
|
|
|-
|httpd, with stats etc
|web
|apache, awstats
|
|
|
|-
|Wiki / image hosting
|web
|mediawiki
|
|
|
|-
|Telecentre management
|(core)
|UgaBytes telecentre management software - explore!
|
|
|
|-
|}

==Business Models==

Discussion of business models that have informed the specifications, and a checkback whether we feel that the current specifications actually accomodate all these models.

The template on top suggests dimensions / criteria from which to look at the various models.

===Business Model Template===

* Description:

* Economics: Free or paid by ....
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications:
* Network / Topology:
* Internet uplink:
* User Devices / Locations:
* Startup Strategy:
* Legal & Regulatory

===Telecentre / Internet Cafe / Hotspot===

* Description: "Classical" telecentre / cafe style

* Economics: Free or paid by users / advertisers / cafe business
* Billing models: typically Prepaid (Time based):
* Applications: typically Browser / Mail / Office / Games
* Network / Topology: wired LAN
* Internet uplink: model works with and without uplink, but typically yes
* User Devices / Locations: Users on business owned PC
* Startup Strategy:
* Legal & Regulatory: ok in most (?) countries

===Telco===

* Description: Telco offering "fixed line" and mobile VoIP telephony

* Economics: Part free (?) (local) / paid by user
* Billing models: typically Prepaid (Time/Data based):
* Applications: VoIP telephony, typically on dedicated hardware
* Network / Topology: Centralized / Inframesh
* Internet uplink: Yes, if terminating external calls / local loop without
* User Devices / Locations: Users at home / office / mobile, Device VoIP handsets, ATA etc
* Startup Strategy:
* Legal & Regulatory: complex, country to country

===(Edu)Content / Media===

* Economics: Free or paid by user / external
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications: Browser, Video, Image, Sound apps
* Network / Topology: n/a
* Internet uplink: not neccessarily, but recommended
* User Devices / Locations: all kinds of devices, local/remote,
* Startup Strategy:
* Legal & Regulatory: apart from restrictions on content, no issues

===Intranet / Neighbour-Net===

* Economics: Typically paid by customer
* Billing models: Contract / "Subscription"
* Applications: All PC apps
* Network / Topology: typically centralized, might be mesh
* Internet uplink: not neccessarily, but recommended
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy:
* Legal & Regulatory: no issues

===Line Sharing===

* Economics: Typically paid by users, in split scheme (e.g. cost per user = (line cost / # of users)*(marginfactor))
* Billing models: Prepaid monthly
* Applications: All PC apps
* Network / Topology: centralized or mesh
* Internet uplink: yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy: bottom up, organic
* Legal & Regulatory: potential issues with DSL or line resell (?), power limits for wireless part

===ISP===

* Economics: Typically user paid
* Billing models: Prepaid monthly, subscription
* Applications: All apps
* Network / Topology: centralized or mesh
* Internet uplink: yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy:
* Legal & Regulatory: regulations for ISP ops, licensing etc

===Web Hosting / Design===

A potential part of an ISPs business.
Seen as outside scope of this project, however simple home pages / website very common and demanded.
E.g. local businesses, etc

===Corporate / Managed Services===

* Economics: Typically user paid
* Billing models: Prepaid monthly, subscription
* Applications: All apps
* Network / Topology: centralized or mesh
* Internet uplink: typically yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy: company initiative
* Legal & Regulatory: potential issues when mixed user groups share same network (e.g. private, corp, gov, etc)

Strong focus on security (all aspects), network separation, QoS, management.

===Guesthouse Net===

* Economics: Typically user (= guesthouse) paid, might be free for customer of guesthouse, or paid for
* Billing models: if paid for, typically voucher prepaid, time based
* Applications: All apps
* Network / Topology: typically centralized
* Internet uplink: yes
* User Devices / Locations: users devices, maybe one or several public access PC
* Startup Strategy: guesthouse initiative
* Legal & Regulatory: no issues

===Housing Complex===

similar to Intranet / Neighbournet

* Economics: Typically user paid, might be included in other service charges or rent
* Billing models: Prepaid monthly or longer term, subscription
* Applications: All apps
* Network / Topology: centralized or mesh, often wired
* Internet uplink: typically yes
* User Devices / Locations: PCs and other, local at homes
* Startup Strategy: owner initiative
* Legal & Regulatory: no issues

===Surveillance===

* Economics: Typically customer paid
* Billing models: Prepaid monthly, subscription
* Applications: Very specific, wireless surveillance cams, motion detectors, etc
* Network / Topology: centralized or mesh
* Internet uplink: typically yes, in order to allow for remote control and alerts
* User Devices / Locations: surveillance gear and control units, typically PC/browser/mobile (SMS notifications)
* Startup Strategy:
* Legal & Regulatory: generally no issues when limited to company/housing premises. issues when extending into public space. ethics.

===Freifunk style Mesh===

* Economics: Typically completely user paid, informal, but might implement business scheme similar to line sharing ((e.g. cost per user = (central uplink cost / # of users)*(marginfactor))
* Billing models: e.g. Prepaid monthly
* Applications: All incl telephony
* Network / Topology: full mesh / inframesh
* Internet uplink: typically yes, but local net relevant
* User Devices / Locations: all types of devices, at user homes / office / businesses, roaming users
* Startup Strategy:
* Legal & Regulatory: potential issues withpower limits, collision with other networks, DSL reuse / resell

===Training / Consultancy===

A side business, outside scope for this project, but clearly relevant.

= Notes from the meeting - Day 3=

==Ndlovu Medical Centre==

Henry introduces:

* Status of mesh: operational, but currently disconnected (concerns about lightning)
* Use of uplink: Browsing (for community users), sync with data center (Johannesburg)
* Status of uplink: promised by Telkom, but not delivered yet

How to get started with a community mesh?

* Donated PCs - 25 pcs
** Give to local entrepreneur types
* Computer school as entry point

* Create a starter kit
** for existing PCs (there is some! mostly free windows)
** preconfigured
** low cost
** probably of the type: Linksys WRT, open-mesh/accton

Financing model

* Some contribution from user: Prepaid - low cost

What is interesting for people?

* music!!! open music server locally?
* free books? educational material
* free local calls
* a free wikipedia / digital doorway

Income from other sources (not the users):

* advertisements

To do / upcoming:

* '''call for a brainstorm meeting within the community'''

* June 9, meeting with provincial directory

* June 24: excursion to Ndlovu? participants of Wireless Africa meeting, Meraka people, Tom, Elektra

Top pain points / whats in the way:

* political level - get OKs from important players

==Hardware reference platform==

===Overall Requirements===

* 12 Volts (best: 11 ... 16)
* low power
* fanless

===Backend server===

* USB 2x
* ethernet 2x
* VGA

Candidate for reference choice:

* bigger solution: VIA, jetway 1.2 GHz, 2x HD, 1 GB RAM, USD 680 ... 820 [http://mini-box.com e.g. mini-box-com]
** power: approx 25W ?
* smaller solution: VIA, AMD Geode 500 MHz
** power: 8 W
* LEX light/neo, e.g. 1 GB C7 approx USD 600 [http://www.lex.com.tw/ http://www.lex.com.tw/]
* soon to come: Atom based low cost desktops (Mark Summer)
* alternatives: [http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99 http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99]

====Software on backend====

Decision: Ubuntu (non X)

----

===Access node===

* ethernet 2x
* PoE
* outdoor casing
* broadcom or atheros chipset
* 5 ... 18 Volts
* Watchdog (option)
* WISPCAR (option)
* serial port

Candidates:

* Linksys WRT54GL
** price: EUR 50, ZAR 600, USD 60
** power: 4 W
** comments:

* Ubiqiti
** price: NS 2: USD 79
** price: PS 2: USD 110
** power: 5 W

* Accton
** price: USD 40
** power: 2-3 W ?
** comments: overheat problems? needs fixed power 5 V? quality of radio? unstable across channels?

* PCEngines board
** price: > USD 250
** power: approx > 8W, depending on radio cards
** comments:

* Soekris

* Gateworks
**
**

* Wiligear

===Solar powering: A word on the fine for every watt installed===

Elektra makes the conservative estimate:

To power a 5 Watt device reliably, install a 80 Watt solar panel.
This means: 16 Watt solar panel per 1 Watt installed.

At about USD 5 per solar panel watt (current rough guess for market price), we have:

USD 80 in solar panel per 1 Watt installed.

Even when demanding less margin from the solar power system (i.e. less reliability, more optimism), the fine for every Watt installed is heavy.

==Next steps==

* Cape Town Village Telco worksprint
* Kobus, Johann, Elektra
** We need a presentation - Sebastian sends to Kobus and all - dead: june 10
*** Metaphores: pipes - water / roads - cars /
** Minutes / Doc

* Software development
** Meraka - Priority: the set of Coova (alternative: WifiDog) / FreeRadius / phpMyPrepaid (alternative: ISPBill) / Nagios
** Inveneo - Priority: IHL, Server squid/cache, proxy, asterisk, Webmin/ISPConfig
** How to work together? SVN server ? location ? Meraka machines accessible form outside?

* Examine the Ubiquiti - Lead: Elektra
** flash OpenWRT [http://wiki.openwrt.org/OpenWrtDocs/Hardware/Ubiquiti OpenWrt Ubiquiti]
** Examine the SDK
** examine internal antenna pol switching (AAP)

* Procurement - Lead: Ajay
** 12 x Inveneo small server, IONs, June 16
** 2 x Inveneo, Hub servers, June 16
** Ubiquiti Nano/Powerstation: one PS2 in place - OK for now
** Linksyses: we have enough, OK
** Boards: we have the Gateworks, OK
** Solar power: one demo system until June 23 - ask Grant: 64 W panel, charge controller, batteries - Lead: Sebastian

* Examine the [http://wiki.inveneo.org/index.php/Inveneo_Server_Linux_1.x Inveneo Hub Linux (IHL)] - Elektra / George

* Examine Open-Mesh - Lead: Sebastian
** examine status and development
** specifically: the Coova/Robin merger?

* Establish Documentation on Wiki

WISPiab work meeting 200806

2008-06-12T11:17:24Z

Sebastian: /* Requirements, Specifications, Wishlist */

[[Category: WISP in a box]]

=Work meeting of the WISP-in-a-box project=

[[The WISP-in-a-box project]]

=Date=

June 2-3-4, 2008

9-17 h

=Location=

Meraka Institute,
Building 43 C,
Hummingbird Room (C128, ground floor)

Pretoria

=Invitation List=

People and organisations with an active interest in building a concrete product that
helps bringing

connectivity to underserviced, underprivileged and overcharged communities in Africa.

Invitation list:

* Steve Song / Shuttleworth Foundation (monday only)
* Rael Lissoos / Dabba
* Henry Marnitz / Ndlovu Medical Centre (wednesday only)
* Mark Summer, Inveneo (with request to forward to Ubiquiti)
* Elektra
* Mike Jensen (not confirmed)
* Kobus Roux, Meraka (NOT monday)
* Karel Matthee, Meraka
* Kim Gush, Meraka
* David Johnson, Meraka
* Chris Morris, Meraka
* Grant Cambridge, Meraka
* Shela Boshomane, Meraka (monday and wednesday)
* George James, Meraka
* Johann Hugo, Meraka
* John Hay, Meraka
* Ajay Makan, Meraka
* Sebastian Buettrich

More proposals are welcome!

Budgets for travel, if needed: Please contact us!

=Contact=

Sebastian

mail: sebastian@less.dk

skype: sebastian_buettrich

cell: (+27) (0) 79 915 32 92

=Timeplan=

The timeplan is draft level and will be adjusted to people's ability to join for limited periods.

'''The first day''' will be dedicated to the '''organizational layer''',

introducing the various projects and teams,
discussing the business models,
identifying overlap of work agendas as well as the main challenges each of the projects are seeing.

'''The second day''' will move down to detail level,
moving from business and organizational models to technology requirements/specifications.

The third day

==Day 1 - Monday, June 2==

===Morning===

====Creating Context====

Introductions, Presentations of participants

(Short 10 mns, informal project introductions)

* Introduction and WISPiab Project (Sebastian Buettrich)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Ndlovu Medical Centre (Henry Marnitz) (moved to Wednesday, June 4)
* Peeble's Valley Mesh (David Johnson)
* Digital Doorway (tba)
* Inveneo platform (Mark Summer)
* WISPiab work status (George James)
* Wireless Africa project (Chris Morris)
* Freifunk, B.a.t.m.a.n. & Meraka Mesh Testbed (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* IP04 (it46, rowetel) (on behalf of the project: Sebastian Buettrich)

===Afternoon===

====Business models====

Introduction: Sebastian

Business models may be classified according to a number of different dimensions -

e.g. financial/economic layer, tech/network topology layer, applications layer, social layer, -

Based on the experience of the participants and projects,
business models should be reviewed with the goal of reaching a downselection of models that should be implemented/supported
in the first iteration of the WISPiab project.

Classical examples:

* Voice services - The Village Telco
* "Line sharing" - sharing internet access between organizations
* Telecentre / Internet Cafe
* Campus / School network

'''The goal''' is to go through all our relevant models, to classify them on all layers,

and to identify the technology implications (such that technology follows business models, and not vice versa), producing a clear results list.

====Cooperations and Resources====

There is significant overlap between projects on the technology layer.
All projects are subscribing to free software models (GPL / CC, etc).

We are operating against a backdrop of

* challenged (human) resource situation
* brain drain / skills exodus
* wanting to build local (i.e. african? ... southern african? .... south african?) capacity

Cooperation between projects seems appropriate and possible.

'''The goal''' is to conclude this meeting with a clear picture of modes of cooperation.

====Advisory Group====

We wish to form an advisory group / peer group, including partly the invitees of this meeting, but not limited to these.

==Day 2 - Tuesday, June 3==

===Morning===

====Technical Requirements / Specifications - detail level====

Examples of concrete detail issues:

* Authentication - where and how
* Billing in mesh networks
* VoIP in mesh networks

'''The goal''' of this session is to fill the matrix of

''technology requirements x project/business model''

and then check this matrix against the various existing hardware/software platforms.

====Hardware platforms aspects====

A number of different hardware/software platforms are fulfilling subsets of our requirements.

The available platforms need to be discussed and evaluated, towards a decision on what to choose.

The platforms that our projects are currently working with are:

* Linksys WRT54, with firmwares OpenWRT, DD-WRT, Freifunk, CoovaAP, and similar
* Open-Mesh, Accton - with Open Mesh Firmware (new firmware anoounced for summer 2008, with: RO.B.IN, orangemesh, COOVA, etc)
* Inveneo platform
* Ubiquti NS, PS
* Meraka Bokkie routers
* pls add!

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Productification / Dissemination / Rollout strategies====

* Strategies for the productification of software packages
** Sourceforge platform plans (Steve?)
** Ubuntu / UCK (Sebastian, Mark, Elektra)
* Rollout capacity

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

==Day 3 - Wednesday, June 4==

===Morning===

==== Ndlovu Medical Center====

Status and Agenda of network at Ndlovu Medical Center

* How can the various projects benefit Ndlovu Medical Center?

====Status, gaps and planning of implementations====

* WISPiab status and work plan
* Dabba / Village Telco work sprint, June 16-20
** prepare and support that workshop

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Conclusions & Next steps====

* Dabba Worksprint
* WISPiab work plan
* Digital Doorway work
* Wireless Africa, June meeting

etc

= Notes from the meeting - Day 1=

==People & Project introductions==

* Introduction and WISPiab Project (Sebastian Buettrich)
* Peeble's Valley Mesh (David Johnson)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Inveneo platform (Mark Summer)
* Freifunk (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* WISPiab work status (George James)
* Two radio mesh router (Johann Hugo)
* Wireless Africa project (Chris Morris)

==Forming an Alliance?==

to be edited

= Notes from the meeting - Day 2=
[[Image:Day2 - WISPiab_Wkshop.jpg|left|thumb|350px|Day2 (L-R) Mark Summer, Johann Hugo, Mike Jensen, Elektra, Sebastian Buettrich, Kobus Roux, George James, Ajay Makan, Karel Matthee
]]

 

==Requirements, Specifications, Wishlist==

We chose the GUI [http://dabba.co.za/wispgui wishlist by Dabba] as an entry to discussing our current specifications set, identifying how we cover the single elements today, identifying dependencies, etc

[[Image:WISPiab meeting 20080603 whiteboard 1.jpg|thumb|left| Whiteboard Day 2]]
[[Image:Working_Logo.jpg|thumb|left|Table context]]

{| border="1" cellpadding="7" cellspacing="0"
!align="left" |What?
!align="left" |Which element
!align="left" |Existing
!align="left" |Who/how
!align="left" |Alternate names/terms
!align="left" |Task
|-
|Network Settings
|core
|FF, IHL, Coova (wifidog) + alternatives, Linksys & Netgear interfaces, webmin/ISPconfig
|
|Network Management, Setup,
|
|-
|ISP settings
|core
|Coova, phpMyPrepaid, OpenWRT (QoS script), master-/wondershaper, webmin/ISPconfig
|
|user/service profiles – provisioning (some of it -> QoS)
|
|-
|VoIP Settings Users, tarriffs
|voice
|AsteriskNow, IP04 HW, Trixbox, A2billing, (Open)SER
|
| -->user profiles, --> VoIP settings
|
|-
|Prepaid Card System (print cards) (ops), ->web, ->voice
|web,voice
|phpMyPrepaid / ISPBill, A2billing
|
|“usage”
|
|-
|CRM
|core
|[http://compiere.com compiere] - explore!
|
|
|
|-
|Accounting -->logs
|core
|phpMyPrepaid/ISPBill, a2billing
|
| ->(if bill) ->ERP
|
|-
|Logo/Company
|core, feeding into the various channels
|(all components have some of it)
|
|themes/skins/ customisation
|
|-
|Network Monitoring
|
|Nagios/Cacti, Open-Mesh, Open NMS, FF (some), MRTG/rrdtool
|core
|Network management
|
|-
|'''Items not contained in Dabba GUI'''
|
|
|
|
|
|-
|Content repository (SW, media, ...), Video Server
|(various, different contents for different channels)
|
|
|
|
|-
|Cache\Proxy with stats
|web
|squid with awstats
|
|
|
|-
|Mail
|core
|Postfix, Courier, webmail: squirrelmail
|
|
|
|-
|Security & encryption
|core
|OpenVPN, GnuPG
|
|
|
|-
|httpd, with stats etc
|web
|apache, awstats
|
|
|
|-
|Wiki / image hosting
|web
|mediawiki
|
|
|
|-
|Telecentre management
|(core)
|UgaBytes telecentre management software - explore!
|
|
|
|-
|}

==Business Models==

Discussion of business models that have informed the specifications, and a checkback whether we feel that the current specifications actually accomodate all these models.

The template on top suggests dimensions / criteria from which to look at the various models.

===Business Model Template===

* Description:

* Economics: Free or paid by ....
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications:
* Network / Topology:
* Internet uplink:
* User Devices / Locations:
* Startup Strategy:
* Legal & Regulatory

===Telecentre / Internet Cafe / Hotspot===

* Description: "Classical" telecentre / cafe style

* Economics: Free or paid by users / advertisers / cafe business
* Billing models: typically Prepaid (Time based):
* Applications: typically Browser / Mail / Office / Games
* Network / Topology: wired LAN
* Internet uplink: model works with and without uplink, but typically yes
* User Devices / Locations: Users on business owned PC
* Startup Strategy:
* Legal & Regulatory: ok in most (?) countries

===Telco===

* Description: Telco offering "fixed line" and mobile VoIP telephony

* Economics: Part free (?) (local) / paid by user
* Billing models: typically Prepaid (Time/Data based):
* Applications: VoIP telephony, typically on dedicated hardware
* Network / Topology: Centralized / Inframesh
* Internet uplink: Yes, if terminating external calls / local loop without
* User Devices / Locations: Users at home / office / mobile, Device VoIP handsets, ATA etc
* Startup Strategy:
* Legal & Regulatory: complex, country to country

===(Edu)Content / Media===

* Economics: Free or paid by user / external
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications: Browser, Video, Image, Sound apps
* Network / Topology: n/a
* Internet uplink: not neccessarily, but recommended
* User Devices / Locations: all kinds of devices, local/remote,
* Startup Strategy:
* Legal & Regulatory: apart from restrictions on content, no issues

===Intranet / Neighbour-Net===

* Economics: Typically paid by customer
* Billing models: Contract / "Subscription"
* Applications: All PC apps
* Network / Topology: typically centralized, might be mesh
* Internet uplink: not neccessarily, but recommended
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy:
* Legal & Regulatory: no issues

===Line Sharing===

* Economics: Typically paid by users, in split scheme (e.g. cost per user = (line cost / # of users)*(marginfactor))
* Billing models: Prepaid monthly
* Applications: All PC apps
* Network / Topology: centralized or mesh
* Internet uplink: yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy: bottom up, organic
* Legal & Regulatory: potential issues with DSL or line resell (?), power limits for wireless part

===ISP===

* Economics: Typically user paid
* Billing models: Prepaid monthly, subscription
* Applications: All apps
* Network / Topology: centralized or mesh
* Internet uplink: yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy:
* Legal & Regulatory: regulations for ISP ops, licensing etc

===Web Hosting / Design===

A potential part of an ISPs business.
Seen as outside scope of this project, however simple home pages / website very common and demanded.
E.g. local businesses, etc

===Corporate / Managed Services===

* Economics: Typically user paid
* Billing models: Prepaid monthly, subscription
* Applications: All apps
* Network / Topology: centralized or mesh
* Internet uplink: typically yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy: company initiative
* Legal & Regulatory: potential issues when mixed user groups share same network (e.g. private, corp, gov, etc)

Strong focus on security (all aspects), network separation, QoS, management.

===Guesthouse Net===

* Economics: Typically user (= guesthouse) paid, might be free for customer of guesthouse, or paid for
* Billing models: if paid for, typically voucher prepaid, time based
* Applications: All apps
* Network / Topology: typically centralized
* Internet uplink: yes
* User Devices / Locations: users devices, maybe one or several public access PC
* Startup Strategy: guesthouse initiative
* Legal & Regulatory: no issues

===Housing Complex===

similar to Intranet / Neighbournet

* Economics: Typically user paid, might be included in other service charges or rent
* Billing models: Prepaid monthly or longer term, subscription
* Applications: All apps
* Network / Topology: centralized or mesh, often wired
* Internet uplink: typically yes
* User Devices / Locations: PCs and other, local at homes
* Startup Strategy: owner initiative
* Legal & Regulatory: no issues

===Surveillance===

* Economics: Typically customer paid
* Billing models: Prepaid monthly, subscription
* Applications: Very specific, wireless surveillance cams, motion detectors, etc
* Network / Topology: centralized or mesh
* Internet uplink: typically yes, in order to allow for remote control and alerts
* User Devices / Locations: surveillance gear and control units, typically PC/browser/mobile (SMS notifications)
* Startup Strategy:
* Legal & Regulatory: generally no issues when limited to company/housing premises. issues when extending into public space. ethics.

===Freifunk style Mesh===

* Economics: Typically completely user paid, informal, but might implement business scheme similar to line sharing ((e.g. cost per user = (central uplink cost / # of users)*(marginfactor))
* Billing models: e.g. Prepaid monthly
* Applications: All incl telephony
* Network / Topology: full mesh / inframesh
* Internet uplink: typically yes, but local net relevant
* User Devices / Locations: all types of devices, at user homes / office / businesses, roaming users
* Startup Strategy:
* Legal & Regulatory: potential issues withpower limits, collision with other networks, DSL reuse / resell

===Training / Consultancy===

A side business, outside scope for this project, but clearly relevant.

= Notes from the meeting - Day 3=

==Ndlovu Medical Centre==

Henry introduces:

* Status of mesh: operational, but currently disconnected (concerns about lightning)
* Use of uplink: Browsing (for community users), sync with data center (Johannesburg)
* Status of uplink: promised by Telkom, but not delivered yet

How to get started with a community mesh?

* Donated PCs - 25 pcs
** Give to local entrepreneur types
* Computer school as entry point

* Create a starter kit
** for existing PCs (there is some! mostly free windows)
** preconfigured
** low cost
** probably of the type: Linksys WRT, open-mesh/accton

Financing model

* Some contribution from user: Prepaid - low cost

What is interesting for people?

* music!!! open music server locally?
* free books? educational material
* free local calls
* a free wikipedia / digital doorway

Income from other sources (not the users):

* advertisements

To do / upcoming:

* '''call for a brainstorm meeting within the community'''

* June 9, meeting with provincial directory

* June 24: excursion to Ndlovu? participants of Wireless Africa meeting, Meraka people, Tom, Elektra

Top pain points / whats in the way:

* political level - get OKs from important players

==Hardware reference platform==

===Overall Requirements===

* 12 Volts (best: 11 ... 16)
* low power
* fanless

===Backend server===

* USB 2x
* ethernet 2x
* VGA

Candidate for reference choice:

* bigger solution: VIA, jetway 1.2 GHz, 2x HD, 1 GB RAM, USD 680 ... 820 [http://mini-box.com e.g. mini-box-com]
** power: approx 25W ?
* smaller solution: VIA, AMD Geode 500 MHz
** power: 8 W
* LEX light/neo, e.g. 1 GB C7 approx USD 600 [http://www.lex.com.tw/ http://www.lex.com.tw/]
* soon to come: Atom based low cost desktops (Mark Summer)
* alternatives: [http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99 http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99]

====Software on backend====

Decision: Ubuntu (non X)

----

===Access node===

* ethernet 2x
* PoE
* outdoor casing
* broadcom or atheros chipset
* 5 ... 18 Volts
* Watchdog (option)
* WISPCAR (option)
* serial port

Candidates:

* Linksys WRT54GL
** price: EUR 50, ZAR 600, USD 60
** power: 4 W
** comments:

* Ubiqiti
** price: NS 2: USD 79
** price: PS 2: USD 110
** power: 5 W

* Accton
** price: USD 40
** power: 2-3 W ?
** comments: overheat problems? needs fixed power 5 V? quality of radio? unstable across channels?

* PCEngines board
** price: > USD 250
** power: approx > 8W, depending on radio cards
** comments:

* Soekris

* Gateworks
**
**

* Wiligear

===Solar powering: A word on the fine for every watt installed===

Elektra makes the conservative estimate:

To power a 5 Watt device reliably, install a 80 Watt solar panel.
This means: 16 Watt solar panel per 1 Watt installed.

At about USD 5 per solar panel watt (current rough guess for market price), we have:

USD 80 in solar panel per 1 Watt installed.

Even when demanding less margin from the solar power system (i.e. less reliability, more optimism), the fine for every Watt installed is heavy.

==Next steps==

* Cape Town Village Telco worksprint
* Kobus, Johann, Elektra
** We need a presentation - Sebastian sends to Kobus and all - dead: june 10
*** Metaphores: pipes - water / roads - cars /
** Minutes / Doc

* Software development
** Meraka - Priority: the set of Coova (alternative: WifiDog) / FreeRadius / phpMyPrepaid (alternative: ISPBill) / Nagios
** Inveneo - Priority: IHL, Server squid/cache, proxy, asterisk, Webmin/ISPConfig
** How to work together? SVN server ? location ? Meraka machines accessible form outside?

* Examine the Ubiquiti - Lead: Elektra
** flash OpenWRT [http://wiki.openwrt.org/OpenWrtDocs/Hardware/Ubiquiti OpenWrt Ubiquiti]
** Examine the SDK
** examine internal antenna pol switching (AAP)

* Procurement - Lead: Ajay
** 12 x Inveneo small server, IONs, June 16
** 2 x Inveneo, Hub servers, June 16
** Ubiquiti Nano/Powerstation: one PS2 in place - OK for now
** Linksyses: we have enough, OK
** Boards: we have the Gateworks, OK
** Solar power: one demo system until June 23 - ask Grant: 64 W panel, charge controller, batteries - Lead: Sebastian

* Examine the [http://wiki.inveneo.org/index.php/Inveneo_Server_Linux_1.x Inveneo Hub Linux (IHL)] - Elektra / George

* Examine Open-Mesh - Lead: Sebastian
** examine status and development
** specifically: the Coova/Robin merger?

* Establish Documentation on Wiki

WISPiab work meeting 200806

2008-06-11T05:48:50Z

Sebastian:

[[Category: WISP in a box]]

=Work meeting of the WISP-in-a-box project=

[[The WISP-in-a-box project]]

=Date=

June 2-3-4, 2008

9-17 h

=Location=

Meraka Institute,
Building 43 C,
Hummingbird Room (C128, ground floor)

Pretoria

=Invitation List=

People and organisations with an active interest in building a concrete product that
helps bringing

connectivity to underserviced, underprivileged and overcharged communities in Africa.

Invitation list:

* Steve Song / Shuttleworth Foundation (monday only)
* Rael Lissoos / Dabba
* Henry Marnitz / Ndlovu Medical Centre (wednesday only)
* Mark Summer, Inveneo (with request to forward to Ubiquiti)
* Elektra
* Mike Jensen (not confirmed)
* Kobus Roux, Meraka (NOT monday)
* Karel Matthee, Meraka
* Kim Gush, Meraka
* David Johnson, Meraka
* Chris Morris, Meraka
* Grant Cambridge, Meraka
* Shela Boshomane, Meraka (monday and wednesday)
* George James, Meraka
* Johann Hugo, Meraka
* John Hay, Meraka
* Ajay Makan, Meraka
* Sebastian Buettrich

More proposals are welcome!

Budgets for travel, if needed: Please contact us!

=Contact=

Sebastian

mail: sebastian@less.dk

skype: sebastian_buettrich

cell: (+27) (0) 79 915 32 92

=Timeplan=

The timeplan is draft level and will be adjusted to people's ability to join for limited periods.

'''The first day''' will be dedicated to the '''organizational layer''',

introducing the various projects and teams,
discussing the business models,
identifying overlap of work agendas as well as the main challenges each of the projects are seeing.

'''The second day''' will move down to detail level,
moving from business and organizational models to technology requirements/specifications.

The third day

==Day 1 - Monday, June 2==

===Morning===

====Creating Context====

Introductions, Presentations of participants

(Short 10 mns, informal project introductions)

* Introduction and WISPiab Project (Sebastian Buettrich)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Ndlovu Medical Centre (Henry Marnitz) (moved to Wednesday, June 4)
* Peeble's Valley Mesh (David Johnson)
* Digital Doorway (tba)
* Inveneo platform (Mark Summer)
* WISPiab work status (George James)
* Wireless Africa project (Chris Morris)
* Freifunk, B.a.t.m.a.n. & Meraka Mesh Testbed (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* IP04 (it46, rowetel) (on behalf of the project: Sebastian Buettrich)

===Afternoon===

====Business models====

Introduction: Sebastian

Business models may be classified according to a number of different dimensions -

e.g. financial/economic layer, tech/network topology layer, applications layer, social layer, -

Based on the experience of the participants and projects,
business models should be reviewed with the goal of reaching a downselection of models that should be implemented/supported
in the first iteration of the WISPiab project.

Classical examples:

* Voice services - The Village Telco
* "Line sharing" - sharing internet access between organizations
* Telecentre / Internet Cafe
* Campus / School network

'''The goal''' is to go through all our relevant models, to classify them on all layers,

and to identify the technology implications (such that technology follows business models, and not vice versa), producing a clear results list.

====Cooperations and Resources====

There is significant overlap between projects on the technology layer.
All projects are subscribing to free software models (GPL / CC, etc).

We are operating against a backdrop of

* challenged (human) resource situation
* brain drain / skills exodus
* wanting to build local (i.e. african? ... southern african? .... south african?) capacity

Cooperation between projects seems appropriate and possible.

'''The goal''' is to conclude this meeting with a clear picture of modes of cooperation.

====Advisory Group====

We wish to form an advisory group / peer group, including partly the invitees of this meeting, but not limited to these.

==Day 2 - Tuesday, June 3==

===Morning===

====Technical Requirements / Specifications - detail level====

Examples of concrete detail issues:

* Authentication - where and how
* Billing in mesh networks
* VoIP in mesh networks

'''The goal''' of this session is to fill the matrix of

''technology requirements x project/business model''

and then check this matrix against the various existing hardware/software platforms.

====Hardware platforms aspects====

A number of different hardware/software platforms are fulfilling subsets of our requirements.

The available platforms need to be discussed and evaluated, towards a decision on what to choose.

The platforms that our projects are currently working with are:

* Linksys WRT54, with firmwares OpenWRT, DD-WRT, Freifunk, CoovaAP, and similar
* Open-Mesh, Accton - with Open Mesh Firmware (new firmware anoounced for summer 2008, with: RO.B.IN, orangemesh, COOVA, etc)
* Inveneo platform
* Ubiquti NS, PS
* Meraka Bokkie routers
* pls add!

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Productification / Dissemination / Rollout strategies====

* Strategies for the productification of software packages
** Sourceforge platform plans (Steve?)
** Ubuntu / UCK (Sebastian, Mark, Elektra)
* Rollout capacity

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

==Day 3 - Wednesday, June 4==

===Morning===

==== Ndlovu Medical Center====

Status and Agenda of network at Ndlovu Medical Center

* How can the various projects benefit Ndlovu Medical Center?

====Status, gaps and planning of implementations====

* WISPiab status and work plan
* Dabba / Village Telco work sprint, June 16-20
** prepare and support that workshop

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Conclusions & Next steps====

* Dabba Worksprint
* WISPiab work plan
* Digital Doorway work
* Wireless Africa, June meeting

etc

= Notes from the meeting - Day 1=

==People & Project introductions==

* Introduction and WISPiab Project (Sebastian Buettrich)
* Peeble's Valley Mesh (David Johnson)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Inveneo platform (Mark Summer)
* Freifunk (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* WISPiab work status (George James)
* Two radio mesh router (Johann Hugo)
* Wireless Africa project (Chris Morris)

==Forming an Alliance?==

to be edited

= Notes from the meeting - Day 2=
[[Image:Day2 - WISPiab_Wkshop.jpg|left|thumb|350px|Day2 (L-R) Mark Summer, Johann Hugo, Mike Jensen, Elektra, Sebastian Buettrich, Kobus Roux, George James, Ajay Makan, Karel Matthee
]]

 

==Requirements, Specifications, Wishlist==

We chose the GUI [http://dabba.co.za/wispgui wishlist by Dabba] as an entry to discussing our current specifications set, identifying how we cover the single elements today, identifying dependencies, etc

[[Image:WISPiab meeting 20080603 whiteboard 1.jpg|thumb|left| Whiteboard Day 2]]
[[Image:Working_Logo.jpg|thumb|left|Table context]]

{| border="1" cellpadding="7" cellspacing="0"
!align="left" |What?
!align="left" |Which element
!align="left" |Existing
!align="left" |Who/how
!align="left" |Alternate names/terms
!align="left" |Task
|-
|Network Settings
|core
|FF, IHL, Coova (wifidog) + alternatives, Linksys & Netgear interfaces, webmin/ISPconfig
|
|Network Management, Setup,
|
|-
|ISP settings
|core
|Coova, phpMyPrepaid, OpenWRT (QoS script), master-/wondershaper, webmin/ISPconfig
|
|user/service profiles – provisioning (some of it -> QoS)
|
|-
|VoIP Settings Users, tarriffs
|voice
|AsteriskNow, IP04 HW, Trixbox, A2billing, (Open)SER
|
| -->user profiles, --> VoIP settings
|
|-
|Prepaid Card System (print cards) (ops), ->web, ->voice
|web,voice
|phpMyPrepaid / ISPBill, A2billing
|
|“usage”
|
|-
|CRM
|core
|[http://compiere.com compiere] - explore!
|
|
|
|-
|Accounting -->logs
|core
|phpMyPrepaid/ISPBill, a2billing
|
| ->(if bill) ->ERP
|
|-
|Logo/Company
|core
|(all components have some of it)
|
|themes/skins/ customisation
|
|-
|Network Monitoring
|
|Nagios/Cacti, Open-Mesh, Open NMS, FF (some), MRTG/rrdtool
|
|Network management
|
|-
|'''Items not contained in Dabba GUI'''
|
|
|
|
|
|-
|Content repository (SW, media, ...), Video Server
|
|
|
|
|
|-
|Cache\Proxy with stats
|
|squid with awstats
|
|
|
|-
|Mail
|
|Postfix, Courier, webmail: squirrelmail
|
|
|
|-
|Security & encryption
|
|OpenVPN, GnuPG
|
|
|
|-
|httpd, with stats etc
|
|apache, awstats
|
|
|
|-
|Wiki / image hosting
|
|mediawiki
|
|
|
|-
|Telecentre management
|
|UgaBytes telecentre management software - explore!
|
|
|
|-
|}

==Business Models==

Discussion of business models that have informed the specifications, and a checkback whether we feel that the current specifications actually accomodate all these models.

The template on top suggests dimensions / criteria from which to look at the various models.

===Business Model Template===

* Description:

* Economics: Free or paid by ....
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications:
* Network / Topology:
* Internet uplink:
* User Devices / Locations:
* Startup Strategy:
* Legal & Regulatory

===Telecentre / Internet Cafe / Hotspot===

* Description: "Classical" telecentre / cafe style

* Economics: Free or paid by users / advertisers / cafe business
* Billing models: typically Prepaid (Time based):
* Applications: typically Browser / Mail / Office / Games
* Network / Topology: wired LAN
* Internet uplink: model works with and without uplink, but typically yes
* User Devices / Locations: Users on business owned PC
* Startup Strategy:
* Legal & Regulatory: ok in most (?) countries

===Telco===

* Description: Telco offering "fixed line" and mobile VoIP telephony

* Economics: Part free (?) (local) / paid by user
* Billing models: typically Prepaid (Time/Data based):
* Applications: VoIP telephony, typically on dedicated hardware
* Network / Topology: Centralized / Inframesh
* Internet uplink: Yes, if terminating external calls / local loop without
* User Devices / Locations: Users at home / office / mobile, Device VoIP handsets, ATA etc
* Startup Strategy:
* Legal & Regulatory: complex, country to country

===(Edu)Content / Media===

* Economics: Free or paid by user / external
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications: Browser, Video, Image, Sound apps
* Network / Topology: n/a
* Internet uplink: not neccessarily, but recommended
* User Devices / Locations: all kinds of devices, local/remote,
* Startup Strategy:
* Legal & Regulatory: apart from restrictions on content, no issues

===Intranet / Neighbour-Net===

* Economics: Typically paid by customer
* Billing models: Contract / "Subscription"
* Applications: All PC apps
* Network / Topology: typically centralized, might be mesh
* Internet uplink: not neccessarily, but recommended
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy:
* Legal & Regulatory: no issues

===Line Sharing===

* Economics: Typically paid by users, in split scheme (e.g. cost per user = (line cost / # of users)*(marginfactor))
* Billing models: Prepaid monthly
* Applications: All PC apps
* Network / Topology: centralized or mesh
* Internet uplink: yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy: bottom up, organic
* Legal & Regulatory: potential issues with DSL or line resell (?), power limits for wireless part

===ISP===

* Economics: Typically user paid
* Billing models: Prepaid monthly, subscription
* Applications: All apps
* Network / Topology: centralized or mesh
* Internet uplink: yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy:
* Legal & Regulatory: regulations for ISP ops, licensing etc

===Web Hosting / Design===

A potential part of an ISPs business.
Seen as outside scope of this project, however simple home pages / website very common and demanded.
E.g. local businesses, etc

===Corporate / Managed Services===

* Economics: Typically user paid
* Billing models: Prepaid monthly, subscription
* Applications: All apps
* Network / Topology: centralized or mesh
* Internet uplink: typically yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy: company initiative
* Legal & Regulatory: potential issues when mixed user groups share same network (e.g. private, corp, gov, etc)

Strong focus on security (all aspects), network separation, QoS, management.

===Guesthouse Net===

* Economics: Typically user (= guesthouse) paid, might be free for customer of guesthouse, or paid for
* Billing models: if paid for, typically voucher prepaid, time based
* Applications: All apps
* Network / Topology: typically centralized
* Internet uplink: yes
* User Devices / Locations: users devices, maybe one or several public access PC
* Startup Strategy: guesthouse initiative
* Legal & Regulatory: no issues

===Housing Complex===

similar to Intranet / Neighbournet

* Economics: Typically user paid, might be included in other service charges or rent
* Billing models: Prepaid monthly or longer term, subscription
* Applications: All apps
* Network / Topology: centralized or mesh, often wired
* Internet uplink: typically yes
* User Devices / Locations: PCs and other, local at homes
* Startup Strategy: owner initiative
* Legal & Regulatory: no issues

===Surveillance===

* Economics: Typically customer paid
* Billing models: Prepaid monthly, subscription
* Applications: Very specific, wireless surveillance cams, motion detectors, etc
* Network / Topology: centralized or mesh
* Internet uplink: typically yes, in order to allow for remote control and alerts
* User Devices / Locations: surveillance gear and control units, typically PC/browser/mobile (SMS notifications)
* Startup Strategy:
* Legal & Regulatory: generally no issues when limited to company/housing premises. issues when extending into public space. ethics.

===Freifunk style Mesh===

* Economics: Typically completely user paid, informal, but might implement business scheme similar to line sharing ((e.g. cost per user = (central uplink cost / # of users)*(marginfactor))
* Billing models: e.g. Prepaid monthly
* Applications: All incl telephony
* Network / Topology: full mesh / inframesh
* Internet uplink: typically yes, but local net relevant
* User Devices / Locations: all types of devices, at user homes / office / businesses, roaming users
* Startup Strategy:
* Legal & Regulatory: potential issues withpower limits, collision with other networks, DSL reuse / resell

===Training / Consultancy===

A side business, outside scope for this project, but clearly relevant.

= Notes from the meeting - Day 3=

==Ndlovu Medical Centre==

Henry introduces:

* Status of mesh: operational, but currently disconnected (concerns about lightning)
* Use of uplink: Browsing (for community users), sync with data center (Johannesburg)
* Status of uplink: promised by Telkom, but not delivered yet

How to get started with a community mesh?

* Donated PCs - 25 pcs
** Give to local entrepreneur types
* Computer school as entry point

* Create a starter kit
** for existing PCs (there is some! mostly free windows)
** preconfigured
** low cost
** probably of the type: Linksys WRT, open-mesh/accton

Financing model

* Some contribution from user: Prepaid - low cost

What is interesting for people?

* music!!! open music server locally?
* free books? educational material
* free local calls
* a free wikipedia / digital doorway

Income from other sources (not the users):

* advertisements

To do / upcoming:

* '''call for a brainstorm meeting within the community'''

* June 9, meeting with provincial directory

* June 24: excursion to Ndlovu? participants of Wireless Africa meeting, Meraka people, Tom, Elektra

Top pain points / whats in the way:

* political level - get OKs from important players

==Hardware reference platform==

===Overall Requirements===

* 12 Volts (best: 11 ... 16)
* low power
* fanless

===Backend server===

* USB 2x
* ethernet 2x
* VGA

Candidate for reference choice:

* bigger solution: VIA, jetway 1.2 GHz, 2x HD, 1 GB RAM, USD 680 ... 820 [http://mini-box.com e.g. mini-box-com]
** power: approx 25W ?
* smaller solution: VIA, AMD Geode 500 MHz
** power: 8 W
* LEX light/neo, e.g. 1 GB C7 approx USD 600 [http://www.lex.com.tw/ http://www.lex.com.tw/]
* soon to come: Atom based low cost desktops (Mark Summer)
* alternatives: [http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99 http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99]

====Software on backend====

Decision: Ubuntu (non X)

----

===Access node===

* ethernet 2x
* PoE
* outdoor casing
* broadcom or atheros chipset
* 5 ... 18 Volts
* Watchdog (option)
* WISPCAR (option)
* serial port

Candidates:

* Linksys WRT54GL
** price: EUR 50, ZAR 600, USD 60
** power: 4 W
** comments:

* Ubiqiti
** price: NS 2: USD 79
** price: PS 2: USD 110
** power: 5 W

* Accton
** price: USD 40
** power: 2-3 W ?
** comments: overheat problems? needs fixed power 5 V? quality of radio? unstable across channels?

* PCEngines board
** price: > USD 250
** power: approx > 8W, depending on radio cards
** comments:

* Soekris

* Gateworks
**
**

* Wiligear

===Solar powering: A word on the fine for every watt installed===

Elektra makes the conservative estimate:

To power a 5 Watt device reliably, install a 80 Watt solar panel.
This means: 16 Watt solar panel per 1 Watt installed.

At about USD 5 per solar panel watt (current rough guess for market price), we have:

USD 80 in solar panel per 1 Watt installed.

Even when demanding less margin from the solar power system (i.e. less reliability, more optimism), the fine for every Watt installed is heavy.

==Next steps==

* Cape Town Village Telco worksprint
* Kobus, Johann, Elektra
** We need a presentation - Sebastian sends to Kobus and all - dead: june 10
*** Metaphores: pipes - water / roads - cars /
** Minutes / Doc

* Software development
** Meraka - Priority: the set of Coova (alternative: WifiDog) / FreeRadius / phpMyPrepaid (alternative: ISPBill) / Nagios
** Inveneo - Priority: IHL, Server squid/cache, proxy, asterisk, Webmin/ISPConfig
** How to work together? SVN server ? location ? Meraka machines accessible form outside?

* Examine the Ubiquiti - Lead: Elektra
** flash OpenWRT [http://wiki.openwrt.org/OpenWrtDocs/Hardware/Ubiquiti OpenWrt Ubiquiti]
** Examine the SDK
** examine internal antenna pol switching (AAP)

* Procurement - Lead: Ajay
** 12 x Inveneo small server, IONs, June 16
** 2 x Inveneo, Hub servers, June 16
** Ubiquiti Nano/Powerstation: one PS2 in place - OK for now
** Linksyses: we have enough, OK
** Boards: we have the Gateworks, OK
** Solar power: one demo system until June 23 - ask Grant: 64 W panel, charge controller, batteries - Lead: Sebastian

* Examine the [http://wiki.inveneo.org/index.php/Inveneo_Server_Linux_1.x Inveneo Hub Linux (IHL)] - Elektra / George

* Examine Open-Mesh - Lead: Sebastian
** examine status and development
** specifically: the Coova/Robin merger?

* Establish Documentation on Wiki

WISPiab specifications

2008-06-11T05:39:39Z

Sebastian: /* Storage, FS */

[[Category: WISP in a box]]

=Introduction=

The following is our work copy of a specification / feature wish list for the WISP-in-a-box product.

It is meant to be commented and refined.

=Business models=

Discussion of business models: [[WISPiab_business_models]]

=High level architecture=

Our currently suggested architecture splits the WISPiab hardware package into two components plus an option:

#Front Access Node
##
# Back end server (with or without screen, depending on existing ...)
##
#(Sub)Laptop as GUI admin (optional)

This seems appropriate based on the analysis of the SW specs in detail.

However, if test implementations seem to suggest reuniting the two tiers on one box, this is an open option, which might bring manageability benefits.

[[Image:WISPiab elements horizontal with net small.png|thumb|left]]

=Software Specification / Feature list for the WISP-in-a-box product=

==Shared functionality==

* All configuration etc to be accessible via browser based GUI
* ssh access

* Routing Protocols
** OLSR
** b.a.t.m.a.n.

==Front access node==

* CoovaAP
** Authentication potentially with 2 options
*** Against itself / on acces node
*** Against back end server Radius

CoovaAP will bring most of the following mandatory features for the front access node.

* OpenSER

==Back end server==

* apache
* php
* mediawiki
* mysql

* ispconfig
** webmin?

* DNS server (DDNS, DynDNS)

* Proxy / Cache
** Squid

===Mail===

* Postfix / Courier
* Webmail: squirrelmail
* gmail syncing desirable
* Google server local? (--> talk to gmail, Kobus)

* Spam/Virus control
** amavis
** spamassassin

===Network management===

* Nagios
* Cacti

* Statistics
** awstats or similar

===Auth, Access, Security, Billing===

* Radius
**FreeRadius
* OpenLDAP
* OpenID

* OpenVPN
* GnuPG

===QoS===

* QoS - details of this not clear yet - what layer? what tools?
** iproute2
** MasterShaper?
** Wondershaper

===Storage, FS===

* NAS – iSCSI

* File servers
** SMB
** NFS
** rsyncing cron'd

* Redundancy - to be specified in more detail
** Would like to build distributed storage - “graded distributed system”

===Voice over IP===

* Asterisk
* OpenSER
* billing integration
** a2billing

===Miscellaneous===

* Local Library of SW
** Documentation
** Integrated Skilling / Education
* patch management
* IpCOP
* wikipedia local copy

* Content filtering ? - discussion!

* Virtualization (XenSource)
** to be discussed - not deemed mandatory

=Hardware Specification / Feature list for the WISP-in-a-box product=

To be spec'ed after completion of SW specs.

==Minimum requirements==

===General requirements for all elements===

* Input: 12 V_dc
* Fanless
* Low power (< 8 W)

===Front access node===

Network interfaces
2 minimum, maybe more

===Back end server===
external switch

==Hardware candidates==

{| rules="rows" frame="hsides" align="left" width="100%" cellpadding=10
|- align="left" valign="top"
!'''Table 1''': Table title
|- bgcolor="lightgrey" align="left" valign="top"
! Name !! candidate for !! CPU Memory Storage !! Power !! Wireless !! Cost !! Comments

|- align="left" valign="top"
| ASUS EEE PC || server? ||
ASUS® EEE PC 700-W - Intel® 900Mhz Pentium®M ULV, 512MB DDR2 Memory, Internal 2GB SSD Based Hard Drive, Intel® 910GML Chipset, 7" 800x480 LCD, 10/100 LAN, WiFi b/g, SD Card Slot, 3xUSB 2.0 / ASUS EEE PC 4g with 4 GB SSD / ASUS EEE 900 with 1 GB RAM, 12 GB SSD
|| power: ? ||- || ? || comments

|- align="left" valign="top"
| dataevolution.com decTOP etc || server? ||
Memory
128MB SDRAM
10GB HDD
|| power: ? ||- || ? || comments

|- align="left" valign="top"
| FON(ERA) || access node ||
CPU: MIPS 180 MHz
Memory: 16 MB ram
|| power || wireless || EUR 40 || comments

|- align="left" valign="top"
| Inveneo Outdoor WiFi Access Point|| access node, server (?) || ??? ask Inveneo || power || 802.11 b/g
Athenos chipset
Peak power: +24dBm (250mW) || Single Radio: $469 USD* Dual Radio: $659 USD* || incl antennas, install kits, outdoor ready

|- align="left" valign="top"
| Inveneo Hub server|| server ||
1.2GHz VIA C7 nanoBGA2 Fanless
VIA CN700 North Bridge
VIA VT8237RP High-bandwidth Vlink Client South Bridge
51MB standard, 1GB optional
One RS-232C serial port (DB-9)
Four USB 2.0 ports (two in front, two in back)
|| < 20 W || -|| Price: starting at $$785 USD* || incl many things, see site :)

|- align="left" valign="top"
| Linksys WRT54G(L) || access node ||
System-On-Chip: Broadcom 5352EKPB

CPU Speed:200 Mhz

Flash size: 4 MiB

RAM: 16 MiB

Wireless: Broadcom BCM43xx 802.11b/g Wireless LAN (integrated) || < 5 W (3.8 if optimized) || wireless || USD 45 || comments

|- align="left" valign="top"
| Accton / Open-Mesh || access node ||
(Atheros AR2315 chipset, 32MB DRAM, 8MB Flash, 1 ethernet port) = Meraki
|| power: ?, 5 V || wireless_ 60 dBm max || USD 45 || comments

|- align="left" valign="top"
| Meraki outdoor || access node ||
Bootloader: RedBoot
CPU: Atheros AR2315
CPU Speed: 180 Mhz
Flash size: 8 MB
RAM: 32 MB
|| Power consumption: 12W max; 3W typical ||
* 200 mW (23dBm) peak transmission power*
* Enhanced receive sensitivity
* External RP-SMA connector
* 802.11 b/g (1-54 Mbps)
* 2dBi omni directional antenna included
|| USD 49/99 || note EULA issues!

http://www.mini-itx.com/

|- align="left" valign="top"
| Mini-ITX / VIA / LEX / Jetway etc || access node, server || varies || power || wireless || cost || see [http://www.mini-itx.com/ http://www.mini-itx.com/] [http://www.via.com.tw/en/products/mainboards/ http://www.via.com.tw/en/products/mainboards/]

|- align="left" valign="top"
| Soekris boards || access node, server (?) || cpu memory storage etc || power || wireless || cost || comments

|- align="left" valign="top"
| Ultra Mobile PCs / sub laptops || becoming a valid candidate as ''Backend/server'' component? ||
many candidates with differing specs, need to check out and test:

* OLPC
* eMate 300
* Classmate PC
* Linutop, Geode LX -based computer
* Longmeng or Dragon Dream, China
* Tianhua GX-1C, Sinomanic in China
* VIA pc-1 Initiative, VIA Technologies digital divide program.
* Zonbu, a low-cost desktop computer
* Eee PC, ASUS and Intel - watch!
* Clio NXT.
* InkMedia MC, another low-cost subnotebook
* Elonex_ONE, subnotebook, expected to be £99

|| ??? - typically low, 3 Watts for OLPC-X01 || typically built in

||

EUR 250 - 400

* OLPC
* eMate 300
* Classmate PC
* Linutop, Geode LX -based computer EUR 280
* Longmeng or Dragon Dream, China
* Tianhua GX-1C, Sinomanic in China
* VIA pc-1 Initiative, VIA Technologies digital divide program.
* Zonbu, a low-cost desktop computer
* Eee PC, model900 = EUR 400, model 4g = EUR 300
* Acer, Q2 2008, approx EUR 250 ?
* Clio NXT.
* InkMedia MC, another low-cost subnotebook
* Elonex_ONE, subnotebook, expected to be £99

|| needs testing and verification as candidates

|- align="left" valign="top"
| WRAP boards || access node, server (?) || cpu memory storage etc || power || wireless || cost || comments

|}

----

==Solar part==

Solar Kit to be spe'ed after HW power is known

WISPiab work meeting 200806

2008-06-11T05:37:03Z

Sebastian:

[[Category: WISP in a box]]

=Work meeting of the WISP-in-a-box project=

[[The WISP-in-a-box project]]

=Date=

June 2-3-4, 2008

9-17 h

=Location=

Meraka Institute,
Building 43 C,
Hummingbird Room (C128, ground floor)

Pretoria

=Invitation List=

People and organisations with an active interest in building a concrete product that
helps bringing

connectivity to underserviced, underprivileged and overcharged communities in Africa.

Invitation list:

* Steve Song / Shuttleworth Foundation (monday only)
* Rael Lissoos / Dabba
* Henry Marnitz / Ndlovu Medical Centre (wednesday only)
* Mark Summer, Inveneo (with request to forward to Ubiquiti)
* Elektra
* Mike Jensen (not confirmed)
* Kobus Roux, Meraka (NOT monday)
* Karel Matthee, Meraka
* Kim Gush, Meraka
* David Johnson, Meraka
* Chris Morris, Meraka
* Grant Cambridge, Meraka
* Shela Boshomane, Meraka (monday and wednesday)
* George James, Meraka
* Johann Hugo, Meraka
* John Hay, Meraka
* Ajay Makan, Meraka
* Sebastian Buettrich

More proposals are welcome!

Budgets for travel, if needed: Please contact us!

=Contact=

Sebastian

mail: sebastian@less.dk

skype: sebastian_buettrich

cell: (+27) (0) 79 915 32 92

=Timeplan=

The timeplan is draft level and will be adjusted to people's ability to join for limited periods.

'''The first day''' will be dedicated to the '''organizational layer''',

introducing the various projects and teams,
discussing the business models,
identifying overlap of work agendas as well as the main challenges each of the projects are seeing.

'''The second day''' will move down to detail level,
moving from business and organizational models to technology requirements/specifications.

The third day

==Day 1 - Monday, June 2==

===Morning===

====Creating Context====

Introductions, Presentations of participants

(Short 10 mns, informal project introductions)

* Introduction and WISPiab Project (Sebastian Buettrich)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Ndlovu Medical Centre (Henry Marnitz) (moved to Wednesday, June 4)
* Peeble's Valley Mesh (David Johnson)
* Digital Doorway (tba)
* Inveneo platform (Mark Summer)
* WISPiab work status (George James)
* Wireless Africa project (Chris Morris)
* Freifunk, B.a.t.m.a.n. & Meraka Mesh Testbed (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* IP04 (it46, rowetel) (on behalf of the project: Sebastian Buettrich)

===Afternoon===

====Business models====

Introduction: Sebastian

Business models may be classified according to a number of different dimensions -

e.g. financial/economic layer, tech/network topology layer, applications layer, social layer, -

Based on the experience of the participants and projects,
business models should be reviewed with the goal of reaching a downselection of models that should be implemented/supported
in the first iteration of the WISPiab project.

Classical examples:

* Voice services - The Village Telco
* "Line sharing" - sharing internet access between organizations
* Telecentre / Internet Cafe
* Campus / School network

'''The goal''' is to go through all our relevant models, to classify them on all layers,

and to identify the technology implications (such that technology follows business models, and not vice versa), producing a clear results list.

====Cooperations and Resources====

There is significant overlap between projects on the technology layer.
All projects are subscribing to free software models (GPL / CC, etc).

We are operating against a backdrop of

* challenged (human) resource situation
* brain drain / skills exodus
* wanting to build local (i.e. african? ... southern african? .... south african?) capacity

Cooperation between projects seems appropriate and possible.

'''The goal''' is to conclude this meeting with a clear picture of modes of cooperation.

====Advisory Group====

We wish to form an advisory group / peer group, including partly the invitees of this meeting, but not limited to these.

==Day 2 - Tuesday, June 3==

===Morning===

====Technical Requirements / Specifications - detail level====

Examples of concrete detail issues:

* Authentication - where and how
* Billing in mesh networks
* VoIP in mesh networks

'''The goal''' of this session is to fill the matrix of

''technology requirements x project/business model''

and then check this matrix against the various existing hardware/software platforms.

====Hardware platforms aspects====

A number of different hardware/software platforms are fulfilling subsets of our requirements.

The available platforms need to be discussed and evaluated, towards a decision on what to choose.

The platforms that our projects are currently working with are:

* Linksys WRT54, with firmwares OpenWRT, DD-WRT, Freifunk, CoovaAP, and similar
* Open-Mesh, Accton - with Open Mesh Firmware (new firmware anoounced for summer 2008, with: RO.B.IN, orangemesh, COOVA, etc)
* Inveneo platform
* Ubiquti NS, PS
* Meraka Bokkie routers
* pls add!

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Productification / Dissemination / Rollout strategies====

* Strategies for the productification of software packages
** Sourceforge platform plans (Steve?)
** Ubuntu / UCK (Sebastian, Mark, Elektra)
* Rollout capacity

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

==Day 3 - Wednesday, June 4==

===Morning===

==== Ndlovu Medical Center====

Status and Agenda of network at Ndlovu Medical Center

* How can the various projects benefit Ndlovu Medical Center?

====Status, gaps and planning of implementations====

* WISPiab status and work plan
* Dabba / Village Telco work sprint, June 16-20
** prepare and support that workshop

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Conclusions & Next steps====

* Dabba Worksprint
* WISPiab work plan
* Digital Doorway work
* Wireless Africa, June meeting

etc

= Notes from the meeting - Day 1=

==People & Project introductions==

* Introduction and WISPiab Project (Sebastian Buettrich)
* Peeble's Valley Mesh (David Johnson)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Inveneo platform (Mark Summer)
* Freifunk (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* WISPiab work status (George James)
* Two radio mesh router (Johann Hugo)
* Wireless Africa project (Chris Morris)

==Forming an Alliance?==

to be edited

= Notes from the meeting - Day 2=
[[Image:Day2 - WISPiab_Wkshop.jpg|left|thumb|350px|Day2 (L-R) Mark Summer, Johann Hugo, Mike Jensen, Elektra, Sebastian Buettrich, Kobus Roux, George James, Ajay Makan, Karel Matthee
]]

 

==Requirements, Specifications, Wishlist==

We chose the GUI [http://dabba.co.za/wispgui wishlist by Dabba] as an entry to discussing our current specifications set, identifying how we cover the single elements today, identifying dependencies, etc

[[Image:WISPiab meeting 20080603 whiteboard 1.jpg|thumb|left| Whiteboard Day 2]]
[[Image:Working_Logo.jpg|thumb|left|Table context]]

{| border="1" cellpadding="7" cellspacing="0"
!align="left" |What?
!align="left" |Which element
!align="left" |Existing
!align="left" |Who/how
!align="left" |Alternate names/terms
!align="left" |Task
|-
|Network Settings
|core
|FF, IHL, Coova (wifidog) + alternatives, Linksys & Netgear interfaces
|
|Network Management, Setup,
|
|-
|ISP settings
|core
|Coova, phpMyPrepaid, OpenWRT (QoS script) (...)shaper
|
|user/service profiles – provisioning (some of it -> QoS)
|
|-
|VoIP Settings Users, tarriffs
|voice
|AsteriskNow IP04 HW, Trixbox, A2billing, (Open)SER
|
| -->user profiles, --> VoIP settings
|
|-
|Prepaid Card System (print cards) (ops), ->web, ->voice
|web,voice
|phpMyPrepaid, A2billing
|
|“usage”
|
|-
|CRM
|core
|compiere
|
|
|
|-
|Accounting -->logs
|core
|phpMyPrepaid, a2billing
|
| ->(if bill) ->ERP
|
|-
|Logo/Company
|core
|(all components have some of it)
|
|themes/skins/ customisation
|
|-
|Network Monitoring
|
|Nagios, Open-Mesh, Open NMS, FF (some), MRTG/rrdtool
|
|Network management
|
|-
|'''Items not contained in Dabba GUI'''
|
|
|
|
|
|-
|Content repository (SW, media, ...)
|
|
|
|
|
|-
|Video Server
|
|
|
|
|
|-
|Cache\Proxy with stats
|
|squid with awstats
|
|
|
|-
|Mail
|
|Postfix, Courier
|
|
|
|-
|Security & encryption
|
|OpenVPN
|
|
|
|-
|httpd, with stats etc
|
|apache, awstats
|
|
|
|-
|Wiki / image hosting
|
|mediawiki
|
|
|
|-
|Telecentre management
|
|UgaBytes telecentre management software - explore!
|
|
|
|-
|}

==Business Models==

Discussion of business models that have informed the specifications, and a checkback whether we feel that the current specifications actually accomodate all these models.

The template on top suggests dimensions / criteria from which to look at the various models.

===Business Model Template===

* Description:

* Economics: Free or paid by ....
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications:
* Network / Topology:
* Internet uplink:
* User Devices / Locations:
* Startup Strategy:
* Legal & Regulatory

===Telecentre / Internet Cafe / Hotspot===

* Description: "Classical" telecentre / cafe style

* Economics: Free or paid by users / advertisers / cafe business
* Billing models: typically Prepaid (Time based):
* Applications: typically Browser / Mail / Office / Games
* Network / Topology: wired LAN
* Internet uplink: model works with and without uplink, but typically yes
* User Devices / Locations: Users on business owned PC
* Startup Strategy:
* Legal & Regulatory: ok in most (?) countries

===Telco===

* Description: Telco offering "fixed line" and mobile VoIP telephony

* Economics: Part free (?) (local) / paid by user
* Billing models: typically Prepaid (Time/Data based):
* Applications: VoIP telephony, typically on dedicated hardware
* Network / Topology: Centralized / Inframesh
* Internet uplink: Yes, if terminating external calls / local loop without
* User Devices / Locations: Users at home / office / mobile, Device VoIP handsets, ATA etc
* Startup Strategy:
* Legal & Regulatory: complex, country to country

===(Edu)Content / Media===

* Economics: Free or paid by user / external
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications: Browser, Video, Image, Sound apps
* Network / Topology: n/a
* Internet uplink: not neccessarily, but recommended
* User Devices / Locations: all kinds of devices, local/remote,
* Startup Strategy:
* Legal & Regulatory: apart from restrictions on content, no issues

===Intranet / Neighbour-Net===

* Economics: Typically paid by customer
* Billing models: Contract / "Subscription"
* Applications: All PC apps
* Network / Topology: typically centralized, might be mesh
* Internet uplink: not neccessarily, but recommended
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy:
* Legal & Regulatory: no issues

===Line Sharing===

* Economics: Typically paid by users, in split scheme (e.g. cost per user = (line cost / # of users)*(marginfactor))
* Billing models: Prepaid monthly
* Applications: All PC apps
* Network / Topology: centralized or mesh
* Internet uplink: yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy: bottom up, organic
* Legal & Regulatory: potential issues with DSL or line resell (?), power limits for wireless part

===ISP===

* Economics: Typically user paid
* Billing models: Prepaid monthly, subscription
* Applications: All apps
* Network / Topology: centralized or mesh
* Internet uplink: yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy:
* Legal & Regulatory: regulations for ISP ops, licensing etc

===Web Hosting / Design===

A potential part of an ISPs business.
Seen as outside scope of this project, however simple home pages / website very common and demanded.
E.g. local businesses, etc

===Corporate / Managed Services===

* Economics: Typically user paid
* Billing models: Prepaid monthly, subscription
* Applications: All apps
* Network / Topology: centralized or mesh
* Internet uplink: typically yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy: company initiative
* Legal & Regulatory: potential issues when mixed user groups share same network (e.g. private, corp, gov, etc)

Strong focus on security (all aspects), network separation, QoS, management.

===Guesthouse Net===

* Economics: Typically user (= guesthouse) paid, might be free for customer of guesthouse, or paid for
* Billing models: if paid for, typically voucher prepaid, time based
* Applications: All apps
* Network / Topology: typically centralized
* Internet uplink: yes
* User Devices / Locations: users devices, maybe one or several public access PC
* Startup Strategy: guesthouse initiative
* Legal & Regulatory: no issues

===Housing Complex===

similar to Intranet / Neighbournet

* Economics: Typically user paid, might be included in other service charges or rent
* Billing models: Prepaid monthly or longer term, subscription
* Applications: All apps
* Network / Topology: centralized or mesh, often wired
* Internet uplink: typically yes
* User Devices / Locations: PCs and other, local at homes
* Startup Strategy: owner initiative
* Legal & Regulatory: no issues

===Surveillance===

* Economics: Typically customer paid
* Billing models: Prepaid monthly, subscription
* Applications: Very specific, wireless surveillance cams, motion detectors, etc
* Network / Topology: centralized or mesh
* Internet uplink: typically yes, in order to allow for remote control and alerts
* User Devices / Locations: surveillance gear and control units, typically PC/browser/mobile (SMS notifications)
* Startup Strategy:
* Legal & Regulatory: generally no issues when limited to company/housing premises. issues when extending into public space. ethics.

===Freifunk style Mesh===

* Economics: Typically completely user paid, informal, but might implement business scheme similar to line sharing ((e.g. cost per user = (central uplink cost / # of users)*(marginfactor))
* Billing models: e.g. Prepaid monthly
* Applications: All incl telephony
* Network / Topology: full mesh / inframesh
* Internet uplink: typically yes, but local net relevant
* User Devices / Locations: all types of devices, at user homes / office / businesses, roaming users
* Startup Strategy:
* Legal & Regulatory: potential issues withpower limits, collision with other networks, DSL reuse / resell

===Training / Consultancy===

A side business, outside scope for this project, but clearly relevant.

= Notes from the meeting - Day 3=

==Ndlovu Medical Centre==

Henry introduces:

* Status of mesh: operational, but currently disconnected (concerns about lightning)
* Use of uplink: Browsing (for community users), sync with data center (Johannesburg)
* Status of uplink: promised by Telkom, but not delivered yet

How to get started with a community mesh?

* Donated PCs - 25 pcs
** Give to local entrepreneur types
* Computer school as entry point

* Create a starter kit
** for existing PCs (there is some! mostly free windows)
** preconfigured
** low cost
** probably of the type: Linksys WRT, open-mesh/accton

Financing model

* Some contribution from user: Prepaid - low cost

What is interesting for people?

* music!!! open music server locally?
* free books? educational material
* free local calls
* a free wikipedia / digital doorway

Income from other sources (not the users):

* advertisements

To do / upcoming:

* '''call for a brainstorm meeting within the community'''

* June 9, meeting with provincial directory

* June 24: excursion to Ndlovu? participants of Wireless Africa meeting, Meraka people, Tom, Elektra

Top pain points / whats in the way:

* political level - get OKs from important players

==Hardware reference platform==

===Overall Requirements===

* 12 Volts (best: 11 ... 16)
* low power
* fanless

===Backend server===

* USB 2x
* ethernet 2x
* VGA

Candidate for reference choice:

* bigger solution: VIA, jetway 1.2 GHz, 2x HD, 1 GB RAM, USD 680 ... 820 [http://mini-box.com e.g. mini-box-com]
** power: approx 25W ?
* smaller solution: VIA, AMD Geode 500 MHz
** power: 8 W
* LEX light/neo, e.g. 1 GB C7 approx USD 600 [http://www.lex.com.tw/ http://www.lex.com.tw/]
* soon to come: Atom based low cost desktops (Mark Summer)
* alternatives: [http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99 http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99]

====Software on backend====

Decision: Ubuntu (non X)

----

===Access node===

* ethernet 2x
* PoE
* outdoor casing
* broadcom or atheros chipset
* 5 ... 18 Volts
* Watchdog (option)
* WISPCAR (option)
* serial port

Candidates:

* Linksys WRT54GL
** price: EUR 50, ZAR 600, USD 60
** power: 4 W
** comments:

* Ubiqiti
** price: NS 2: USD 79
** price: PS 2: USD 110
** power: 5 W

* Accton
** price: USD 40
** power: 2-3 W ?
** comments: overheat problems? needs fixed power 5 V? quality of radio? unstable across channels?

* PCEngines board
** price: > USD 250
** power: approx > 8W, depending on radio cards
** comments:

* Soekris

* Gateworks
**
**

* Wiligear

===Solar powering: A word on the fine for every watt installed===

Elektra makes the conservative estimate:

To power a 5 Watt device reliably, install a 80 Watt solar panel.
This means: 16 Watt solar panel per 1 Watt installed.

At about USD 5 per solar panel watt (current rough guess for market price), we have:

USD 80 in solar panel per 1 Watt installed.

Even when demanding less margin from the solar power system (i.e. less reliability, more optimism), the fine for every Watt installed is heavy.

==Next steps==

* Cape Town Village Telco worksprint
* Kobus, Johann, Elektra
** We need a presentation - Sebastian sends to Kobus and all - dead: june 10
*** Metaphores: pipes - water / roads - cars /
** Minutes / Doc

* Software development
** Meraka - Priority: the set of Coova (alternative: WifiDog) / FreeRadius / phpMyPrepaid (alternative: ISPBill) / Nagios
** Inveneo - Priority: IHL, Server squid/cache, proxy, asterisk, Webmin/ISPConfig
** How to work together? SVN server ? location ? Meraka machines accessible form outside?

* Examine the Ubiquiti - Lead: Elektra
** flash OpenWRT [http://wiki.openwrt.org/OpenWrtDocs/Hardware/Ubiquiti OpenWrt Ubiquiti]
** Examine the SDK
** examine internal antenna pol switching (AAP)

* Procurement - Lead: Ajay
** 12 x Inveneo small server, IONs, June 16
** 2 x Inveneo, Hub servers, June 16
** Ubiquiti Nano/Powerstation: one PS2 in place - OK for now
** Linksyses: we have enough, OK
** Boards: we have the Gateworks, OK
** Solar power: one demo system until June 23 - ask Grant: 64 W panel, charge controller, batteries - Lead: Sebastian

* Examine the [http://wiki.inveneo.org/index.php/Inveneo_Server_Linux_1.x Inveneo Hub Linux (IHL)] - Elektra / George

* Examine Open-Mesh - Lead: Sebastian
** examine status and development
** specifically: the Coova/Robin merger?

* Establish Documentation on Wiki

File:WISPiab meeting 20080605 whiteboard 1.jpg

2008-06-10T19:51:20Z

Sebastian: whiteboard of open discussions after work meeting

whiteboard of open discussions after work meeting

WISPiab brainstorm on way forward 200806

2008-06-10T19:18:58Z

Sebastian: New page: Category: WISP in a box ==detailed software development plan== ==detailed (human) resource plan== ==collab server, svn, etc== ==hardware: build solar powered prototype== ==outr...

[[Category: WISP in a box]]

==detailed software development plan==

==detailed (human) resource plan==

==collab server, svn, etc==

==hardware: build solar powered prototype==

==outreach: conferences and papers==

==ndlovu tests==

visit june 24?

WISPiab work meeting 200806

2008-06-05T11:11:13Z

Sebastian: /* Next steps */

[[Category: WISP in a box]]

=Work meeting of the WISP-in-a-box project=

[[The WISP-in-a-box project]]

=Date=

June 2-3-4, 2008

9-17 h

=Location=

Meraka Institute,
Building 43 C,
Hummingbird Room (C128, ground floor)

Pretoria

=Invitation List=

People and organisations with an active interest in building a concrete product that
helps bringing

connectivity to underserviced, underprivileged and overcharged communities in Africa.

Invitation list:

* Steve Song / Shuttleworth Foundation (monday only)
* Rael Lissoos / Dabba
* Henry Marnitz / Ndlovu Medical Centre (wednesday only)
* Mark Summer, Inveneo (with request to forward to Ubiquiti)
* Elektra
* Mike Jensen (not confirmed)
* Kobus Roux, Meraka (NOT monday)
* Karel Matthee, Meraka
* Kim Gush, Meraka
* David Johnson, Meraka
* Chris Morris, Meraka
* Grant Cambridge, Meraka
* Shela Boshomane, Meraka (monday and wednesday)
* George James, Meraka
* Johann Hugo, Meraka
* John Hay, Meraka
* Ajay Makan, Meraka
* Sebastian Buettrich

More proposals are welcome!

Budgets for travel, if needed: Please contact us!

=Contact=

Sebastian

mail: sebastian@less.dk

skype: sebastian_buettrich

cell: (+27) (0) 79 915 32 92

=Timeplan=

The timeplan is draft level and will be adjusted to people's ability to join for limited periods.

'''The first day''' will be dedicated to the '''organizational layer''',

introducing the various projects and teams,
discussing the business models,
identifying overlap of work agendas as well as the main challenges each of the projects are seeing.

'''The second day''' will move down to detail level,
moving from business and organizational models to technology requirements/specifications.

The third day

==Day 1 - Monday, June 2==

===Morning===

====Creating Context====

Introductions, Presentations of participants

(Short 10 mns, informal project introductions)

* Introduction and WISPiab Project (Sebastian Buettrich)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Ndlovu Medical Centre (Henry Marnitz) (moved to Wednesday, June 4)
* Peeble's Valley Mesh (David Johnson)
* Digital Doorway (tba)
* Inveneo platform (Mark Summer)
* WISPiab work status (George James)
* Wireless Africa project (Chris Morris)
* Freifunk, B.a.t.m.a.n. & Meraka Mesh Testbed (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* IP04 (it46, rowetel) (on behalf of the project: Sebastian Buettrich)

===Afternoon===

====Business models====

Introduction: Sebastian

Business models may be classified according to a number of different dimensions -

e.g. financial/economic layer, tech/network topology layer, applications layer, social layer, -

Based on the experience of the participants and projects,
business models should be reviewed with the goal of reaching a downselection of models that should be implemented/supported
in the first iteration of the WISPiab project.

Classical examples:

* Voice services - The Village Telco
* "Line sharing" - sharing internet access between organizations
* Telecentre / Internet Cafe
* Campus / School network

'''The goal''' is to go through all our relevant models, to classify them on all layers,

and to identify the technology implications (such that technology follows business models, and not vice versa), producing a clear results list.

====Cooperations and Resources====

There is significant overlap between projects on the technology layer.
All projects are subscribing to free software models (GPL / CC, etc).

We are operating against a backdrop of

* challenged (human) resource situation
* brain drain / skills exodus
* wanting to build local (i.e. african? ... southern african? .... south african?) capacity

Cooperation between projects seems appropriate and possible.

'''The goal''' is to conclude this meeting with a clear picture of modes of cooperation.

====Advisory Group====

We wish to form an advisory group / peer group, including partly the invitees of this meeting, but not limited to these.

==Day 2 - Tuesday, June 3==

===Morning===

====Technical Requirements / Specifications - detail level====

Examples of concrete detail issues:

* Authentication - where and how
* Billing in mesh networks
* VoIP in mesh networks

'''The goal''' of this session is to fill the matrix of

''technology requirements x project/business model''

and then check this matrix against the various existing hardware/software platforms.

====Hardware platforms aspects====

A number of different hardware/software platforms are fulfilling subsets of our requirements.

The available platforms need to be discussed and evaluated, towards a decision on what to choose.

The platforms that our projects are currently working with are:

* Linksys WRT54, with firmwares OpenWRT, DD-WRT, Freifunk, CoovaAP, and similar
* Open-Mesh, Accton - with Open Mesh Firmware (new firmware anoounced for summer 2008, with: RO.B.IN, orangemesh, COOVA, etc)
* Inveneo platform
* Ubiquti NS, PS
* Meraka Bokkie routers
* pls add!

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Productification / Dissemination / Rollout strategies====

* Strategies for the productification of software packages
** Sourceforge platform plans (Steve?)
** Ubuntu / UCK (Sebastian, Mark, Elektra)
* Rollout capacity

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

==Day 3 - Wednesday, June 4==

===Morning===

==== Ndlovu Medical Center====

Status and Agenda of network at Ndlovu Medical Center

* How can the various projects benefit Ndlovu Medical Center?

====Status, gaps and planning of implementations====

* WISPiab status and work plan
* Dabba / Village Telco work sprint, June 16-20
** prepare and support that workshop

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Conclusions & Next steps====

* Dabba Worksprint
* WISPiab work plan
* Digital Doorway work
* Wireless Africa, June meeting

etc

= Notes from the meeting - Day 1=

==People & Project introductions==

* Introduction and WISPiab Project (Sebastian Buettrich)
* Peeble's Valley Mesh (David Johnson)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Inveneo platform (Mark Summer)
* Freifunk (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* WISPiab work status (George James)
* Two radio mesh router (Johann Hugo)
* Wireless Africa project (Chris Morris)

==Forming an Alliance?==

to be edited

= Notes from the meeting - Day 2=
[[Image:Day2 - WISPiab_Wkshop.jpg|left|thumb|350px|Day2 (L-R) Mark Summer, Johann Hugo, Mike Jensen, Elektra, Sebastian Buettrich, Kobus Roux, George James, Ajay Makan, Karel Matthee
]]

 

==Requirements, Specifications, Wishlist==

We chose the GUI [http://dabba.co.za/wispgui wishlist by Dabba] as an entry to discussing our current specifications set, identifying how we cover the single elements today, identifying dependencies, etc

[[Image:WISPiab meeting 20080603 whiteboard 1.jpg|thumb|left| Whiteboard Day 2]]
[[Image:Working_Logo.jpg|thumb|left|Table context]]

{| border="1" cellpadding="7" cellspacing="0"
!align="left" |What?
!align="left" |Which element
!align="left" |Existing
!align="left" |Who/how
!align="left" |Alternate names/terms
!align="left" |Task
|-
|Network Settings
|core
|FF, IHL, Coova (wifidog) + alternatives, Linksys & Netgear interfaces
|
|Network Management, Setup,
|
|-
|ISP settings
|core
|Coova, phpMyPrepaid, OpenWRT (QoS script) (...)shaper
|
|user/service profiles – provisioning (some of it -> QoS)
|
|-
|VoIP Settings Users, tarriffs
|voice
|AsteriskNow IP04 HW, Trixbox, A2billing, (Open)SER
|
| -->user profiles, --> VoIP settings
|
|-
|Prepaid Card System (print cards) (ops), ->web, ->voice
|web,voice
|phpMyPrepaid, A2billing
|
|“usage”
|
|-
|CRM
|core
|compiere
|
|
|
|-
|Accounting -->logs
|core
|phpMyPrepaid, a2billing
|
| ->(if bill) ->ERP
|
|-
|Logo/Company
|core
|(all components have some of it)
|
|themes/skins/ customisation
|
|-
|Network Monitoring
|
|Nagios, Open-Mesh, Open NMS, FF (some), MRTG/rrdtool
|
|Network management
|
|-
|Content
|
|
|
|
|
|-
|Video Server
|
|
|
|
|
|-
|Cache\Proxy with stats
|
|squid with awstats
|
|
|
|-
|Mail
|
|
|
|
|
|-
|Security encryption
|
|
|
|
|
|-
|httpd, with stats etc
|
|apache, awstats
|
|
|
|-
|Wiki / image hosting
|
|
|
|
|
|-
|Telecentre management
|
|UgaBytes telecentre management software?
|
|
|
|-
|}

==Business Models==

Discussion of business models that have informed the specifications, and a checkback whether we feel that the current specifications actually accomodate all these models.

The template on top suggests dimensions / criteria from which to look at the various models.

===Business Model Template===

* Description:

* Economics: Free or paid by ....
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications:
* Network / Topology:
* Internet uplink:
* User Devices / Locations:
* Startup Strategy:
* Legal & Regulatory

===Telecentre / Internet Cafe / Hotspot===

* Description: "Classical" telecentre / cafe style

* Economics: Free or paid by users / advertisers / cafe business
* Billing models: typically Prepaid (Time based):
* Applications: typically Browser / Mail / Office / Games
* Network / Topology: wired LAN
* Internet uplink: model works with and without uplink, but typically yes
* User Devices / Locations: Users on business owned PC
* Startup Strategy:
* Legal & Regulatory: ok in most (?) countries

===Telco===

* Description: Telco offering "fixed line" and mobile VoIP telephony

* Economics: Part free (?) (local) / paid by user
* Billing models: typically Prepaid (Time/Data based):
* Applications: VoIP telephony, typically on dedicated hardware
* Network / Topology: Centralized / Inframesh
* Internet uplink: Yes, if terminating external calls / local loop without
* User Devices / Locations: Users at home / office / mobile, Device VoIP handsets, ATA etc
* Startup Strategy:
* Legal & Regulatory: complex, country to country

===(Edu)Content / Media===

* Economics: Free or paid by user / external
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications: Browser, Video, Image, Sound apps
* Network / Topology: n/a
* Internet uplink: not neccessarily, but recommended
* User Devices / Locations: all kinds of devices, local/remote,
* Startup Strategy:
* Legal & Regulatory: apart from restrictions on content, no issues

===Intranet / Neighbour-Net===

* Economics: Typically paid by customer
* Billing models: Contract / "Subscription"
* Applications: All PC apps
* Network / Topology: typically centralized, might be mesh
* Internet uplink: not neccessarily, but recommended
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy:
* Legal & Regulatory: no issues

===Line Sharing===

* Economics: Typically paid by users, in split scheme (e.g. cost per user = (line cost / # of users)*(marginfactor))
* Billing models: Prepaid monthly
* Applications: All PC apps
* Network / Topology: centralized or mesh
* Internet uplink: yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy: bottom up, organic
* Legal & Regulatory: potential issues with DSL or line resell (?), power limits for wireless part

===ISP===

* Economics: Typically user paid
* Billing models: Prepaid monthly, subscription
* Applications: All apps
* Network / Topology: centralized or mesh
* Internet uplink: yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy:
* Legal & Regulatory: regulations for ISP ops, licensing etc

===Web Hosting / Design===

A potential part of an ISPs business.
Seen as outside scope of this project, however simple home pages / website very common and demanded.
E.g. local businesses, etc

===Corporate / Managed Services===

* Economics: Typically user paid
* Billing models: Prepaid monthly, subscription
* Applications: All apps
* Network / Topology: centralized or mesh
* Internet uplink: typically yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy: company initiative
* Legal & Regulatory: potential issues when mixed user groups share same network (e.g. private, corp, gov, etc)

Strong focus on security (all aspects), network separation, QoS, management.

===Guesthouse Net===

* Economics: Typically user (= guesthouse) paid, might be free for customer of guesthouse, or paid for
* Billing models: if paid for, typically voucher prepaid, time based
* Applications: All apps
* Network / Topology: typically centralized
* Internet uplink: yes
* User Devices / Locations: users devices, maybe one or several public access PC
* Startup Strategy: guesthouse initiative
* Legal & Regulatory: no issues

===Housing Complex===

similar to Intranet / Neighbournet

* Economics: Typically user paid, might be included in other service charges or rent
* Billing models: Prepaid monthly or longer term, subscription
* Applications: All apps
* Network / Topology: centralized or mesh, often wired
* Internet uplink: typically yes
* User Devices / Locations: PCs and other, local at homes
* Startup Strategy: owner initiative
* Legal & Regulatory: no issues

===Surveillance===

* Economics: Typically customer paid
* Billing models: Prepaid monthly, subscription
* Applications: Very specific, wireless surveillance cams, motion detectors, etc
* Network / Topology: centralized or mesh
* Internet uplink: typically yes, in order to allow for remote control and alerts
* User Devices / Locations: surveillance gear and control units, typically PC/browser/mobile (SMS notifications)
* Startup Strategy:
* Legal & Regulatory: generally no issues when limited to company/housing premises. issues when extending into public space. ethics.

===Freifunk style Mesh===

* Economics: Typically completely user paid, informal, but might implement business scheme similar to line sharing ((e.g. cost per user = (central uplink cost / # of users)*(marginfactor))
* Billing models: e.g. Prepaid monthly
* Applications: All incl telephony
* Network / Topology: full mesh / inframesh
* Internet uplink: typically yes, but local net relevant
* User Devices / Locations: all types of devices, at user homes / office / businesses, roaming users
* Startup Strategy:
* Legal & Regulatory: potential issues withpower limits, collision with other networks, DSL reuse / resell

===Training / Consultancy===

A side business, outside scope for this project, but clearly relevant.

= Notes from the meeting - Day 3=

==Ndlovu Medical Centre==

Henry introduces:

* Status of mesh: operational, but currently disconnected (concerns about lightning)
* Use of uplink: Browsing (for community users), sync with data center (Johannesburg)
* Status of uplink: promised by Telkom, but not delivered yet

How to get started with a community mesh?

* Donated PCs - 25 pcs
** Give to local entrepreneur types
* Computer school as entry point

* Create a starter kit
** for existing PCs (there is some! mostly free windows)
** preconfigured
** low cost
** probably of the type: Linksys WRT, open-mesh/accton

Financing model

* Some contribution from user: Prepaid - low cost

What is interesting for people?

* music!!! open music server locally?
* free books? educational material
* free local calls
* a free wikipedia / digital doorway

Income from other sources (not the users):

* advertisements

To do / upcoming:

* '''call for a brainstorm meeting within the community'''

* June 9, meeting with provincial directory

* June 24: excursion to Ndlovu? participants of Wireless Africa meeting, Meraka people, Tom, Elektra

Top pain points / whats in the way:

* political level - get OKs from important players

==Hardware reference platform==

===Overall Requirements===

* 12 Volts (best: 11 ... 16)
* low power
* fanless

===Backend server===

* USB 2x
* ethernet 2x
* VGA

Candidate for reference choice:

* bigger solution: VIA, jetway 1.2 GHz, 2x HD, 1 GB RAM, USD 680 ... 820 [http://mini-box.com e.g. mini-box-com]
** power: approx 25W ?
* smaller solution: VIA, AMD Geode 500 MHz
** power: 8 W
* LEX light/neo, e.g. 1 GB C7 approx USD 600 [http://www.lex.com.tw/ http://www.lex.com.tw/]
* soon to come: Atom based low cost desktops (Mark Summer)
* alternatives: [http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99 http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99]

====Software on backend====

Decision: Ubuntu (non X)

----

===Access node===

* ethernet 2x
* PoE
* outdoor casing
* broadcom or atheros chipset
* 5 ... 18 Volts
* Watchdog (option)
* WISPCAR (option)
* serial port

Candidates:

* Linksys WRT54GL
** price: EUR 50, ZAR 600, USD 60
** power: 4 W
** comments:

* Ubiqiti
** price: NS 2: USD 79
** price: PS 2: USD 110
** power: 5 W

* Accton
** price: USD 40
** power: 2-3 W ?
** comments: overheat problems? needs fixed power 5 V? quality of radio? unstable across channels?

* PCEngines board
** price: > USD 250
** power: approx > 8W, depending on radio cards
** comments:

* Soekris

* Gateworks
**
**

* Wiligear

===Solar powering: A word on the fine for every watt installed===

Elektra makes the conservative estimate:

To power a 5 Watt device reliably, install a 80 Watt solar panel.
This means: 16 Watt solar panel per 1 Watt installed.

At about USD 5 per solar panel watt (current rough guess for market price), we have:

USD 80 in solar panel per 1 Watt installed.

Even when demanding less margin from the solar power system (i.e. less reliability, more optimism), the fine for every Watt installed is heavy.

==Next steps==

* Cape Town Village Telco worksprint
* Kobus, Johann, Elektra
** We need a presentation - Sebastian sends to Kobus and all - dead: june 10
*** Metaphores: pipes - water / roads - cars /
** Minutes / Doc

* Software development
** Meraka - Priority: the set of Coova (alternative: WifiDog) / FreeRadius / phpMyPrepaid (alternative: ISPBill) / Nagios
** Inveneo - Priority: IHL, Server squid/cache, proxy, asterisk, Webmin/ISPConfig
** How to work together? SVN server ? location ? Meraka machines accessible form outside?

* Examine the Ubiquiti - Lead: Elektra
** flash OpenWRT [http://wiki.openwrt.org/OpenWrtDocs/Hardware/Ubiquiti OpenWrt Ubiquiti]
** Examine the SDK
** examine internal antenna pol switching (AAP)

* Procurement - Lead: Ajay
** 12 x Inveneo small server, IONs, June 16
** 2 x Inveneo, Hub servers, June 16
** Ubiquiti Nano/Powerstation: one PS2 in place - OK for now
** Linksyses: we have enough, OK
** Boards: we have the Gateworks, OK
** Solar power: one demo system until June 23 - ask Grant: 64 W panel, charge controller, batteries - Lead: Sebastian

* Examine the [http://wiki.inveneo.org/index.php/Inveneo_Server_Linux_1.x Inveneo Hub Linux (IHL)] - Elektra / George

* Examine Open-Mesh - Lead: Sebastian
** examine status and development
** specifically: the Coova/Robin merger?

* Establish Documentation on Wiki

WISPiab work meeting 200806

2008-06-05T10:37:20Z

Sebastian: /* Next steps */

[[Category: WISP in a box]]

=Work meeting of the WISP-in-a-box project=

[[The WISP-in-a-box project]]

=Date=

June 2-3-4, 2008

9-17 h

=Location=

Meraka Institute,
Building 43 C,
Hummingbird Room (C128, ground floor)

Pretoria

=Invitation List=

People and organisations with an active interest in building a concrete product that
helps bringing

connectivity to underserviced, underprivileged and overcharged communities in Africa.

Invitation list:

* Steve Song / Shuttleworth Foundation (monday only)
* Rael Lissoos / Dabba
* Henry Marnitz / Ndlovu Medical Centre (wednesday only)
* Mark Summer, Inveneo (with request to forward to Ubiquiti)
* Elektra
* Mike Jensen (not confirmed)
* Kobus Roux, Meraka (NOT monday)
* Karel Matthee, Meraka
* Kim Gush, Meraka
* David Johnson, Meraka
* Chris Morris, Meraka
* Grant Cambridge, Meraka
* Shela Boshomane, Meraka (monday and wednesday)
* George James, Meraka
* Johann Hugo, Meraka
* John Hay, Meraka
* Ajay Makan, Meraka
* Sebastian Buettrich

More proposals are welcome!

Budgets for travel, if needed: Please contact us!

=Contact=

Sebastian

mail: sebastian@less.dk

skype: sebastian_buettrich

cell: (+27) (0) 79 915 32 92

=Timeplan=

The timeplan is draft level and will be adjusted to people's ability to join for limited periods.

'''The first day''' will be dedicated to the '''organizational layer''',

introducing the various projects and teams,
discussing the business models,
identifying overlap of work agendas as well as the main challenges each of the projects are seeing.

'''The second day''' will move down to detail level,
moving from business and organizational models to technology requirements/specifications.

The third day

==Day 1 - Monday, June 2==

===Morning===

====Creating Context====

Introductions, Presentations of participants

(Short 10 mns, informal project introductions)

* Introduction and WISPiab Project (Sebastian Buettrich)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Ndlovu Medical Centre (Henry Marnitz) (moved to Wednesday, June 4)
* Peeble's Valley Mesh (David Johnson)
* Digital Doorway (tba)
* Inveneo platform (Mark Summer)
* WISPiab work status (George James)
* Wireless Africa project (Chris Morris)
* Freifunk, B.a.t.m.a.n. & Meraka Mesh Testbed (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* IP04 (it46, rowetel) (on behalf of the project: Sebastian Buettrich)

===Afternoon===

====Business models====

Introduction: Sebastian

Business models may be classified according to a number of different dimensions -

e.g. financial/economic layer, tech/network topology layer, applications layer, social layer, -

Based on the experience of the participants and projects,
business models should be reviewed with the goal of reaching a downselection of models that should be implemented/supported
in the first iteration of the WISPiab project.

Classical examples:

* Voice services - The Village Telco
* "Line sharing" - sharing internet access between organizations
* Telecentre / Internet Cafe
* Campus / School network

'''The goal''' is to go through all our relevant models, to classify them on all layers,

and to identify the technology implications (such that technology follows business models, and not vice versa), producing a clear results list.

====Cooperations and Resources====

There is significant overlap between projects on the technology layer.
All projects are subscribing to free software models (GPL / CC, etc).

We are operating against a backdrop of

* challenged (human) resource situation
* brain drain / skills exodus
* wanting to build local (i.e. african? ... southern african? .... south african?) capacity

Cooperation between projects seems appropriate and possible.

'''The goal''' is to conclude this meeting with a clear picture of modes of cooperation.

====Advisory Group====

We wish to form an advisory group / peer group, including partly the invitees of this meeting, but not limited to these.

==Day 2 - Tuesday, June 3==

===Morning===

====Technical Requirements / Specifications - detail level====

Examples of concrete detail issues:

* Authentication - where and how
* Billing in mesh networks
* VoIP in mesh networks

'''The goal''' of this session is to fill the matrix of

''technology requirements x project/business model''

and then check this matrix against the various existing hardware/software platforms.

====Hardware platforms aspects====

A number of different hardware/software platforms are fulfilling subsets of our requirements.

The available platforms need to be discussed and evaluated, towards a decision on what to choose.

The platforms that our projects are currently working with are:

* Linksys WRT54, with firmwares OpenWRT, DD-WRT, Freifunk, CoovaAP, and similar
* Open-Mesh, Accton - with Open Mesh Firmware (new firmware anoounced for summer 2008, with: RO.B.IN, orangemesh, COOVA, etc)
* Inveneo platform
* Ubiquti NS, PS
* Meraka Bokkie routers
* pls add!

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Productification / Dissemination / Rollout strategies====

* Strategies for the productification of software packages
** Sourceforge platform plans (Steve?)
** Ubuntu / UCK (Sebastian, Mark, Elektra)
* Rollout capacity

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

==Day 3 - Wednesday, June 4==

===Morning===

==== Ndlovu Medical Center====

Status and Agenda of network at Ndlovu Medical Center

* How can the various projects benefit Ndlovu Medical Center?

====Status, gaps and planning of implementations====

* WISPiab status and work plan
* Dabba / Village Telco work sprint, June 16-20
** prepare and support that workshop

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Conclusions & Next steps====

* Dabba Worksprint
* WISPiab work plan
* Digital Doorway work
* Wireless Africa, June meeting

etc

= Notes from the meeting - Day 1=

==People & Project introductions==

* Introduction and WISPiab Project (Sebastian Buettrich)
* Peeble's Valley Mesh (David Johnson)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Inveneo platform (Mark Summer)
* Freifunk (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* WISPiab work status (George James)
* Two radio mesh router (Johann Hugo)
* Wireless Africa project (Chris Morris)

==Forming an Alliance?==

to be edited

= Notes from the meeting - Day 2=
[[Image:Day2 - WISPiab_Wkshop.jpg|left|thumb|350px|Day2 (L-R) Mark Summer, Johann Hugo, Mike Jensen, Elektra, Sebastian Buettrich, Kobus Roux, George James, Ajay Makan, Karel Matthee
]]

 

==Requirements, Specifications, Wishlist==

We chose the GUI [http://dabba.co.za/wispgui wishlist by Dabba] as an entry to discussing our current specifications set, identifying how we cover the single elements today, identifying dependencies, etc

[[Image:WISPiab meeting 20080603 whiteboard 1.jpg|thumb|left| Whiteboard Day 2]]
[[Image:Working_Logo.jpg|thumb|left|Table context]]

{| border="1" cellpadding="7" cellspacing="0"
!align="left" |What?
!align="left" |Which element
!align="left" |Existing
!align="left" |Who/how
!align="left" |Alternate names/terms
!align="left" |Task
|-
|Network Settings
|core
|FF, IHL, Coova (wifidog) + alternatives, Linksys & Netgear interfaces
|
|Network Management, Setup,
|
|-
|ISP settings
|core
|Coova, phpMyPrepaid, OpenWRT (QoS script) (...)shaper
|
|user/service profiles – provisioning (some of it -> QoS)
|
|-
|VoIP Settings Users, tarriffs
|voice
|AsteriskNow IP04 HW, Trixbox, A2billing, (Open)SER
|
| -->user profiles, --> VoIP settings
|
|-
|Prepaid Card System (print cards) (ops), ->web, ->voice
|web,voice
|phpMyPrepaid, A2billing
|
|“usage”
|
|-
|CRM
|core
|compiere
|
|
|
|-
|Accounting -->logs
|core
|phpMyPrepaid, a2billing
|
| ->(if bill) ->ERP
|
|-
|Logo/Company
|core
|(all components have some of it)
|
|themes/skins/ customisation
|
|-
|Network Monitoring
|
|Nagios, Open-Mesh, Open NMS, FF (some), MRTG/rrdtool
|
|Network management
|
|-
|Content
|
|
|
|
|
|-
|Video Server
|
|
|
|
|
|-
|Cache\Proxy with stats
|
|squid with awstats
|
|
|
|-
|Mail
|
|
|
|
|
|-
|Security encryption
|
|
|
|
|
|-
|httpd, with stats etc
|
|apache, awstats
|
|
|
|-
|Wiki / image hosting
|
|
|
|
|
|-
|Telecentre management
|
|UgaBytes telecentre management software?
|
|
|
|-
|}

==Business Models==

Discussion of business models that have informed the specifications, and a checkback whether we feel that the current specifications actually accomodate all these models.

The template on top suggests dimensions / criteria from which to look at the various models.

===Business Model Template===

* Description:

* Economics: Free or paid by ....
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications:
* Network / Topology:
* Internet uplink:
* User Devices / Locations:
* Startup Strategy:
* Legal & Regulatory

===Telecentre / Internet Cafe / Hotspot===

* Description: "Classical" telecentre / cafe style

* Economics: Free or paid by users / advertisers / cafe business
* Billing models: typically Prepaid (Time based):
* Applications: typically Browser / Mail / Office / Games
* Network / Topology: wired LAN
* Internet uplink: model works with and without uplink, but typically yes
* User Devices / Locations: Users on business owned PC
* Startup Strategy:
* Legal & Regulatory: ok in most (?) countries

===Telco===

* Description: Telco offering "fixed line" and mobile VoIP telephony

* Economics: Part free (?) (local) / paid by user
* Billing models: typically Prepaid (Time/Data based):
* Applications: VoIP telephony, typically on dedicated hardware
* Network / Topology: Centralized / Inframesh
* Internet uplink: Yes, if terminating external calls / local loop without
* User Devices / Locations: Users at home / office / mobile, Device VoIP handsets, ATA etc
* Startup Strategy:
* Legal & Regulatory: complex, country to country

===(Edu)Content / Media===

* Economics: Free or paid by user / external
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications: Browser, Video, Image, Sound apps
* Network / Topology: n/a
* Internet uplink: not neccessarily, but recommended
* User Devices / Locations: all kinds of devices, local/remote,
* Startup Strategy:
* Legal & Regulatory: apart from restrictions on content, no issues

===Intranet / Neighbour-Net===

* Economics: Typically paid by customer
* Billing models: Contract / "Subscription"
* Applications: All PC apps
* Network / Topology: typically centralized, might be mesh
* Internet uplink: not neccessarily, but recommended
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy:
* Legal & Regulatory: no issues

===Line Sharing===

* Economics: Typically paid by users, in split scheme (e.g. cost per user = (line cost / # of users)*(marginfactor))
* Billing models: Prepaid monthly
* Applications: All PC apps
* Network / Topology: centralized or mesh
* Internet uplink: yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy: bottom up, organic
* Legal & Regulatory: potential issues with DSL or line resell (?), power limits for wireless part

===ISP===

* Economics: Typically user paid
* Billing models: Prepaid monthly, subscription
* Applications: All apps
* Network / Topology: centralized or mesh
* Internet uplink: yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy:
* Legal & Regulatory: regulations for ISP ops, licensing etc

===Web Hosting / Design===

A potential part of an ISPs business.
Seen as outside scope of this project, however simple home pages / website very common and demanded.
E.g. local businesses, etc

===Corporate / Managed Services===

* Economics: Typically user paid
* Billing models: Prepaid monthly, subscription
* Applications: All apps
* Network / Topology: centralized or mesh
* Internet uplink: typically yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy: company initiative
* Legal & Regulatory: potential issues when mixed user groups share same network (e.g. private, corp, gov, etc)

Strong focus on security (all aspects), network separation, QoS, management.

===Guesthouse Net===

* Economics: Typically user (= guesthouse) paid, might be free for customer of guesthouse, or paid for
* Billing models: if paid for, typically voucher prepaid, time based
* Applications: All apps
* Network / Topology: typically centralized
* Internet uplink: yes
* User Devices / Locations: users devices, maybe one or several public access PC
* Startup Strategy: guesthouse initiative
* Legal & Regulatory: no issues

===Housing Complex===

similar to Intranet / Neighbournet

* Economics: Typically user paid, might be included in other service charges or rent
* Billing models: Prepaid monthly or longer term, subscription
* Applications: All apps
* Network / Topology: centralized or mesh, often wired
* Internet uplink: typically yes
* User Devices / Locations: PCs and other, local at homes
* Startup Strategy: owner initiative
* Legal & Regulatory: no issues

===Surveillance===

* Economics: Typically customer paid
* Billing models: Prepaid monthly, subscription
* Applications: Very specific, wireless surveillance cams, motion detectors, etc
* Network / Topology: centralized or mesh
* Internet uplink: typically yes, in order to allow for remote control and alerts
* User Devices / Locations: surveillance gear and control units, typically PC/browser/mobile (SMS notifications)
* Startup Strategy:
* Legal & Regulatory: generally no issues when limited to company/housing premises. issues when extending into public space. ethics.

===Freifunk style Mesh===

* Economics: Typically completely user paid, informal, but might implement business scheme similar to line sharing ((e.g. cost per user = (central uplink cost / # of users)*(marginfactor))
* Billing models: e.g. Prepaid monthly
* Applications: All incl telephony
* Network / Topology: full mesh / inframesh
* Internet uplink: typically yes, but local net relevant
* User Devices / Locations: all types of devices, at user homes / office / businesses, roaming users
* Startup Strategy:
* Legal & Regulatory: potential issues withpower limits, collision with other networks, DSL reuse / resell

===Training / Consultancy===

A side business, outside scope for this project, but clearly relevant.

= Notes from the meeting - Day 3=

==Ndlovu Medical Centre==

Henry introduces:

* Status of mesh: operational, but currently disconnected (concerns about lightning)
* Use of uplink: Browsing (for community users), sync with data center (Johannesburg)
* Status of uplink: promised by Telkom, but not delivered yet

How to get started with a community mesh?

* Donated PCs - 25 pcs
** Give to local entrepreneur types
* Computer school as entry point

* Create a starter kit
** for existing PCs (there is some! mostly free windows)
** preconfigured
** low cost
** probably of the type: Linksys WRT, open-mesh/accton

Financing model

* Some contribution from user: Prepaid - low cost

What is interesting for people?

* music!!! open music server locally?
* free books? educational material
* free local calls
* a free wikipedia / digital doorway

Income from other sources (not the users):

* advertisements

To do / upcoming:

* '''call for a brainstorm meeting within the community'''

* June 9, meeting with provincial directory

* June 24: excursion to Ndlovu? participants of Wireless Africa meeting, Meraka people, Tom, Elektra

Top pain points / whats in the way:

* political level - get OKs from important players

==Hardware reference platform==

===Overall Requirements===

* 12 Volts (best: 11 ... 16)
* low power
* fanless

===Backend server===

* USB 2x
* ethernet 2x
* VGA

Candidate for reference choice:

* bigger solution: VIA, jetway 1.2 GHz, 2x HD, 1 GB RAM, USD 680 ... 820 [http://mini-box.com e.g. mini-box-com]
** power: approx 25W ?
* smaller solution: VIA, AMD Geode 500 MHz
** power: 8 W
* LEX light/neo, e.g. 1 GB C7 approx USD 600 [http://www.lex.com.tw/ http://www.lex.com.tw/]
* soon to come: Atom based low cost desktops (Mark Summer)
* alternatives: [http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99 http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99]

====Software on backend====

Decision: Ubuntu (non X)

----

===Access node===

* ethernet 2x
* PoE
* outdoor casing
* broadcom or atheros chipset
* 5 ... 18 Volts
* Watchdog (option)
* WISPCAR (option)
* serial port

Candidates:

* Linksys WRT54GL
** price: EUR 50, ZAR 600, USD 60
** power: 4 W
** comments:

* Ubiqiti
** price: NS 2: USD 79
** price: PS 2: USD 110
** power: 5 W

* Accton
** price: USD 40
** power: 2-3 W ?
** comments: overheat problems? needs fixed power 5 V? quality of radio? unstable across channels?

* PCEngines board
** price: > USD 250
** power: approx > 8W, depending on radio cards
** comments:

* Soekris

* Gateworks
**
**

* Wiligear

===Solar powering: A word on the fine for every watt installed===

Elektra makes the conservative estimate:

To power a 5 Watt device reliably, install a 80 Watt solar panel.
This means: 16 Watt solar panel per 1 Watt installed.

At about USD 5 per solar panel watt (current rough guess for market price), we have:

USD 80 in solar panel per 1 Watt installed.

Even when demanding less margin from the solar power system (i.e. less reliability, more optimism), the fine for every Watt installed is heavy.

==Next steps==

* Cape Town Village Telco worksprint
* Kobus, Johann, Elektra
** We need a presentation - Sebastian sends to Kobus and all - dead: june 10
*** Metaphores: pipes - water / roads - cars /
** Minutes / Doc

* Software development
** Meraka - Priority: the set of Coova (alternative: WifiDog) / FreeRadius / phpMyPrepaid (alternative: ISPBill) / Nagios
** Inveneo - Priority: IHL, Server squid/cache, proxy, asterisk, Webmin/ISPConfig
** How to work together? SVN server ? location ? Meraka machines accessible form outside?

* Examine the Ubiquiti - Lead: Elektra
** flash OpenWRT [http://wiki.openwrt.org/OpenWrtDocs/Hardware/Ubiquiti OpenWrt Ubiquiti]
** Examine the SDK
** examine internal antenna pol switching (AAP)

* Procurement - Lead: Kobus/Ajay ?
** ??? x Inveneo small server, or Via direct
** Ubiquiti Nano/Powerstation
** Linksyses: assume we ave enough
** Solar power: one demo system until June 23 - ask Grant: 64 W panel, charge controller, batteries (

* Examine the [http://wiki.inveneo.org/index.php/Inveneo_Server_Linux_1.x Inveneo Hub Linux (IHL)] - Elektra / George

* Examine Open-Mesh - Lead: Sebastian
** examine status and development
** specifically: the Coova/Robin merger?

* Establish Documentation on Wiki

WISPiab work meeting 200806

2008-06-05T09:50:03Z

Sebastian: /* Next steps */

[[Category: WISP in a box]]

=Work meeting of the WISP-in-a-box project=

[[The WISP-in-a-box project]]

=Date=

June 2-3-4, 2008

9-17 h

=Location=

Meraka Institute,
Building 43 C,
Hummingbird Room (C128, ground floor)

Pretoria

=Invitation List=

People and organisations with an active interest in building a concrete product that
helps bringing

connectivity to underserviced, underprivileged and overcharged communities in Africa.

Invitation list:

* Steve Song / Shuttleworth Foundation (monday only)
* Rael Lissoos / Dabba
* Henry Marnitz / Ndlovu Medical Centre (wednesday only)
* Mark Summer, Inveneo (with request to forward to Ubiquiti)
* Elektra
* Mike Jensen (not confirmed)
* Kobus Roux, Meraka (NOT monday)
* Karel Matthee, Meraka
* Kim Gush, Meraka
* David Johnson, Meraka
* Chris Morris, Meraka
* Grant Cambridge, Meraka
* Shela Boshomane, Meraka (monday and wednesday)
* George James, Meraka
* Johann Hugo, Meraka
* John Hay, Meraka
* Ajay Makan, Meraka
* Sebastian Buettrich

More proposals are welcome!

Budgets for travel, if needed: Please contact us!

=Contact=

Sebastian

mail: sebastian@less.dk

skype: sebastian_buettrich

cell: (+27) (0) 79 915 32 92

=Timeplan=

The timeplan is draft level and will be adjusted to people's ability to join for limited periods.

'''The first day''' will be dedicated to the '''organizational layer''',

introducing the various projects and teams,
discussing the business models,
identifying overlap of work agendas as well as the main challenges each of the projects are seeing.

'''The second day''' will move down to detail level,
moving from business and organizational models to technology requirements/specifications.

The third day

==Day 1 - Monday, June 2==

===Morning===

====Creating Context====

Introductions, Presentations of participants

(Short 10 mns, informal project introductions)

* Introduction and WISPiab Project (Sebastian Buettrich)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Ndlovu Medical Centre (Henry Marnitz) (moved to Wednesday, June 4)
* Peeble's Valley Mesh (David Johnson)
* Digital Doorway (tba)
* Inveneo platform (Mark Summer)
* WISPiab work status (George James)
* Wireless Africa project (Chris Morris)
* Freifunk, B.a.t.m.a.n. & Meraka Mesh Testbed (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* IP04 (it46, rowetel) (on behalf of the project: Sebastian Buettrich)

===Afternoon===

====Business models====

Introduction: Sebastian

Business models may be classified according to a number of different dimensions -

e.g. financial/economic layer, tech/network topology layer, applications layer, social layer, -

Based on the experience of the participants and projects,
business models should be reviewed with the goal of reaching a downselection of models that should be implemented/supported
in the first iteration of the WISPiab project.

Classical examples:

* Voice services - The Village Telco
* "Line sharing" - sharing internet access between organizations
* Telecentre / Internet Cafe
* Campus / School network

'''The goal''' is to go through all our relevant models, to classify them on all layers,

and to identify the technology implications (such that technology follows business models, and not vice versa), producing a clear results list.

====Cooperations and Resources====

There is significant overlap between projects on the technology layer.
All projects are subscribing to free software models (GPL / CC, etc).

We are operating against a backdrop of

* challenged (human) resource situation
* brain drain / skills exodus
* wanting to build local (i.e. african? ... southern african? .... south african?) capacity

Cooperation between projects seems appropriate and possible.

'''The goal''' is to conclude this meeting with a clear picture of modes of cooperation.

====Advisory Group====

We wish to form an advisory group / peer group, including partly the invitees of this meeting, but not limited to these.

==Day 2 - Tuesday, June 3==

===Morning===

====Technical Requirements / Specifications - detail level====

Examples of concrete detail issues:

* Authentication - where and how
* Billing in mesh networks
* VoIP in mesh networks

'''The goal''' of this session is to fill the matrix of

''technology requirements x project/business model''

and then check this matrix against the various existing hardware/software platforms.

====Hardware platforms aspects====

A number of different hardware/software platforms are fulfilling subsets of our requirements.

The available platforms need to be discussed and evaluated, towards a decision on what to choose.

The platforms that our projects are currently working with are:

* Linksys WRT54, with firmwares OpenWRT, DD-WRT, Freifunk, CoovaAP, and similar
* Open-Mesh, Accton - with Open Mesh Firmware (new firmware anoounced for summer 2008, with: RO.B.IN, orangemesh, COOVA, etc)
* Inveneo platform
* Ubiquti NS, PS
* Meraka Bokkie routers
* pls add!

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Productification / Dissemination / Rollout strategies====

* Strategies for the productification of software packages
** Sourceforge platform plans (Steve?)
** Ubuntu / UCK (Sebastian, Mark, Elektra)
* Rollout capacity

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

==Day 3 - Wednesday, June 4==

===Morning===

==== Ndlovu Medical Center====

Status and Agenda of network at Ndlovu Medical Center

* How can the various projects benefit Ndlovu Medical Center?

====Status, gaps and planning of implementations====

* WISPiab status and work plan
* Dabba / Village Telco work sprint, June 16-20
** prepare and support that workshop

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Conclusions & Next steps====

* Dabba Worksprint
* WISPiab work plan
* Digital Doorway work
* Wireless Africa, June meeting

etc

= Notes from the meeting - Day 1=

==People & Project introductions==

* Introduction and WISPiab Project (Sebastian Buettrich)
* Peeble's Valley Mesh (David Johnson)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Inveneo platform (Mark Summer)
* Freifunk (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* WISPiab work status (George James)
* Two radio mesh router (Johann Hugo)
* Wireless Africa project (Chris Morris)

==Forming an Alliance?==

to be edited

= Notes from the meeting - Day 2=
[[Image:Day2 - WISPiab_Wkshop.jpg|left|thumb|350px|Day2 (L-R) Mark Summer, Johann Hugo, Mike Jensen, Elektra, Sebastian Buettrich, Kobus Roux, George James, Ajay Makan, Karel Matthee
]]

 

==Requirements, Specifications, Wishlist==

We chose the GUI [http://dabba.co.za/wispgui wishlist by Dabba] as an entry to discussing our current specifications set, identifying how we cover the single elements today, identifying dependencies, etc

[[Image:WISPiab meeting 20080603 whiteboard 1.jpg|thumb|left| Whiteboard Day 2]]
[[Image:Working_Logo.jpg|thumb|left|Table context]]

{| border="1" cellpadding="7" cellspacing="0"
!align="left" |What?
!align="left" |Which element
!align="left" |Existing
!align="left" |Who/how
!align="left" |Alternate names/terms
!align="left" |Task
|-
|Network Settings
|core
|FF, IHL, Coova (wifidog) + alternatives, Linksys & Netgear interfaces
|
|Network Management, Setup,
|
|-
|ISP settings
|core
|Coova, phpMyPrepaid, OpenWRT (QoS script) (...)shaper
|
|user/service profiles – provisioning (some of it -> QoS)
|
|-
|VoIP Settings Users, tarriffs
|voice
|AsteriskNow IP04 HW, Trixbox, A2billing, (Open)SER
|
| -->user profiles, --> VoIP settings
|
|-
|Prepaid Card System (print cards) (ops), ->web, ->voice
|web,voice
|phpMyPrepaid, A2billing
|
|“usage”
|
|-
|CRM
|core
|compiere
|
|
|
|-
|Accounting -->logs
|core
|phpMyPrepaid, a2billing
|
| ->(if bill) ->ERP
|
|-
|Logo/Company
|core
|(all components have some of it)
|
|themes/skins/ customisation
|
|-
|Network Monitoring
|
|Nagios, Open-Mesh, Open NMS, FF (some), MRTG/rrdtool
|
|Network management
|
|-
|Content
|
|
|
|
|
|-
|Video Server
|
|
|
|
|
|-
|Cache\Proxy with stats
|
|squid with awstats
|
|
|
|-
|Mail
|
|
|
|
|
|-
|Security encryption
|
|
|
|
|
|-
|httpd, with stats etc
|
|apache, awstats
|
|
|
|-
|Wiki / image hosting
|
|
|
|
|
|-
|Telecentre management
|
|UgaBytes telecentre management software?
|
|
|
|-
|}

==Business Models==

Discussion of business models that have informed the specifications, and a checkback whether we feel that the current specifications actually accomodate all these models.

The template on top suggests dimensions / criteria from which to look at the various models.

===Business Model Template===

* Description:

* Economics: Free or paid by ....
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications:
* Network / Topology:
* Internet uplink:
* User Devices / Locations:
* Startup Strategy:
* Legal & Regulatory

===Telecentre / Internet Cafe / Hotspot===

* Description: "Classical" telecentre / cafe style

* Economics: Free or paid by users / advertisers / cafe business
* Billing models: typically Prepaid (Time based):
* Applications: typically Browser / Mail / Office / Games
* Network / Topology: wired LAN
* Internet uplink: model works with and without uplink, but typically yes
* User Devices / Locations: Users on business owned PC
* Startup Strategy:
* Legal & Regulatory: ok in most (?) countries

===Telco===

* Description: Telco offering "fixed line" and mobile VoIP telephony

* Economics: Part free (?) (local) / paid by user
* Billing models: typically Prepaid (Time/Data based):
* Applications: VoIP telephony, typically on dedicated hardware
* Network / Topology: Centralized / Inframesh
* Internet uplink: Yes, if terminating external calls / local loop without
* User Devices / Locations: Users at home / office / mobile, Device VoIP handsets, ATA etc
* Startup Strategy:
* Legal & Regulatory: complex, country to country

===(Edu)Content / Media===

* Economics: Free or paid by user / external
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications: Browser, Video, Image, Sound apps
* Network / Topology: n/a
* Internet uplink: not neccessarily, but recommended
* User Devices / Locations: all kinds of devices, local/remote,
* Startup Strategy:
* Legal & Regulatory: apart from restrictions on content, no issues

===Intranet / Neighbour-Net===

* Economics: Typically paid by customer
* Billing models: Contract / "Subscription"
* Applications: All PC apps
* Network / Topology: typically centralized, might be mesh
* Internet uplink: not neccessarily, but recommended
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy:
* Legal & Regulatory: no issues

===Line Sharing===

* Economics: Typically paid by users, in split scheme (e.g. cost per user = (line cost / # of users)*(marginfactor))
* Billing models: Prepaid monthly
* Applications: All PC apps
* Network / Topology: centralized or mesh
* Internet uplink: yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy: bottom up, organic
* Legal & Regulatory: potential issues with DSL or line resell (?), power limits for wireless part

===ISP===

* Economics: Typically user paid
* Billing models: Prepaid monthly, subscription
* Applications: All apps
* Network / Topology: centralized or mesh
* Internet uplink: yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy:
* Legal & Regulatory: regulations for ISP ops, licensing etc

===Web Hosting / Design===

A potential part of an ISPs business.
Seen as outside scope of this project, however simple home pages / website very common and demanded.
E.g. local businesses, etc

===Corporate / Managed Services===

* Economics: Typically user paid
* Billing models: Prepaid monthly, subscription
* Applications: All apps
* Network / Topology: centralized or mesh
* Internet uplink: typically yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy: company initiative
* Legal & Regulatory: potential issues when mixed user groups share same network (e.g. private, corp, gov, etc)

Strong focus on security (all aspects), network separation, QoS, management.

===Guesthouse Net===

* Economics: Typically user (= guesthouse) paid, might be free for customer of guesthouse, or paid for
* Billing models: if paid for, typically voucher prepaid, time based
* Applications: All apps
* Network / Topology: typically centralized
* Internet uplink: yes
* User Devices / Locations: users devices, maybe one or several public access PC
* Startup Strategy: guesthouse initiative
* Legal & Regulatory: no issues

===Housing Complex===

similar to Intranet / Neighbournet

* Economics: Typically user paid, might be included in other service charges or rent
* Billing models: Prepaid monthly or longer term, subscription
* Applications: All apps
* Network / Topology: centralized or mesh, often wired
* Internet uplink: typically yes
* User Devices / Locations: PCs and other, local at homes
* Startup Strategy: owner initiative
* Legal & Regulatory: no issues

===Surveillance===

* Economics: Typically customer paid
* Billing models: Prepaid monthly, subscription
* Applications: Very specific, wireless surveillance cams, motion detectors, etc
* Network / Topology: centralized or mesh
* Internet uplink: typically yes, in order to allow for remote control and alerts
* User Devices / Locations: surveillance gear and control units, typically PC/browser/mobile (SMS notifications)
* Startup Strategy:
* Legal & Regulatory: generally no issues when limited to company/housing premises. issues when extending into public space. ethics.

===Freifunk style Mesh===

* Economics: Typically completely user paid, informal, but might implement business scheme similar to line sharing ((e.g. cost per user = (central uplink cost / # of users)*(marginfactor))
* Billing models: e.g. Prepaid monthly
* Applications: All incl telephony
* Network / Topology: full mesh / inframesh
* Internet uplink: typically yes, but local net relevant
* User Devices / Locations: all types of devices, at user homes / office / businesses, roaming users
* Startup Strategy:
* Legal & Regulatory: potential issues withpower limits, collision with other networks, DSL reuse / resell

===Training / Consultancy===

A side business, outside scope for this project, but clearly relevant.

= Notes from the meeting - Day 3=

==Ndlovu Medical Centre==

Henry introduces:

* Status of mesh: operational, but currently disconnected (concerns about lightning)
* Use of uplink: Browsing (for community users), sync with data center (Johannesburg)
* Status of uplink: promised by Telkom, but not delivered yet

How to get started with a community mesh?

* Donated PCs - 25 pcs
** Give to local entrepreneur types
* Computer school as entry point

* Create a starter kit
** for existing PCs (there is some! mostly free windows)
** preconfigured
** low cost
** probably of the type: Linksys WRT, open-mesh/accton

Financing model

* Some contribution from user: Prepaid - low cost

What is interesting for people?

* music!!! open music server locally?
* free books? educational material
* free local calls
* a free wikipedia / digital doorway

Income from other sources (not the users):

* advertisements

To do / upcoming:

* '''call for a brainstorm meeting within the community'''

* June 9, meeting with provincial directory

* June 24: excursion to Ndlovu? participants of Wireless Africa meeting, Meraka people, Tom, Elektra

Top pain points / whats in the way:

* political level - get OKs from important players

==Hardware reference platform==

===Overall Requirements===

* 12 Volts (best: 11 ... 16)
* low power
* fanless

===Backend server===

* USB 2x
* ethernet 2x
* VGA

Candidate for reference choice:

* bigger solution: VIA, jetway 1.2 GHz, 2x HD, 1 GB RAM, USD 680 ... 820 [http://mini-box.com e.g. mini-box-com]
** power: approx 25W ?
* smaller solution: VIA, AMD Geode 500 MHz
** power: 8 W
* LEX light/neo, e.g. 1 GB C7 approx USD 600 [http://www.lex.com.tw/ http://www.lex.com.tw/]
* soon to come: Atom based low cost desktops (Mark Summer)
* alternatives: [http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99 http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99]

====Software on backend====

Decision: Ubuntu (non X)

----

===Access node===

* ethernet 2x
* PoE
* outdoor casing
* broadcom or atheros chipset
* 5 ... 18 Volts
* Watchdog (option)
* WISPCAR (option)
* serial port

Candidates:

* Linksys WRT54GL
** price: EUR 50, ZAR 600, USD 60
** power: 4 W
** comments:

* Ubiqiti
** price: NS 2: USD 79
** price: PS 2: USD 110
** power: 5 W

* Accton
** price: USD 40
** power: 2-3 W ?
** comments: overheat problems? needs fixed power 5 V? quality of radio? unstable across channels?

* PCEngines board
** price: > USD 250
** power: approx > 8W, depending on radio cards
** comments:

* Soekris

* Gateworks
**
**

* Wiligear

===Solar powering: A word on the fine for every watt installed===

Elektra makes the conservative estimate:

To power a 5 Watt device reliably, install a 80 Watt solar panel.
This means: 16 Watt solar panel per 1 Watt installed.

At about USD 5 per solar panel watt (current rough guess for market price), we have:

USD 80 in solar panel per 1 Watt installed.

Even when demanding less margin from the solar power system (i.e. less reliability, more optimism), the fine for every Watt installed is heavy.

==Next steps==

* Cape Town Village Telco worksprint
* Kobus, Johann, Elektra
** We need a presentation - Sebastian sends to Kobus and all - dead: june 10
*** Metaphores: pipes - water / roads - cars /
** Minutes / Doc

* Software development
** Meraka - Priority: the set of Coova (alternative: WifiDog) / FreeRadius / phpMyPrepaid (alternative: ISPBill) / Nagios
** Inveneo - Priority: IHL, Server squid/cache, proxy, asterisk, Webmin/ISPConfig
** How to work together? SVN server ? location ? Meraka machines accessible form outside?

* Examine the Ubiquiti - Lead: Elektra
** flash OpenWRT [http://wiki.openwrt.org/OpenWrtDocs/Hardware/Ubiquiti OpenWrt Ubiquiti]
** Examine the SDK
** examine internal antenna pol switching (AAP)

* Procurement - Lead: Kobus/Ajay ?
** ??? x Inveneo small server, or Via direct
** Ubiquiti Nano/Powerstation
** Linksyses: assume we ave enough
** Solar power: one demo system until June 23 - ask Grant: 64 W panel, charge controller, batteries (

* Examine the [http://wiki.inveneo.org/index.php/Inveneo_Server_Linux_1.x Inveneo Hub Linux (IHL)] - Elektra / George

* Examine Open-Mesh - Lead: Sebastian
** talk to them, examine status and development

* Establish Documentation on Wiki

WISPiab work meeting 200806

2008-06-05T08:01:14Z

Sebastian: /* Next steps */

[[Category: WISP in a box]]

=Work meeting of the WISP-in-a-box project=

[[The WISP-in-a-box project]]

=Date=

June 2-3-4, 2008

9-17 h

=Location=

Meraka Institute,
Building 43 C,
Hummingbird Room (C128, ground floor)

Pretoria

=Invitation List=

People and organisations with an active interest in building a concrete product that
helps bringing

connectivity to underserviced, underprivileged and overcharged communities in Africa.

Invitation list:

* Steve Song / Shuttleworth Foundation (monday only)
* Rael Lissoos / Dabba
* Henry Marnitz / Ndlovu Medical Centre (wednesday only)
* Mark Summer, Inveneo (with request to forward to Ubiquiti)
* Elektra
* Mike Jensen (not confirmed)
* Kobus Roux, Meraka (NOT monday)
* Karel Matthee, Meraka
* Kim Gush, Meraka
* David Johnson, Meraka
* Chris Morris, Meraka
* Grant Cambridge, Meraka
* Shela Boshomane, Meraka (monday and wednesday)
* George James, Meraka
* Johann Hugo, Meraka
* John Hay, Meraka
* Ajay Makan, Meraka
* Sebastian Buettrich

More proposals are welcome!

Budgets for travel, if needed: Please contact us!

=Contact=

Sebastian

mail: sebastian@less.dk

skype: sebastian_buettrich

cell: (+27) (0) 79 915 32 92

=Timeplan=

The timeplan is draft level and will be adjusted to people's ability to join for limited periods.

'''The first day''' will be dedicated to the '''organizational layer''',

introducing the various projects and teams,
discussing the business models,
identifying overlap of work agendas as well as the main challenges each of the projects are seeing.

'''The second day''' will move down to detail level,
moving from business and organizational models to technology requirements/specifications.

The third day

==Day 1 - Monday, June 2==

===Morning===

====Creating Context====

Introductions, Presentations of participants

(Short 10 mns, informal project introductions)

* Introduction and WISPiab Project (Sebastian Buettrich)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Ndlovu Medical Centre (Henry Marnitz) (moved to Wednesday, June 4)
* Peeble's Valley Mesh (David Johnson)
* Digital Doorway (tba)
* Inveneo platform (Mark Summer)
* WISPiab work status (George James)
* Wireless Africa project (Chris Morris)
* Freifunk, B.a.t.m.a.n. & Meraka Mesh Testbed (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* IP04 (it46, rowetel) (on behalf of the project: Sebastian Buettrich)

===Afternoon===

====Business models====

Introduction: Sebastian

Business models may be classified according to a number of different dimensions -

e.g. financial/economic layer, tech/network topology layer, applications layer, social layer, -

Based on the experience of the participants and projects,
business models should be reviewed with the goal of reaching a downselection of models that should be implemented/supported
in the first iteration of the WISPiab project.

Classical examples:

* Voice services - The Village Telco
* "Line sharing" - sharing internet access between organizations
* Telecentre / Internet Cafe
* Campus / School network

'''The goal''' is to go through all our relevant models, to classify them on all layers,

and to identify the technology implications (such that technology follows business models, and not vice versa), producing a clear results list.

====Cooperations and Resources====

There is significant overlap between projects on the technology layer.
All projects are subscribing to free software models (GPL / CC, etc).

We are operating against a backdrop of

* challenged (human) resource situation
* brain drain / skills exodus
* wanting to build local (i.e. african? ... southern african? .... south african?) capacity

Cooperation between projects seems appropriate and possible.

'''The goal''' is to conclude this meeting with a clear picture of modes of cooperation.

====Advisory Group====

We wish to form an advisory group / peer group, including partly the invitees of this meeting, but not limited to these.

==Day 2 - Tuesday, June 3==

===Morning===

====Technical Requirements / Specifications - detail level====

Examples of concrete detail issues:

* Authentication - where and how
* Billing in mesh networks
* VoIP in mesh networks

'''The goal''' of this session is to fill the matrix of

''technology requirements x project/business model''

and then check this matrix against the various existing hardware/software platforms.

====Hardware platforms aspects====

A number of different hardware/software platforms are fulfilling subsets of our requirements.

The available platforms need to be discussed and evaluated, towards a decision on what to choose.

The platforms that our projects are currently working with are:

* Linksys WRT54, with firmwares OpenWRT, DD-WRT, Freifunk, CoovaAP, and similar
* Open-Mesh, Accton - with Open Mesh Firmware (new firmware anoounced for summer 2008, with: RO.B.IN, orangemesh, COOVA, etc)
* Inveneo platform
* Ubiquti NS, PS
* Meraka Bokkie routers
* pls add!

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Productification / Dissemination / Rollout strategies====

* Strategies for the productification of software packages
** Sourceforge platform plans (Steve?)
** Ubuntu / UCK (Sebastian, Mark, Elektra)
* Rollout capacity

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

==Day 3 - Wednesday, June 4==

===Morning===

==== Ndlovu Medical Center====

Status and Agenda of network at Ndlovu Medical Center

* How can the various projects benefit Ndlovu Medical Center?

====Status, gaps and planning of implementations====

* WISPiab status and work plan
* Dabba / Village Telco work sprint, June 16-20
** prepare and support that workshop

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Conclusions & Next steps====

* Dabba Worksprint
* WISPiab work plan
* Digital Doorway work
* Wireless Africa, June meeting

etc

= Notes from the meeting - Day 1=

==People & Project introductions==

* Introduction and WISPiab Project (Sebastian Buettrich)
* Peeble's Valley Mesh (David Johnson)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Inveneo platform (Mark Summer)
* Freifunk (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* WISPiab work status (George James)
* Two radio mesh router (Johann Hugo)
* Wireless Africa project (Chris Morris)

==Forming an Alliance?==

to be edited

= Notes from the meeting - Day 2=
[[Image:Day2 - WISPiab_Wkshop.jpg|left|thumb|350px|Day2 (L-R) Mark Summer, Johann Hugo, Mike Jensen, Elektra, Sebastian Buettrich, Kobus Roux, George James, Ajay Makan, Karel Matthee
]]

 

==Requirements, Specifications, Wishlist==

We chose the GUI [http://dabba.co.za/wispgui wishlist by Dabba] as an entry to discussing our current specifications set, identifying how we cover the single elements today, identifying dependencies, etc

[[Image:WISPiab meeting 20080603 whiteboard 1.jpg|thumb|left| Whiteboard Day 2]]
[[Image:Working_Logo.jpg|thumb|left|Table context]]

{| border="1" cellpadding="7" cellspacing="0"
!align="left" |What?
!align="left" |Which element
!align="left" |Existing
!align="left" |Who/how
!align="left" |Alternate names/terms
!align="left" |Task
|-
|Network Settings
|core
|FF, IHL, Coova (wifidog) + alternatives, Linksys & Netgear interfaces
|
|Network Management, Setup,
|
|-
|ISP settings
|core
|Coova, phpMyPrepaid, OpenWRT (QoS script) (...)shaper
|
|user/service profiles – provisioning (some of it -> QoS)
|
|-
|VoIP Settings Users, tarriffs
|voice
|AsteriskNow IP04 HW, Trixbox, A2billing, (Open)SER
|
| -->user profiles, --> VoIP settings
|
|-
|Prepaid Card System (print cards) (ops), ->web, ->voice
|web,voice
|phpMyPrepaid, A2billing
|
|“usage”
|
|-
|CRM
|core
|compiere
|
|
|
|-
|Accounting -->logs
|core
|phpMyPrepaid, a2billing
|
| ->(if bill) ->ERP
|
|-
|Logo/Company
|core
|(all components have some of it)
|
|themes/skins/ customisation
|
|-
|Network Monitoring
|
|Nagios, Open-Mesh, Open NMS, FF (some), MRTG/rrdtool
|
|Network management
|
|-
|Content
|
|
|
|
|
|-
|Video Server
|
|
|
|
|
|-
|Cache\Proxy with stats
|
|squid with awstats
|
|
|
|-
|Mail
|
|
|
|
|
|-
|Security encryption
|
|
|
|
|
|-
|httpd, with stats etc
|
|apache, awstats
|
|
|
|-
|Wiki / image hosting
|
|
|
|
|
|-
|Telecentre management
|
|UgaBytes telecentre management software?
|
|
|
|-
|}

==Business Models==

Discussion of business models that have informed the specifications, and a checkback whether we feel that the current specifications actually accomodate all these models.

The template on top suggests dimensions / criteria from which to look at the various models.

===Business Model Template===

* Description:

* Economics: Free or paid by ....
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications:
* Network / Topology:
* Internet uplink:
* User Devices / Locations:
* Startup Strategy:
* Legal & Regulatory

===Telecentre / Internet Cafe / Hotspot===

* Description: "Classical" telecentre / cafe style

* Economics: Free or paid by users / advertisers / cafe business
* Billing models: typically Prepaid (Time based):
* Applications: typically Browser / Mail / Office / Games
* Network / Topology: wired LAN
* Internet uplink: model works with and without uplink, but typically yes
* User Devices / Locations: Users on business owned PC
* Startup Strategy:
* Legal & Regulatory: ok in most (?) countries

===Telco===

* Description: Telco offering "fixed line" and mobile VoIP telephony

* Economics: Part free (?) (local) / paid by user
* Billing models: typically Prepaid (Time/Data based):
* Applications: VoIP telephony, typically on dedicated hardware
* Network / Topology: Centralized / Inframesh
* Internet uplink: Yes, if terminating external calls / local loop without
* User Devices / Locations: Users at home / office / mobile, Device VoIP handsets, ATA etc
* Startup Strategy:
* Legal & Regulatory: complex, country to country

===(Edu)Content / Media===

* Economics: Free or paid by user / external
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications: Browser, Video, Image, Sound apps
* Network / Topology: n/a
* Internet uplink: not neccessarily, but recommended
* User Devices / Locations: all kinds of devices, local/remote,
* Startup Strategy:
* Legal & Regulatory: apart from restrictions on content, no issues

===Intranet / Neighbour-Net===

* Economics: Typically paid by customer
* Billing models: Contract / "Subscription"
* Applications: All PC apps
* Network / Topology: typically centralized, might be mesh
* Internet uplink: not neccessarily, but recommended
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy:
* Legal & Regulatory: no issues

===Line Sharing===

* Economics: Typically paid by users, in split scheme (e.g. cost per user = (line cost / # of users)*(marginfactor))
* Billing models: Prepaid monthly
* Applications: All PC apps
* Network / Topology: centralized or mesh
* Internet uplink: yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy: bottom up, organic
* Legal & Regulatory: potential issues with DSL or line resell (?), power limits for wireless part

===ISP===

* Economics: Typically user paid
* Billing models: Prepaid monthly, subscription
* Applications: All apps
* Network / Topology: centralized or mesh
* Internet uplink: yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy:
* Legal & Regulatory: regulations for ISP ops, licensing etc

===Web Hosting / Design===

A potential part of an ISPs business.
Seen as outside scope of this project, however simple home pages / website very common and demanded.
E.g. local businesses, etc

===Corporate / Managed Services===

* Economics: Typically user paid
* Billing models: Prepaid monthly, subscription
* Applications: All apps
* Network / Topology: centralized or mesh
* Internet uplink: typically yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy: company initiative
* Legal & Regulatory: potential issues when mixed user groups share same network (e.g. private, corp, gov, etc)

Strong focus on security (all aspects), network separation, QoS, management.

===Guesthouse Net===

* Economics: Typically user (= guesthouse) paid, might be free for customer of guesthouse, or paid for
* Billing models: if paid for, typically voucher prepaid, time based
* Applications: All apps
* Network / Topology: typically centralized
* Internet uplink: yes
* User Devices / Locations: users devices, maybe one or several public access PC
* Startup Strategy: guesthouse initiative
* Legal & Regulatory: no issues

===Housing Complex===

similar to Intranet / Neighbournet

* Economics: Typically user paid, might be included in other service charges or rent
* Billing models: Prepaid monthly or longer term, subscription
* Applications: All apps
* Network / Topology: centralized or mesh, often wired
* Internet uplink: typically yes
* User Devices / Locations: PCs and other, local at homes
* Startup Strategy: owner initiative
* Legal & Regulatory: no issues

===Surveillance===

* Economics: Typically customer paid
* Billing models: Prepaid monthly, subscription
* Applications: Very specific, wireless surveillance cams, motion detectors, etc
* Network / Topology: centralized or mesh
* Internet uplink: typically yes, in order to allow for remote control and alerts
* User Devices / Locations: surveillance gear and control units, typically PC/browser/mobile (SMS notifications)
* Startup Strategy:
* Legal & Regulatory: generally no issues when limited to company/housing premises. issues when extending into public space. ethics.

===Freifunk style Mesh===

* Economics: Typically completely user paid, informal, but might implement business scheme similar to line sharing ((e.g. cost per user = (central uplink cost / # of users)*(marginfactor))
* Billing models: e.g. Prepaid monthly
* Applications: All incl telephony
* Network / Topology: full mesh / inframesh
* Internet uplink: typically yes, but local net relevant
* User Devices / Locations: all types of devices, at user homes / office / businesses, roaming users
* Startup Strategy:
* Legal & Regulatory: potential issues withpower limits, collision with other networks, DSL reuse / resell

===Training / Consultancy===

A side business, outside scope for this project, but clearly relevant.

= Notes from the meeting - Day 3=

==Ndlovu Medical Centre==

Henry introduces:

* Status of mesh: operational, but currently disconnected (concerns about lightning)
* Use of uplink: Browsing (for community users), sync with data center (Johannesburg)
* Status of uplink: promised by Telkom, but not delivered yet

How to get started with a community mesh?

* Donated PCs - 25 pcs
** Give to local entrepreneur types
* Computer school as entry point

* Create a starter kit
** for existing PCs (there is some! mostly free windows)
** preconfigured
** low cost
** probably of the type: Linksys WRT, open-mesh/accton

Financing model

* Some contribution from user: Prepaid - low cost

What is interesting for people?

* music!!! open music server locally?
* free books? educational material
* free local calls
* a free wikipedia / digital doorway

Income from other sources (not the users):

* advertisements

To do / upcoming:

* '''call for a brainstorm meeting within the community'''

* June 9, meeting with provincial directory

* June 24: excursion to Ndlovu? participants of Wireless Africa meeting, Meraka people, Tom, Elektra

Top pain points / whats in the way:

* political level - get OKs from important players

==Hardware reference platform==

===Overall Requirements===

* 12 Volts (best: 11 ... 16)
* low power
* fanless

===Backend server===

* USB 2x
* ethernet 2x
* VGA

Candidate for reference choice:

* bigger solution: VIA, jetway 1.2 GHz, 2x HD, 1 GB RAM, USD 680 ... 820 [http://mini-box.com e.g. mini-box-com]
** power: approx 25W ?
* smaller solution: VIA, AMD Geode 500 MHz
** power: 8 W
* LEX light/neo, e.g. 1 GB C7 approx USD 600 [http://www.lex.com.tw/ http://www.lex.com.tw/]
* soon to come: Atom based low cost desktops (Mark Summer)
* alternatives: [http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99 http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99]

====Software on backend====

Decision: Ubuntu (non X)

----

===Access node===

* ethernet 2x
* PoE
* outdoor casing
* broadcom or atheros chipset
* 5 ... 18 Volts
* Watchdog (option)
* WISPCAR (option)
* serial port

Candidates:

* Linksys WRT54GL
** price: EUR 50, ZAR 600, USD 60
** power: 4 W
** comments:

* Ubiqiti
** price: NS 2: USD 79
** price: PS 2: USD 110
** power: 5 W

* Accton
** price: USD 40
** power: 2-3 W ?
** comments: overheat problems? needs fixed power 5 V? quality of radio? unstable across channels?

* PCEngines board
** price: > USD 250
** power: approx > 8W, depending on radio cards
** comments:

* Soekris

* Gateworks
**
**

* Wiligear

===Solar powering: A word on the fine for every watt installed===

Elektra makes the conservative estimate:

To power a 5 Watt device reliably, install a 80 Watt solar panel.
This means: 16 Watt solar panel per 1 Watt installed.

At about USD 5 per solar panel watt (current rough guess for market price), we have:

USD 80 in solar panel per 1 Watt installed.

Even when demanding less margin from the solar power system (i.e. less reliability, more optimism), the fine for every Watt installed is heavy.

==Next steps==

* Cape Town Village Telco worksprint

* Examine the Ubiquiti - Lead: Elektra
** flash OpenWRT [http://wiki.openwrt.org/OpenWrtDocs/Hardware/Ubiquiti OpenWrt Ubiquiti]
** Examine the SDK
** examine internal antenna pol switching (AAP)

* Procurement - Lead: Kobus/Ajay ?
** ??? x Inveneo small server, or Via direct
** Ubiquiti Nano/Powerstation
** Linksyses: assume we ave enough
** Solar power: one demo system until June 23 - ask Grant: 64 W panel, charge controller, batteries (

* Examine the [http://wiki.inveneo.org/index.php/Inveneo_Server_Linux_1.x Inveneo Hub Linux (IHL)] - Elektra / George

* Software development
** Meraka - Priority: the set of Coova (alternative: WifiDog) / FreeRadius / phpMyPrepaid (alternative: ISPBill) / Nagios
** Inveneo - Priority: IHL, Server squid/cache, proxy, asterisk, Webmin/ISPConfig
** How to work together? SVN server ? location ? Meraka machines accessible form outside?

* Examine Open-Mesh - Lead: Sebastian
** talk to them, examine status and development

* Establish Documentation on Wiki

WISPiab work meeting 200806

2008-06-05T07:42:38Z

Sebastian:

[[Category: WISP in a box]]

=Work meeting of the WISP-in-a-box project=

[[The WISP-in-a-box project]]

=Date=

June 2-3-4, 2008

9-17 h

=Location=

Meraka Institute,
Building 43 C,
Hummingbird Room (C128, ground floor)

Pretoria

=Invitation List=

People and organisations with an active interest in building a concrete product that
helps bringing

connectivity to underserviced, underprivileged and overcharged communities in Africa.

Invitation list:

* Steve Song / Shuttleworth Foundation (monday only)
* Rael Lissoos / Dabba
* Henry Marnitz / Ndlovu Medical Centre (wednesday only)
* Mark Summer, Inveneo (with request to forward to Ubiquiti)
* Elektra
* Mike Jensen (not confirmed)
* Kobus Roux, Meraka (NOT monday)
* Karel Matthee, Meraka
* Kim Gush, Meraka
* David Johnson, Meraka
* Chris Morris, Meraka
* Grant Cambridge, Meraka
* Shela Boshomane, Meraka (monday and wednesday)
* George James, Meraka
* Johann Hugo, Meraka
* John Hay, Meraka
* Ajay Makan, Meraka
* Sebastian Buettrich

More proposals are welcome!

Budgets for travel, if needed: Please contact us!

=Contact=

Sebastian

mail: sebastian@less.dk

skype: sebastian_buettrich

cell: (+27) (0) 79 915 32 92

=Timeplan=

The timeplan is draft level and will be adjusted to people's ability to join for limited periods.

'''The first day''' will be dedicated to the '''organizational layer''',

introducing the various projects and teams,
discussing the business models,
identifying overlap of work agendas as well as the main challenges each of the projects are seeing.

'''The second day''' will move down to detail level,
moving from business and organizational models to technology requirements/specifications.

The third day

==Day 1 - Monday, June 2==

===Morning===

====Creating Context====

Introductions, Presentations of participants

(Short 10 mns, informal project introductions)

* Introduction and WISPiab Project (Sebastian Buettrich)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Ndlovu Medical Centre (Henry Marnitz) (moved to Wednesday, June 4)
* Peeble's Valley Mesh (David Johnson)
* Digital Doorway (tba)
* Inveneo platform (Mark Summer)
* WISPiab work status (George James)
* Wireless Africa project (Chris Morris)
* Freifunk, B.a.t.m.a.n. & Meraka Mesh Testbed (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* IP04 (it46, rowetel) (on behalf of the project: Sebastian Buettrich)

===Afternoon===

====Business models====

Introduction: Sebastian

Business models may be classified according to a number of different dimensions -

e.g. financial/economic layer, tech/network topology layer, applications layer, social layer, -

Based on the experience of the participants and projects,
business models should be reviewed with the goal of reaching a downselection of models that should be implemented/supported
in the first iteration of the WISPiab project.

Classical examples:

* Voice services - The Village Telco
* "Line sharing" - sharing internet access between organizations
* Telecentre / Internet Cafe
* Campus / School network

'''The goal''' is to go through all our relevant models, to classify them on all layers,

and to identify the technology implications (such that technology follows business models, and not vice versa), producing a clear results list.

====Cooperations and Resources====

There is significant overlap between projects on the technology layer.
All projects are subscribing to free software models (GPL / CC, etc).

We are operating against a backdrop of

* challenged (human) resource situation
* brain drain / skills exodus
* wanting to build local (i.e. african? ... southern african? .... south african?) capacity

Cooperation between projects seems appropriate and possible.

'''The goal''' is to conclude this meeting with a clear picture of modes of cooperation.

====Advisory Group====

We wish to form an advisory group / peer group, including partly the invitees of this meeting, but not limited to these.

==Day 2 - Tuesday, June 3==

===Morning===

====Technical Requirements / Specifications - detail level====

Examples of concrete detail issues:

* Authentication - where and how
* Billing in mesh networks
* VoIP in mesh networks

'''The goal''' of this session is to fill the matrix of

''technology requirements x project/business model''

and then check this matrix against the various existing hardware/software platforms.

====Hardware platforms aspects====

A number of different hardware/software platforms are fulfilling subsets of our requirements.

The available platforms need to be discussed and evaluated, towards a decision on what to choose.

The platforms that our projects are currently working with are:

* Linksys WRT54, with firmwares OpenWRT, DD-WRT, Freifunk, CoovaAP, and similar
* Open-Mesh, Accton - with Open Mesh Firmware (new firmware anoounced for summer 2008, with: RO.B.IN, orangemesh, COOVA, etc)
* Inveneo platform
* Ubiquti NS, PS
* Meraka Bokkie routers
* pls add!

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Productification / Dissemination / Rollout strategies====

* Strategies for the productification of software packages
** Sourceforge platform plans (Steve?)
** Ubuntu / UCK (Sebastian, Mark, Elektra)
* Rollout capacity

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

==Day 3 - Wednesday, June 4==

===Morning===

==== Ndlovu Medical Center====

Status and Agenda of network at Ndlovu Medical Center

* How can the various projects benefit Ndlovu Medical Center?

====Status, gaps and planning of implementations====

* WISPiab status and work plan
* Dabba / Village Telco work sprint, June 16-20
** prepare and support that workshop

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Conclusions & Next steps====

* Dabba Worksprint
* WISPiab work plan
* Digital Doorway work
* Wireless Africa, June meeting

etc

= Notes from the meeting - Day 1=

==People & Project introductions==

* Introduction and WISPiab Project (Sebastian Buettrich)
* Peeble's Valley Mesh (David Johnson)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Inveneo platform (Mark Summer)
* Freifunk (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* WISPiab work status (George James)
* Two radio mesh router (Johann Hugo)
* Wireless Africa project (Chris Morris)

==Forming an Alliance?==

to be edited

= Notes from the meeting - Day 2=
[[Image:Day2 - WISPiab_Wkshop.jpg|left|thumb|350px|Day2 (L-R) Mark Summer, Johann Hugo, Mike Jensen, Elektra, Sebastian Buettrich, Kobus Roux, George James, Ajay Makan, Karel Matthee
]]

 

==Requirements, Specifications, Wishlist==

We chose the GUI [http://dabba.co.za/wispgui wishlist by Dabba] as an entry to discussing our current specifications set, identifying how we cover the single elements today, identifying dependencies, etc

[[Image:WISPiab meeting 20080603 whiteboard 1.jpg|thumb|left| Whiteboard Day 2]]
[[Image:Working_Logo.jpg|thumb|left|Table context]]

{| border="1" cellpadding="7" cellspacing="0"
!align="left" |What?
!align="left" |Which element
!align="left" |Existing
!align="left" |Who/how
!align="left" |Alternate names/terms
!align="left" |Task
|-
|Network Settings
|core
|FF, IHL, Coova (wifidog) + alternatives, Linksys & Netgear interfaces
|
|Network Management, Setup,
|
|-
|ISP settings
|core
|Coova, phpMyPrepaid, OpenWRT (QoS script) (...)shaper
|
|user/service profiles – provisioning (some of it -> QoS)
|
|-
|VoIP Settings Users, tarriffs
|voice
|AsteriskNow IP04 HW, Trixbox, A2billing, (Open)SER
|
| -->user profiles, --> VoIP settings
|
|-
|Prepaid Card System (print cards) (ops), ->web, ->voice
|web,voice
|phpMyPrepaid, A2billing
|
|“usage”
|
|-
|CRM
|core
|compiere
|
|
|
|-
|Accounting -->logs
|core
|phpMyPrepaid, a2billing
|
| ->(if bill) ->ERP
|
|-
|Logo/Company
|core
|(all components have some of it)
|
|themes/skins/ customisation
|
|-
|Network Monitoring
|
|Nagios, Open-Mesh, Open NMS, FF (some), MRTG/rrdtool
|
|Network management
|
|-
|Content
|
|
|
|
|
|-
|Video Server
|
|
|
|
|
|-
|Cache\Proxy with stats
|
|squid with awstats
|
|
|
|-
|Mail
|
|
|
|
|
|-
|Security encryption
|
|
|
|
|
|-
|httpd, with stats etc
|
|apache, awstats
|
|
|
|-
|Wiki / image hosting
|
|
|
|
|
|-
|Telecentre management
|
|UgaBytes telecentre management software?
|
|
|
|-
|}

==Business Models==

Discussion of business models that have informed the specifications, and a checkback whether we feel that the current specifications actually accomodate all these models.

The template on top suggests dimensions / criteria from which to look at the various models.

===Business Model Template===

* Description:

* Economics: Free or paid by ....
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications:
* Network / Topology:
* Internet uplink:
* User Devices / Locations:
* Startup Strategy:
* Legal & Regulatory

===Telecentre / Internet Cafe / Hotspot===

* Description: "Classical" telecentre / cafe style

* Economics: Free or paid by users / advertisers / cafe business
* Billing models: typically Prepaid (Time based):
* Applications: typically Browser / Mail / Office / Games
* Network / Topology: wired LAN
* Internet uplink: model works with and without uplink, but typically yes
* User Devices / Locations: Users on business owned PC
* Startup Strategy:
* Legal & Regulatory: ok in most (?) countries

===Telco===

* Description: Telco offering "fixed line" and mobile VoIP telephony

* Economics: Part free (?) (local) / paid by user
* Billing models: typically Prepaid (Time/Data based):
* Applications: VoIP telephony, typically on dedicated hardware
* Network / Topology: Centralized / Inframesh
* Internet uplink: Yes, if terminating external calls / local loop without
* User Devices / Locations: Users at home / office / mobile, Device VoIP handsets, ATA etc
* Startup Strategy:
* Legal & Regulatory: complex, country to country

===(Edu)Content / Media===

* Economics: Free or paid by user / external
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications: Browser, Video, Image, Sound apps
* Network / Topology: n/a
* Internet uplink: not neccessarily, but recommended
* User Devices / Locations: all kinds of devices, local/remote,
* Startup Strategy:
* Legal & Regulatory: apart from restrictions on content, no issues

===Intranet / Neighbour-Net===

* Economics: Typically paid by customer
* Billing models: Contract / "Subscription"
* Applications: All PC apps
* Network / Topology: typically centralized, might be mesh
* Internet uplink: not neccessarily, but recommended
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy:
* Legal & Regulatory: no issues

===Line Sharing===

* Economics: Typically paid by users, in split scheme (e.g. cost per user = (line cost / # of users)*(marginfactor))
* Billing models: Prepaid monthly
* Applications: All PC apps
* Network / Topology: centralized or mesh
* Internet uplink: yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy: bottom up, organic
* Legal & Regulatory: potential issues with DSL or line resell (?), power limits for wireless part

===ISP===

* Economics: Typically user paid
* Billing models: Prepaid monthly, subscription
* Applications: All apps
* Network / Topology: centralized or mesh
* Internet uplink: yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy:
* Legal & Regulatory: regulations for ISP ops, licensing etc

===Web Hosting / Design===

A potential part of an ISPs business.
Seen as outside scope of this project, however simple home pages / website very common and demanded.
E.g. local businesses, etc

===Corporate / Managed Services===

* Economics: Typically user paid
* Billing models: Prepaid monthly, subscription
* Applications: All apps
* Network / Topology: centralized or mesh
* Internet uplink: typically yes
* User Devices / Locations: PCs and other, local at office or homes
* Startup Strategy: company initiative
* Legal & Regulatory: potential issues when mixed user groups share same network (e.g. private, corp, gov, etc)

Strong focus on security (all aspects), network separation, QoS, management.

===Guesthouse Net===

* Economics: Typically user (= guesthouse) paid, might be free for customer of guesthouse, or paid for
* Billing models: if paid for, typically voucher prepaid, time based
* Applications: All apps
* Network / Topology: typically centralized
* Internet uplink: yes
* User Devices / Locations: users devices, maybe one or several public access PC
* Startup Strategy: guesthouse initiative
* Legal & Regulatory: no issues

===Housing Complex===

similar to Intranet / Neighbournet

* Economics: Typically user paid, might be included in other service charges or rent
* Billing models: Prepaid monthly or longer term, subscription
* Applications: All apps
* Network / Topology: centralized or mesh, often wired
* Internet uplink: typically yes
* User Devices / Locations: PCs and other, local at homes
* Startup Strategy: owner initiative
* Legal & Regulatory: no issues

===Surveillance===

* Economics: Typically customer paid
* Billing models: Prepaid monthly, subscription
* Applications: Very specific, wireless surveillance cams, motion detectors, etc
* Network / Topology: centralized or mesh
* Internet uplink: typically yes, in order to allow for remote control and alerts
* User Devices / Locations: surveillance gear and control units, typically PC/browser/mobile (SMS notifications)
* Startup Strategy:
* Legal & Regulatory: generally no issues when limited to company/housing premises. issues when extending into public space. ethics.

===Freifunk style Mesh===

* Economics: Typically completely user paid, informal, but might implement business scheme similar to line sharing ((e.g. cost per user = (central uplink cost / # of users)*(marginfactor))
* Billing models: e.g. Prepaid monthly
* Applications: All incl telephony
* Network / Topology: full mesh / inframesh
* Internet uplink: typically yes, but local net relevant
* User Devices / Locations: all types of devices, at user homes / office / businesses, roaming users
* Startup Strategy:
* Legal & Regulatory: potential issues withpower limits, collision with other networks, DSL reuse / resell

===Training / Consultancy===

A side business, outside scope for this project, but clearly relevant.

= Notes from the meeting - Day 3=

==Ndlovu Medical Centre==

Henry introduces:

* Status of mesh: operational, but currently disconnected (concerns about lightning)
* Use of uplink: Browsing (for community users), sync with data center (Johannesburg)
* Status of uplink: promised by Telkom, but not delivered yet

How to get started with a community mesh?

* Donated PCs - 25 pcs
** Give to local entrepreneur types
* Computer school as entry point

* Create a starter kit
** for existing PCs (there is some! mostly free windows)
** preconfigured
** low cost
** probably of the type: Linksys WRT, open-mesh/accton

Financing model

* Some contribution from user: Prepaid - low cost

What is interesting for people?

* music!!! open music server locally?
* free books? educational material
* free local calls
* a free wikipedia / digital doorway

Income from other sources (not the users):

* advertisements

To do / upcoming:

* '''call for a brainstorm meeting within the community'''

* June 9, meeting with provincial directory

* June 24: excursion to Ndlovu? participants of Wireless Africa meeting, Meraka people, Tom, Elektra

Top pain points / whats in the way:

* political level - get OKs from important players

==Hardware reference platform==

===Overall Requirements===

* 12 Volts (best: 11 ... 16)
* low power
* fanless

===Backend server===

* USB 2x
* ethernet 2x
* VGA

Candidate for reference choice:

* bigger solution: VIA, jetway 1.2 GHz, 2x HD, 1 GB RAM, USD 680 ... 820 [http://mini-box.com e.g. mini-box-com]
** power: approx 25W ?
* smaller solution: VIA, AMD Geode 500 MHz
** power: 8 W
* LEX light/neo, e.g. 1 GB C7 approx USD 600 [http://www.lex.com.tw/ http://www.lex.com.tw/]
* soon to come: Atom based low cost desktops (Mark Summer)
* alternatives: [http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99 http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99]

====Software on backend====

Decision: Ubuntu (non X)

----

===Access node===

* ethernet 2x
* PoE
* outdoor casing
* broadcom or atheros chipset
* 5 ... 18 Volts
* Watchdog (option)
* WISPCAR (option)
* serial port

Candidates:

* Linksys WRT54GL
** price: EUR 50, ZAR 600, USD 60
** power: 4 W
** comments:

* Ubiqiti
** price: NS 2: USD 79
** price: PS 2: USD 110
** power: 5 W

* Accton
** price: USD 40
** power: 2-3 W ?
** comments: overheat problems? needs fixed power 5 V? quality of radio? unstable across channels?

* PCEngines board
** price: > USD 250
** power: approx > 8W, depending on radio cards
** comments:

* Soekris

* Gateworks
**
**

* Wiligear

===Solar powering: A word on the fine for every watt installed===

Elektra makes the conservative estimate:

To power a 5 Watt device reliably, install a 80 Watt solar panel.
This means: 16 Watt solar panel per 1 Watt installed.

At about USD 5 per solar panel watt (current rough guess for market price), we have:

USD 80 in solar panel per 1 Watt installed.

Even when demanding less margin from the solar power system (i.e. less reliability, more optimism), the fine for every Watt installed is heavy.

==Next steps==

* Examine the Ubiquiti - Lead: Elektra
** flash OpenWRT
** Examine the SDK

* Procurement - Lead: Kobus/Ajay
** ??? x Inveneo small server
**

* Examine the Inveneo Hub Linux (IHL)

* Software development
** Meraka - Priority: the set of Coova (alternative: WifiDog) / FreeRadius / phpMyPrepaid (alternative: ISPBill) / Nagios
** Inveneo - Priority: Server squid/cache, proxy, asterisk, Webmin/ISPConfig

WISPiab work meeting 200806

2008-06-04T15:37:07Z

Sebastian: /* Backend server */

[[Category: WISP in a box]]

=Work meeting of the WISP-in-a-box project=

[[The WISP-in-a-box project]]

=Date=

June 2-3-4, 2008

9-17 h

=Location=

Meraka Institute,
Building 43 C,
Hummingbird Room (C128, ground floor)

Pretoria

=Invitation List=

People and organisations with an active interest in building a concrete product that
helps bringing

connectivity to underserviced, underprivileged and overcharged communities in Africa.

Invitation list:

* Steve Song / Shuttleworth Foundation (monday only)
* Rael Lissoos / Dabba
* Henry Marnitz / Ndlovu Medical Centre (wednesday only)
* Mark Summer, Inveneo (with request to forward to Ubiquiti)
* Elektra
* Mike Jensen (not confirmed)
* Kobus Roux, Meraka (NOT monday)
* Karel Matthee, Meraka
* Kim Gush, Meraka
* David Johnson, Meraka
* Chris Morris, Meraka
* Grant Cambridge, Meraka
* Shela Boshomane, Meraka (monday and wednesday)
* George James, Meraka
* Johann Hugo, Meraka
* John Hay, Meraka
* Ajay Makan, Meraka
* Sebastian Buettrich

More proposals are welcome!

Budgets for travel, if needed: Please contact us!

=Contact=

Sebastian

mail: sebastian@less.dk

skype: sebastian_buettrich

cell: (+27) (0) 79 915 32 92

=Timeplan=

The timeplan is draft level and will be adjusted to people's ability to join for limited periods.

'''The first day''' will be dedicated to the '''organizational layer''',

introducing the various projects and teams,
discussing the business models,
identifying overlap of work agendas as well as the main challenges each of the projects are seeing.

'''The second day''' will move down to detail level,
moving from business and organizational models to technology requirements/specifications.

The third day

==Day 1 - Monday, June 2==

===Morning===

====Creating Context====

Introductions, Presentations of participants

(Short 10 mns, informal project introductions)

* Introduction and WISPiab Project (Sebastian Buettrich)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Ndlovu Medical Centre (Henry Marnitz) (moved to Wednesday, June 4)
* Peeble's Valley Mesh (David Johnson)
* Digital Doorway (tba)
* Inveneo platform (Mark Summer)
* WISPiab work status (George James)
* Wireless Africa project (Chris Morris)
* Freifunk, B.a.t.m.a.n. & Meraka Mesh Testbed (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* IP04 (it46, rowetel) (on behalf of the project: Sebastian Buettrich)

===Afternoon===

====Business models====

Introduction: Sebastian

Business models may be classified according to a number of different dimensions -

e.g. financial/economic layer, tech/network topology layer, applications layer, social layer, -

Based on the experience of the participants and projects,
business models should be reviewed with the goal of reaching a downselection of models that should be implemented/supported
in the first iteration of the WISPiab project.

Classical examples:

* Voice services - The Village Telco
* "Line sharing" - sharing internet access between organizations
* Telecentre / Internet Cafe
* Campus / School network

'''The goal''' is to go through all our relevant models, to classify them on all layers,

and to identify the technology implications (such that technology follows business models, and not vice versa), producing a clear results list.

====Cooperations and Resources====

There is significant overlap between projects on the technology layer.
All projects are subscribing to free software models (GPL / CC, etc).

We are operating against a backdrop of

* challenged (human) resource situation
* brain drain / skills exodus
* wanting to build local (i.e. african? ... southern african? .... south african?) capacity

Cooperation between projects seems appropriate and possible.

'''The goal''' is to conclude this meeting with a clear picture of modes of cooperation.

====Advisory Group====

We wish to form an advisory group / peer group, including partly the invitees of this meeting, but not limited to these.

==Day 2 - Tuesday, June 3==

===Morning===

====Technical Requirements / Specifications - detail level====

Examples of concrete detail issues:

* Authentication - where and how
* Billing in mesh networks
* VoIP in mesh networks

'''The goal''' of this session is to fill the matrix of

''technology requirements x project/business model''

and then check this matrix against the various existing hardware/software platforms.

====Hardware platforms aspects====

A number of different hardware/software platforms are fulfilling subsets of our requirements.

The available platforms need to be discussed and evaluated, towards a decision on what to choose.

The platforms that our projects are currently working with are:

* Linksys WRT54, with firmwares OpenWRT, DD-WRT, Freifunk, CoovaAP, and similar
* Open-Mesh, Accton - with Open Mesh Firmware (new firmware anoounced for summer 2008, with: RO.B.IN, orangemesh, COOVA, etc)
* Inveneo platform
* Ubiquti NS, PS
* Meraka Bokkie routers
* pls add!

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Productification / Dissemination / Rollout strategies====

* Strategies for the productification of software packages
** Sourceforge platform plans (Steve?)
** Ubuntu / UCK (Sebastian, Mark, Elektra)
* Rollout capacity

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

==Day 3 - Wednesday, June 4==

===Morning===

==== Ndlovu Medical Center====

Status and Agenda of network at Ndlovu Medical Center

* How can the various projects benefit Ndlovu Medical Center?

====Status, gaps and planning of implementations====

* WISPiab status and work plan
* Dabba / Village Telco work sprint, June 16-20
** prepare and support that workshop

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Conclusions & Next steps====

* Dabba Worksprint
* WISPiab work plan
* Digital Doorway work
* Wireless Africa, June meeting

etc

= Notes from the meeting - Day 1=

==People & Project introductions==

* Introduction and WISPiab Project (Sebastian Buettrich)
* Peeble's Valley Mesh (David Johnson)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Inveneo platform (Mark Summer)
* Freifunk (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* WISPiab work status (George James)
* Two radio mesh router (Johann Hugo)
* Wireless Africa project (Chris Morris)

==Forming an Alliance?==

to be edited

= Notes from the meeting - Day 2=
[[Image:Day2 - WISPiab_Wkshop.jpg|left|thumb|350px|Day2 (L-R) Mark Summer, Johann Hugo, Mike Jensen, Elektra, Sebastian Buettrich, Kobus Roux, George James, Ajay Makan, Karel Matthee
]]

 

==Requirements, Specifications, Wishlist==

We chose the GUI [http://dabba.co.za/wispgui wishlist by Dabba] as an entry to discussing our current specifications set, identifying how we cover the single elements today, identifying dependencies, etc

[[Image:WISPiab meeting 20080603 whiteboard 1.jpg|thumb|left| Whiteboard Day 2]]
[[Image:Working_Logo.jpg|thumb|left|Table context]]

{| border="1" cellpadding="7" cellspacing="0"
!align="left" |What?
!align="left" |Which element
!align="left" |Existing
!align="left" |Who/how
!align="left" |Alternate names/terms
!align="left" |Task
|-
|Network Settings
|core
|FF, IHL, Coova (wifidog) + alternatives, Linksys & Netgear interfaces
|
|Network Management, Setup,
|
|-
|ISP settings
|core
|Coova, phpMyPrepaid, OpenWRT (QoS script) (...)shaper
|
|user/service profiles – provisioning (some of it -> QoS)
|
|-
|VoIP Settings Users, tarriffs
|voice
|AsteriskNow IP04 HW, Trixbox, A2billing, (Open)SER
|
| -->user profiles, --> VoIP settings
|
|-
|Prepaid Card System (print cards) (ops), ->web, ->voice
|web,voice
|phpMyPrepaid, A2billing
|
|“usage”
|
|-
|CRM
|core
|compiere
|
|
|
|-
|Accounting -->logs
|core
|phpMyPrepaid, a2billing
|
| ->(if bill) ->ERP
|
|-
|Logo/Company
|core
|(all components have some of it)
|
|themes/skins/ customisation
|
|-
|Network Monitoring
|
|Nagios, Open-Mesh, Open NMS, FF (some), MRTG/rrdtool
|
|Network management
|
|-
|Content
|
|
|
|
|
|-
|Video Server
|
|
|
|
|
|-
|Cache\Proxy with stats
|
|squid with awstats
|
|
|
|-
|Mail
|
|
|
|
|
|-
|Security encryption
|
|
|
|
|
|-
|httpd, with stats etc
|
|apache, awstats
|
|
|
|-
|Wiki / image hosting
|
|
|
|
|
|-
|Telecentre management
|
|UgaBytes telecentre management software?
|
|
|
|-
|}

==Business Models==

Discussion of business models that have informed the specifications, and a checkback whether we feel that the current specifications actually accomodate all these models.

The template on top suggests dimensions / criteria from which to look at the various models.

===Business Model Template===

* Description:

* Economics: Free or paid by ....
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications:
* Network / Topology:
* Internet uplink:
* User Devices / Locations:
* Startup Strategy:
* Legal & Regulatory

===Telecentre / Internet Cafe / Hotspot===

* Description: "Classical" telecentre / cafe style

* Economics: Free or paid by users / advertisers / cafe business
* Billing models: typically Prepaid (Time based):
* Applications: typically Browser / Mail / Office / Games
* Network / Topology: wired LAN
* Internet uplink: model works with and without uplink, but typically yes
* User Devices / Locations: Users on business owned PC
* Startup Strategy:
* Legal & Regulatory: ok in most (?) countries

===Telco===

* Description: Telco offering "fixed line" and mobile VoIP telephony

* Economics: Part free (?) (local) / paid by user
* Billing models: typically Prepaid (Time/Data based):
* Applications: VoIP telephony, typically on dedicated hardware
* Network / Topology: Centralized / Inframesh
* Internet uplink: Yes, if terminating external calls / local loop without
* User Devices / Locations: Users at home / office / mobile, Device VoIP handsets, ATA etc
* Startup Strategy:
* Legal & Regulatory: complex, country to country

===(Edu)Content / Media===

===Intranet / Neighbour-Net===

===Line Sharing===

===ISP===

===Web Hosting / Design===

===Corporate / Managend Services===

===Guesthouse Net===

===Housing Complex===

===Surveillance===

===Freifunk style Mesh===

===Training / Consultancy===

= Notes from the meeting - Day 3=

==Ndlovu Medical Centre==

Henry introduces:

* Status of mesh: operational, but currently disconnected (concerns about lightning)
* Use of uplink: Browsing (for community users), sync with data center (Johannesburg)
* Status of uplink: promised by Telkom, but not delivered yet

How to get started with a community mesh?

* Donated PCs - 25 pcs
** Give to local entrepreneur types
* Computer school as entry point

* Create a starter kit
** for existing PCs (there is some! mostly free windows)
** preconfigured
** low cost
** probably of the type: Linksys WRT, open-mesh/accton

Financing model

* Some contribution from user: Prepaid - low cost

What is interesting for people?

* music!!! open music server locally?
* free books? educational material
* free local calls
* a free wikipedia / digital doorway

Income from other sources (not the users):

* advertisements

To do / upcoming:

* '''call for a brainstorm meeting within the community'''

* June 9, meeting with provincial directory

* June 24: excursion to Ndlovu? participants of Wireless Africa meeting, Meraka people, Tom, Elektra

Top pain points / whats in the way:

* political level - get OKs from important players

==Hardware reference platform==

===Overall Requirements===

* 12 Volts (best: 11 ... 16)
* low power
* fanless

===Backend server===

* USB 2x
* ethernet 2x
* VGA

Candidate for reference choice:

* bigger solution: VIA, jetway 1.2 GHz, 2x HD, 1 GB RAM, USD 680 ... 820 [http://mini-box.com e.g. mini-box-com]
** power: approx 25W ?
* smaller solution: VIA, AMD Geode 500 MHz
** power: 8 W
* LEX light/neo, e.g. 1 GB C7 approx USD 600 [http://www.lex.com.tw/ http://www.lex.com.tw/]
* soon to come: Atom based low cost desktops (Mark Summer)
* alternatives: [http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99 http://www.mini-box.com/Alix-2B0-Board-2-LAN-2-MINI-PCI_LX700?sc=8&category=99]

====Software on backend====

Decision: Ubuntu (non X)

----

===Access node===

* ethernet 2x
* PoE
* outdoor casing
* broadcom or atheros chipset
* 5 ... 18 Volts
* Watchdog (option)
* WISPCAR (option)
* serial port

Candidates:

* Linksys WRT54GL
** price: EUR 50, ZAR 600, USD 60
** power: 4 W
** comments:

* Ubiqiti
** price: NS 2: USD 79
** price: PS 2: USD 110
** power: 5 W

* Accton
** price: USD 40
** power: 2-3 W ?
** comments: overheat problems? needs fixed power 5 V? quality of radio? unstable across channels?

* PCEngines board
** price: > USD 250
** power: approx > 8W, depending on radio cards
** comments:

* Soekris

* Gateworks
**
**

* Wiligear

===A word on the punishment for every watt===

Elektra, conservative estimate:

To power a 5 Watt device reliably, install a 80 Watt solar panel.

This means: 16 Watt solar panel per 1 Watt installed.

At about USD 5 per solar panel watt (current rough guess for market price), we have:

USD 80 in solar panel per 1 Watt installed.

Even when demanding less margin from the solar power system (i.e. less solar panels per consumer), the fine for every Watt installed is heavy.

==Next steps==

* Examine the Ubiquiti - Lead: Elektra
** flash OpenWRT
** Examine the SDK

* Procurement - Lead: Kobus/Ajay
** ??? x Inveneo small server
**

* Examine the Inveneo Hub Linux (IHL)

* Software development
** Meraka - Priority: the set of Coova (alternative: WifiDog) / FreeRadius / phpMyPrepaid (alternative: ISPBill) / Nagios
** Inveneo - Priority: Server squid/cache, proxy, asterisk, Webmin/ISPConfig

WISPiab work meeting 200806

2008-06-04T15:12:34Z

Sebastian: /* Requirements, Specifications, Wishlist */

[[Category: WISP in a box]]

=Work meeting of the WISP-in-a-box project=

[[The WISP-in-a-box project]]

=Date=

June 2-3-4, 2008

9-17 h

=Location=

Meraka Institute,
Building 43 C,
Hummingbird Room (C128, ground floor)

Pretoria

=Invitation List=

People and organisations with an active interest in building a concrete product that
helps bringing

connectivity to underserviced, underprivileged and overcharged communities in Africa.

Invitation list:

* Steve Song / Shuttleworth Foundation (monday only)
* Rael Lissoos / Dabba
* Henry Marnitz / Ndlovu Medical Centre (wednesday only)
* Mark Summer, Inveneo (with request to forward to Ubiquiti)
* Elektra
* Mike Jensen (not confirmed)
* Kobus Roux, Meraka (NOT monday)
* Karel Matthee, Meraka
* Kim Gush, Meraka
* David Johnson, Meraka
* Chris Morris, Meraka
* Grant Cambridge, Meraka
* Shela Boshomane, Meraka (monday and wednesday)
* George James, Meraka
* Johann Hugo, Meraka
* John Hay, Meraka
* Ajay Makan, Meraka
* Sebastian Buettrich

More proposals are welcome!

Budgets for travel, if needed: Please contact us!

=Contact=

Sebastian

mail: sebastian@less.dk

skype: sebastian_buettrich

cell: (+27) (0) 79 915 32 92

=Timeplan=

The timeplan is draft level and will be adjusted to people's ability to join for limited periods.

'''The first day''' will be dedicated to the '''organizational layer''',

introducing the various projects and teams,
discussing the business models,
identifying overlap of work agendas as well as the main challenges each of the projects are seeing.

'''The second day''' will move down to detail level,
moving from business and organizational models to technology requirements/specifications.

The third day

==Day 1 - Monday, June 2==

===Morning===

====Creating Context====

Introductions, Presentations of participants

(Short 10 mns, informal project introductions)

* Introduction and WISPiab Project (Sebastian Buettrich)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Ndlovu Medical Centre (Henry Marnitz) (moved to Wednesday, June 4)
* Peeble's Valley Mesh (David Johnson)
* Digital Doorway (tba)
* Inveneo platform (Mark Summer)
* WISPiab work status (George James)
* Wireless Africa project (Chris Morris)
* Freifunk, B.a.t.m.a.n. & Meraka Mesh Testbed (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* IP04 (it46, rowetel) (on behalf of the project: Sebastian Buettrich)

===Afternoon===

====Business models====

Introduction: Sebastian

Business models may be classified according to a number of different dimensions -

e.g. financial/economic layer, tech/network topology layer, applications layer, social layer, -

Based on the experience of the participants and projects,
business models should be reviewed with the goal of reaching a downselection of models that should be implemented/supported
in the first iteration of the WISPiab project.

Classical examples:

* Voice services - The Village Telco
* "Line sharing" - sharing internet access between organizations
* Telecentre / Internet Cafe
* Campus / School network

'''The goal''' is to go through all our relevant models, to classify them on all layers,

and to identify the technology implications (such that technology follows business models, and not vice versa), producing a clear results list.

====Cooperations and Resources====

There is significant overlap between projects on the technology layer.
All projects are subscribing to free software models (GPL / CC, etc).

We are operating against a backdrop of

* challenged (human) resource situation
* brain drain / skills exodus
* wanting to build local (i.e. african? ... southern african? .... south african?) capacity

Cooperation between projects seems appropriate and possible.

'''The goal''' is to conclude this meeting with a clear picture of modes of cooperation.

====Advisory Group====

We wish to form an advisory group / peer group, including partly the invitees of this meeting, but not limited to these.

==Day 2 - Tuesday, June 3==

===Morning===

====Technical Requirements / Specifications - detail level====

Examples of concrete detail issues:

* Authentication - where and how
* Billing in mesh networks
* VoIP in mesh networks

'''The goal''' of this session is to fill the matrix of

''technology requirements x project/business model''

and then check this matrix against the various existing hardware/software platforms.

====Hardware platforms aspects====

A number of different hardware/software platforms are fulfilling subsets of our requirements.

The available platforms need to be discussed and evaluated, towards a decision on what to choose.

The platforms that our projects are currently working with are:

* Linksys WRT54, with firmwares OpenWRT, DD-WRT, Freifunk, CoovaAP, and similar
* Open-Mesh, Accton - with Open Mesh Firmware (new firmware anoounced for summer 2008, with: RO.B.IN, orangemesh, COOVA, etc)
* Inveneo platform
* Ubiquti NS, PS
* Meraka Bokkie routers
* pls add!

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Productification / Dissemination / Rollout strategies====

* Strategies for the productification of software packages
** Sourceforge platform plans (Steve?)
** Ubuntu / UCK (Sebastian, Mark, Elektra)
* Rollout capacity

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

==Day 3 - Wednesday, June 4==

===Morning===

==== Ndlovu Medical Center====

Status and Agenda of network at Ndlovu Medical Center

* How can the various projects benefit Ndlovu Medical Center?

====Status, gaps and planning of implementations====

* WISPiab status and work plan
* Dabba / Village Telco work sprint, June 16-20
** prepare and support that workshop

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Conclusions & Next steps====

* Dabba Worksprint
* WISPiab work plan
* Digital Doorway work
* Wireless Africa, June meeting

etc

= Notes from the meeting - Day 1=

==People & Project introductions==

* Introduction and WISPiab Project (Sebastian Buettrich)
* Peeble's Valley Mesh (David Johnson)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Inveneo platform (Mark Summer)
* Freifunk (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* WISPiab work status (George James)
* Two radio mesh router (Johann Hugo)
* Wireless Africa project (Chris Morris)

==Forming an Alliance?==

to be edited

= Notes from the meeting - Day 2=
[[Image:Day2 - WISPiab_Wkshop.jpg|left|thumb|350px|Day2 (L-R) Mark Summer, Johann Hugo, Mike Jensen, Elektra, Sebastian Buettrich, Kobus Roux, George James, Ajay Makan, Karel Matthee
]]

 

==Requirements, Specifications, Wishlist==

We chose the GUI [http://dabba.co.za/wispgui wishlist by Dabba] as an entry to discussing our current specifications set, identifying how we cover the single elements today, identifying dependencies, etc

[[Image:WISPiab meeting 20080603 whiteboard 1.jpg|thumb|left| Whiteboard Day 2]]
[[Image:Working_Logo.jpg|thumb|left|Table context]]

{| border="1" cellpadding="7" cellspacing="0"
!align="left" |What?
!align="left" |Which element
!align="left" |Existing
!align="left" |Who/how
!align="left" |Alternate names/terms
!align="left" |Task
|-
|Network Settings
|core
|FF, IHL, Coova (wifidog) + alternatives, Linksys & Netgear interfaces
|
|Network Management, Setup,
|
|-
|ISP settings
|core
|Coova, phpMyPrepaid, OpenWRT (QoS script) (...)shaper
|
|user/service profiles – provisioning (some of it -> QoS)
|
|-
|VoIP Settings Users, tarriffs
|voice
|AsteriskNow IP04 HW, Trixbox, A2billing, (Open)SER
|
| -->user profiles, --> VoIP settings
|
|-
|Prepaid Card System (print cards) (ops), ->web, ->voice
|web,voice
|phpMyPrepaid, A2billing
|
|“usage”
|
|-
|CRM
|core
|compiere
|
|
|
|-
|Accounting -->logs
|core
|phpMyPrepaid, a2billing
|
| ->(if bill) ->ERP
|
|-
|Logo/Company
|core
|(all components have some of it)
|
|themes/skins/ customisation
|
|-
|Network Monitoring
|
|Nagios, Open-Mesh, Open NMS, FF (some), MRTG/rrdtool
|
|Network management
|
|-
|Content
|
|
|
|
|
|-
|Video Server
|
|
|
|
|
|-
|Cache\Proxy with stats
|
|squid with awstats
|
|
|
|-
|Mail
|
|
|
|
|
|-
|Security encryption
|
|
|
|
|
|-
|httpd, with stats etc
|
|apache, awstats
|
|
|
|-
|Wiki / image hosting
|
|
|
|
|
|-
|Telecentre management
|
|UgaBytes telecentre management software?
|
|
|
|-
|}

==Business Models==

Discussion of business models that have informed the specifications, and a checkback whether we feel that the current specifications actually accomodate all these models.

The template on top suggests dimensions / criteria from which to look at the various models.

===Business Model Template===

* Description:

* Economics: Free or paid by ....
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications:
* Network / Topology:
* Internet uplink:
* User Devices / Locations:
* Startup Strategy:
* Legal & Regulatory

===Telecentre / Internet Cafe / Hotspot===

* Description: "Classical" telecentre / cafe style

* Economics: Free or paid by users / advertisers / cafe business
* Billing models: typically Prepaid (Time based):
* Applications: typically Browser / Mail / Office / Games
* Network / Topology: wired LAN
* Internet uplink: model works with and without uplink, but typically yes
* User Devices / Locations: Users on business owned PC
* Startup Strategy:
* Legal & Regulatory: ok in most (?) countries

===Telco===

* Description: Telco offering "fixed line" and mobile VoIP telephony

* Economics: Part free (?) (local) / paid by user
* Billing models: typically Prepaid (Time/Data based):
* Applications: VoIP telephony, typically on dedicated hardware
* Network / Topology: Centralized / Inframesh
* Internet uplink: Yes, if terminating external calls / local loop without
* User Devices / Locations: Users at home / office / mobile, Device VoIP handsets, ATA etc
* Startup Strategy:
* Legal & Regulatory: complex, country to country

===(Edu)Content / Media===

===Intranet / Neighbour-Net===

===Line Sharing===

===ISP===

===Web Hosting / Design===

===Corporate / Managend Services===

===Guesthouse Net===

===Housing Complex===

===Surveillance===

===Freifunk style Mesh===

===Training / Consultancy===

= Notes from the meeting - Day 3=

==Ndlovu Medical Centre==

Henry introduces:

* Status of mesh: operational, but currently disconnected (concerns about lightning)
* Use of uplink: Browsing (for community users), sync with data center (Johannesburg)
* Status of uplink: promised by Telkom, but not delivered yet

How to get started with a community mesh?

* Donated PCs - 25 pcs
** Give to local entrepreneur types
* Computer school as entry point

* Create a starter kit
** for existing PCs (there is some! mostly free windows)
** preconfigured
** low cost
** probably of the type: Linksys WRT, open-mesh/accton

Financing model

* Some contribution from user: Prepaid - low cost

What is interesting for people?

* music!!! open music server locally?
* free books? educational material
* free local calls
* a free wikipedia / digital doorway

Income from other sources (not the users):

* advertisements

To do / upcoming:

* '''call for a brainstorm meeting within the community'''

* June 9, meeting with provincial directory

* June 24: excursion to Ndlovu? participants of Wireless Africa meeting, Meraka people, Tom, Elektra

Top pain points / whats in the way:

* political level - get OKs from important players

==Hardware reference platform==

===Overall Requirements===

* 12 Volts (best: 11 ... 16)
* low power
* fanless

===Backend server===

* USB 2x
* ethernet 2x
* VGA

Candidate for reference choice:

* bigger solution: VIA, jetway 1.2 GHz, 2x HD, 1 GB RAM, USD 680 ... 820 [http://mini-box.com e.g. mini-box-com]
** power: approx 25W ?
* smaller solution: VIA, AMD Geode 500 MHz
** power: 8 W
* LEX light/neo, e.g. 1 GB C7 approx USD 600 [http://www.lex.com.tw/ http://www.lex.com.tw/]
* soon to come: Atom based low cost desktops (Mark Summer)

====Software on backend====

Decision: Ubuntu (non X)

----

===Access node===

* ethernet 2x
* PoE
* outdoor casing
* broadcom or atheros chipset
* 5 ... 18 Volts
* Watchdog (option)
* WISPCAR (option)
* serial port

Candidates:

* Linksys WRT54GL
** price: EUR 50, ZAR 600, USD 60
** power: 4 W
** comments:

* Ubiqiti
** price: NS 2: USD 79
** price: PS 2: USD 110
** power: 5 W

* Accton
** price: USD 40
** power: 2-3 W ?
** comments: overheat problems? needs fixed power 5 V? quality of radio? unstable across channels?

* PCEngines board
** price: > USD 250
** power: approx > 8W, depending on radio cards
** comments:

* Soekris

* Gateworks
**
**

* Wiligear

===A word on the punishment for every watt===

Elektra, conservative estimate:

To power a 5 Watt device reliably, install a 80 Watt solar panel.

This means: 16 Watt solar panel per 1 Watt installed.

At about USD 5 per solar panel watt (current rough guess for market price), we have:

USD 80 in solar panel per 1 Watt installed.

Even when demanding less margin from the solar power system (i.e. less solar panels per consumer), the fine for every Watt installed is heavy.

==Next steps==

* Examine the Ubiquiti - Lead: Elektra
** flash OpenWRT
** Examine the SDK

* Procurement - Lead: Kobus/Ajay
** ??? x Inveneo small server
**

* Examine the Inveneo Hub Linux (IHL)

* Software development
** Meraka - Priority: the set of Coova (alternative: WifiDog) / FreeRadius / phpMyPrepaid (alternative: ISPBill) / Nagios
** Inveneo - Priority: Server squid/cache, proxy, asterisk, Webmin/ISPConfig

WISPiab work meeting 200806

2008-06-04T15:08:22Z

Sebastian: /* Requirements, Specifications, Wishlist */

[[Category: WISP in a box]]

=Work meeting of the WISP-in-a-box project=

[[The WISP-in-a-box project]]

=Date=

June 2-3-4, 2008

9-17 h

=Location=

Meraka Institute,
Building 43 C,
Hummingbird Room (C128, ground floor)

Pretoria

=Invitation List=

People and organisations with an active interest in building a concrete product that
helps bringing

connectivity to underserviced, underprivileged and overcharged communities in Africa.

Invitation list:

* Steve Song / Shuttleworth Foundation (monday only)
* Rael Lissoos / Dabba
* Henry Marnitz / Ndlovu Medical Centre (wednesday only)
* Mark Summer, Inveneo (with request to forward to Ubiquiti)
* Elektra
* Mike Jensen (not confirmed)
* Kobus Roux, Meraka (NOT monday)
* Karel Matthee, Meraka
* Kim Gush, Meraka
* David Johnson, Meraka
* Chris Morris, Meraka
* Grant Cambridge, Meraka
* Shela Boshomane, Meraka (monday and wednesday)
* George James, Meraka
* Johann Hugo, Meraka
* John Hay, Meraka
* Ajay Makan, Meraka
* Sebastian Buettrich

More proposals are welcome!

Budgets for travel, if needed: Please contact us!

=Contact=

Sebastian

mail: sebastian@less.dk

skype: sebastian_buettrich

cell: (+27) (0) 79 915 32 92

=Timeplan=

The timeplan is draft level and will be adjusted to people's ability to join for limited periods.

'''The first day''' will be dedicated to the '''organizational layer''',

introducing the various projects and teams,
discussing the business models,
identifying overlap of work agendas as well as the main challenges each of the projects are seeing.

'''The second day''' will move down to detail level,
moving from business and organizational models to technology requirements/specifications.

The third day

==Day 1 - Monday, June 2==

===Morning===

====Creating Context====

Introductions, Presentations of participants

(Short 10 mns, informal project introductions)

* Introduction and WISPiab Project (Sebastian Buettrich)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Ndlovu Medical Centre (Henry Marnitz) (moved to Wednesday, June 4)
* Peeble's Valley Mesh (David Johnson)
* Digital Doorway (tba)
* Inveneo platform (Mark Summer)
* WISPiab work status (George James)
* Wireless Africa project (Chris Morris)
* Freifunk, B.a.t.m.a.n. & Meraka Mesh Testbed (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* IP04 (it46, rowetel) (on behalf of the project: Sebastian Buettrich)

===Afternoon===

====Business models====

Introduction: Sebastian

Business models may be classified according to a number of different dimensions -

e.g. financial/economic layer, tech/network topology layer, applications layer, social layer, -

Based on the experience of the participants and projects,
business models should be reviewed with the goal of reaching a downselection of models that should be implemented/supported
in the first iteration of the WISPiab project.

Classical examples:

* Voice services - The Village Telco
* "Line sharing" - sharing internet access between organizations
* Telecentre / Internet Cafe
* Campus / School network

'''The goal''' is to go through all our relevant models, to classify them on all layers,

and to identify the technology implications (such that technology follows business models, and not vice versa), producing a clear results list.

====Cooperations and Resources====

There is significant overlap between projects on the technology layer.
All projects are subscribing to free software models (GPL / CC, etc).

We are operating against a backdrop of

* challenged (human) resource situation
* brain drain / skills exodus
* wanting to build local (i.e. african? ... southern african? .... south african?) capacity

Cooperation between projects seems appropriate and possible.

'''The goal''' is to conclude this meeting with a clear picture of modes of cooperation.

====Advisory Group====

We wish to form an advisory group / peer group, including partly the invitees of this meeting, but not limited to these.

==Day 2 - Tuesday, June 3==

===Morning===

====Technical Requirements / Specifications - detail level====

Examples of concrete detail issues:

* Authentication - where and how
* Billing in mesh networks
* VoIP in mesh networks

'''The goal''' of this session is to fill the matrix of

''technology requirements x project/business model''

and then check this matrix against the various existing hardware/software platforms.

====Hardware platforms aspects====

A number of different hardware/software platforms are fulfilling subsets of our requirements.

The available platforms need to be discussed and evaluated, towards a decision on what to choose.

The platforms that our projects are currently working with are:

* Linksys WRT54, with firmwares OpenWRT, DD-WRT, Freifunk, CoovaAP, and similar
* Open-Mesh, Accton - with Open Mesh Firmware (new firmware anoounced for summer 2008, with: RO.B.IN, orangemesh, COOVA, etc)
* Inveneo platform
* Ubiquti NS, PS
* Meraka Bokkie routers
* pls add!

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Productification / Dissemination / Rollout strategies====

* Strategies for the productification of software packages
** Sourceforge platform plans (Steve?)
** Ubuntu / UCK (Sebastian, Mark, Elektra)
* Rollout capacity

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

==Day 3 - Wednesday, June 4==

===Morning===

==== Ndlovu Medical Center====

Status and Agenda of network at Ndlovu Medical Center

* How can the various projects benefit Ndlovu Medical Center?

====Status, gaps and planning of implementations====

* WISPiab status and work plan
* Dabba / Village Telco work sprint, June 16-20
** prepare and support that workshop

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Conclusions & Next steps====

* Dabba Worksprint
* WISPiab work plan
* Digital Doorway work
* Wireless Africa, June meeting

etc

= Notes from the meeting - Day 1=

==People & Project introductions==

* Introduction and WISPiab Project (Sebastian Buettrich)
* Peeble's Valley Mesh (David Johnson)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Inveneo platform (Mark Summer)
* Freifunk (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* WISPiab work status (George James)
* Two radio mesh router (Johann Hugo)
* Wireless Africa project (Chris Morris)

==Forming an Alliance?==

to be edited

= Notes from the meeting - Day 2=
[[Image:Day2 - WISPiab_Wkshop.jpg|left|thumb|350px|Day2 (L-R) Mark Summer, Johann Hugo, Mike Jensen, Elektra, Sebastian Buettrich, Kobus Roux, George James, Ajay Makan, Karel Matthee
]]

 

==Requirements, Specifications, Wishlist==

We chose the GUI [http://dabba.co.za/wispgui wishlist by Dabba] as an entry to discussing our current specifications set, identifying how we cover the single elements today, identifying dependencies, etc

[[Image:WISPiab meeting 20080603 whiteboard 1.jpg|thumb|left| Whiteboard Day 2]]
[[Image:Working_Logo.jpg|thumb|left|Table context]]

{| border="1" cellpadding="7" cellspacing="0"
!align="left" |What?
!align="left" |Which element
!align="left" |Existing
!align="left" |Who/how
!align="left" |Alternate names/terms
!align="left" |Task
|-
|Network Settings
|core
|FF, IHL, Coova (wifidog) + alternatives, Linksys & Netgear interfaces
|
|Network Management, Setup,
|
|-
|ISP settings
|core
|Coova, phpMyPrepaid, OpenWRT (QoS script) (...)shaper
|
|user/service profiles – provisioning (some of it -> QoS)
|
|-
|VoIP Settings Users, tarriffs
|voice
|AsteriskNow IP04 HW, Trixbox, A2billing, (Open)SER
|
| -->user profiles, --> VoIP settings
|
|-
|Prepaid Card System (print cards) (ops), ->web, ->voice
|web,voice
|phpMyPrepaid, A2billing
|
|“usage”
|
|-
|CRM
|core
|compiere
|
|
|
|-
|Accounting -->logs
|core
|phpMyPrepaid, a2billing
|
| ->(if bill) ->ERP
|
|-
|Logo/Company
|core
|(all components have some of it)
|
|themes/skins/ customisation
|
|-
|Network Monitoring
|
|Nagios, Open-Mesh, Open NMS, FF (some), MRTG
|
|Network management
|
|-
|Content
|
|
|
|
|
|-
|Video Server
|
|
|
|
|
|-
|Cache\Proxy with stats
|
|squid with awstats
|
|
|
|-
|Mail
|
|
|
|
|
|-
|Security encryption
|
|
|
|
|
|-
|httpd, with stats etc
|
|apache, awstats
|
|
|
|-
|Wiki / image hosting
|
|
|
|
|
|-
|Telecentre management
|
|UgaBytes telecentre management software?
|
|
|
|-
|}

==Business Models==

Discussion of business models that have informed the specifications, and a checkback whether we feel that the current specifications actually accomodate all these models.

The template on top suggests dimensions / criteria from which to look at the various models.

===Business Model Template===

* Description:

* Economics: Free or paid by ....
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications:
* Network / Topology:
* Internet uplink:
* User Devices / Locations:
* Startup Strategy:
* Legal & Regulatory

===Telecentre / Internet Cafe / Hotspot===

* Description: "Classical" telecentre / cafe style

* Economics: Free or paid by users / advertisers / cafe business
* Billing models: typically Prepaid (Time based):
* Applications: typically Browser / Mail / Office / Games
* Network / Topology: wired LAN
* Internet uplink: model works with and without uplink, but typically yes
* User Devices / Locations: Users on business owned PC
* Startup Strategy:
* Legal & Regulatory: ok in most (?) countries

===Telco===

* Description: Telco offering "fixed line" and mobile VoIP telephony

* Economics: Part free (?) (local) / paid by user
* Billing models: typically Prepaid (Time/Data based):
* Applications: VoIP telephony, typically on dedicated hardware
* Network / Topology: Centralized / Inframesh
* Internet uplink: Yes, if terminating external calls / local loop without
* User Devices / Locations: Users at home / office / mobile, Device VoIP handsets, ATA etc
* Startup Strategy:
* Legal & Regulatory: complex, country to country

===(Edu)Content / Media===

===Intranet / Neighbour-Net===

===Line Sharing===

===ISP===

===Web Hosting / Design===

===Corporate / Managend Services===

===Guesthouse Net===

===Housing Complex===

===Surveillance===

===Freifunk style Mesh===

===Training / Consultancy===

= Notes from the meeting - Day 3=

==Ndlovu Medical Centre==

Henry introduces:

* Status of mesh: operational, but currently disconnected (concerns about lightning)
* Use of uplink: Browsing (for community users), sync with data center (Johannesburg)
* Status of uplink: promised by Telkom, but not delivered yet

How to get started with a community mesh?

* Donated PCs - 25 pcs
** Give to local entrepreneur types
* Computer school as entry point

* Create a starter kit
** for existing PCs (there is some! mostly free windows)
** preconfigured
** low cost
** probably of the type: Linksys WRT, open-mesh/accton

Financing model

* Some contribution from user: Prepaid - low cost

What is interesting for people?

* music!!! open music server locally?
* free books? educational material
* free local calls
* a free wikipedia / digital doorway

Income from other sources (not the users):

* advertisements

To do / upcoming:

* '''call for a brainstorm meeting within the community'''

* June 9, meeting with provincial directory

* June 24: excursion to Ndlovu? participants of Wireless Africa meeting, Meraka people, Tom, Elektra

Top pain points / whats in the way:

* political level - get OKs from important players

==Hardware reference platform==

===Overall Requirements===

* 12 Volts (best: 11 ... 16)
* low power
* fanless

===Backend server===

* USB 2x
* ethernet 2x
* VGA

Candidate for reference choice:

* bigger solution: VIA, jetway 1.2 GHz, 2x HD, 1 GB RAM, USD 680 ... 820 [http://mini-box.com e.g. mini-box-com]
** power: approx 25W ?
* smaller solution: VIA, AMD Geode 500 MHz
** power: 8 W
* LEX light/neo, e.g. 1 GB C7 approx USD 600 [http://www.lex.com.tw/ http://www.lex.com.tw/]
* soon to come: Atom based low cost desktops (Mark Summer)

====Software on backend====

Decision: Ubuntu (non X)

----

===Access node===

* ethernet 2x
* PoE
* outdoor casing
* broadcom or atheros chipset
* 5 ... 18 Volts
* Watchdog (option)
* WISPCAR (option)
* serial port

Candidates:

* Linksys WRT54GL
** price: EUR 50, ZAR 600, USD 60
** power: 4 W
** comments:

* Ubiqiti
** price: NS 2: USD 79
** price: PS 2: USD 110
** power: 5 W

* Accton
** price: USD 40
** power: 2-3 W ?
** comments: overheat problems? needs fixed power 5 V? quality of radio? unstable across channels?

* PCEngines board
** price: > USD 250
** power: approx > 8W, depending on radio cards
** comments:

* Soekris

* Gateworks
**
**

* Wiligear

===A word on the punishment for every watt===

Elektra, conservative estimate:

To power a 5 Watt device reliably, install a 80 Watt solar panel.

This means: 16 Watt solar panel per 1 Watt installed.

At about USD 5 per solar panel watt (current rough guess for market price), we have:

USD 80 in solar panel per 1 Watt installed.

Even when demanding less margin from the solar power system (i.e. less solar panels per consumer), the fine for every Watt installed is heavy.

==Next steps==

* Examine the Ubiquiti - Lead: Elektra
** flash OpenWRT
** Examine the SDK

* Procurement - Lead: Kobus/Ajay
** ??? x Inveneo small server
**

* Examine the Inveneo Hub Linux (IHL)

* Software development
** Meraka - Priority: the set of Coova (alternative: WifiDog) / FreeRadius / phpMyPrepaid (alternative: ISPBill) / Nagios
** Inveneo - Priority: Server squid/cache, proxy, asterisk, Webmin/ISPConfig

WISPiab work meeting 200806

2008-06-04T15:05:28Z

Sebastian: /* Next steps */

[[Category: WISP in a box]]

=Work meeting of the WISP-in-a-box project=

[[The WISP-in-a-box project]]

=Date=

June 2-3-4, 2008

9-17 h

=Location=

Meraka Institute,
Building 43 C,
Hummingbird Room (C128, ground floor)

Pretoria

=Invitation List=

People and organisations with an active interest in building a concrete product that
helps bringing

connectivity to underserviced, underprivileged and overcharged communities in Africa.

Invitation list:

* Steve Song / Shuttleworth Foundation (monday only)
* Rael Lissoos / Dabba
* Henry Marnitz / Ndlovu Medical Centre (wednesday only)
* Mark Summer, Inveneo (with request to forward to Ubiquiti)
* Elektra
* Mike Jensen (not confirmed)
* Kobus Roux, Meraka (NOT monday)
* Karel Matthee, Meraka
* Kim Gush, Meraka
* David Johnson, Meraka
* Chris Morris, Meraka
* Grant Cambridge, Meraka
* Shela Boshomane, Meraka (monday and wednesday)
* George James, Meraka
* Johann Hugo, Meraka
* John Hay, Meraka
* Ajay Makan, Meraka
* Sebastian Buettrich

More proposals are welcome!

Budgets for travel, if needed: Please contact us!

=Contact=

Sebastian

mail: sebastian@less.dk

skype: sebastian_buettrich

cell: (+27) (0) 79 915 32 92

=Timeplan=

The timeplan is draft level and will be adjusted to people's ability to join for limited periods.

'''The first day''' will be dedicated to the '''organizational layer''',

introducing the various projects and teams,
discussing the business models,
identifying overlap of work agendas as well as the main challenges each of the projects are seeing.

'''The second day''' will move down to detail level,
moving from business and organizational models to technology requirements/specifications.

The third day

==Day 1 - Monday, June 2==

===Morning===

====Creating Context====

Introductions, Presentations of participants

(Short 10 mns, informal project introductions)

* Introduction and WISPiab Project (Sebastian Buettrich)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Ndlovu Medical Centre (Henry Marnitz) (moved to Wednesday, June 4)
* Peeble's Valley Mesh (David Johnson)
* Digital Doorway (tba)
* Inveneo platform (Mark Summer)
* WISPiab work status (George James)
* Wireless Africa project (Chris Morris)
* Freifunk, B.a.t.m.a.n. & Meraka Mesh Testbed (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* IP04 (it46, rowetel) (on behalf of the project: Sebastian Buettrich)

===Afternoon===

====Business models====

Introduction: Sebastian

Business models may be classified according to a number of different dimensions -

e.g. financial/economic layer, tech/network topology layer, applications layer, social layer, -

Based on the experience of the participants and projects,
business models should be reviewed with the goal of reaching a downselection of models that should be implemented/supported
in the first iteration of the WISPiab project.

Classical examples:

* Voice services - The Village Telco
* "Line sharing" - sharing internet access between organizations
* Telecentre / Internet Cafe
* Campus / School network

'''The goal''' is to go through all our relevant models, to classify them on all layers,

and to identify the technology implications (such that technology follows business models, and not vice versa), producing a clear results list.

====Cooperations and Resources====

There is significant overlap between projects on the technology layer.
All projects are subscribing to free software models (GPL / CC, etc).

We are operating against a backdrop of

* challenged (human) resource situation
* brain drain / skills exodus
* wanting to build local (i.e. african? ... southern african? .... south african?) capacity

Cooperation between projects seems appropriate and possible.

'''The goal''' is to conclude this meeting with a clear picture of modes of cooperation.

====Advisory Group====

We wish to form an advisory group / peer group, including partly the invitees of this meeting, but not limited to these.

==Day 2 - Tuesday, June 3==

===Morning===

====Technical Requirements / Specifications - detail level====

Examples of concrete detail issues:

* Authentication - where and how
* Billing in mesh networks
* VoIP in mesh networks

'''The goal''' of this session is to fill the matrix of

''technology requirements x project/business model''

and then check this matrix against the various existing hardware/software platforms.

====Hardware platforms aspects====

A number of different hardware/software platforms are fulfilling subsets of our requirements.

The available platforms need to be discussed and evaluated, towards a decision on what to choose.

The platforms that our projects are currently working with are:

* Linksys WRT54, with firmwares OpenWRT, DD-WRT, Freifunk, CoovaAP, and similar
* Open-Mesh, Accton - with Open Mesh Firmware (new firmware anoounced for summer 2008, with: RO.B.IN, orangemesh, COOVA, etc)
* Inveneo platform
* Ubiquti NS, PS
* Meraka Bokkie routers
* pls add!

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Productification / Dissemination / Rollout strategies====

* Strategies for the productification of software packages
** Sourceforge platform plans (Steve?)
** Ubuntu / UCK (Sebastian, Mark, Elektra)
* Rollout capacity

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

==Day 3 - Wednesday, June 4==

===Morning===

==== Ndlovu Medical Center====

Status and Agenda of network at Ndlovu Medical Center

* How can the various projects benefit Ndlovu Medical Center?

====Status, gaps and planning of implementations====

* WISPiab status and work plan
* Dabba / Village Telco work sprint, June 16-20
** prepare and support that workshop

====Hands-on work====

Part of this session will be practical experiments with the platforms -
if appropriate, in breakout sessions.

===Afternoon===

====Conclusions & Next steps====

* Dabba Worksprint
* WISPiab work plan
* Digital Doorway work
* Wireless Africa, June meeting

etc

= Notes from the meeting - Day 1=

==People & Project introductions==

* Introduction and WISPiab Project (Sebastian Buettrich)
* Peeble's Valley Mesh (David Johnson)
* Dabba / Orange Farm / Village Telco (Rael Lissoos)
* Inveneo platform (Mark Summer)
* Freifunk (Elektra)
* DIY Guide & Zambia LinkNet (Karel Matthee)
* WISPiab work status (George James)
* Two radio mesh router (Johann Hugo)
* Wireless Africa project (Chris Morris)

==Forming an Alliance?==

to be edited

= Notes from the meeting - Day 2=
[[Image:Day2 - WISPiab_Wkshop.jpg|left|thumb|350px|Day2 (L-R) Mark Summer, Johann Hugo, Mike Jensen, Elektra, Sebastian Buettrich, Kobus Roux, George James, Ajay Makan, Karel Matthee
]]

 

==Requirements, Specifications, Wishlist==

We chose the GUI [http://dabba.co.za/wispgui wishlist by Dabba] as an entry to discussing our current specifications set, identifying how we cover the single elements today, identifying dependencies, etc

[[Image:WISPiab meeting 20080603 whiteboard 1.jpg|thumb|left| Whiteboard Day 2]]
[[Image:Working_Logo.jpg|thumb|left|Table context]]

{| border="1" cellpadding="7" cellspacing="0"
!align="left" |What?
!align="left" |Which element
!align="left" |Existing
!align="left" |Who/how
!align="left" |Alternate names/terms
!align="left" |Task
|-
|Network Settings
|core
|FF, IHL, Coova (wifidog) + alternatives, Linksys & Netgear interfaces
|
|Network Management, Setup,
|
|-
|ISP settings
|core
|Coova, phpMyPrepaid, OpenWRT (QoS script) (...)shaper
|
|user/service profiles – provisioning (some of it -> QoS)
|
|-
|VoIP Settings Users, tarriffs
|voice
|AsteriskNow IP04 HW, Trixbox, A2billing, (Open)SER
|
| -->user profiles, --> VoIP settings
|
|-
|Prepaid Card System (print cards) (ops), ->web, ->voice
|web,voice
|phpMyPrepaid, A2billing
|
|“usage”
|
|-
|CRM
|core
|compiere
|
|
|
|-
|Accounting -->logs
|core
|phpMyPrepaid, a2billing
|
| ->(if bill) ->ERP
|
|-
|Logo/Company
|core
|(all components have some of it)
|
|themes/skins/ customisation
|
|-
|Network Monitoring
|
|Nagios, Open-Mesh, Open NMS, FF (some)
|
|Network management
|
|-
|Content
|
|
|
|
|
|-
|Video Server
|
|
|
|
|
|-
|Cache\Proxy
|
|
|
|
|
|-
|Mail
|
|
|
|
|
|-
|Security encryption
|
|
|
|
|
|-
|Wiki / image hosting
|
|
|
|
|
|-
|Telecentre management
|
|UgaBytes telecentre management software?
|
|
|
|-
|}

==Business Models==

Discussion of business models that have informed the specifications, and a checkback whether we feel that the current specifications actually accomodate all these models.

The template on top suggests dimensions / criteria from which to look at the various models.

===Business Model Template===

* Description:

* Economics: Free or paid by ....
* Billing models: Subscription / Prepaid (Time/Data based):
* Applications:
* Network / Topology:
* Internet uplink:
* User Devices / Locations:
* Startup Strategy:
* Legal & Regulatory

===Telecentre / Internet Cafe / Hotspot===

* Description: "Classical" telecentre / cafe style

* Economics: Free or paid by users / advertisers / cafe business
* Billing models: typically Prepaid (Time based):
* Applications: typically Browser / Mail / Office / Games
* Network / Topology: wired LAN
* Internet uplink: model works with and without uplink, but typically yes
* User Devices / Locations: Users on business owned PC
* Startup Strategy:
* Legal & Regulatory: ok in most (?) countries

===Telco===

* Description: Telco offering "fixed line" and mobile VoIP telephony

* Economics: Part free (?) (local) / paid by user
* Billing models: typically Prepaid (Time/Data based):
* Applications: VoIP telephony, typically on dedicated hardware
* Network / Topology: Centralized / Inframesh
* Internet uplink: Yes, if terminating external calls / local loop without
* User Devices / Locations: Users at home / office / mobile, Device VoIP handsets, ATA etc
* Startup Strategy:
* Legal & Regulatory: complex, country to country

===(Edu)Content / Media===

===Intranet / Neighbour-Net===

===Line Sharing===

===ISP===

===Web Hosting / Design===

===Corporate / Managend Services===

===Guesthouse Net===

===Housing Complex===

===Surveillance===

===Freifunk style Mesh===

===Training / Consultancy===

= Notes from the meeting - Day 3=

==Ndlovu Medical Centre==

Henry introduces:

* Status of mesh: operational, but currently disconnected (concerns about lightning)
* Use of uplink: Browsing (for community users), sync with data center (Johannesburg)
* Status of uplink: promised by Telkom, but not delivered yet

How to get started with a community mesh?

* Donated PCs - 25 pcs
** Give to local entrepreneur types
* Computer school as entry point

* Create a starter kit
** for existing PCs (there is some! mostly free windows)
** preconfigured
** low cost
** probably of the type: Linksys WRT, open-mesh/accton

Financing model

* Some contribution from user: Prepaid - low cost

What is interesting for people?

* music!!! open music server locally?
* free books? educational material
* free local calls
* a free wikipedia / digital doorway

Income from other sources (not the users):

* advertisements

To do / upcoming:

* '''call for a brainstorm meeting within the community'''

* June 9, meeting with provincial directory

* June 24: excursion to Ndlovu? participants of Wireless Africa meeting, Meraka people, Tom, Elektra

Top pain points / whats in the way:

* political level - get OKs from important players

==Hardware reference platform==

===Overall Requirements===

* 12 Volts (best: 11 ... 16)
* low power
* fanless

===Backend server===

* USB 2x
* ethernet 2x
* VGA

Candidate for reference choice:

* bigger solution: VIA, jetway 1.2 GHz, 2x HD, 1 GB RAM, USD 680 ... 820 [http://mini-box.com e.g. mini-box-com]
** power: approx 25W ?
* smaller solution: VIA, AMD Geode 500 MHz
** power: 8 W
* LEX light/neo, e.g. 1 GB C7 approx USD 600 [http://www.lex.com.tw/ http://www.lex.com.tw/]
* soon to come: Atom based low cost desktops (Mark Summer)

====Software on backend====

Decision: Ubuntu (non X)

----

===Access node===

* ethernet 2x
* PoE
* outdoor casing
* broadcom or atheros chipset
* 5 ... 18 Volts
* Watchdog (option)
* WISPCAR (option)
* serial port

Candidates:

* Linksys WRT54GL
** price: EUR 50, ZAR 600, USD 60
** power: 4 W
** comments:

* Ubiqiti
** price: NS 2: USD 79
** price: PS 2: USD 110
** power: 5 W

* Accton
** price: USD 40
** power: 2-3 W ?
** comments: overheat problems? needs fixed power 5 V? quality of radio? unstable across channels?

* PCEngines board
** price: > USD 250
** power: approx > 8W, depending on radio cards
** comments:

* Soekris

* Gateworks
**
**

* Wiligear

===A word on the punishment for every watt===

Elektra, conservative estimate:

To power a 5 Watt device reliably, install a 80 Watt solar panel.

This means: 16 Watt solar panel per 1 Watt installed.

At about USD 5 per solar panel watt (current rough guess for market price), we have:

USD 80 in solar panel per 1 Watt installed.

Even when demanding less margin from the solar power system (i.e. less solar panels per consumer), the fine for every Watt installed is heavy.

==Next steps==

* Examine the Ubiquiti - Lead: Elektra
** flash OpenWRT
** Examine the SDK

* Procurement - Lead: Kobus/Ajay
** ??? x Inveneo small server
**

* Examine the Inveneo Hub Linux (IHL)

* Software development
** Meraka - Priority: the set of Coova (alternative: WifiDog) / FreeRadius / phpMyPrepaid (alternative: ISPBill) / Nagios
** Inveneo - Priority: Server squid/cache, proxy, asterisk, Webmin/ISPConfig

WISPiab work meeting 200806

2008-06-04T14:56:31Z

Sebastian: /* Requirements, Specifications, Wishlist */

WISPiab work meeting 200806

2008-06-04T14:45:22Z

Sebastian: /* Next steps */

WISPiab work meeting 200806

2008-06-04T14:37:39Z

Sebastian: /* Software on backend */

WISPiab work meeting 200806

2008-06-04T14:36:40Z

Sebastian: /* Backend server */

WISPiab work meeting 200806

2008-06-04T14:27:33Z

Sebastian: /* A word on the punishment for every watt */

WISPiab work meeting 200806

2008-06-04T14:07:24Z

Sebastian:

WISPiab work meeting 200806

2008-06-04T13:31:16Z

Sebastian:

WISPiab work meeting 200806

2008-06-04T12:54:44Z

Sebastian:

WISPiab work meeting 200806

2008-06-04T10:32:37Z

Sebastian: /* Ndlovu Medical Centre */

WISPiab work meeting 200806

2008-06-04T10:20:52Z

Sebastian: /* Ndlovu Medical Centre */

WISPiab work meeting 200806

2008-06-04T10:07:19Z

Sebastian: /* Ndlovu Medical Centre */

WISPiab work meeting 200806

2008-06-04T09:48:31Z

Sebastian:

WISPiab work meeting 200806

2008-06-04T08:16:38Z

Sebastian: /* Requirements, Specifications, Wishlist */

WISPiab work meeting 200806

2008-06-04T07:59:52Z

Sebastian: /* Business Models */

WISPiab work meeting 200806

2008-06-04T07:38:08Z

Sebastian: /* Notes from the meeting - Day 2 */

WISPiab work meeting 200806

2008-06-04T07:37:45Z

Sebastian: /* Notes from the meeting - Day 2 */

WISPiab work meeting 200806

2008-06-04T07:36:31Z

Sebastian: /* Business Models */

WISPiab work meeting 200806

2008-06-04T07:32:00Z

Sebastian: /* Requirements, Specifications, Wishlist */