open mesh networks

Notes for The open mesh networks.

http://www.rlhc.net/blog/2009/06/22/linuxplanet-com-setting-up-a-linux-based-open-mesh-wireless-network-part-1/

Excerpt:

“Mesh networks are a type of wireless network. As you’ll discover, mesh networking is great for blanketing Wi-Fi in larger areas. They are especially useful in places where the environment changes frequently, such as people and walls moving around in malls, trees and buildings growing around an apartment complex, boats moving around the docks, and trucks coming in and out of stops. Additionally, they are perfect for locations and applications where it’s hard to run network cabling.

Instead of having to run Ethernet cables to each of the access points, mesh networks work wirelessly. Only one mesh node (or more for larger networks) must be grounded and plugged into an Internet connection. Other mesh nodes, acting as repeaters, can be placed throughout a building or outdoor area, only requiring power. When someone surfs the web from a repeater, the traffic hops from node-to-node, making it back to a gateway. The hops can vary depending upon the current signal levels among them all. Hence the common saying about mesh, “self configuring and healing”, and why they are perfect for busy areas.

Where does Linux or open source come into play? Well, there’s Open-Mesh, a volunteer-based organization that provides hardware and services for mesh networks. The comparatively low-cost hardware, or nodes, are loaded with open-source firmware.

The service or dashboard is provided for free by Open-Mesh and lets operators manage their mesh networks online. Then for user authentication (username and password-based access) or pay-for-use applications, there’s the free CoovaOM or CoovaAAA services in addition to other paid options.

In this two-part tutorial series, we’ll set up a mesh network using the Open-Mesh gear and services. First we’ll gather the hardware, create a Dashboard account, and configure the network settings. Then in the next part, we’ll experiment with the internal splash page, third-party captive portal, set up web filtering with OpenDNS, and finally install the nodes and test coverage. Now lets get started!

Gathering the Hardware

First you need to estimate how many mesh nodes/routers you need to cover the desired area. Each node provides about the same coverage as a normal wireless router or access point. However keep in mind, each node needs to at least

overlap in coverage with one other node. You can mount them anywhere with a power outlet, however, if the budget and time is limited you’ll probably want to stick with indoor locations.

Don’t forget about pumping in the Internet. You must have at least one node hooked to an Internet connection. You’d then call it a gateway node; other nodes that aren’t directly connected to the Internet are called repeater nodes. For larger locations and networks, you’d use two or more gateways, thus multiple Internet connections would be required. This would provide users with better bandwidth, as each hop between nodes cuts the bandwidth in about half. It would also provide redundancy for the Internet access; one goes down you still have the other.

You can refer to the guide from Open-Mesh for help on designing and deploying your mesh network.

You can use the Open-Mesh line of hardware. Prices range from $29 for lower-grade nodes and $49 for professional-level–both very affordable. The professional node includes the hardware watchdog chip that auto restarts the node when errors or problems are detected. It also supports longer Power-over-Ethernet (PoE) runs. Additionally, it has both a 2dbi onboard chip diversity antenna and a removable external 2.5dbi antenna.

The following features are on both the lower-cost and professional nodes:

•Use of the Open-Mesh Dashboard to control and monitor your networks.
•Dual ESSIDs (network names); one open for the public users and another one that’s firewalled and WPA-encrypted for secure private access.
•Optional splash page feature for the public access that’s fully customizable with the HTML/WYSIWYG editor.
•User authentication and billing options via third-party solutions from Coova.org, WiFi-CPA.com, WorldSpot.net, or any RADIUS server.
•Redirect users after they view the splash page or login.
•Bandwidth (speed) limitation settings for the public access.
•Wireless bridge mode on non-gateway nodes lets you plug in a computer for the public access.
•Automatic firmware downloads and updates.
•PoE support, with longer runs supported by the professional nodes.
•SSH and Telnet redboot access.
You could alternatively flash your own supported equipment with the Open-Mesh firmware. Remember, the node features can greatly impact the design and installation. So make sure you carefully compare the features between the vendors and nodes.

Now when the postal worker drops off the equipment, don’t get ahead of yourself and start installing right off the bat.”

open mesh

I ordered two devices today, one of the professional devices and the other one of the cheaper, the part that scares me the most is the freight costs. Will comment more when they arrive, plus I have to look at the time they take to arrive to see if is a suitable project for a student to setup and manage

Open mesh networks

Got told today that I have to look at open mesh networks, this might be the first wave of open wifi acces for students.

Distance covered by one mesh pod is 150 feet = 45.72 meters

Also solar panels may be needed
A couple of years ago there was an offer to help get solar panels or solar cells in schools, I need to find some more information relating to this.

There is school gen which sounds like a possible solution. http://www.schoolgen.co.nz/

So far I found a couple of schools in Auckland which have solar panel technology installed.

One thing the students will have to sort out is best placement for this technology idea, locations of the mesh devices, and development of the secure system.

Developing an open mesh network is described in detail
http://www.linuxplanet.com/linuxplanet/tutorials/6758/1/

Other ideas could include
Copied from http://www.readwriteweb.com/archives/vodafone_nz_iphone_3g.php
This situation just screams for more public wireless access, city wide mesh networks and the like. That way you are no longer dependent on a very small number of mobile phone providers.

Here's a few pointers:
* http://www.fon.com/ : Home Wireless Hotspot community. Basic idea is that if you share your connection, you can use anyone elses connection for free. Super easy to setup, they sell cheap plug & play hardware. Not available in Australia or New Zealand yet, but anyone can set up a local competitor.

* http://www.cantenna.com/ : broadcast wifi signal over huge distances; so no excuses that this won't work in the country side.

* http://www.open-mesh.com/ : Cheap tools to set up a mesh network; that basically means a decentralized network. In other words, if enough people participate you can send data for free from one end of a city to the other at very high speeds.

These are solutions that can be build bottom up by communities and if successful will wet Vodaphone's pants, because they will lose a lot of money on their useless unaffordable 3G network.

Resources
http://www.nsrc.org/wireless.html
http://wireless.ictp.it/groups/wireless/weblog/0c7ff/Mesh_Networking_.html

More information on open mesh
http://www.open-mesh.com/store/
http://www.openmesh.org/
https://www.open-mesh.org/

Open mesh networks in use, gained information off twitter
http://www.callahansclevelanddiary.com/?p=956
http://www.brewedfreshdaily.com/2009/open-mesh-wifi-on-bill-callahans-block

Setup and configuration
https://om.coova.net/ - Access Management for Open-mesh Networks
http://coova.org/wiki/index.php/CoovaAAA - CoovaAAA is a free Authentication, Authorization, and Accounting service.

Dashboard, a way to host this ourseleves and not through open mesh
http://orangemesh.sourceforge.net/ - OrangeMesh is way to central hold your information on your own servers, this means that I dont have to see the techs to open the network up to allow our system to talk to their system