WirelessAfrica - User contributions [en]

DIY Mesh Guide Software and Resources

2011-12-07T07:03:28Z

Ajay: /* Resources */

{|align="right"
| style="height:100%;width:20em;border:1px solid #D9D9D9;background-color:#F2F2F2;" valign="top" |

*[[DIY_Mesh_Guide|'''DIY Mesh Guide Home''']]
*[[DIY_Mesh_Guide_Download|'''Download Guide''']]
*[[DIY_Mesh_Guide_Feedback|'''Feedback Received''']]
*[[DIY_Mesh_Guide_Software_and_Resources|'''Hardware & Software requirements and Resources''']]
|}

== Pilot mesh projects ==

A number of pilot mesh projects across the world have demonstrated that a community can establish and maintain a wireless mesh network and have access to a range of modern information and communication services. Below are some of the examples mentioned in the guide.

*[http://www.cuwireless.net/ Champaign-Urbana Community Wireless Network (CUWiN)]

*[http://start.freifunk.net/ Freifunk.net] and [http://wiki.freifunk.net/Hauptseite Freifunk wiki site]

*[http://www.tibtec.org/ Dharamsala Community Wireless Mesh Network]

*[http://link.net.zm/ Linknet], Macha, Zambia

*Peebles Valley in South Africa [[Mpumulanga Mesh]] and [http://www.fmfi.org.za/wiki/index.php/Mpumalanga_Mesh:Project_Overview First Mile First Inch (FMFI) Mpumalanga Mesh]

==Hardware Required==

Wireless routers: Linksys WRT54G (up to version 4.0) or Linksys WRT54GL (version 1.0 or 1.1). From WRT54G version 5.0 the flash memory has been reduced from 4MB to 2MB and as a result the memory is no longer sufficient for the Freifunk firmware. The Linksys WRT54GL is currently one of the most popular devices for wireless networking.

Running old firmware on new hardware can hang up the router. You can check the [http://en.wikipedia.org/wiki/WRT54G Wikipedia Linksys page] for specifications of the different Linksys models and hardware revisions.

==Software Required==

The Freifunk and DD-WRT firmware is continually being updated and new releases are available on a regular basis. Always check for the latest versions online as the DIY Guide might not be updated regularly enough to reflect the newest versions of the firmware.

* '''Freifunk firmware version x.x.x''' (The latest version of the firmware can be download from http://download-master.berlin.freifunk.net/ipkg/_g+gl/ ) If the full names of the files are not fully displayed, move the mouse over each name/link and notice the bottom left corner of your screen for the full name of the file. All these files are the same except for the language (i.e. English, German, etc.) they have been built for. To download the English version, select openwrt-g-freifunk-x.x.x-en.bin. Note the folder/directory to which this file is stored on your local machine. The firmware is continually being updated and revised. You can see the [http://download-master.berlin.freifunk.net/ipkg/readme.txt readme.txt] in the Freifunk packages directory for an explanation of the different firmware packages available.

* '''DD-WRT firmware version x.x''' (download from http://www.dd-wrt.com/dd-wrtv2/downloads.php ) Select ''stable'' → select ''dd-wrt.vxx SP2'' → select ''standard'' → select ''dd-wrt.vxx_wrt54g.bin''

* '''Putty.exe''' - This is a Windows SSH client, required for any PC/laptop running Windows (download from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html or other website on the internet)

* '''Tcpdump''' (download the latest tcpdump and libpcap library from http://downloads.openwrt.org/whiterussian/packages/ )

* '''dot-draw''' (download the latest olsrd-mod-dot-draw package from http://downloads.openwrt.org/whiterussian/packages/ )

==Resources==

*[http://wire.less.dk/cantenna/ '''Video - Making a Cantenna'''] The video shows, step-by-step, the building of a cantenna (antenna made from a can) for wireless networking (Wi-Fi, WLAN at 2.4 Ghz). Without audio, and with simple subtitles and clear pantomimic instructions, the video lends itself well to localisation.

*[http://wndw.net/download.html '''Wireless Networking in the Developing World'''] The overall goal of this book is to help you build affordable communication technology in your local community by making best use of whatever resources are available. Using inexpensive off-the-shelf equipment and local sources for materials and fabricating parts yourself, you can build reliable network links with very little budget. By working with your local community, you can build a telecommunications infrastructure that benefits everyone who participates in it.

*[http://www.it46.se/downloads/voip4d/en_voip4d_it46_release_web.pdf '''VoIP-4D Primer''' - Building Voice Infrastructure in Developing Regions] The guide explains the essentials of telephony use over the internet in developing countries. It also includes hands-on guidelines and configuration files as a background to building your own telephony system

----
Please report any broken links to '''diymeshguide[at]meraka.org.za'''

DIY Mesh Guide Software and Resources

2011-12-07T07:02:46Z

Ajay: /* Resources */

{|align="right"
| style="height:100%;width:20em;border:1px solid #D9D9D9;background-color:#F2F2F2;" valign="top" |

*[[DIY_Mesh_Guide|'''DIY Mesh Guide Home''']]
*[[DIY_Mesh_Guide_Download|'''Download Guide''']]
*[[DIY_Mesh_Guide_Feedback|'''Feedback Received''']]
*[[DIY_Mesh_Guide_Software_and_Resources|'''Hardware & Software requirements and Resources''']]
|}

== Pilot mesh projects ==

A number of pilot mesh projects across the world have demonstrated that a community can establish and maintain a wireless mesh network and have access to a range of modern information and communication services. Below are some of the examples mentioned in the guide.

*[http://www.cuwireless.net/ Champaign-Urbana Community Wireless Network (CUWiN)]

*[http://start.freifunk.net/ Freifunk.net] and [http://wiki.freifunk.net/Hauptseite Freifunk wiki site]

*[http://www.tibtec.org/ Dharamsala Community Wireless Mesh Network]

*[http://link.net.zm/ Linknet], Macha, Zambia

*Peebles Valley in South Africa [[Mpumulanga Mesh]] and [http://www.fmfi.org.za/wiki/index.php/Mpumalanga_Mesh:Project_Overview First Mile First Inch (FMFI) Mpumalanga Mesh]

==Hardware Required==

Wireless routers: Linksys WRT54G (up to version 4.0) or Linksys WRT54GL (version 1.0 or 1.1). From WRT54G version 5.0 the flash memory has been reduced from 4MB to 2MB and as a result the memory is no longer sufficient for the Freifunk firmware. The Linksys WRT54GL is currently one of the most popular devices for wireless networking.

Running old firmware on new hardware can hang up the router. You can check the [http://en.wikipedia.org/wiki/WRT54G Wikipedia Linksys page] for specifications of the different Linksys models and hardware revisions.

==Software Required==

The Freifunk and DD-WRT firmware is continually being updated and new releases are available on a regular basis. Always check for the latest versions online as the DIY Guide might not be updated regularly enough to reflect the newest versions of the firmware.

* '''Freifunk firmware version x.x.x''' (The latest version of the firmware can be download from http://download-master.berlin.freifunk.net/ipkg/_g+gl/ ) If the full names of the files are not fully displayed, move the mouse over each name/link and notice the bottom left corner of your screen for the full name of the file. All these files are the same except for the language (i.e. English, German, etc.) they have been built for. To download the English version, select openwrt-g-freifunk-x.x.x-en.bin. Note the folder/directory to which this file is stored on your local machine. The firmware is continually being updated and revised. You can see the [http://download-master.berlin.freifunk.net/ipkg/readme.txt readme.txt] in the Freifunk packages directory for an explanation of the different firmware packages available.

* '''DD-WRT firmware version x.x''' (download from http://www.dd-wrt.com/dd-wrtv2/downloads.php ) Select ''stable'' → select ''dd-wrt.vxx SP2'' → select ''standard'' → select ''dd-wrt.vxx_wrt54g.bin''

* '''Putty.exe''' - This is a Windows SSH client, required for any PC/laptop running Windows (download from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html or other website on the internet)

* '''Tcpdump''' (download the latest tcpdump and libpcap library from http://downloads.openwrt.org/whiterussian/packages/ )

* '''dot-draw''' (download the latest olsrd-mod-dot-draw package from http://downloads.openwrt.org/whiterussian/packages/ )

==Resources==

*[http://wire.less.dk/cantenna/ '''Video - Making a Cantenna'''] The video shows, step-by-step, the building of a cantenna (antenna made from a can) for wireless networking (Wi-Fi, WLAN at 2.4 Ghz). Without audio, and with simple subtitles and clear pantomimic instructions, the video lends itself well to localisation.

*[http://http://wndw.net/download.html '''Wireless Networking in the Developing World'''] The overall goal of this book is to help you build affordable communication technology in your local community by making best use of whatever resources are available. Using inexpensive off-the-shelf equipment and local sources for materials and fabricating parts yourself, you can build reliable network links with very little budget. By working with your local community, you can build a telecommunications infrastructure that benefits everyone who participates in it.

*[http://www.it46.se/downloads/voip4d/en_voip4d_it46_release_web.pdf '''VoIP-4D Primer''' - Building Voice Infrastructure in Developing Regions] The guide explains the essentials of telephony use over the internet in developing countries. It also includes hands-on guidelines and configuration files as a background to building your own telephony system

----
Please report any broken links to '''diymeshguide[at]meraka.org.za'''

DIY Mesh Guide Software and Resources

2011-12-07T07:01:43Z

Ajay: /* Resources */ Correction of broken link, thanks to Karen Nyhus for spotting the error

{|align="right"
| style="height:100%;width:20em;border:1px solid #D9D9D9;background-color:#F2F2F2;" valign="top" |

*[[DIY_Mesh_Guide|'''DIY Mesh Guide Home''']]
*[[DIY_Mesh_Guide_Download|'''Download Guide''']]
*[[DIY_Mesh_Guide_Feedback|'''Feedback Received''']]
*[[DIY_Mesh_Guide_Software_and_Resources|'''Hardware & Software requirements and Resources''']]
|}

== Pilot mesh projects ==

A number of pilot mesh projects across the world have demonstrated that a community can establish and maintain a wireless mesh network and have access to a range of modern information and communication services. Below are some of the examples mentioned in the guide.

*[http://www.cuwireless.net/ Champaign-Urbana Community Wireless Network (CUWiN)]

*[http://start.freifunk.net/ Freifunk.net] and [http://wiki.freifunk.net/Hauptseite Freifunk wiki site]

*[http://www.tibtec.org/ Dharamsala Community Wireless Mesh Network]

*[http://link.net.zm/ Linknet], Macha, Zambia

*Peebles Valley in South Africa [[Mpumulanga Mesh]] and [http://www.fmfi.org.za/wiki/index.php/Mpumalanga_Mesh:Project_Overview First Mile First Inch (FMFI) Mpumalanga Mesh]

==Hardware Required==

Wireless routers: Linksys WRT54G (up to version 4.0) or Linksys WRT54GL (version 1.0 or 1.1). From WRT54G version 5.0 the flash memory has been reduced from 4MB to 2MB and as a result the memory is no longer sufficient for the Freifunk firmware. The Linksys WRT54GL is currently one of the most popular devices for wireless networking.

Running old firmware on new hardware can hang up the router. You can check the [http://en.wikipedia.org/wiki/WRT54G Wikipedia Linksys page] for specifications of the different Linksys models and hardware revisions.

==Software Required==

The Freifunk and DD-WRT firmware is continually being updated and new releases are available on a regular basis. Always check for the latest versions online as the DIY Guide might not be updated regularly enough to reflect the newest versions of the firmware.

* '''Freifunk firmware version x.x.x''' (The latest version of the firmware can be download from http://download-master.berlin.freifunk.net/ipkg/_g+gl/ ) If the full names of the files are not fully displayed, move the mouse over each name/link and notice the bottom left corner of your screen for the full name of the file. All these files are the same except for the language (i.e. English, German, etc.) they have been built for. To download the English version, select openwrt-g-freifunk-x.x.x-en.bin. Note the folder/directory to which this file is stored on your local machine. The firmware is continually being updated and revised. You can see the [http://download-master.berlin.freifunk.net/ipkg/readme.txt readme.txt] in the Freifunk packages directory for an explanation of the different firmware packages available.

* '''DD-WRT firmware version x.x''' (download from http://www.dd-wrt.com/dd-wrtv2/downloads.php ) Select ''stable'' → select ''dd-wrt.vxx SP2'' → select ''standard'' → select ''dd-wrt.vxx_wrt54g.bin''

* '''Putty.exe''' - This is a Windows SSH client, required for any PC/laptop running Windows (download from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html or other website on the internet)

* '''Tcpdump''' (download the latest tcpdump and libpcap library from http://downloads.openwrt.org/whiterussian/packages/ )

* '''dot-draw''' (download the latest olsrd-mod-dot-draw package from http://downloads.openwrt.org/whiterussian/packages/ )

==Resources==

*[http://wire.less.dk/cantenna/ '''Video - Making a Cantenna'''] The video shows, step-by-step, the building of a cantenna (antenna made from a can) for wireless networking (Wi-Fi, WLAN at 2.4 Ghz). Without audio, and with simple subtitles and clear pantomimic instructions, the video lends itself well to localisation.

*[http://wndw.net/pdf/wndw-ebook.pdf '''Wireless Networking in the Developing World'''] The overall goal of this book is to help you build affordable communication technology in your local community by making best use of whatever resources are available. Using inexpensive off-the-shelf equipment and local sources for materials and fabricating parts yourself, you can build reliable network links with very little budget. By working with your local community, you can build a telecommunications infrastructure that benefits everyone who participates in it.

*[http://www.it46.se/downloads/voip4d/en_voip4d_it46_release_web.pdf '''VoIP-4D Primer''' - Building Voice Infrastructure in Developing Regions] The guide explains the essentials of telephony use over the internet in developing countries. It also includes hands-on guidelines and configuration files as a background to building your own telephony system

----
Please report any broken links to '''diymeshguide[at]meraka.org.za'''

VO Requirements & Functionality Questions

2009-10-15T07:13:59Z

Ajay: New page: == Understanding the bigger picture == The development on this project is done in phases. New functionalities/features are added with each phase until we reach our target system. All deve...

== Understanding the bigger picture ==

The development on this project is done in phases. New functionalities/features are added with each phase until we reach our target system. All development work of every phase should be aligned with our end system in mind. In order for developers to make the right design choices that will not limit future functionality, they need to have a clear end target that they are working towards.

This page is here to help the developers to get a better understanding of the bigger picture and to make sure the target we design for is clearly defined and does not move around.

Please add any project related questions/thoughts on this page so that we can sort them and see what information is still missing.

=== VO (village operator) in action ===

Lets assume the the new VO has all the kit installed. The gateway (WISP) box is connected to the Internet and he is now ready to commission his new business. His first customers are three Dinaledi schools, the local Municipality and two owners of a local Spaza shop who wants a mesh connection at the shop and at both their homes. The two shop owners are very excited and they want to put a web server at their shop and they are thinking about opening a little Internet cafe very soon.

=== Definitions ===
* User - An accounting entity with a user name and password. Typically represents an individual or an organisation.
* Edge device - A device that is part of the mesh network (talk mesh protocol) and allows other devices to connect through the mesh. HPNs and Basic Mesh Nodes are edge devices.
* HPN - High Performance Node
* BN - Basic Node

=== Random questions / thoughts ===

* What Internet contract packages are available from the VO - prepaid, contract, SA local, gov sites only ???
:: 1 - Access to government sites (incl. educational network) for free - e.g. see P.I.T. (http://www.pit.co.za)
:: 2 - Access to other Internet services to be similar to SA ISP - ADSL offerings (e.g. http://www.broadbanddeals.co.za/index.php?mode=cat&id=ADSL).
:: 3 - A complete and complex model (like mobile offerings) could include:
::: I - Setup/joining fee + monthly fee + usage fee + cancellation fee
::: II - Different usage fees for mesh + education/gov + SA peers + international
::: III - Different fees at different time of day / time of week
::: IV - Different fees for different ports at the gateway
::: V - Different fees for quality of service being offered
::: VI - Different fees for (near-) real-time traffic than for potential store-and-forward traffic
::: VII - Fees for additional services (VoIP, local hosting, local e-mail, etc.), each with its own fee structure
:: 4 - In an ideal world, everyone on the mesh should get unlimited access with fixed monthly fee. Other users to be serviced by downstream providers (e.g. Internet Cafés).

* Is data traffic on the mesh free / flat fee / pay per usage
:: 1 - Local traffic is free. Acceptable use policy to be applied (e.g. http://www.is.co.za/legal/Acceptable+Use+Policy+(continued).htm).

* must a user do some login before he can use the mesh
:: 1 - Specific edge devices can be vetted as flat-fee, requiring no login for attached devices
:: 2 - All others will require user login (e.g. following captive portal instructions)

* must the mesh be able to log all user traffic between mesh users
:: 1 - Amount of traffic entering and exiting at edge devices should be logged and categorised
:: 2 - Amount of traffic on specific radio links within the mesh should be logged and categorised
:: 3 - Amount of traffic entering and exiting at gateway should be logged and categorised
:: 4 - Traffic required for billing purposes should be logged

* can a user use the mesh without buying prepaid/account from the VO
:: 1 - Yes, assuming the edge device have been approved beforehand.

* How must a prepaid package be activated / deactivated
:: 1 - The user or the edge device to be given time, capacity, or flat approval.
:: 2 - Village Operator can deactivate a user account or edge device in case of abuse.
:: 3 - New users and new devices, not yet approved, and deactivated devices, to present captive portal with activation instructions.

* Are there any bandwidth limits tied to a Internet package
:: 1 - Preferably no capacity limits.
:: 2 - Prioritisation of traffic according to device type (HPN higher pri than BN), and/or service (VoIP higher pri than HTTP)?
:: 3 - No bandwidth limits.

* Are there any data caps associated with the different package
:: 1 - Preferably no, unless it is forced by on-sell of upstream ISP offering (see first question about Internet packages)

* Must a prepaid user login before he can use the Internet
:: 1 - User based prepaid will require login. Edge device based accounting require no login.

* Must a prepaid user login before he can send data on the mesh (no Internet)
:: 1 - No, assuming the edge device has been approved for use on the mesh.

* How about a gaming server on the mesh, does it need to login some where
:: 1 - Depends on the administrator of the gaming server. (Or any other local online content/facility/service provider).

* Can more than one user share the same prepaid account, and at the same time
:: 1 - Yes

* If a school uses prepaid, do they share the same account, or each user in school
:: 1 - General Internet access at school can be user (individuals or groups) based or edge device based. Depends on school policy.

* How will someone running an Internet cafe resell his prepaid bandwidth
:: 1 - Internet café business offerings outside immediate scope of the WISP software. Depending on Café owner, and Café management software, access could be provided on a time basis or capacity basis.

* Is a prepaid account tied to certain time duration
:: 1 - Yes. And those that are capacity based may also expire after 3(?) months.

* How does a person get onto the network?
:: 1 - Activation instructions presented on captive portal. Village Operator to provide login details and/or device approval.

* If login is necessary, how do peripherals like printers and ATAs authenticate?
:: 1 - Local traffic don't need login.
:: 2 - Edge devices can be the basis for accounting, in which case further connected devices don't need login.

* What devices should be 'approved' for use on the network
:: 1 - Edge devices

=== The VO ===
A VO is a person or an entity whose primary objective is running (at a profit) a wireless network. To this end, the following describes the needs or requirements of the VO to meet his objective.

The VO needs:

1. A healthy and working network

2. Diagnostic tools for the network

3. To manage users or subscribers to the network

4. Service management of the network

5. A view of the usage of the network

6. To manage (activate/deactivate) edge devices on the network

1. A healthy and working network

-> Each network element MUST handle all routing and communications other network elements.

-> Each network element MUST require of the VO as minimum as possible configuration without compromising its usability or effectiveness.

2. Diagnostic tools for the network

At a minimum, the VO is provided with a web based diagnostic tools.

-> The diagnostic tools are enough for the VO to establish any problem that may be there.

-> The diagnostic tools can interface with other systems, e.g SMS, email.

3. To manage users or subscribers to the network

-> VO will be able create and modify user accounts

-> VO provides a number of service options for different users

-> VO can monitor usage of the internet connection

-> VO can monitor usage of the local network

-> VO can block access to the network for certain users

4. Service management of the network

-> The VO is able to prioritise certain services within the network

-> The VO is able to block or enable certain services

5. A view of the usage of the network

-> The VO is able to see the usage of the whole network

-> The VO is able to see the usage of each network element

6. To manage (activate/deactivate) edge devices in the network

-> VO can allow (new) edge devices to join the network

-> VO can block edge devices from accessing the mesh network

WISP in a Box Development

2009-10-15T07:13:26Z

Ajay: /* Development */

{|align="right"
| style="height:100%;width:20em;border:1px solid #D9D9D9;background-color:#F2F2F2;" valign="top" |
*[[WISP_in_a_Box_Development|'''WISP in a Box Development Home''']]
|}

== Developer Guide ==

WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project.

In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:

* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.

* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.

* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their contributions to the project usually take the form of running the software, reporting bugs on the mailing list and requesting features.

* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and desire to contribute code patches, documentation and their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributors. Contributors are a necessary condition to the long-term sustainability of any Libré project. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.

* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.

[[Image:libre_software_cycle.png|left|frame|The Libré Software Development Cycle]]

 

=== Upstream Projects ===

WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:

* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.

=== Setup Checklist ===

{| cellpadding="5" cellspacing="0" border="1"
! Task !! Description
|- valign="top"
| Development Workstation ||
* x86
* FreeBSD or Ubuntu
* 1x Edimax 7711UM USB WiFi network card
|- valign="top"
| WISP Server ||
* AMD ION
* 1GB RAM
* 80GB Hard Drive
* D-Link USB Ethernet
|- valign="top"
| Development Mesh Node ||
* D-Link DIR-300
|- valign="top"
| Deployment Mesh Node ||
* HPN
|- valign="top"
| Subscribe to mailing lists || TODO
|- valign="top"
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)
|- valign="top"
| Configure WispBox Development Environment ||
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment
|- valign="top"
| Configure Afrimesh Development Environment ||
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment
|-
|}

=== Core Project Infrastructure ===

{| cellpadding="5" cellspacing="0" border="1"
! Resource !! URL !! Description
|-
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.
|-
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.
|-
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!
|-
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh
|-
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development ||
|-
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki
|-
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki
|-
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout ||
|-
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout ||
|-
| Package Repository || https://launchpad.net/~wispinabox ||
|-
| Build Server || TO COME ||
|-
|}

=== Resources ===

* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers to Entry''']] - Neary Consulting [http://www.neary-consulting.com]

== Development ==

=== [[VO Requirements & Functionality Questions]] ===

WISP in a Box Development

2009-10-15T07:12:18Z

Ajay:

User:Ajay

2009-08-06T13:10:32Z

Ajay: /* Development Team Research Pages */

==DIY Mesh Guide==
[[DIY_Mesh_Guide]]

==WISP in a box project==

[[The_WISP-in-a-box_project]]

[[WISP-in-a-box_Way_Forward]]

[[WISP_Coova_phpMyPrepaid]]

==High Performance Node ==

[[High_performance_node_page]] - migrated

[[High_Performance_Node_-_Setup]] Setup for bokkie routers at Ndlovu

[[High_Performance_Node_-_Specification]] - migrated

[[High_Performance_Node_-_Dev_and_Test_Network]] - migrated

[[High_Performance_Node_-_Software]] Software related - migrated

==VoIP==

[[VoIP]]

== Development Team Research Pages ==
'''George: ''' [[George%27s_Research]] - migrated

'''Johann: ''' [[Johann%27s_Research]] - migrated

'''Lawrence: ''' [[Lawrence%27s_Research]] - migrated

'''Ntuthuko: ''' [[Ntuthuko%27s_Research]] - migrated

'''Tom: ''' [[Tom%27s_research]]

'''Ajay: ''' [[Ajay%27s_research]] - migrated

'''Gerhard: ''' [[Gerhard%27s_research]] - migrated

'''John: ''' [[John%27s_research]] - migrated

'''Antoine:''' [[Antoine%27s_Research]]

User:Ajay

2009-08-06T13:10:14Z

Ajay: /* High Performance Node */

==DIY Mesh Guide==
[[DIY_Mesh_Guide]]

==WISP in a box project==

[[The_WISP-in-a-box_project]]

[[WISP-in-a-box_Way_Forward]]

[[WISP_Coova_phpMyPrepaid]]

==High Performance Node ==

[[High_performance_node_page]] - migrated

[[High_Performance_Node_-_Setup]] Setup for bokkie routers at Ndlovu

[[High_Performance_Node_-_Specification]] - migrated

[[High_Performance_Node_-_Dev_and_Test_Network]] - migrated

[[High_Performance_Node_-_Software]] Software related - migrated

==VoIP==

[[VoIP]]

== Development Team Research Pages ==
'''George: ''' [[George%27s_Research]]

'''Johann: ''' [[Johann%27s_Research]] - migrated

'''Lawrence: ''' [[Lawrence%27s_Research]] - migrated

'''Ntuthuko: ''' [[Ntuthuko%27s_Research]] - migrated

'''Tom: ''' [[Tom%27s_research]]

'''Ajay: ''' [[Ajay%27s_research]] - migrated

'''Gerhard: ''' [[Gerhard%27s_research]] - migrated

'''John: ''' [[John%27s_research]] - migrated

'''Antoine:''' [[Antoine%27s_Research]]

George's Research

2009-08-06T13:07:59Z

Ajay: Replacing page with 'Category: Development Team Research Pages migrated to wireless dev'

[[Category: Development Team Research Pages]]

migrated to wireless dev

MediaWiki:Sidebar

2009-08-05T08:24:14Z

Ajay:

* navigation
** mainpage|Wireless Africa Home
** currentevents-url|currentevents
** recentchanges-url|recentchanges
** Downloads|Downloads
** HowTos|HowTos
** Contact|Contact
** Links|Links
** http://wirelessafrica.meraka.org.za/map/|Project Sites Google Map
** helppage|help

*Technology research
**Wireless Mesh Networking|Wireless Mesh Networking
**Wireless Network Technology|Wireless Network Technology
**Research areas being addressed|Research areas being addressed
**Real-Time Video Coding|Real-Time Video Coding group

*Technology Development
**WISP in a Box Development|WISP Development

*Testbed networks
**49-node Indoor Mesh|49-node Indoor Mesh
**Pretoria Mesh|Pretoria Mesh
**Mpumulanga Mesh|Mpumulanga Mesh
**Mamelodi Mesh|Mamelodi Mesh

*Social research
**http://llisa.meraka.org.za|Living Labs in Southern Africa (LLiSA)

*Resources
**Cost Tables|Cost Tables
**DIY_Mesh_Guide|DIY Mesh Guide

*Partners\Collaborations
**http://www.cs.ucsb.edu/|UCSB - computer science
**http://www.wireless-world-research.org/|WWRF
**http://www.cuwireless.net/|CUWiN
**http://www.fmfi.org.za/|First Mile First Inch
**http://link.net.zm/ |Linknet
**http://www.wireless-africa.org|Wireless Africa - IDRC

MediaWiki:Sidebar

2009-08-05T08:23:26Z

Ajay:

WISP in a Box Development

2009-08-05T08:22:23Z

Ajay:

{|align="right"
| style="height:100%;width:20em;border:1px solid #D9D9D9;background-color:#F2F2F2;" valign="top" |
*[[WISP_in_a_Box_Development|'''WISP in a Box Development Home''']]
|}

== Developer Guide ==

WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project.

In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:

* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.

* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.

* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their contributions to the project usually take the form of running the software, reporting bugs on the mailing list and requesting features.

* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and desire to contribute code patches, documentation and their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributors. Contributors are a necessary condition to the long-term sustainability of any Libré project. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.

* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.

[[Image:libre_software_cycle.png|left|frame|The Libré Software Development Cycle]]

 

=== Upstream Projects ===

WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:

* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.

=== Setup Checklist ===

{| cellpadding="5" cellspacing="0" border="1"
! Task !! Description
|- valign="top"
| Development Workstation ||
* x86
* FreeBSD or Ubuntu
* 1x ??? USB WiFi network card
|- valign="top"
| WISP Server ||
* AMD ION
* 1GB RAM
* 80GB Hard Drive
* D-Link USB Ethernet
|- valign="top"
| Development Mesh Node ||
* D-Link DIR-300
|- valign="top"
| Deployment Mesh Node ||
* HPN
|- valign="top"
| Subscribe to mailing lists || TODO
|- valign="top"
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)
|- valign="top"
| Configure WispBox Development Environment ||
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment
|- valign="top"
| Configure Afrimesh Development Environment ||
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment
|-
|}

=== Core Project Infrastructure ===

{| cellpadding="5" cellspacing="0" border="1"
! Resource !! URL !! Description
|-
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.
|-
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.
|-
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!
|-
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh
|-
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development ||
|-
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki
|-
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki
|-
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout ||
|-
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout ||
|-
| Package Repository || https://launchpad.net/~wispinabox ||
|-
| Build Server || TO COME ||
|-
|}

=== Resources ===

* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers to Entry''']] - Neary Consulting [http://www.neary-consulting.com]

----

WISP in a Box Development

2009-08-05T08:21:53Z

Ajay:

{|align="right"
| style="height:100%;width:20em;border:1px solid #D9D9D9;background-color:#F2F2F2;" valign="top" |
*[[WISP_in_a_Box_Development|'''WISP_in_a_Box_Developmen Home''']]
|}

== Developer Guide ==

WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project.

In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:

* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.

* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.

* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their contributions to the project usually take the form of running the software, reporting bugs on the mailing list and requesting features.

* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and desire to contribute code patches, documentation and their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributors. Contributors are a necessary condition to the long-term sustainability of any Libré project. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.

* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.

[[Image:libre_software_cycle.png|left|frame|The Libré Software Development Cycle]]

 

=== Upstream Projects ===

WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:

* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.

=== Setup Checklist ===

{| cellpadding="5" cellspacing="0" border="1"
! Task !! Description
|- valign="top"
| Development Workstation ||
* x86
* FreeBSD or Ubuntu
* 1x ??? USB WiFi network card
|- valign="top"
| WISP Server ||
* AMD ION
* 1GB RAM
* 80GB Hard Drive
* D-Link USB Ethernet
|- valign="top"
| Development Mesh Node ||
* D-Link DIR-300
|- valign="top"
| Deployment Mesh Node ||
* HPN
|- valign="top"
| Subscribe to mailing lists || TODO
|- valign="top"
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)
|- valign="top"
| Configure WispBox Development Environment ||
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment
|- valign="top"
| Configure Afrimesh Development Environment ||
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment
|-
|}

=== Core Project Infrastructure ===

{| cellpadding="5" cellspacing="0" border="1"
! Resource !! URL !! Description
|-
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.
|-
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.
|-
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!
|-
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh
|-
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development ||
|-
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki
|-
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki
|-
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout ||
|-
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout ||
|-
| Package Repository || https://launchpad.net/~wispinabox ||
|-
| Build Server || TO COME ||
|-
|}

=== Resources ===

* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers to Entry''']] - Neary Consulting [http://www.neary-consulting.com]

----

WISP in a Box Development

2009-08-05T08:21:39Z

Ajay:

{|align="right"
| style="height:100%;width:20em;border:1px solid #D9D9D9;background-color:#F2F2F2;" valign="top" |
*[[WISP_in_a_Box_Development]]|'''WISP_in_a_Box_Developmen Home''']]
|}

== Developer Guide ==

WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project.

In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:

* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.

* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.

* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their contributions to the project usually take the form of running the software, reporting bugs on the mailing list and requesting features.

* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and desire to contribute code patches, documentation and their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributors. Contributors are a necessary condition to the long-term sustainability of any Libré project. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.

* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.

[[Image:libre_software_cycle.png|left|frame|The Libré Software Development Cycle]]

 

=== Upstream Projects ===

WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:

* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.

=== Setup Checklist ===

{| cellpadding="5" cellspacing="0" border="1"
! Task !! Description
|- valign="top"
| Development Workstation ||
* x86
* FreeBSD or Ubuntu
* 1x ??? USB WiFi network card
|- valign="top"
| WISP Server ||
* AMD ION
* 1GB RAM
* 80GB Hard Drive
* D-Link USB Ethernet
|- valign="top"
| Development Mesh Node ||
* D-Link DIR-300
|- valign="top"
| Deployment Mesh Node ||
* HPN
|- valign="top"
| Subscribe to mailing lists || TODO
|- valign="top"
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)
|- valign="top"
| Configure WispBox Development Environment ||
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment
|- valign="top"
| Configure Afrimesh Development Environment ||
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment
|-
|}

=== Core Project Infrastructure ===

{| cellpadding="5" cellspacing="0" border="1"
! Resource !! URL !! Description
|-
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.
|-
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.
|-
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!
|-
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh
|-
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development ||
|-
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki
|-
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki
|-
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout ||
|-
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout ||
|-
| Package Repository || https://launchpad.net/~wispinabox ||
|-
| Build Server || TO COME ||
|-
|}

=== Resources ===

* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers to Entry''']] - Neary Consulting [http://www.neary-consulting.com]

----

WISP in a Box Development

2009-08-05T08:21:21Z

Ajay:

{|align="right"
| style="height:100%;width:20em;border:1px solid #D9D9D9;background-color:#F2F2F2;" valign="top" |
*[[WISP_in_a_Box_Developmen|'''WISP_in_a_Box_Developmen Home''']]
|}

== Developer Guide ==

WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project.

In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:

* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.

* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.

* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their contributions to the project usually take the form of running the software, reporting bugs on the mailing list and requesting features.

* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and desire to contribute code patches, documentation and their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributors. Contributors are a necessary condition to the long-term sustainability of any Libré project. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.

* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.

[[Image:libre_software_cycle.png|left|frame|The Libré Software Development Cycle]]

 

=== Upstream Projects ===

WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:

* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.

=== Setup Checklist ===

{| cellpadding="5" cellspacing="0" border="1"
! Task !! Description
|- valign="top"
| Development Workstation ||
* x86
* FreeBSD or Ubuntu
* 1x ??? USB WiFi network card
|- valign="top"
| WISP Server ||
* AMD ION
* 1GB RAM
* 80GB Hard Drive
* D-Link USB Ethernet
|- valign="top"
| Development Mesh Node ||
* D-Link DIR-300
|- valign="top"
| Deployment Mesh Node ||
* HPN
|- valign="top"
| Subscribe to mailing lists || TODO
|- valign="top"
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)
|- valign="top"
| Configure WispBox Development Environment ||
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment
|- valign="top"
| Configure Afrimesh Development Environment ||
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment
|-
|}

=== Core Project Infrastructure ===

{| cellpadding="5" cellspacing="0" border="1"
! Resource !! URL !! Description
|-
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.
|-
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.
|-
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!
|-
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh
|-
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development ||
|-
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki
|-
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki
|-
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout ||
|-
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout ||
|-
| Package Repository || https://launchpad.net/~wispinabox ||
|-
| Build Server || TO COME ||
|-
|}

=== Resources ===

* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers to Entry''']] - Neary Consulting [http://www.neary-consulting.com]

----

WISP in a Box Development

2009-08-05T08:20:49Z

Ajay:

{|align="right"
| style="height:100%;width:20em;border:1px solid #D9D9D9;background-color:#F2F2F2;" valign="top" |
*[[DIY_Mesh_Guide|'''DIY Mesh Guide Home''']]
|}

----

== Developer Guide ==

WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project.

In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:

* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.

* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.

* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their contributions to the project usually take the form of running the software, reporting bugs on the mailing list and requesting features.

* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and desire to contribute code patches, documentation and their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributors. Contributors are a necessary condition to the long-term sustainability of any Libré project. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.

* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.

[[Image:libre_software_cycle.png|left|frame|The Libré Software Development Cycle]]

 

=== Upstream Projects ===

WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:

* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.

=== Setup Checklist ===

{| cellpadding="5" cellspacing="0" border="1"
! Task !! Description
|- valign="top"
| Development Workstation ||
* x86
* FreeBSD or Ubuntu
* 1x ??? USB WiFi network card
|- valign="top"
| WISP Server ||
* AMD ION
* 1GB RAM
* 80GB Hard Drive
* D-Link USB Ethernet
|- valign="top"
| Development Mesh Node ||
* D-Link DIR-300
|- valign="top"
| Deployment Mesh Node ||
* HPN
|- valign="top"
| Subscribe to mailing lists || TODO
|- valign="top"
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)
|- valign="top"
| Configure WispBox Development Environment ||
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment
|- valign="top"
| Configure Afrimesh Development Environment ||
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment
|-
|}

=== Core Project Infrastructure ===

{| cellpadding="5" cellspacing="0" border="1"
! Resource !! URL !! Description
|-
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.
|-
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.
|-
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!
|-
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh
|-
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development ||
|-
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki
|-
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki
|-
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout ||
|-
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout ||
|-
| Package Repository || https://launchpad.net/~wispinabox ||
|-
| Build Server || TO COME ||
|-
|}

=== Resources ===

* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers to Entry''']] - Neary Consulting [http://www.neary-consulting.com]

----

WISP in a Box Development

2009-08-05T07:41:59Z

Ajay:

----

== Developer Guide ==

WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project.

In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:

* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.

* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.

* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their contributions to the project usually take the form of running the software, reporting bugs on the mailing list and requesting features.

* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and desire to contribute code patches, documentation and their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributors. Contributors are a necessary condition to the long-term sustainability of any Libré project. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.

* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.

[[Image:libre_software_cycle.png|left|frame|The Libré Software Development Cycle]]

 

=== Upstream Projects ===

WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:

* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.

=== Setup Checklist ===

{| cellpadding="5" cellspacing="0" border="1"
! Task !! Description
|- valign="top"
| Development Workstation ||
* x86
* FreeBSD or Ubuntu
* 1x ??? USB WiFi network card
|- valign="top"
| WISP Server ||
* AMD ION
* 1GB RAM
* 80GB Hard Drive
* D-Link USB Ethernet
|- valign="top"
| Development Mesh Node ||
* D-Link DIR-300
|- valign="top"
| Deployment Mesh Node ||
* HPN
|- valign="top"
| Subscribe to mailing lists || TODO
|- valign="top"
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)
|- valign="top"
| Configure WispBox Development Environment ||
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment
|- valign="top"
| Configure Afrimesh Development Environment ||
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment
|-
|}

=== Core Project Infrastructure ===

{| cellpadding="5" cellspacing="0" border="1"
! Resource !! URL !! Description
|-
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.
|-
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.
|-
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!
|-
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh
|-
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development ||
|-
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki
|-
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki
|-
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout ||
|-
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout ||
|-
| Package Repository || https://launchpad.net/~wispinabox ||
|-
| Build Server || TO COME ||
|-
|}

=== Resources ===

* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers to Entry''']] - Neary Consulting [http://www.neary-consulting.com]

----

WISP in a Box Development

2009-08-05T07:36:13Z

Ajay: /* Developer Guide */

WISP in a Box Development

2009-08-05T07:36:02Z

Ajay: formatting of page

WISP in a Box Development

2009-08-05T07:35:45Z

Ajay:

----

== Developer Guide ==

WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project.

In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:

* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.

* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.

* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their contributions to the project usually take the form of running the software, reporting bugs on the mailing list and requesting features.

* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and desire to contribute code patches, documentation and their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributors. Contributors are a necessary condition to the long-term sustainability of any Libré project. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.

* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.

[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]

 

=== Upstream Projects ===

WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:

* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.

=== Setup Checklist ===

{| cellpadding="5" cellspacing="0" border="1"
! Task !! Description
|- valign="top"
| Development Workstation ||
* x86
* FreeBSD or Ubuntu
* 1x ??? USB WiFi network card
|- valign="top"
| WISP Server ||
* AMD ION
* 1GB RAM
* 80GB Hard Drive
* D-Link USB Ethernet
|- valign="top"
| Development Mesh Node ||
* D-Link DIR-300
|- valign="top"
| Deployment Mesh Node ||
* HPN
|- valign="top"
| Subscribe to mailing lists || TODO
|- valign="top"
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)
|- valign="top"
| Configure WispBox Development Environment ||
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment
|- valign="top"
| Configure Afrimesh Development Environment ||
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment
|-
|}

=== Core Project Infrastructure ===

{| cellpadding="5" cellspacing="0" border="1"
! Resource !! URL !! Description
|-
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.
|-
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.
|-
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!
|-
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh
|-
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development ||
|-
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki
|-
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki
|-
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout ||
|-
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout ||
|-
| Package Repository || https://launchpad.net/~wispinabox ||
|-
| Build Server || TO COME ||
|-
|}

=== Resources ===

* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers to Entry''']] - Neary Consulting [http://www.neary-consulting.com]

----

MediaWiki:Sidebar

2009-07-28T11:54:46Z

Ajay: creating a WISP link in the sidebar

Antoine's Research

2009-07-07T09:02:21Z

Ajay:

[[Category: Development Team Research Pages]][[Category: WISP in a box]]

<blockquote>
“ The greatest challenge to any thinker is stating the problem in a way that will allow a solution. 

  - Bertrand Russell
</blockquote>

<blockquote>
“ Go to the people 
Live among the people 
Learn from the people 
Plan with the people 
Work with the people 
Start with what the people know 
Build on what the people have 
Teach by showing; learn by doing 
Not a showcase but a pattern 
Not odds and ends but a system 
Not a piecemeal but an integrated approach 
Not to conform but to transform 
Not relief but release 

  - James Yen
</blockquote>

= ARCHITECTURE =
[[image:antoine-architecture.png|Architecture]]

= TESTBED =

[[image:antoine-testbed.png|Test Bed]]
2x Inveneo (CSIR's)
2x Linksys WRT54GL (Antoine's)
8x Meraki routers (CSIR's)
2x Accton routers (Antoine's)

= PREPARE DEVELOPMENT ENVIRONMENT =

== 1. Check out sources ==
* Check out meraka trunk
TODO - we need a name for this code so that we can create a public source repo for it!
* One of:
** Check out: OpenWRT Kamikaze
$ cd ~
$ svn checkout https://svn.openwrt.org/openwrt/trunk/ kamikaze/
$ cd kamikaze/
$ ./scripts/feeds update -a # Checkout the extra packages
$ ./scripts/feeds install <name_1> <name_2> # Creates the symlinks for the packages you like to install
$ make menuconfig # Select your target, packages and other options. Only select the packages you need.
$ make world
** Symink to existing OpenWRT
TODO

== 2. Configure OpenWRT ==
* Read:
http://wiki.openwrt.org/OpenWrtDocs/BuildingKamikazeHowTo
http://wiki.openwrt.org/OpenWrtDocs/Packages
* Do: Check out SVN version of coova-chilli
cd package ; svn co http://dev.coova.org/svn/coova-ap/packages/kamikaze/coova-chilli ; cd ..
* Run:
./scripts/feeds install libnetsnmp
./scripts/feeds install batmand
./scripts/feeds install batmand-adv
./scripts/feeds install libjson
./scripts/feeds install curl
* Compile packages:
make package/feeds/packages/net-snmp-compile
make package/feeds/packages/libjson-c-compile
* Select packages:
Base->libpthread
Administration->meraka-widgets
Libraries->libjson
Libraries->libcurl
Libraries->libnetsnmp
Libraries->libopenssl
Network->Captive Portals->coova-chilli
Network->batmand
Network->curl

* Edit: package/opkg/files/opkg.conf : 2
src packages http://l-cube.artifactual.org.za/~antoine/firmware/packages/mipsel

== 3. Build Everything ==
* Run:
make
TODO

= INSTALLATION AND CONFIGURATION FOR LINKSYS WRT54G(L) =

== 0. prepare router ==
* Handy:
nvram set boot_wait=on
nvram commit
wget http://l-cube.artifactual.org.za/~antoine/firmware/openwrt-brcm-2.4-squashfs.trx -O - | mtd -e linux -r write - linux
opkg update
opkg install snmpd ; ln -s ../init.d/snmpd S70snmpd

== 1. flash router ==
* Run:
wget http://l-cube.artifactual.org.za/~antoine/firmware/openwrt-brcm-2.4-squashfs.trx -O - | mtd -e linux -r write - linux

== 2.a. configure portal interface (when using wireless port for dev - DEPRECATE) ==
* Read: http://wiki.openwrt.org/OpenWrtDocs/KamikazeConfiguration/NonBridgedWiFi/
* Run:
uci delete network.lan.type
uci set wireless.@wifi-iface[0].network=wifi # TODO - that's whats with the numbers
* DEPRECATE Append: /etc/config/network
config 'interface' 'wifi'
option 'ifname' 'wl0'
* Run:
uci set dhcp.lan.ignore=1
uci set wireless.wl0.disabled=0
uci set network.wifi.ifname=wl0
uci set network.wifi.proto=static
uci set network.wifi.ipaddr=0.0.0.0
uci commit
reboot
* Test:
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -I POSTROUTING -t nat -o eth0.0 -j MASQUERADE
* Append: TODO
echo "echo 1 > /proc/sys/net/ipv4/ip_forward" >> ???
echo "iptables -I POSTROUTING -t nat -o eth0.0 -j MASQUERADE" >> ???

== 2.b. Configure router for B.A.T.M.A.N. (using lan port for dev) ==
* Read:
https://dev.open-mesh.net/svn/batman/trunk/batman-adv-kernelland/batman-core/README
http://open-mesh.net/batman/doc/RoutingVodoo
http://www.blogin.it/check-batman.html
http://trac2.assembla.com/nightwing/browser/trunk/etc/config/batman
http://trac2.assembla.com/nightwing/browser/trunk/etc/config/batman_mode
* Run: (configure LAN interface)
uci delete network.lan.type
uci delete network.lan.gateway
uci delete network.lan.dns
uci set network.lan.ipaddr=192.168.1.1
uci commit
* Run: (temmporarily disable firewall so we can get in to the WAN interface from my own lan side)
iptables --flush
* Run: (OPTIONAL: configure WAN interface for a gateway mesh-node)
uci set network.wan.proto=static
uci set network.wan.ipaddr=192.168.20.200
uci set network.wan.netmask=255.255.255.0
uci set network.wan.dns=192.168.20.5
uci set network.wan.gateway=192.168.20.1
uci commit
* Edit: /etc/config/wireless
append 'cfg' to wifi-iface
* Run: (bring up WIFI interface)
uci set network.wifi=interface
uci set network.wifi.ifname=wl0
uci set wireless.wl0.disabled=0
uci set wireless.wl0.channel=5
uci set wireless.cfg.network=wifi
uci set wireless.cfg.mode=adhoc # TODO - wtf is it with the numbers ?
uci set wireless.cfg.ssid=batman
uci set wireless.cfg.bssid="BB:BB:BB:BB:BB:BB"
uci commit
reboot
* Append: /etc/opkg.conf (for some reason libpthread has gone missing from master)
src packages http://l-cube.artifactual.org.za/~antoine/firmware/packages/mipsel
* One of:
** Run: (install BATMAN)
opkg update
opkg install kmod-batgat # gateway only
opkg install batmand batmand-adv # TODO - how do we get the stable branch to install ?
** Run:
http://downloads.open-mesh.net/batman/stable/mipsel-kamikaze/batmand_0.3-current_mipsel-kk-elf-32-lsb-static.tgz
* Configure: (gateway mesh-node)
rm /etc/rc.d/S45firewall
uci set network.wifi.proto=static
uci set network.wifi.ipaddr=10.0.0.1
uci set network.wifi.netmask=255.0.0.0
* Configure: (normal mesh-node)
rm /etc/rc.d/S45firewall
uci set network.wifi.proto=static
uci set network.wifi.ipaddr=10.0.0.2
uci set network.wifi.netmask=255.0.0.0
uci set network.lan.dns=192.168.20.5 # TODO - LOSE
* Test: (on gateway mesh-node)
iptables -t nat -A POSTROUTING -o eth0.1 -j MASQUERADE # NAT mesh nodes
batmand -g 100mbit wl0 # Start BATMAN
batmand -s 192.168.20.226 -g 100mbit wl0 # If you want viz
batmand -c -d 1 # Monitor
uci set batmand.general.interface=wl0
uci set batmand.general.gateway_class=100mbit
uci set batmand.general.visualisation_srv=192.168.20.226
uci commit
* Test: (on normal mesh-node)
batmand -r 3 wl0
batmand -s 192.168.20.226 -r 3 wl0
uci set batmand.general.interface=wl0
uci set batmand.general.routing_class=3
uci set batmand.general.visualisation_srv=192.168.20.226
uci commit
# iptables -t nat -A POSTROUTING --source 192.168.0.0/24 -o gate0 -j MASQUERADE
iptables -t nat -A POSTROUTING --source 192.168.1.0/24 -o gate0 -j MASQUERADE
ifconfig eth0.0 0.0.0.0 # for portal
/etc/init.d/chilli start # for portal
* Test: (on meraki normal mesh-node)
batmand -r 3 ath0 # Start BATMAN
batmand -s 192.168.20.226 -r 3 ath0 # If you want viz
iptables -t nat -A POSTROUTING --source 192.168.1.0/24 -o gate0 -j MASQUERADE # NAT any clients of this node
uci set batmand.general.interface=ath0
uci set batmand.general.routing_class=3
uci set batmand.general.visualisation_srv=192.168.20.226
uci commit
* Run:
cd /etc/rc.d
ln -s ../init.d/batmand S80batmand
* Clean up before restarting BATMAN: - TODO

== configure vis server ==

* Read:
https://list.open-mesh.net/pipermail/b.a.t.m.a.n/2008-November/001041.html
* Do on dashboard:
svn co http://downloads.open-mesh.net/svn/batman/trunk/ batman-svn
cd batman-svn/vis
make
./vis eth0

== 3. configure portal (coova-chilli) ==
* Read:
!!! http://hotcakes.wiki.sourceforge.net/Coova+Chilli+JSON+Interface
!!! https://help.ubuntu.com/community/WifiDocs/CoovaChilli
http://daloradius.wiki.sourceforge.net/Chillispot+Integration
http://coova.org/wiki/index.php/CoovaChilli/JSON
http://coova.org/wordpress/index.php/2007/08/15/any-page-a-login-page/
* Run:
opkg update
opkg install kmod-tun
opkg install http://l-cube.artifactual.org.za/~antoine/firmware/packages/mipsel/coova-chilli_1.0.12-1_mipsel.ipk
* AUTO * Edit: /etc/chilli/defaults
HS_WANIF=eth0.0 (gate0 for batman)
HS_LANIF=wl0 (eth0.0 for batman)
(HS_NETWORK=192.168.1.0/24 for batman)
(HS_UAMLISTEN=192.168.1.1 for batman)
HS_DNS1=10.1.0.1 (192.168.20.5)
HS_RADIUS=192.168.20.225
HS_RADIUS2=192.168.20.225
HS_ADMUSR=chillispot
HS_ADMPWD=thechillispotsecret
HS_RADSECRET=theradiussecret
HS_UAMSECRET=theuamsecret
HS_UAMALLOW=10.1.0.0/24,192.168.20.0/24 (192.168.1.0/24, 192.168.20.0/24)
HS_UAMSERVER=10.1.0.1 (192.168.1.1)
HS_UAMHOMEPAGE=http://\$HS_UAMLISTEN:\$HS_UAMPORT/www/coova.html # redirects to HS_UAMFORMAT
HS_UAMFORMAT=http://\$HS_UAMSERVER:\$HS_UAMPORT/www/index.html # does JSON login
HS_UAMSERVICE=http://192.168.20.225/cgi-bin/uam.pl # Generates pap-password - Needs perl
* AUTO * Edit: meraka-portal/files/www/cgi-bin/uam.pl
$uamsecret = "theaumsecret";
* AUTO * Edit: /etc/chilli/www/ChilliLibrary.js:296
var logonUrl = chilliController.urlRoot() + 'logon?username=' + escape(username) + '&response=' + resp.response;
* Do on node:
scp -r antoine@l-cube.artifactual.org.za:~/Projects/meraka/trunk/package/meraka-portal/files/* /
* Do on dashboard-server:
scp -r antoine@l-cube.artifactual.org.za:~/Projects/meraka/trunk/package/meraka-portal/files/www/cgi-bin/* /usr/lib/cgi-bin
* Test:
reboot
#echo 1 > /proc/sys/net/ipv4/ip_forward
#iptables -I POSTROUTING -t nat -o eth0.0 -j MASQUERADE
ifconfig eth0.0 0.0.0.0 # (BATMAN)
/etc/init.d/chilli start
http://192.168.1.1:3990/json/status?lang=en
* Run:
/etc/rc.d ; ln -s ../init.d/chilli S70chilli

== 3b. Integrate coova-chilli + B.A.T.M.A.N.
* Do: (on mesh-node)
uci set network.lan.ipaddr=0.0.0.0
uci set network.wifi.proto=static
uci set network.wifi.ipaddr=10.0.0.2
uci set network.wifi.netmask=255.0.0.0
uci commit

== 4. install afromesh-* ==
* Run:
make package/afromesh-widgets-compile V=99
make package/index
# scp ./build_dir/mipsel/meraka-widgets-0.1/village-bus-* root@192.168.20.200:/www/cgi-bin/
opkg remove meraka-widgets
opkg install http://l-cube.artifactual.org.za/~antoine/firmware/packages/mipsel/meraka-widgets_0.1-1_mipsel.ipk
clear;opkg remove meraka-widgets;opkg update;opkg install http://192.168.20.100/~antoine/firmware/packages/mipsel/meraka-widgets_0.1-1_mipsel.ipk
clear;opkg remove meraka-widgets;opkg install http://192.168.20.100/~antoine/firmware/packages/mipsel/meraka-widgets_0.1-1_mipsel.ipk

clear;opkg remove afromesh-widgets;opkg install http://192.168.20.100/~antoine/firmware/packages/mipsel/afromesh-widgets_0.1-1_mipsel.ipk

= INSTALLATION AND CONFIGURATION FOR OPENMESH =
== 1. FLASHING OPENMESH ==
* Read:
http://www.open-mesh.com/activekb/questions/8/Flashing+the+Accton+Mini-Router+with+ROBIN
http://wiki.openwrt.org/OpenWrtDocs/Hardware/Fon/Fonera

= INSTALLATION AND CONFIGURATION FOR MERAKI =

== 1. FLASHING MERAKI ==
* Useful:
screwdriver
soldering iron
A max232 and a handful of capacitors
hammer (sledge)
* Read:
http://sodoityourself.com/max232-serial-level-converter
http://www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBoot
http://wiki.openwrt.org/OpenWrtDocs/Hardware/Meraki/Mini
* Edit: (Baud rate)
/Users/antoine/Projects/meraka/ext/kamikaze/target/linux/atheros/config-2.6.26
/Users/antoine/Projects/meraka/ext/kamikaze/target/linux/atheros/config-2.6.27
* Do:
Set computer/laptop ethernet to 192.168.84.9 and plug in Meraki
-> Serial @ 115200
^C to break into redboot
* Test kernel:
baudrate -b 9600
-> Serial @ 9600
load -r -d -b 0x80041000 -m http -p 80 -h 192.168.84.9 /~antoine/firmware/openwrt-atheros-vmlinux.gz
exec
# ??? load -h 192.168.84.9 -p 80 -m http /~antoine/firmware/openwrt-atheros-vmlinux.elf
* Create partitions:
fis delete linux
fis delete rootfs
# fis create -b 0x80041000 -l 0x340000 -f 0xa8150000 -e 0x80041000 -r 0x80041000 -n linux
# fis create -b 0x80041000 -l 0x340000 -f 0xa8490000 -e 0x80041000 -r 0x80041000 -n rootfs
fis list
* Flash the kernel and root filesystem -> OPTION 1: Boot directly from RedBoot
load -r -b 0x80041000 -m http -p 80 -h 192.168.84.9 /~antoine/firmware/openwrt-atheros-vmlinux.gz
fis create -r 0x80041000 -e 0x80041000 linux
load -r -b 0x80041000 -m http -p 80 -h 192.168.84.9 /~antoine/firmware/openwrt-atheros-root.jffs2-64k
fis create -r 0x80041000 -e 0x80041000 rootfs
** Test:
fis load -d linux
exec
** Activate:
fconfig (-l to show script)
>> fis load -d linux
>> exec
** For Reference the orig is:
check_mac
load art_ap51.elf
go
fis load stage2
exec
* Flash the kernel and root filesystem -> OPTION 2: Booting using the Meraki stage2 loader
TODO

== 2. CONFIGURING MERAKI ==
* Configure:
uci delete network.lan.type
uci set wireless.wifi0.disabled=0
uci set network.wifi=interface
uci set network.wifi.ifname=ath0
uci set wireless.wifi0.channel=5
uci set wireless.@wifi-iface[0].ssid=batman
uci set wireless.@wifi-iface[0].mode=adhoc # TODO - edit /etc/config/wireless -> config 'wifi-iface' 'cfg'
uci set wireless.@wifi-iface[0].bssid="BB:BB:BB:BB:BB:BB"
uci set wireless.@wifi-iface[0].network=wifi # ??? was lan
# uci set wireless.@wifi-iface[0].device=ath0 # ??? seems to be happy with being called wifi0
uci commit
** Test:
ifconfig ath0 10.0.0.3
* Bring eth0 up on local net:
ifconfig eth0 192.168.20.201
route add default gw 192.168.20.1
vi /etc/resolv.conf
* Edit: /etc/opkg.conf
src packages http://l-cube.artifactual.org.za/~antoine/firmware/packages/mips
* B.A.T.M.A.N:
opkg install batmand
** Configure:
rm /etc/rc.d/S45firewall
uci set network.wifi.proto=static
uci set network.wifi.ipaddr=10.0.0.10
uci set network.wifi.netmask=255.0.0.0
** Test:
batmand -r 3 ath0 # Start BATMAN
iptables -t nat -A POSTROUTING --source 192.168.1.0/24 -o gate0 -j MASQUERADE # NAT any clients of this node
batmand -c -d 2 # Monitor

= INSTALLATION AND CONFIGURATION FOR GATEWAY SERVER (Inveneo) =

== 0. Get OS install image onto a USB Stick ==
* xubuntu:
. unetbootin
. root (hd1,0)
. kernel /casper/vmlinuz file=preseed/xubuntu.seed boot=casper
. initrd /casper/initrd.gz
. boot
* Puppy:
. kernel /vmlinuz
. initrd /initrd.gz
. boot

== 1. Depends ==
* Starting with ubuntu-8.10 JEOS
apt-get --no-install-recommends install ssh
apt-get --no-install-recommends install mysql-server mysql-client mysql-common (mysql admin password: 1nvene0)
apt-get install freeradius freeradius-mysql
apt-get install apache2
??? apt-get --no-install-recommends install dnsmasq
(optional) apt-get install make gcc autoconf libtool libmysqlclient15-dev gdb
(optional for vmware-tools) sudo apt-get install linux-headers-`uname -r` (From: http://www.marc-seeger.de/2008/08/06/vmware-tools-on-ubuntu-jeos/)
(optional for vmware-tools) ln -s /usr/src/linux-headers-2.6.27-7-server /usr/src/linux

* Starting with xubuntu-8.10-rc desktop edition
apt-get install ssh (for openssh-server)
apt-get install rrdtool snmp (needed for: phpMyPrepaid)
apt-get install mysql-server mysql-client mysql-common (needed for: phpMyPrepaid)
apt-get install apache2 (needed for: phpMyPrepaid)
apt-get install php5 php5-snmp php5-gd php5-mysql (needed for: phpMyPrepaid)
apt-get install freeradius freeradius-mysql
apt-get install dnsmasq (for dns/dhcp and tftp)
wget http://ap.coova.org/chilli/coova-chilli_1.0.12-1_i386.deb
dpkg -i ./coova-chilli_1.0.12-1_i386.deb
* Without php-myprepaid
apt-get install freeradius

== 2. Configure Billing ==
* Read: man rlm_counter
http://projects.asn.pl/freemods/wiki/rlm_backcounter
http://www.warungdigital.com/freeradius-disconnected-user-when-time-limit-exceed.htm
* Edit: /etc/freeradius/modules/counter
# check-name sets the maximum value of the counter & read from user db
# count-attribute sets the counter increment
counter prepaid {
filename = ${db_dir}/db.prepaid
counter-name = Prepaid-Session-Time
check-name = Max-Prepaid-Session
count-attribute = Acct-Session-Time
key = User-Name
reset = never
reply-name = Session-Timeout
cache-size = 1000
}
* Edit: /etc/freeradius/radiusd.conf
line 709 uncomment: daily
line 710 add: prepaid
* Edit: /etc/freeradius/sites-enabled/default
line 166: uncomment daily
line 167: add prepaid
line 320: uncomment daily
line 321: add prepaid
* Edit: /etc/freeradius/users.chilli -> Add to prepaid users:
Max-Prepaid-Session=360
* Check:
chown -R freerad:freerad /etc/freeradius
* Add: /etc/group
www-data to freerad

== 3. Customer Management - dashboard server ==
* Read:
!!! http://wiki.freeradius.org/Status
http://wiki.freeradius.org/SNMP_HOWTO
http://www.w3.org/TR/css3-layout/
* Do:
ln -s /etc/freeradius/sites-available/status /etc/freeradius/sites-enabled/status
* Status:
echo "Message-Authenticator = 0x00, FreeRADIUS-Statistics-Type = 31" | radclient localhost:18120 status adminsecret
/var/log/freeradius/radutmp, /var/log/freeradius/radwtmp
radwho, radlast

== 4a. configure flatfile authentication (freeradius - running on dashboard server -> ubuntu JEOS) ==
* Read:
!!! http://coova.org/wiki/index.php/CoovaChilli/RADIUS
http://wiki.freeradius.org/index.php/FreeRADIUS_Wiki:FAQ#How_do_I_get_radius_to_pick_up_changes_in_the_raddb.2Fusers_file.3F
* Run:
apt-get install freeradius
* Edit: /etc/freeradius/radiusd.conf:113
pidfile = /var/run/freeradius/freeradius.pid
* Edit: /etc/freeradius/clients.conf
client 192.168.20.0/24 {
secret = theradiussecret
shortname = meshportal
#nastype = other
}
* Edit: /etc/freeradius/users
$INCLUDE users.chilli
DEFAULT Auth-Type := Reject
Reply-Message = "Login attempt failed.",
Fall-Through = No
* Create: /etc/freeradius/users.chilli
chillispot ClearText-Password := "thechillispotsecret"
joe ClearText-Password := "smith"
guest ClearText-Password := "guest"
Session-Timeout = 300,
Idle-Timeout = 60,
WISPr-Bandwidth-Max-Up = 64000,
WISPr-Bandwidth-Max-Down = 32000
prepaid ClearText-Password := "prepaid", Max-Prepaid-Session := 3600
Reply-Message := "%{Session-Timeout} left %{User-Name}."
* Test:
radiusd -X
radtest chillispot chillispot 192.168.20.225 10 theradiussecret
/etc/init.d/freeradius start
kill -1 `cat /var/run/freeradius/freeradius.pid`
* Edit: /etc/group (Permissions)
freerad:x:124:www-data
* Run: (Permissions)
chmod -R g+w /etc/freeradius
* Run:
copy over our custom radius users files&dir

== 4b. configure mysql authentication (freeradius - running on dashboard server -> ubuntu JEOS) ==
* Install:
apt-get install libmysqlclient-dev
* Edit: /etc/freeradius/users (disable flat file user entries)
. comment out users.chilli include and DEFAULT rule
* Edit: /etc/freeradius/sql.conf
database = "mysql"
server = "localhost"
login = "radius"
password = "radpass"
radius_db = "radius"
* Edit: /etc/freeradius/sites-enabled/default
authorize:152 -> sql
accounting:344 -> sql
session:369 -> sql
post-auth:396 -> sql
* Edit: village-bus-radius/Makefile
.set correct mysql username and password
* Run: (create radius tables for mysql)
make mysql
* Run: (populate radius tables for mysql with defaults & test data)
make mysql-populate

== 5. install asterisk & a2billing ==
* Read:
http://www.asterisk2billing.org/cgi-bin/trac.cgi/wiki/Installation%20Guide
* Do:
wget http://www.asterisk2billing.org/downloads/A2Billing_1.3.4.tar.gz
RTFM -> VOIP Lab C From IT46

== 6. install, configure and create maps ==

* Install
** Get a big hard drive
** Download the database
** Install software
** Import data

* Configure
** Configure dashboard with your location

* Creation
** Mapnik updates weekly on Wednesdays, be sure to get changes in early!
** Osma takes around 12 hours
** Examples
http://openstreetmap.org/edit?lat=-34.138061&lon=18.339733&zoom=15
Trigger re-render: http://www.informationfreeway.org/?lat=-34.138061&lon=18.339733&zoom=15&layers=B0000F000F
http://openstreetmap.org/?lat=-34.13962&lon=18.33913&zoom=17
Trigger re-render: Tile url + '/dirty' at the end

= SIP BEHIND MESH ROUTER =
* Read:
http://siproxd.sourceforge.net/siproxd_guide/siproxd_guide_c7s4.html
http://forum.openwrt.org/viewtopic.php?id=9538
http://forum.pfsense.org/index.php?topic=8928.msg53442
* Install:
opkg install siproxd libosip2
opkg install libltdl # Argh - TODO - file a ticket against siproxd deps
opkg install iptables-mod-nat-extra # kmod-ipt-nat-extra
* Edit: siproxd.conf
sip_listen_port = 5060
daemonize = 1
silence_log = 1
user = nobody
registration_file = /var/log/siproxd_registrations
pid_file = /var/run/siproxd.pid
rtp_proxy_enable = 1
rtp_port_low = 7070
rtp_port_high = 7089
rtp_timeout = 300
default_expires = 600
debug_level = 0x00000000
debug_port = 0
if_inbound = eth0
if_outbound = gate0
* Run:
iptables -t nat -A PREROUTING -m udp -p udp -i eth0 --destination-port 5060 -j REDIRECT
iptables -A INPUT -m udp -p udp -i gate0 --dport 5060 -j ACCEPT
iptables -A INPUT -m udp -p udp -i gate0 --dport 7070:7089 -j ACCEPT
* Test:
/usr/sbin/siproxd -d -1 --config /etc/siproxd.conf
* Run:
uci set siproxd.general.config_file="/etc/siproxd.conf"
uci commit
ln -s ../init.d/siproxd S85siproxd
* Try:
http://siproxd.sourceforge.net/siproxd_guide/siproxd_guide_c7s5.html

VoIP

2009-06-17T15:44:51Z

Ajay: Replacing page with 'Category: VoIP migrated to wireless dev'

[[Category: VoIP]]

migrated to wireless dev

Johann's Research

2009-06-17T15:37:24Z

Ajay:

[[Category: Development Team Research Pages]][[Category: Johann's Research Pages]]

migrated to wireless dev

Community wireless networks

2009-06-17T15:35:01Z

Ajay: Replacing page with 'migrated to wireless dev'

migrated to wireless dev

EeePC and FreeBSD page

2009-06-17T15:24:52Z

Ajay: Replacing page with 'migrated to wireless dev'

migrated to wireless dev

User:Ajay

2009-06-17T15:14:00Z

Ajay: /* Development Team Research Pages */

==DIY Mesh Guide==
[[DIY_Mesh_Guide]]

==WISP in a box project==

[[The_WISP-in-a-box_project]]

[[WISP-in-a-box_Way_Forward]]

[[WISP_Coova_phpMyPrepaid]]

==High Performance Node ==

[[High_performance_node_page]]

[[High_Performance_Node_-_Setup]] Setup for bokkie routers at Ndlovu

[[High_Performance_Node_-_Specification]] - migrated

[[High_Performance_Node_-_Dev_and_Test_Network]] - migrated

[[High_Performance_Node_-_Software]] Software related - migrated

==VoIP==

[[VoIP]]

== Development Team Research Pages ==
'''George: ''' [[George%27s_Research]]

'''Johann: ''' [[Johann%27s_Research]] - migrated

'''Lawrence: ''' [[Lawrence%27s_Research]] - migrated

'''Ntuthuko: ''' [[Ntuthuko%27s_Research]] - migrated

'''Tom: ''' [[Tom%27s_research]]

'''Ajay: ''' [[Ajay%27s_research]] - migrated

'''Gerhard: ''' [[Gerhard%27s_research]] - migrated

'''John: ''' [[John%27s_research]] - migrated

'''Antoine:''' [[Antoine%27s_Research]]

Johann's Research

2009-06-17T14:47:48Z

Ajay: /* VOIP page */

[[Category: Development Team Research Pages]][[Category: Johann's Research Pages]]

I'm not sure if my stuff is really research, but this is some of the stuff that I'm busy with:

== [[High performance node page]] ==
- migrated

== [[HPN design discussions page]] ==
- migrated

== [[HPN to-do/done page]] ==
- migrated

== [[APEX backbone]] ==
- migrated

== [[Installing cacti on FreeBSD]] ==
- migrated

== [[Community wireless networks ]] ==

== [[EeePC and FreeBSD page]] ==

== [[Meraka wireless Network]] ==

- migrated

== [[VOIP page]] ==
- not migrated

Johann's Research

2009-06-17T14:42:10Z

Ajay: /* VOIP page */

Johann's Research

2009-06-17T14:31:30Z

Ajay: /* High performance node page */

High performance node page

2009-06-17T14:27:40Z

Ajay: Replacing page with 'migrated to wireless dev'

migrated to wireless dev

Johann's Research

2009-06-17T13:39:27Z

Ajay: /* Installing cacti on FreeBSD */

[[Category: Development Team Research Pages]][[Category: Johann's Research Pages]]

I'm not sure if my stuff is really research, but this is some of the stuff that I'm busy with:

== [[High performance node page]] ==

== [[HPN design discussions page]] ==
- migrated

== [[HPN to-do/done page]] ==
- migrated

== [[APEX backbone]] ==
- migrated

== [[Installing cacti on FreeBSD]] ==
- migrated

== [[Community wireless networks ]] ==

== [[EeePC and FreeBSD page]] ==

== [[Meraka wireless Network]] ==

- migrated

== [[VOIP page]] ==

Installing cacti on FreeBSD

2009-06-17T13:38:06Z

Ajay: Replacing page with 'migrated to wireless dev'

migrated to wireless dev

Initial (old) hunting description

2009-06-17T13:35:04Z

Ajay: Replacing page with 'migrated to wireless dev'

migrated to wireless dev

Johann's Research

2009-06-17T11:59:26Z

Ajay: /* Meraka wireless Network */

[[Category: Development Team Research Pages]][[Category: Johann's Research Pages]]

I'm not sure if my stuff is really research, but this is some of the stuff that I'm busy with:

== [[High performance node page]] ==

== [[HPN design discussions page]] ==
- migrated

== [[HPN to-do/done page]] ==
- migrated

== [[APEX backbone]] ==
- migrated

== [[Installing cacti on FreeBSD]] ==

== [[Community wireless networks ]] ==

== [[EeePC and FreeBSD page]] ==

== [[Meraka wireless Network]] ==

- migrated

== [[VOIP page]] ==

Meraka wireless Network

2009-06-17T11:59:06Z

Ajay: Replacing page with 'migrated to wireless dev'

migrated to wireless dev

Johann's Research

2009-06-17T11:58:13Z

Ajay: /* APEX backbone */

[[Category: Development Team Research Pages]][[Category: Johann's Research Pages]]

I'm not sure if my stuff is really research, but this is some of the stuff that I'm busy with:

== [[High performance node page]] ==

== [[HPN design discussions page]] ==
- migrated

== [[HPN to-do/done page]] ==
- migrated

== [[APEX backbone]] ==
- migrated

== [[Installing cacti on FreeBSD]] ==

== [[Community wireless networks ]] ==

== [[EeePC and FreeBSD page]] ==

== [[Meraka wireless Network]] ==

== [[VOIP page]] ==

Johann's Research

2009-06-17T11:57:58Z

Ajay:

[[Category: Development Team Research Pages]][[Category: Johann's Research Pages]]

I'm not sure if my stuff is really research, but this is some of the stuff that I'm busy with:

== [[High performance node page]] ==

== [[HPN design discussions page]] ==
- migrated

== [[HPN to-do/done page]] ==
- migrated

== [[APEX backbone]] ==

== [[Installing cacti on FreeBSD]] ==

== [[Community wireless networks ]] ==

== [[EeePC and FreeBSD page]] ==

== [[Meraka wireless Network]] ==

== [[VOIP page]] ==

Johann's Research

2009-06-17T11:56:48Z

Ajay:

[[Category: Development Team Research Pages]][[Category: Johann's Research Pages]]

I'm not sure if my stuff is really research, but this is some of the stuff that I'm busy with:

== [[High performance node page]] ==

== [[HPN design discussions page]] ==
- migrated

== [[HPN to-do/done page]] ==

== [[APEX backbone]] ==

== [[Installing cacti on FreeBSD]] ==

== [[Community wireless networks ]] ==

== [[EeePC and FreeBSD page]] ==

== [[Meraka wireless Network]] ==

== [[VOIP page]] ==

Johann's Research

2009-06-17T11:55:33Z

Ajay:

[[Category: Development Team Research Pages]][[Category: Johann's Research Pages]]

I'm not sure if my stuff is really research, but this is some of the stuff that I'm busy with:

== [[High performance node page]] ==

== [[HPN design discussions page]] == - migrated

== [[HPN to-do/done page]] ==

== [[APEX backbone]] ==

== [[Installing cacti on FreeBSD]] ==

== [[Community wireless networks ]] ==

== [[EeePC and FreeBSD page]] ==

== [[Meraka wireless Network]] ==

== [[VOIP page]] ==

HPN design discussions page

2009-06-17T11:47:51Z

Ajay: Replacing page with ' migrated to wireless dev'

migrated to wireless dev

User:Ajay

2009-06-17T11:30:58Z

Ajay:

==DIY Mesh Guide==
[[DIY_Mesh_Guide]]

==WISP in a box project==

[[The_WISP-in-a-box_project]]

[[WISP-in-a-box_Way_Forward]]

[[WISP_Coova_phpMyPrepaid]]

==High Performance Node ==

[[High_performance_node_page]]

[[High_Performance_Node_-_Setup]] Setup for bokkie routers at Ndlovu

[[High_Performance_Node_-_Specification]] - migrated

[[High_Performance_Node_-_Dev_and_Test_Network]] - migrated

[[High_Performance_Node_-_Software]] Software related - migrated

==VoIP==

[[VoIP]]

== Development Team Research Pages ==
'''George: ''' [[George%27s_Research]]

'''Johann: ''' [[Johann%27s_Research]]

'''Lawrence: ''' [[Lawrence%27s_Research]] - migrated

'''Ntuthuko: ''' [[Ntuthuko%27s_Research]] - migrated

'''Tom: ''' [[Tom%27s_research]]

'''Ajay: ''' [[Ajay%27s_research]] - migrated

'''Gerhard: ''' [[Gerhard%27s_research]] - migrated

'''John: ''' [[John%27s_research]] - migrated

'''Antoine:''' [[Antoine%27s_Research]]

Ajay's research

2009-06-17T11:25:34Z

Ajay: Replacing page with 'Category: Development Team Research Pages migrated to wireless dev'

[[Category: Development Team Research Pages]]

migrated to wireless dev

User:Ajay

2009-06-17T11:19:53Z

Ajay: /* Development Team Research Pages */

==DIY Mesh Guide==
[[DIY_Mesh_Guide]]

==WISP in a box project==

[[The_WISP-in-a-box_project]]

[[WISP-in-a-box_Way_Forward]]

[[WISP_Coova_phpMyPrepaid]]

==High Performance Node ==

[[High_performance_node_page]]

[[High_Performance_Node_-_Setup]] Setup for bokkie routers at Ndlovu

[[High_Performance_Node_-_Specification]] - migrated

[[High_Performance_Node_-_Dev_and_Test_Network]] - migrated

[[High_Performance_Node_-_Software]] Software related - migrated

==VoIP==

[[VoIP]]

== Development Team Research Pages ==
'''George: ''' [[George%27s_Research]]

'''Johann: ''' [[Johann%27s_Research]]

'''Lawrence: ''' [[Lawrence%27s_Research]] - migrated

'''Ntuthuko: ''' [[Ntuthuko%27s_Research]] - migrated

'''Tom: ''' [[Tom%27s_research]]

'''Ajay: ''' [[Ajay%27s_research]] - migrated

'''Gerhard: ''' [[Gerhard%27s_research]]

'''John: ''' [[John%27s_research]] - migrated

'''Antoine:''' [[Antoine%27s_Research]]

Gerhard's research

2009-06-17T10:56:49Z

Ajay:

[[Category: Development Team Research Pages]]

migrated to wireless dev

User:Ajay

2009-06-17T10:53:19Z

Ajay: /* Development Team Research Pages */

==DIY Mesh Guide==
[[DIY_Mesh_Guide]]

==WISP in a box project==

[[The_WISP-in-a-box_project]]

[[WISP-in-a-box_Way_Forward]]

[[WISP_Coova_phpMyPrepaid]]

==High Performance Node ==

[[High_performance_node_page]]

[[High_Performance_Node_-_Setup]] Setup for bokkie routers at Ndlovu

[[High_Performance_Node_-_Specification]] - migrated

[[High_Performance_Node_-_Dev_and_Test_Network]] - migrated

[[High_Performance_Node_-_Software]] Software related - migrated

==VoIP==

[[VoIP]]

== Development Team Research Pages ==
'''George: ''' [[George%27s_Research]]

'''Johann: ''' [[Johann%27s_Research]]

'''Lawrence: ''' [[Lawrence%27s_Research]] - migrated

'''Ntuthuko: ''' [[Ntuthuko%27s_Research]] - migrated

'''Tom: ''' [[Tom%27s_research]]

'''Ajay: ''' [[Ajay%27s_research]]

'''Gerhard: ''' [[Gerhard%27s_research]]

'''John: ''' [[John%27s_research]] - migrated

'''Antoine:''' [[Antoine%27s_Research]]

Ntuthuko's Research

2009-06-17T10:48:56Z

Ajay:

[[Category: Development Team Research Pages]]

migrated to wireless dev

User:Ajay

2009-06-17T10:44:54Z

Ajay: /* Development Team Research Pages */

==DIY Mesh Guide==
[[DIY_Mesh_Guide]]

==WISP in a box project==

[[The_WISP-in-a-box_project]]

[[WISP-in-a-box_Way_Forward]]

[[WISP_Coova_phpMyPrepaid]]

==High Performance Node ==

[[High_performance_node_page]]

[[High_Performance_Node_-_Setup]] Setup for bokkie routers at Ndlovu

[[High_Performance_Node_-_Specification]] - migrated

[[High_Performance_Node_-_Dev_and_Test_Network]] - migrated

[[High_Performance_Node_-_Software]] Software related - migrated

==VoIP==

[[VoIP]]

== Development Team Research Pages ==
'''George: ''' [[George%27s_Research]]

'''Johann: ''' [[Johann%27s_Research]]

'''Lawrence: ''' [[Lawrence%27s_Research]] - migrated

'''Ntuthuko: ''' [[Ntuthuko%27s_Research]]

'''Tom: ''' [[Tom%27s_research]]

'''Ajay: ''' [[Ajay%27s_research]]

'''Gerhard: ''' [[Gerhard%27s_research]]

'''John: ''' [[John%27s_research]] - migrated

'''Antoine:''' [[Antoine%27s_Research]]

Lawrence's Research

2009-06-17T10:43:16Z

Ajay: Replacing page with 'Category: Development Team Research Pages migrated to wireless dev'

[[Category: Development Team Research Pages]]

migrated to wireless dev

User:Ajay

2009-06-11T08:07:42Z

Ajay: /* Development Team Research Pages */

==DIY Mesh Guide==
[[DIY_Mesh_Guide]]

==WISP in a box project==

[[The_WISP-in-a-box_project]]

[[WISP-in-a-box_Way_Forward]]

[[WISP_Coova_phpMyPrepaid]]

==High Performance Node ==

[[High_performance_node_page]]

[[High_Performance_Node_-_Setup]] Setup for bokkie routers at Ndlovu

[[High_Performance_Node_-_Specification]] - migrated

[[High_Performance_Node_-_Dev_and_Test_Network]] - migrated

[[High_Performance_Node_-_Software]] Software related - migrated

==VoIP==

[[VoIP]]

== Development Team Research Pages ==
'''George: ''' [[George%27s_Research]]

'''Johann: ''' [[Johann%27s_Research]]

'''Lawrence: ''' [[Lawrence%27s_Research]]

'''Ntuthuko: ''' [[Ntuthuko%27s_Research]]

'''Tom: ''' [[Tom%27s_research]]

'''Ajay: ''' [[Ajay%27s_research]]

'''Gerhard: ''' [[Gerhard%27s_research]]

'''John: ''' [[John%27s_research]] - migrated

'''Antoine:''' [[Antoine%27s_Research]]