Sudo Room - User contributions [en]

Mesh/Distributed Services

2016-06-19T04:51:13Z

Maxb: /* Active Services */

The [[mesh]] network should provide communication services, so that it offers value to its users beyond mere connectivity to the Internet. What can be done to help it strengthen ties among Oakland residents, and to benefit the community? This wiki page is here to collect ideas about what services could/should be offered.

Services (such as file sharing, email, contacts, calendar, and phone) should be provided based on existing free/open source software. Orientation & setup could be built into the introductory process for new mesh users.

Some general aspects worth considering:
* Security
* Integration into a user account distributed database with master-master replication and low latency (ex. [http://www.datastax.com/resources/whitepapers/benchmarking-top-nosql-databases Cassandra]).

== Active Services ==
The service browser is unfinished, but as we're working on building out the network and setting up services on the network, we can document what we currently have running here for now:

== Architecture: Centralized & decentralized services ==
A central philosophical and practical consideration is how services will be provided. Do we fundamentally want the mesh to be a centralized entity which offers certain services to all members? Or a platform on which individual members can offer services? Or a hybrid?

As it stands now (summer 2015), the mesh offers some opportunity for individual members to offer services. For instance, it's possible for anybody on the mesh to offer services that are accessible elsewhere on the mesh. Should there be (for instance) a central, community-curated file server? Or should it just be up to anybody who wants to, to offer up file shares?

Are there certain kinds of sharing we want to discourage or prohibit, and if so, what will be the social and technical means for enforcement? How will we respond if people start openly sharing copyrighted music and movies? Proprietary software? Child porn? It's worthwhile to think through these scenarios, as a successful network that lacks any kind of governance would become an attractive resource for those whose illegal activities cannot be pursued in the open on the Internet. (An example of this dynamic: [http://www.seattletimes.com/seattle-news/crime/state-supreme-court-rules-against-backpagecom-in-sex-trafficking-suit/ State Supreme Court rules against Backpage.com in sex-trafficking suit], Seattle Times, Sept. 2015)

==Storage / File Systems==

There are several options for a distributed file system and each have there advantages and disadvantages. The distributed file system can be used to offer file storage or reduce latency across the network.

* [http://opensfs.org/lustre/ Lustre] - Used by sixty percent of the top 100 websites.
** Performance: Amazingly fast! I can assert that Lustre can serve a lot of streams and that encoding speed is not affected by accessing files via Lustre.
** [http://en.wikipedia.org/wiki/POSIX POSIX] compatibility: Very good!. No need to modify applications to use luster.
** Replication, Load Balancing and Fail Over: Very bad!. For replication load balancing we and fail over we need to rely on other software such as virtual IPs and DRDB.
** Installation: The worst!. Impossible to install by mere mortals. Requires a very specific combination of kernel, lustre patches and tweaks to get it working. And current luster patches usually work with old kernels that are incompatible with new hardware/software.

* [https://code.google.com/p/mogilefs/ MogileFS]
** Performance: Good for small files but not usable for medium to large files. This is mostly due to HTTP overhead since all files are send/receive via HTTP requests that encode all data in base64 adding a 33% overhead to each file.
** POXIS compatibility: Non existent. All applications require to be modified to use MogileFS that renders it useless for streaming/encoding since most streaming servers and encoding tools do not understand the protocol.
** Replication and failover out of the box and load balancing can be implemented in the application by accessing more than one tracker at a time.
** Installation: Relatively easy and ready to use packages exist in most distributions. The only difficulty I found was setting the database master-slave to eliminate the single point of failure.

* [http://www.gluster.org/ GlusterFS]
** Performance: Very bad for streaming. I cannot reach more than a few Mbps in a 10Gbps network. Clients and Server CPU skyrockets on heavy writes. For encoding works because the CPU is saturated before the network and I/O.
** POXIS: Almost compatible. The tools I use can access gluster mounts as normal folders in disk but in some edge cases things start causing problems. Check gluster mailing lists and you will see there are a lot of problems.
** Replication, Failover and Load balancing: The best! if they actually worked. Gluster is very new and it has a lot of bugs and performance problems.
** Installation is too easy. The management command line is amazing and setting replicated, striped and distributed volumes among several servers can not be any easier.

([http://stackoverflow.com/questions/916902/lustre-gluster-or-mogilefs-for-video-storage-encoding-and-streaming source of above information])

* [http://hadoop.apache.org/ Hadoop] (HDFS) - slow and has a lot of proprietary derivatives (MapR, GPFS, and [http://gigaom.com/2012/07/11/because-hadoop-isnt-perfect-8-ways-to-replace-hdfs/ other alternatives])
* [http://www.xtreemfs.org/ XtreemFS] - slow and we need more research on it.
* Cassandra File System (CFS) - proprietary software made by DataStax and included in the Enterprise Edition of their software.
* [http://en.wikipedia.org/wiki/Network_File_System Network File Sytem] (NFS) - comparable to Lustre, but the [http://wiki.lustre.org/index.php/NFS_vs._Lustre IO bandwidth doesn't scale].

'''Non-distributed file systems'''
There's the option to use a modern file system with [http://en.wikipedia.org/wiki/Rsync rsync].
[http://rudd-o.com/linux-and-free-software/ways-in-which-zfs-is-better-than-btrfs Comparison of ZFS and BTRFS]
[http://porky.linuxjournal.com:8080/LJ/218/11250.html A Quick Introduction to Modern Filesystems]

==Databases and Servers==

These are decentralized databases and servers that could ultimately be optimized to store data nearest to where people access it. A significant factors with mesh networks, that as "size and complexity continues to grow, mesh networks that contain multiple hops become increasingly vulnerable to problems such as bandwidth degradation, radio interference and network latency.<ref>[http://www.strixsystems.com/products/datasheets/strixwhitepaper_multihop.pdf Solving the Wireless Mesh Multi-Hop Dilemma]</ref>" There are several other methods of improving network latency, but all means should be tested and implemented to improve services.

* [https://cassandra.apache.org/ cassandra] - a decentralized database with asynchronous masterless replication allowing low latency operations for all clients. Cassandra has [http://en.wikipedia.org/wiki/Hadoop Hadoop] integration, with MapReduce support.
* [https://couchdb.apache.org/ CouchDB] - I can tell you that it quickly becomes complicated to write multi-user app with CouchDB. Decent access control means that you need a database per user and likely a few extra databases. You then have to set all of these databases up to synchronize between each other which is further complicated by the limitations on what information is available by the limitations on how synchronization rules and filters can be written. There seem to be no good tools for managing/visualizing these complex relationships so you end up having to roll your own.
* [https://github.com/mirage/irmin irmin] - a distributed database with built-in snapshot, branch and revert mechanisms. (similar to git)
* [http://code.google.com/p/leveldb/ levelDB] - a fast and lightweight key/value database library.
* [http://www.mongodb.org/ mongoDB] - an open-source document database, a NoSQL database. Written in C++.
* [http://nodejs.org/ node.js] - an HTTP server written in javascript.
* [http://pouchdb.com/ PouchDB] - a javascript based couchDB.
* [https://github.com/dominictarr/scuttlebutt scuttlebutt] - a data synchronization protocol, or a peer-to-peer replicable data structure.
* [https://tahoe-lafs.org/trac/tahoe-lafs tahoe-lafs] - a decentralized database.

==Communications==

*[http://radicale.org/ radicale] - a CalDAV (calendar) and CardDAV (contacts) server.
*[http://keithp.com/blogs/calypso/ calypso] - Radicale fork with a git back-end (by Keith Packard of X11 fame)
*[http://villagetelco.org Village telco] - an initiative to build low-cost community telephone network hardware and software that can be set up in minutes anywhere in the world. No mobile phone towers or land lines are required, it uses the internet. It has a Simple Unified Dashboard (SPUD) for mesh networks.
*[https://ripple.com/currency/ Ripple] (XRP) - a math-based crypto-currency designed to work seamlessly with the Internet. Powered by a global network of computers; a fast, direct, and secure way to send payments on the web. '''It can be used to prevent malious attacks on servers.'''
*[http://openbts.org/ OpenBTS] - open source cell phone tower software.
*[http://www.openmama.org/what-is-openmama OpenMAMA] - a high performance middleware agnostic messaging API that interfaces with a variety of message oriented middleware systems
*an encrypted asynchronous messaging system to replace email
*a module to have collaborative documents, voting, and groups (ie. [http://en.wikipedia.org/wiki/Collaborative_software groupware])
** Read information about the [http://mitar.tnode.com/post/73983101095/peer-to-peer-voting-scheme peer-to-peer voting scheme].
*a module for peer to peer file sharing.
*a module for object-orientated tagging, shareable feeds.
*a module for feeds and posts, such as [http://www.trsst.com/ Trsst].
* [http://www.frontlinesms.com/ Frontline SMS] - a free, open-source desktop application that allows you to send texts.

==Mapping==

* [http://nodewatcher.readthedocs.org/en/latest/installation.html NodeWatcher] - an open source network planning, deployment, monitoring and maintanance platform.
* [http://wiki.ninux.org/InstallNodeshot NodeShot] - an easy to use wireless community map server.
* [https://github.com/freifunk/openwifimap-html5 OpenWiFiMap] - a database and map for free network WiFi routers (freifunk and others, too!).
* [https://github.com/libremap LibreMap] - a scalable, global and decentralized router database and map visualization for community networks, such as guifi, ninux, etc.
* [http://tidepools.co Tidepools] - collaborative local mapping software
* [http://ediblecities.org/ Edible Cities] - a food mapping project
* Bulletin Board / Local Classified Ads
** Community Asset Mapping (ex. [http://thepyre.org/wiki/Mycelia Mycelia])

== Protocols ==
* [https://tent.io/ Tent] - a method to store all your data in one place that you control. Instead of your digital life being spread across many services.
* [https://www.docker.io/ Docker] - an open-source project to easily create lightweight, portable, self-sufficient containers from any application.
* [http://maidsafe.net/ MaidSafe] - an encrypted, fully distributed data management service. This network manages static and dynamic data as well as communications. (charges money)
* [https://github.com/telehash/telehash.org/blob/master/v3/intro.md Telehash] - "Telehash is a 100% open, secure mesh networking technology with these design principles: full end-to-end encryption, all the time; strict privacy: no content, identity, or metadata is ever revealed to third parties; maximum app/device compatibility: suitable for embedded, mobile, and web usage; making privacy the easy choice for developers; flexible transport protocols, for compatibility with existing layers; native implementations for the widest possible variety of languages/platforms. The telehash team includes collaborators from around the world, many of whom were the principal architects of XMPP. It is intended as a next-generation protocol advancing the original goals of Jabber."

== Social Platforms ==
* [https://joindiaspora.com/ Diaspora] - a decentralized social network
* [https://identi.ca/ Identi.ca] - a high-performance Open Source social engine.
* [http://pump.io/ Pump] - a stream server that does most of what people really want from a social network.
* [http://twister.net.co/ Twister] - a decentralized, peer to peer microblogging platform

==Utilities and Misc.==
* [https://sudoroom.org/wiki/Mesh/Firmware/Zeroconf Avahi] - a mDNS responder that allows you to broadcast services
* [http://localwiki.org/ Local Wiki] - create a local wikipedia (eg; http://oaklandwiki.org)
* a module for sensor data (eg; Temperature, Seismic activity, air pollution)
* [http://dev.wlan-si.net/wiki/PiplMesh PiplMesh] - an open source social networking and info portal for wireless networks used as a welcome page when users connect to the network.
* [https://neocities.org/ Neocities] ([https://github.com/neocities/neocities git]) - create free user sites
* [http://crabgrass.riseuplabs.org/ Crabgrass] - a project out of riseup labs, a ruby rails application for community organizing. It's not the easiest to run your own instance, but very easy to sign up to their server ([https://we.riseup.net/ we.riseup.net])

= References =
<references/>

Mesh/WalkThrough

2016-03-11T01:23:57Z

Maxb: Removed incorrect info

This a walkthrough for flashing a node with the sudomesh firmware and then configuring it with makenode. At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish (OSX should mostly work) OS and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The basic idea of getting a node (router) on the mesh consists of flashing (copying files to [https://en.wikipedia.org/wiki/Flash_memory flash memory]) an operating system to the node and then using a software configurator finish setup .

To build an OpenWRT image from scratch, visit this How To: [[Mesh/Build An OpenWRT Image]]

= Build Environment =

The directions that follow assume you are runing a linux-ish distro (OSX should work). Many of the quoted commands listed below may need `sudo` prepended to them. For the moment, Windows users will have to figure out some of these steps on their own. Sorry :/

=Installing OpenWRT=

==Supported Hardware==
At the moment, we are supporting the following routers for home nodes:
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 TP-Link WDR3500] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 TP-Link WDR3600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 TP-Link WDR4300] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n600 Western Digital MyNet N600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n750 Western Digital MyNet N750] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin firmware image]

==Images==
Sudomesh firmware images can be found here:
[https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/ https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/]

Download the image according to your hardware. For example, if you have a Western Digital MyNet N600, download the image named: openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin, or use the links above

==Flashing==
There are different techniques for flashing each of the routers. Use the links above to the openwrt wiki and follow the instructions there to flash the router with the firmware you've downloaded.

==Confirm Installation==
In order to confirm that the installation has proceeded correctly, use an ethernet cable to connect your computer to the "internet/WAN" port of your router and set your IP address to an address on the 172.22.0.0/24 subnet:
<code>$ ip addr add 172.22.0.9/24 dev IF_NAME</code>
(where IF_NAME is the name of your ethernet interface)
You ''may'' want to stop network-manager (not all distros use this, but Ubuntu does):
<code>$ /etc/init.d/network-manager stop</code>

You can also assign yourself the address via a network manager, both in linux and OSX.

<code>$ ssh root@172.22.0.1</code>

The default password will be: `meshtheplanet`

You ''may'' need to restart the router, but be careful not to restart it while it's in the process of flashing.

=Configuring=
These are the steps for configuring your newly flashed router. It will retrieve hardware information about the node, prompt you for a few config settings, and then query the meshnode database to get an available IP address and subnet.

==Prerequisites==
You'll need:
* A newish version of nodejs and npm. Follow the recommended instructions at [https://docs.npmjs.com/getting-started/installing-node npmjs.com].
* Git. In Debian based distros you can do: <code>$ apt-get install git</code>. For OSX you can probably use homebrew or your preferred package manager.

==Setup==
Download [https://github.com/sudomesh/makenode makenode]. The easiest way to do this will likely be with git:
<code>$ git clone https://github.com/sudomesh/makenode.git</code>

Then you need to install nodejs/npm packages:
* <code>$ cd makenode</code>
* <code>$ npm install</code>
* <code>$ cp settings.js.example settings.js</code>

The default settings in `settings.js` should suffice in most cases, but if you need to make changes, do them there.

If you'd like to add your ssh key to the router, add it to the `configs/authorized_keys` file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.

==Running==
You should now be able to run makenode:
<code>$ ./makenode.js</code>

Makenode will detect the hardware on the router and ask you to input some data about the node. Some notes:
* Set the "txpower" to 20. This should be set in the code, but hasn't been just yet.
* The password for the private ssid should be at least 8 characters or you will not be able to connect
* For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* The max downstream and upstream bandwidth are the maximum amount of bandwidth you want to share on the "peoplesopen.net" network. They are measured in kbps (kilobits per second), so if you'd like to share 10mbps (megabits per second), enter 10000. You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device.

==What now?==

If configuration proceeded correctly, you should see the 'peoplesopen.net' and 'pplsopen.net-node2node' wifi interfaces when running `sudo iwlist wlan0 scan` or when looking at available wifi networks.

It's recommended that you read the [[Home and extender nodes#Home_nodes|Home node info]] to find out more about the way that your new mesh node works.

Mesh/Press

2016-02-13T05:35:37Z

Maxb: Adding press articles

*27 November 2013 - [http://oaklandnorth.net/2013/11/27/mesh-network-offers-potential-for-free-wireless-internet-in-oakland/ Mesh network offers potential for free wireless Internet in Oakland] by Jake Nichol (Oakland North).
*21 July 2014 - [http://techpresident.com/news/25200/oakland-sudo-mesh-counter-censorship-digital-divide-mesh-net Oakland's Sudo Mesh Looks to Counter Censorship and Digital Divide With a Mesh Network] by Ben Valentine (TechPresident).
*8 October 2015 - [https://oaklandnorth.net/2015/10/08/fcc-rule-threatens-oakland-mesh-network-wi-fi-projects/ Proposed FCC rule threatens Oakland mesh network, Wi-Fi projects] by Jennifer Glenfield (Oakland North).

Mesh/WalkThrough

2016-02-13T05:26:00Z

Maxb: /* Installing OpenWRT */

This a walkthrough for flashing a node with the sudomesh firmware and then configuring it with makenode. At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish (OSX should mostly work) OS and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The basic idea of getting a node (router) on the mesh consists of flashing (copying files to [https://en.wikipedia.org/wiki/Flash_memory flash memory]) an operating system to the node and then using a software configurator finish setup .

To build an OpenWRT image from scratch, visit this How To: [[Mesh/Build An OpenWRT Image]]

= Build Environment =

The directions that follow assume you are runing a linux-ish distro (OSX should work). Many of the quoted commands listed below may need `sudo` prepended to them. For the moment, Windows users will have to figure out some of these steps on their own. Sorry :/

=Installing OpenWRT=

==Supported Hardware==
At the moment, we are supporting the following routers for home nodes:
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 TP-Link WDR3500] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 TP-Link WDR3600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 TP-Link WDR4300] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n600 Western Digital MyNet N600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n750 Western Digital MyNet N750] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin firmware image]

The following are supported routers for extender nodes:
* Ubiquiti NanoStation M5 (newer models shipped after early 2014) - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin firmware image]
* Ubiquiti NanoStation M5 (older models shipped prior to 2014) - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin firmware image]

==Images==
Sudomesh firmware images can be found here:
[https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/ https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/]

Download the image according to your hardware. For example, if you have a Western Digital MyNet N600, download the image named: openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin, or use the links above

==Flashing==
There are different techniques for flashing each of the routers. Use the links above to the openwrt wiki and follow the instructions there to flash the router with the firmware you've downloaded.

==Confirm Installation==
In order to confirm that the installation has proceeded correctly, use an ethernet cable to connect your computer to the "internet/WAN" port of your router and set your IP address to an address on the 172.22.0.0/24 subnet:
<code>$ ip addr add 172.22.0.9/24 dev IF_NAME</code>
(where IF_NAME is the name of your ethernet interface)
You ''may'' want to stop network-manager (not all distros use this, but Ubuntu does):
<code>$ /etc/init.d/network-manager stop</code>

You can also assign yourself the address via a network manager, both in linux and OSX.

<code>$ ssh root@172.22.0.1</code>

The default password will be: `meshtheplanet`

You ''may'' need to restart the router, but be careful not to restart it while it's in the process of flashing.

=Configuring=
These are the steps for configuring your newly flashed router. It will retrieve hardware information about the node, prompt you for a few config settings, and then query the meshnode database to get an available IP address and subnet.

==Prerequisites==
On your computer you'll need:
* A newish version of nodejs and npm. Follow the recommended instructions at [https://docs.npmjs.com/getting-started/installing-node npmjs.com].
* Git. In Debian based distros you can do: <code>$ apt-get install git</code>. For OSX you can probably use homebrew or your preferred package manager.

==Setup==
All of these steps will be performed on your computer. You'll need to set your computer's IP address to an IP on the 172.22.0.0/24 range (ie. 172.22.0.9/24). Any address will suffice as long as its NOT 172.22.0.1 

Download [https://github.com/sudomesh/makenode makenode]. The easiest way to do this will likely be with git:
<code>$ git clone https://github.com/sudomesh/makenode.git</code>

Then you need to install nodejs/npm packages:
* <code>$ cd makenode</code>
* <code>$ npm install</code>
* <code>$ cp settings.js.example settings.js</code>

The default settings in `settings.js` should suffice in most cases, but if you need to make changes, do them there.

If you'd like to add your ssh key to the router, add it to the `configs/authorized_keys` file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.

==Running==
You should now be able to run makenode:
<code>$ ./makenode.js</code>

Makenode will detect the hardware on the router and ask you to input some data about the node. Some notes:
* Set the "txpower" to 20. This should be set in the code, but hasn't been just yet.
* The password for the private ssid should be at least 8 characters or you will not be able to connect
* For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* The max downstream and upstream bandwidth are the maximum amount of bandwidth you want to share on the "peoplesopen.net" network. They are measured in kbps (kilobits per second), so if you'd like to share 10mbps (megabits per second), enter 10000. You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device.

==What now?==

If configuration proceeded correctly, you should see the 'peoplesopen.net' and 'pplsopen.net-node2node' wifi interfaces when running `sudo iwlist wlan0 scan` or when looking at available wifi networks.

It's recommended that you read the [[Home and extender nodes#Home_nodes|Home node info]] to find out more about the way that your new mesh node works.

Mesh/WalkThrough

2016-02-13T03:14:54Z

Maxb: /* Prerequisites */

This a walkthrough for flashing a node with the sudomesh firmware and then configuring it with makenode. At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish (OSX should mostly work) OS and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The basic idea of getting a node (router) on the mesh consists of flashing (copying files to [https://en.wikipedia.org/wiki/Flash_memory flash memory]) an operating system to the node and then using a software configurator finish setup .

To build an OpenWRT image from scratch, visit this How To: [[Mesh/Build An OpenWRT Image]]

= Build Environment =

The directions that follow assume you are runing a linux-ish distro (OSX should work). Many of the quoted commands listed below may need `sudo` prepended to them. For the moment, Windows users will have to figure out some of these steps on their own. Sorry :/

=Installing OpenWRT=

==Supported Hardware==
At the moment, we are supporting the following routers for home nodes:
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 TP-Link WDR3500] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 TP-Link WDR3600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 TP-Link WDR4300] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n600 Western Digital MyNet N600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n750 Western Digital MyNet N750] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin firmware image]

The following are supported routers for extender nodes:
* Ubiquiti NanoStation M5 (newer models shipped after early 2014) - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin firmware image]
* Ubiquiti NanoStation M5 (older models shipped prior to 2014) - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin firmware image]

==Images==
Sudomesh firmware images can be found here:
[https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/ https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/]

Download the image according to your hardware. For example, if you have a Western Digital MyNet N600, download the image named: openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin, or use the links above

==Flashing==
There are different techniques for flashing each of the routers. Use the links above to the openwrt wiki and follow the instructions there to flash the router with the firmware you've downloaded.

==Confirm Installation==
In order to confirm that the installation has proceeded correctly, use an ethernet cable to connect your computer to the "internet/WAN" port of your router and set your IP address to an address on the 172.22.0.0/24 subnet:
<code>$ ip addr add 172.22.0.9/24 dev IF_NAME</code>
(where IF_NAME is the name of your ethernet interface)
You ''may'' want to stop network-manager (not all distros use this, but Ubuntu does):
<code>$ /etc/init.d/network-manager stop</code>

You can also assign yourself the address via a network manager, both in linux and OSX.

<code>$ ssh root@172.22.0.1</code>

The default password will be: `meshtheplanet`

You ''may'' need to restart the router, but be careful not to restart it while it's in the process of flashing.

=Configuring=
These are the steps for configuring your newly flashed router. It will retrieve hardware information about the node, prompt you for a few config settings, and then query the meshnode database to get an available IP address and subnet.

==Prerequisites==
On your computer you'll need:
* A newish version of nodejs and npm. Follow the recommended instructions at [https://docs.npmjs.com/getting-started/installing-node npmjs.com].
* Git. In Debian based distros you can do: <code>$ apt-get install git</code>. For OSX you can probably use homebrew or your preferred package manager.

==Setup==
All of these steps will be performed on your computer. You'll need to set your computer's IP address to an IP on the 172.22.0.0/24 range (ie. 172.22.0.9/24). Any address will suffice as long as its NOT 172.22.0.1 

Download [https://github.com/sudomesh/makenode makenode]. The easiest way to do this will likely be with git:
<code>$ git clone https://github.com/sudomesh/makenode.git</code>

Then you need to install nodejs/npm packages:
* <code>$ cd makenode</code>
* <code>$ npm install</code>
* <code>$ cp settings.js.example settings.js</code>

The default settings in `settings.js` should suffice in most cases, but if you need to make changes, do them there.

If you'd like to add your ssh key to the router, add it to the `configs/authorized_keys` file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.

==Running==
You should now be able to run makenode:
<code>$ ./makenode.js</code>

Makenode will detect the hardware on the router and ask you to input some data about the node. Some notes:
* Set the "txpower" to 20. This should be set in the code, but hasn't been just yet.
* The password for the private ssid should be at least 8 characters or you will not be able to connect
* For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* The max downstream and upstream bandwidth are the maximum amount of bandwidth you want to share on the "peoplesopen.net" network. They are measured in kbps (kilobits per second), so if you'd like to share 10mbps (megabits per second), enter 10000. You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device.

==What now?==

If configuration proceeded correctly, you should see the 'peoplesopen.net' and 'pplsopen.net-node2node' wifi interfaces when running `sudo iwlist wlan0 scan` or when looking at available wifi networks.

It's recommended that you read the [[Home and extender nodes#Home_nodes|Home node info]] to find out more about the way that your new mesh node works.

Mesh/WalkThrough

2016-02-13T03:14:10Z

Maxb: /* Configuring */

This a walkthrough for flashing a node with the sudomesh firmware and then configuring it with makenode. At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish (OSX should mostly work) OS and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The basic idea of getting a node (router) on the mesh consists of flashing (copying files to [https://en.wikipedia.org/wiki/Flash_memory flash memory]) an operating system to the node and then using a software configurator finish setup .

To build an OpenWRT image from scratch, visit this How To: [[Mesh/Build An OpenWRT Image]]

= Build Environment =

The directions that follow assume you are runing a linux-ish distro (OSX should work). Many of the quoted commands listed below may need `sudo` prepended to them. For the moment, Windows users will have to figure out some of these steps on their own. Sorry :/

=Installing OpenWRT=

==Supported Hardware==
At the moment, we are supporting the following routers for home nodes:
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 TP-Link WDR3500] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 TP-Link WDR3600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 TP-Link WDR4300] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n600 Western Digital MyNet N600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n750 Western Digital MyNet N750] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin firmware image]

The following are supported routers for extender nodes:
* Ubiquiti NanoStation M5 (newer models shipped after early 2014) - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin firmware image]
* Ubiquiti NanoStation M5 (older models shipped prior to 2014) - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin firmware image]

==Images==
Sudomesh firmware images can be found here:
[https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/ https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/]

Download the image according to your hardware. For example, if you have a Western Digital MyNet N600, download the image named: openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin, or use the links above

==Flashing==
There are different techniques for flashing each of the routers. Use the links above to the openwrt wiki and follow the instructions there to flash the router with the firmware you've downloaded.

==Confirm Installation==
In order to confirm that the installation has proceeded correctly, use an ethernet cable to connect your computer to the "internet/WAN" port of your router and set your IP address to an address on the 172.22.0.0/24 subnet:
<code>$ ip addr add 172.22.0.9/24 dev IF_NAME</code>
(where IF_NAME is the name of your ethernet interface)
You ''may'' want to stop network-manager (not all distros use this, but Ubuntu does):
<code>$ /etc/init.d/network-manager stop</code>

You can also assign yourself the address via a network manager, both in linux and OSX.

<code>$ ssh root@172.22.0.1</code>

The default password will be: `meshtheplanet`

You ''may'' need to restart the router, but be careful not to restart it while it's in the process of flashing.

=Configuring=
These are the steps for configuring your newly flashed router. It will retrieve hardware information about the node, prompt you for a few config settings, and then query the meshnode database to get an available IP address and subnet.

==Prerequisites==
You'll need:
* A newish version of nodejs and npm. Follow the recommended instructions at [https://docs.npmjs.com/getting-started/installing-node npmjs.com].
* Git. In Debian based distros you can do: <code>$ apt-get install git</code>. For OSX you can probably use homebrew or your preferred package manager.

==Setup==
All of these steps will be performed on your computer. You'll need to set your computer's IP address to an IP on the 172.22.0.0/24 range (ie. 172.22.0.9/24). Any address will suffice as long as its NOT 172.22.0.1 

Download [https://github.com/sudomesh/makenode makenode]. The easiest way to do this will likely be with git:
<code>$ git clone https://github.com/sudomesh/makenode.git</code>

Then you need to install nodejs/npm packages:
* <code>$ cd makenode</code>
* <code>$ npm install</code>
* <code>$ cp settings.js.example settings.js</code>

The default settings in `settings.js` should suffice in most cases, but if you need to make changes, do them there.

If you'd like to add your ssh key to the router, add it to the `configs/authorized_keys` file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.

==Running==
You should now be able to run makenode:
<code>$ ./makenode.js</code>

Makenode will detect the hardware on the router and ask you to input some data about the node. Some notes:
* Set the "txpower" to 20. This should be set in the code, but hasn't been just yet.
* The password for the private ssid should be at least 8 characters or you will not be able to connect
* For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* The max downstream and upstream bandwidth are the maximum amount of bandwidth you want to share on the "peoplesopen.net" network. They are measured in kbps (kilobits per second), so if you'd like to share 10mbps (megabits per second), enter 10000. You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device.

==What now?==

If configuration proceeded correctly, you should see the 'peoplesopen.net' and 'pplsopen.net-node2node' wifi interfaces when running `sudo iwlist wlan0 scan` or when looking at available wifi networks.

It's recommended that you read the [[Home and extender nodes#Home_nodes|Home node info]] to find out more about the way that your new mesh node works.

Mesh/WalkThrough

2016-02-13T03:12:18Z

Maxb: /* Configuring */

This a walkthrough for flashing a node with the sudomesh firmware and then configuring it with makenode. At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish (OSX should mostly work) OS and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The basic idea of getting a node (router) on the mesh consists of flashing (copying files to [https://en.wikipedia.org/wiki/Flash_memory flash memory]) an operating system to the node and then using a software configurator finish setup .

To build an OpenWRT image from scratch, visit this How To: [[Mesh/Build An OpenWRT Image]]

= Build Environment =

The directions that follow assume you are runing a linux-ish distro (OSX should work). Many of the quoted commands listed below may need `sudo` prepended to them. For the moment, Windows users will have to figure out some of these steps on their own. Sorry :/

=Installing OpenWRT=

==Supported Hardware==
At the moment, we are supporting the following routers for home nodes:
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 TP-Link WDR3500] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 TP-Link WDR3600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 TP-Link WDR4300] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n600 Western Digital MyNet N600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n750 Western Digital MyNet N750] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin firmware image]

The following are supported routers for extender nodes:
* Ubiquiti NanoStation M5 (newer models shipped after early 2014) - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin firmware image]
* Ubiquiti NanoStation M5 (older models shipped prior to 2014) - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin firmware image]

==Images==
Sudomesh firmware images can be found here:
[https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/ https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/]

Download the image according to your hardware. For example, if you have a Western Digital MyNet N600, download the image named: openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin, or use the links above

==Flashing==
There are different techniques for flashing each of the routers. Use the links above to the openwrt wiki and follow the instructions there to flash the router with the firmware you've downloaded.

==Confirm Installation==
In order to confirm that the installation has proceeded correctly, use an ethernet cable to connect your computer to the "internet/WAN" port of your router and set your IP address to an address on the 172.22.0.0/24 subnet:
<code>$ ip addr add 172.22.0.9/24 dev IF_NAME</code>
(where IF_NAME is the name of your ethernet interface)
You ''may'' want to stop network-manager (not all distros use this, but Ubuntu does):
<code>$ /etc/init.d/network-manager stop</code>

You can also assign yourself the address via a network manager, both in linux and OSX.

<code>$ ssh root@172.22.0.1</code>

The default password will be: `meshtheplanet`

You ''may'' need to restart the router, but be careful not to restart it while it's in the process of flashing.

=Configuring=
These are the steps for configuring your newly flashed router. It will retrieve hardware information about the node, prompt you for a few config settings, and then query the meshnode database to get an available IP address and subnet.

==Prerequisites==
You'll need:
* A newish version of nodejs and npm. Follow the recommended instructions at [https://docs.npmjs.com/getting-started/installing-node npmjs.com].
* Git. In Debian based distros you can do: <code>$ apt-get install git</code>. For OSX you can probably use homebrew or your preferred package manager.

==Setup==
All of these steps will be performed on your computer.
Download [https://github.com/sudomesh/makenode makenode]. The easiest way to do this will likely be with git:
<code>$ git clone https://github.com/sudomesh/makenode.git</code>

Then you need to install nodejs/npm packages:
* <code>$ cd makenode</code>
* <code>$ npm install</code>
* <code>$ cp settings.js.example settings.js</code>

The default settings in `settings.js` should suffice in most cases, but if you need to make changes, do them there.

If you'd like to add your ssh key to the router, add it to the `configs/authorized_keys` file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.

==Running==
You should now be able to run makenode:
<code>$ ./makenode.js</code>

Makenode will detect the hardware on the router and ask you to input some data about the node. Some notes:
* Set the "txpower" to 20. This should be set in the code, but hasn't been just yet.
* The password for the private ssid should be at least 8 characters or you will not be able to connect
* For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* The max downstream and upstream bandwidth are the maximum amount of bandwidth you want to share on the "peoplesopen.net" network. They are measured in kbps (kilobits per second), so if you'd like to share 10mbps (megabits per second), enter 10000. You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device.

==What now?==

If configuration proceeded correctly, you should see the 'peoplesopen.net' and 'pplsopen.net-node2node' wifi interfaces when running `sudo iwlist wlan0 scan` or when looking at available wifi networks.

It's recommended that you read the [[Home and extender nodes#Home_nodes|Home node info]] to find out more about the way that your new mesh node works.

Mesh/Funding

2016-02-12T20:26:46Z

Maxb: /* Grants */ Knight Foundation Grant info

=Grants=
*[http://www.awesomefoundation.org/en/chapters/knowledge Awesome Foundation - Knowledge Chapter]
*[http://www.awesomefoundation.org/en/chapters/openweb Awesome Foundation - Open Web]
*[http://www.awesomefoundation.org/en/chapters/awesomewithoutborders Awesome Without Borders]
*[http://www.awesomefoundation.org/en/chapters/sf Awesome Foundation - SF]
*[http://thepollinationproject.org/ The Pollination Project]
:We already applied for and received this one in 2014 ($1000)
*[https://www.opentechfund.org/submit Open Tech Fund]
:Applied for OTFâ€™s Internet Freedom Fund in Jan 2016 and declined with this message:
<blockquote>
Determination status: Dropped

Next Deadline:

Goals and principles:
This sounds like a great community project, but we does not fall under our
remit. OTFâ€™s Internet Freedom Fund generally funds tools and technologies
that can be immediately used in repressive regimes to counteract censorship
and surveillance.

NYC has awesome mesh networks, Red Hook being the most famous. There is a
huge project here funded by the city to bring mesh to other boroughs. Also,
this seems like a project that should be funded by the local community - is
there similar funding for San Fran for something like this? That might be
more in line with the community approach this project is taking.

Technical merit:

Reasonable, realistic and sustainable:

Other comments:
Please refer to our list of alternative sources to see if any of them might
be a better fit. https://www.opentech.fund/apply/alternative-sources-support

</blockquote>
*[https://knightfoundation.org Knight Foundation]
:Applied for Knight Foundation Journalism and Media Innovation grant in Dec. 2015 and declined.
*[http://nlnet.nl/ NL Net Foundation]
*[http://www.internetsociety.org/what-we-do/grants-awards/community-grants Internet Society's Community Grants]
*[http://www.challenge.bfi.org/ The Buckminster Fuller Challenge]
*[http://www.opensocietyfoundations.org/grants/transparency-and-new-technologies-initiative Open Society Foundations Transparency and New Technologies Initiative]
*[https://impactchallenge.withgoogle.com/bayarea2014/ Google Impact] - 500K grant to social change nonprofits in the Bay Area.

=Crowdfunding=
For our initial batch of crowdfunded hardware, we ran a 60-day campaign on WePay. See [https://sudoroom.org/wiki/Mesh/Purchases#First_crowd-sourced_purchase this page] for details on that campaign, purchases and standing funds.

=Sustainable Business Models=
==Preliminary Notes/Brainstorm==
*cost
**buying routers
**people adopt routers
**people buy routers
*couple of full time real employees
**mounting routers/antennae
**managing of network
*bandwidth
*electricity
*advertising on splash page
*name the wifi network as the web address
*sell service to business districts
*digital bulletin boards
*skill share board
*begging for cash model
**OLPC model: people pay 2x for themselves and someone else
*ISPs ToS donâ€™t allow you to share bandwidth
**get local ISPs to contribute
**monkeybrains?
**competing with Unwired, and their radio frequency
*legal advisers???

Mesh/Funding

2016-02-12T20:21:11Z

Maxb: /* Grants */ Adding info about OTF grant application

=Grants=
*[http://www.awesomefoundation.org/en/chapters/knowledge Awesome Foundation - Knowledge Chapter]
*[http://www.awesomefoundation.org/en/chapters/openweb Awesome Foundation - Open Web]
*[http://www.awesomefoundation.org/en/chapters/awesomewithoutborders Awesome Without Borders]
*[http://www.awesomefoundation.org/en/chapters/sf Awesome Foundation - SF]
*[http://thepollinationproject.org/ The Pollination Project]
:We already applied for and received this one in 2014 ($1000)
*[https://www.opentechfund.org/submit Open Tech Fund]
:Applied for OTFâ€™s Internet Freedom Fund in Jan 2016 and declined with this message:
<blockquote>
Determination status: Dropped

Next Deadline:

Goals and principles:
This sounds like a great community project, but we does not fall under our
remit. OTFâ€™s Internet Freedom Fund generally funds tools and technologies
that can be immediately used in repressive regimes to counteract censorship
and surveillance.

NYC has awesome mesh networks, Red Hook being the most famous. There is a
huge project here funded by the city to bring mesh to other boroughs. Also,
this seems like a project that should be funded by the local community - is
there similar funding for San Fran for something like this? That might be
more in line with the community approach this project is taking.

Technical merit:

Reasonable, realistic and sustainable:

Other comments:
Please refer to our list of alternative sources to see if any of them might
be a better fit. https://www.opentech.fund/apply/alternative-sources-support

</blockquote>
*[http://nlnet.nl/ NL Net Foundation]
*[http://www.internetsociety.org/what-we-do/grants-awards/community-grants Internet Society's Community Grants]
*[http://www.challenge.bfi.org/ The Buckminster Fuller Challenge]
*[http://www.opensocietyfoundations.org/grants/transparency-and-new-technologies-initiative Open Society Foundations Transparency and New Technologies Initiative]
*[https://impactchallenge.withgoogle.com/bayarea2014/ Google Impact] - 500K grant to social change nonprofits in the Bay Area.

=Crowdfunding=
For our initial batch of crowdfunded hardware, we ran a 60-day campaign on WePay. See [https://sudoroom.org/wiki/Mesh/Purchases#First_crowd-sourced_purchase this page] for details on that campaign, purchases and standing funds.

=Sustainable Business Models=
==Preliminary Notes/Brainstorm==
*cost
**buying routers
**people adopt routers
**people buy routers
*couple of full time real employees
**mounting routers/antennae
**managing of network
*bandwidth
*electricity
*advertising on splash page
*name the wifi network as the web address
*sell service to business districts
*digital bulletin boards
*skill share board
*begging for cash model
**OLPC model: people pay 2x for themselves and someone else
*ISPs ToS donâ€™t allow you to share bandwidth
**get local ISPs to contribute
**monkeybrains?
**competing with Unwired, and their radio frequency
*legal advisers???

Mesh/Firmware

2016-02-06T05:40:32Z

Maxb: /* Splash page (Garden Gnome) */

Documentation for the sudo mesh firmware.

= ToDo =

[https://github.com/sudomesh/sudowrt-firmware/issues?q=is%3Aopen+is%3Aissue+milestone%3A%220.2+-+initial+developer+release%22 Issues for version 0.2]

[https://github.com/sudomesh/sudowrt-firmware/issues?q=is%3Aopen+is%3Aissue+milestone%3A%220.3+-+Improved+UI%22 Issues for version 0.3]

Issues for later versions:
* Basic admin web UI for node database that let's you log in and list current nodes.
* fake captive portal working
* service browser working
* hardware watchdog working on ar71xx
* support for manually configured non-openwrt extender nodes
** Allow user to switch ethernet ports into "extender node (manual)" mode
** Only one network (either adhoc or open) can be extended using this mode. The user must be able to select which.
** Set up port forwarding from home node to each manually configured extender node for web UI access, e.g. 1443 to 443 on extender node 1, etc.
*** This can be always-on for e.g. up to 16 ports without causing problems since it is only for traffic destined for the home node IP.
*** There should be links to the extender node web UIs from the home node web UI.
* Apply for internet-routable IPv6 subnet and give each node their own subnet + hand out IPv6 addresses to clients
* extender node firmware working on old atheros chipset
* Remote firmware updates working
** Use either DNS-SD to list and pick an update server at random or IPv6 multi-homing?
* Remote automated root password reset (via h.sudomesh.org)
* IPv6 support for extender nodes
* Figure out how to legally use lower 5 ghz frequencies and ensure fancy back-off features are working
* Run OpenVPN on exit node.

In the future:
* Support TDMA on Linux (Adri is working on FreeBSD support, maybe we can port).

= Stuff we are working on =

<big>Ranked from most to least important</big>

== InternetIsDownRedirect ==

When the node doesn't have internet access, it will redirect traffic to our mesh hosted [[Mesh/Firmware#Splash_page|Splash Page]].

We need something hosted on the node that can check if it has access to the internet. There's a bit of an issue where certain OSes won't connect to APs that don't have internet access. [[User:Juul|Juul]] will look into building a hack that properly manages these requests and redirects them to our node-hosted site.

InternetIsDownRedirect may also have to fake the expected captive portal detection responses? We need to figure out if android/iOS/Mac/Windows will connect to a wifi that does not have internet access.

Status: Implemented except for OS-specific captive portal requests.

== Splash page (Garden Gnome) ==

We can capture OS specific probes in order to specifically redirect captive portal requests without affecting any other network traffic.

Chris (snake_wrangler) was working on it and calling it the Garden Gnome.
[[User:maxb|maxb]] picked up the idea and ran with it in nodejs: https://github.com/sudomesh/garden-gnome

Features:

* Brief info on the mesh
* Link to our website?

Status:

[[User:maxb|maxb]] has implemented it! We need a tiny bit of polishing, especially for corner case browsers.

== Extender node firmware ==

See the [[Technical Overview]] to learn about home nodes and extender nodes.

With the extender node firmware we're targeting a variety of hardware (if not chipsets), and we don't want to run any sort of makenode after the firmware has been flashed.

We're doing this by creating a /file/etc/uci-defaults script which will run first boot and can set configs depending on the "board" type:
[https://gist.github.com/max-b/97bd7d59259cfbdfbbb2 uci-defaults script gist]

== Mesh Protocol ==

[http://www.open-mesh.org/projects/batman-adv/wiki BATMAN-adv] was the protocol that we had assumed we'd be able to use. Unfortunately, it looks as though it won't support tunneling over the internet, which is one of the primary features we had been hoping to implement. See [https://lists.sudoroom.org/pipermail/mesh-dev/2014-October/000019.html our mailing list convo].

We're now using [https://github.com/jech/babeld babel]. It's been looking pretty good for our particular applications. There are some security/trust issues that we'd like to investigate further - see http://lists.alioth.debian.org/pipermail/babel-users/2015-April/001973.html for some ideas that babel might incorporate in the future.

Status: Ready, but can be improved

== Multiple virtual network interfaces with their own SSIDs ==

*The Mesh interface: An ad-hock mode, unprotected interface for the mesh nodes to talk to each other with Babel handling routing, ssid: pplsopen-node2node
*The Open interface: An access-point-mode, unprotected interface, for non-mesh devices to connect to the mesh, ssid: peoplesopen.net
*The Private interface: An access-point mode, private interface with WPA2, for the people who own the nodes, ssid: Decided by node owner

Traffic on the private interface should be completely separated from traffic on the non-private interfaces unless a client connected to the private interface requests an IP on the mesh.

Maybe the last one is optional because some people may not need that feature (they already have another access point and they want to keep it), but then how do people administrate the router?

In order to serve a secure web admin config to home users, we'll probably always serve 3 APs with one private WPA encrypted home link so that users can access their admin page.

Status: Implemented

== Web admin interface ==

Development information should be put in [[Mesh/Firmware/Web_Admin_Development|Web Admin Dev]]. This section can remain a wish-list.

A very simple one-page interface. It should do at least the following:

*Display some set of user statistics
:Ideally we could list/graph the number of people who have associated with your mesh node.
:We could also just list/graph the up/down data of people who have been using the mesh.
:[http://lightsquid.sourceforge.net LightSquid] (used by pfSense)

*Set location, name, description.
:But do you want to know the location centrally as well so that you can display nodes on the map? Will people enter this information twice or will you pull this information from nodes and then display on the map? Same for name and description. I would suggest that information is stored only once. In your case on the node itself. So probably you can then pull this information through nodewatcher scripts on nodes and then display nodes the map. Just really should not require people to enter or maintain information on two places because it desyncs very fast. [[User:Mitar|Mitar]] ([[User talk:Mitar|talk]]) 22:20, 24 July 2013 (PDT)
*Let people select how much bandwidth they share.
:They always share 100% when they're not using the connection themselves.
::This works if people are using their private SSIDs on the node. But if the node is connected to their existing home network you might not easily configure such sharing. But maybe there is a way to detect that host network is free and can limits can be increased. [[User:Mitar|Mitar]] ([[User talk:Mitar|talk]]) 22:20, 24 July 2013 (PDT)
:Do any ISPs have bandwidth caps around here? If so, let people specify how many MB to share per month.
:Maybe also a button for temporary increase limits (make them more restrictive) which are then after some time automatically restored.
*Let people change the admin password and the private wifi wpa2 password.
:Probably private SSID as well.
*Donate / "buy routers as presents for your friends"-button.
:One idea we had (but this is probably better for splash screen) is "adopt a node". Where a neighbor who uses a node a lot and depends on the node can donate some money to keep it up, but can then give a nickname or avatar to the node. Or something. [[User:Mitar|Mitar]] ([[User talk:Mitar|talk]]) 22:20, 24 July 2013 (PDT)

Status: [[User:Maxb|Maxb]] implemented a luci-based ui. We decided we hate luci, so we're going to use the ubus uhttpd rpc protocol with a jsonrpc front-end. It's a bit copy-pasta'd from the openwireless router.

Source here:

https://github.com/sudomesh/sudowrt-luci2-webclient

== Remote Updates ==

Once we deploy nodes, we'll want a way to update them as appropriate. The already built node configurator operates along similar lines, but we'd need to do some tweaking in order to make it work on the mesh. Also, we'd want to give the users the options to turn remote updates off. A somewhat decentralized system would be nice as well.

== Watchdog script ==

Node tests itself to see if it has connectivity, etc and resets itself if necessary. OpenWrt supports the hardware watchdog on our PicoStations without any additional hacking, yay!

By default the hardware watchdog will automatically hard-reset the AP if /dev/watchdog is not written to at least once every 60 seconds. A Lua library has been written to interface with the batman-adv kernel module through the batctl command line utility. We need to identify a list of conditions that require a hard-reset and work them into the Lua watchdog script in the openwrt-firmware repository.

The Freifunk group has an awesome watchdog setup, details: http://wiki.freifunk.net/Kamikaze/LuCI/Watchdog

list of possible reset conditions: high sustained load, cron goes down, sshd goes down.

[https://github.com/wlanslovenija/firmware-packages-opkg/tree/master/util/nodewatcher-watchdog nodewatcher watchdog]

Potential use of [https://en.wikipedia.org/wiki/Quilt_%28software%29 Quilt] to update nodes.

== Quality of Service (QoS) ==

We want those who own a node to decide how much internet they share with the network. This software allows users to shape their bandwidth based on type. There's an paper regarding [http://www.scribd.com/doc/155501125/Layer-7-Classificarion-and-Policing-in-the-PfSense layer 7 traffic shaping] too.

Our supported hardware needs a very lightweight software, which is why we've been using [http://lartc.org/manpages/tc.txt tc] (traffic control). It only allows the users to determine how much internet they share with the network.

'''Complete Distributions'''

These have firewall and network management tools included with the distribution.

* [https://www.pfsense.org/ pfSense] - a widely used firewall distribution, but there are most definitely difficulties with it.
* [http://www.zentyal.org/ Zentyal] - a firewall distribution with easy to use graphical interface.
* [http://m0n0.ch/wall/ m0n0wall] - a lightweight firewall distribution meant for embedded systems.

'''Packages'''

These are tools often used in network management distributions.

* [http://www.netfilter.org/ netfilter/iptables] - a set of hooks inside the Linux kernel that allows kernel modules to register callback functions with the network stack.
* [http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2 iproute2] - a collection of utilities for controlling TCP / IP networking and traffic control.
* [http://l7-filter.clearfoundation.com/ l7-filter] (p2p filtering) - identifies packets based on application layer data. It classifies packets to be used with a bandwidth shaper.
* [http://www.ipp2p.org/ ipp2p] (p2p filtering) - identifies peer-to-peer (P2P) data in IP traffic.
* [http://suricata-ids.org/ Suricata] - a high performance network [http://en.wikipedia.org/wiki/Network_intrusion_detection_system intrusion detection system] (IDS), [http://en.wikipedia.org/wiki/Intrusion_prevention_system intrusion prevention system] (IPS), and network security monitoring engine.
* [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls-ipfw.html ipfirewall] (ipfw) - a freeBSD firewall that uses netdummy.
* [http://info.iet.unipi.it/~luigi/dummynet/ netdummy] - a freeBSD traffic shaper and bandwidth manager.
* [http://people.freebsd.org/~mtm/ipfw-classifyd.tar.bz2 ipfw-classifyd] - an application layer classifier for ipfw firewall for freeBSD.

== Virtual Private Network (VPN) ==

The firmware should tunnel all internet traffic from the mesh through a VPN server, unless this feature is specifically disabled. This should not be a single server, as that would be a single point of failure.

* [https://github.com/sudomesh/tunneldigger TunnelDigger] - a lightweight tunneling client/server.
* [https://github.com/heyaaron/openmesher OpenMesher] - another option, but not ideal because of memory constraints on embedded systems.

Here is our [[Mesh/Network_topology|Network Topology]].

== Mesh VPuN ==

If the mesh does not see any other nodes (and maybe even if it does?), and it has internet, then it should connect to another node or two over a [[VPuN]] server. The easy solution is to use the same VPuN servers as for the internet connection.

[[Mesh/Network_topology|Network Topology]]

Status: Implemented

== Location and status reporting ==

Something that reports location and status when polled. I think we can probably get away with using snmp v1.

We developed this format and easy to publish status data from nodes for our [http://dev.wlan-si.net/wiki/Nodewatcher/NodeTelemetryProvider nodewatcher]. OpenWrt packages are [https://github.com/wlanslovenija/firmware-packages-opkg/tree/master/util here]. [[User:Mitar|Mitar]] ([[User talk:Mitar|talk]]) 22:02, 11 July 2013 (PDT)

Nice to have:

*Status info: How many nodes is your node connected to. Is the internet link working.
*An "I don't know what my internet bandwidth is, test it for me"-function.
*Usage statistics (so people can see how many people they helped get internet!)
:This is the most important thing! [[User:Mitar|Mitar]] ([[User talk:Mitar|talk]]) 22:20, 24 July 2013 (PDT)
:You should add as well graphs on how much bandwidth was consumed by the node. This is useful when hosts see that their Internet is slow and believe that it was because of the node. Then they can check and see if it is really node (which often is not) or maybe just ISP has problems. Important because people like to attribute issues they have to nodes they don't understand. [[User:Mitar|Mitar]] ([[User talk:Mitar|talk]]) 22:20, 24 July 2013 (PDT)
*Let people put up a bit of info about their node / house / co-op, on a simple web page that people can access only if they're connected to that node. It could be shown as part of the splash page.

Status: Waiting for nodewatcher project to finish

== Intelligent Wifi Channel Switching ==

It would be nice to be able to have the network intelligently determine channels but we don't want a node changing channel if it means other nodes connected to it will have to change as well so it may make sense to only set the channel once on first boot based on which channels have other nodes.

== IPv6 support ==

We should have IPv6 support, but I am ok with launching the mesh with only IPv4 and adding in IPv6 later. We can do without IPv6 but not without IPv4 ([[User:Juul|Juul]] ([[User talk:Juul|talk]]))

= Stuff the firmware could have =

== DNS server ==

Each node could run its own (caching) DNS server.

For now, if you're logged into the private network on a node, going to http://my.node will take you to the web admin interface

Status:

Implemented web admin URL, but no caching DNS server yet.

== RSSI Testing and Logging ==

At intervals, the nodes could conduct RSSI tests and log them with some way to compare and visualize signal strengths over time.

== Caching web proxy ==

We could use [http://www.pps.univ-paris-diderot.fr/~jch/software/polipo/ Polipo] to improve people's browsing experience. Not sure how much cpu and memory this would need. We may not be able to run it on the routers with less than 32 MB ram (e.g. the Bullet 2 HPs).

Maxb has installed polio as a transparent caching proxy on a picostation 2HP. It improved web browsing significantly! However, it sorta breaks "net neutrality". Also - it'll be irrelevant for https and it might break some things (webdav?).

I wonder if you could (as an end user?) enable/disable this kinda proxying? On splash page? We would need MAC, but it would only get logged on the mesh node itself (not network wide....)

== Block ads and tracking ==

We could use e.g. [http://www.pps.univ-paris-diderot.fr/~jch/software/polipo/ Polipo] with the sources from both adblock plus and ghostery. If we implement this, it should be an optional (default off) feature that you can select on the splash page, with a "remember this" that remembers either using a cookie or using your MAC (but then we'd be logging people's MAC addresses :-S). The block should probably be time-limited (e.g. 30 days).

Now that we're running more powerful devices, I wonder if we could actually run this kind of blocking on the actual mesh nodes. That way we could do a "remember this" MAC and only store it on the mesh node itself (NOT network-wide).

= Compatible devices =

We're going to target ar71xx devices with decent storage + processing speed + memory for "router board" nodes.

Right now we're using for "router board" nodes:
WD MyNet N750 and/or TP-Link TL-WDR4300
The MyNets are no longer in production, but the TL-WDR4300 are the exact same board, just with external antennas.

Then we are using [[extender node|extender nodes]] which plug into the home node and just bridge/forward traffic. This could theoretically be any router which supports openwrt. We've begun by targeting a variety of ubiquiti long-distance outdoor radios (Nanostation M line, Bullet M line, Picostation M line, Nanobridge/beam/etc).

We would also like to support non-openwrt routers (like Ubiquiti Airfiber and Nanobeam 802.11ac devices) but these will only be able to extend one of the three networks (Mesh, Public or Private) and will need to use WDS mode to do so (at least for Mesh).

Mesh/Network topology

2016-02-05T23:55:52Z

Maxb: /* wifi topology */

[[File:Network topology diagram-hi.png|thumb|png (hi), [[Mesh/Diagrams#Network Topology Diagram|see more]]]]
= peoplesopen.net topology =
For information about the people's open network topology, refer to this [[Mesh/Diagrams#Network Topology Diagram|network topology diagram]].

= wifi topology =

[[File:Mesh topology diagram.png|thumb]]

We use 2.4 ghz 802.11g or 802.11n wifi gear with omni or semi-directional antennas to provide connectivity to devices such as laptops and smartphones at street level and within buildings. We are currently using a variety of gear including Ubiquiti Picostation M2 HP and Ubiquiti Bullet M2 HP routers for the outdoor APs.

A high-speed wireless backbone for the mesh will be provided by 5 ghz 802.11n hardware, usually with point to point or point to multipoint connections mounted in high places such as on rooftops, flagpoles or antenna towers. We currently have a variety of Ubiquiti M5 routers such as airgrids, nanobridges, nanostations and a rocket.

See the [[Mesh/Home and extender nodes|Home and extender nodes]] for more info about how these are setup.

All of the outdoor gear will be Power over Ethernet (PoE), requiring only a single cable for network and power connectivity.

= mesh topology =

All routers run the Babel mesh routing protocol. The street-level 2.4 ghz routers should ideally be able to function in the event that e.g. an earthquake takes out all of the point to point and point to multipoint rooftop nodes (more alignment sensitive) and the mesh should remain functional, though it could become segmented.

The relays / [[VPuN]] servers (see the internet connectivity section) also run Babel, so mesh traffic can flow from one part of the mesh, through the internet, through a relay, and into another part of the mesh if some of the mesh nodes are connected to the internet.

= internet connectivity =

There are four primary types of devices in the mesh:

*Clients: E.g. smart phones or laptops connected to the mesh.
:These do not run the meshing protocol.
*Mesh nodes: Wifi routers running OpenWRT.
:This includes home nodes and their extender nodes
*Relays / [[Mesh/VPuN|VPuN servers]]: Professionally hosted servers that relay mesh traffic over the internet.
:These run the meshing protocol. Mesh nodes are connected to them with L2TP tunnels.
*Exit nodes: Co-located servers that appear as the source IP for packets from mesh to internet.
:Both relays and exit nodes serve as a layer of protection between people sharing their internet connections with the mesh. A relay can also be an exit server and this may in fact end up being the case in most instances.

Some mesh routers will be hosted in homes that already have internet connections. If an internet connection is available, a mesh router will open an L2TP tunnel (using the tunneldigger software) to several relay nodes over the internet connection. A relay could be e.g. a VPS without a bandwidth cap. The relays all run Babel and function as part of the mesh through the L2TP tunnels to the mesh nodes. Each relay will have a connection to an exit nodes. The relays allow segments of the mesh that are not connected with wifi to be connected over the internet.

Each relay is connected to one exit node (tunnel type not yet decided). It does NAT (IP Masquerading) on traffic coming from the mesh and headed for the internet. All traffic coming from the mesh and going to the wider internet goes through an exit node. The source IP of data coming from the mesh thus appears as the IP of one of the exit nodes. This provides a layer of protection such that e.g. abuse complaints will be sent to the mesh organization instead of the individuals who donate some of their internet bandwidth to the mesh.
:Until network has an AS, only one exit node should be made and multiple relay nodes should connect to that exit node (Tunneldigger software can be reused for that). Otherwise clients can have issues when routing protocol decides to move from one exit node to another.
:It is important that nodes are connecting to relays and relays to exit nodes and that no IPs of those connecting to relays and exit nodes is stored.

Mesh/Blog

2016-01-26T22:35:45Z

Maxb: Extender Node Mounting at San Pabloish

<startfeed />
=Sharing Internet with the Neighborhood=

I ([[User:Maxb|Maxb]]) put a bullet m2 on my roof as an [[Mesh/Home and extender nodes#Extender_nodes|extender node]]. We have a bunch of these big ol 2.4ghz antennas which I think are pretty high gain and my house has some upstream bandwidth to share, so if you're in the neighborhood and need some wifi, [http://map.sudomesh.org/select/san-pabloish/ feel free to come by and get on the network.]

[[File:PeoplesOpen.net-Extender-Node-Bullet-M2-1.jpg|200px]][[File:PeoplesOpen.net-Extender-Node-BulletM2-2.jpg|200px]]

=Downtown Oakland Access Point=

We spent last Sunday installing a 2.4ghz AP pointing NW towards the street at 1212 Broadway in Downtown Oakland in the [https://getclef.com/ Clef] offices. They have a 1gbps connection in their 12th story office and they were willing to share, so we set up a Nanostation M2 pointing towards the street in an attempt to create an open AP. The tricky thing about setting up APs is that while our antenna is quite strong and has high gain, the majority of devices that would connect to it are weak and have low gain (mobile, laptops, etc). We're going to do some monitoring and testing of how usable the signal is on the street, and we may have to do some adjustments and add another antenna. It may be obvious, but one of our members is quite a cable management specialist :)

<gallery>
PeoplesOpen.net-Clef-Installation-1.jpeg|Showing off work
PeoplesOpen.net-Clef-Installation-2.jpeg|Cable Management
PeoplesOpen.net-Clef-Installation-3.jpeg|Aiming towards the street
</gallery>

=Alpha Testing Network=
We've been doing alpha testing on our what's looking to be the network v0.2 for the last couple months. A lot of our firmware/etc code has been tightened up and we're starting to get good results. There are obviously a lot of metrics that are worth considering when evaluating the success of a network, but uptime is a good start, and we're finally getting 90%+ uptime on all of our nodes. That might not sound impressive, but these are pieces of hardware that are hosted at various folks houses, so coordinating the reboot of a router that's in someone's living room can be a challenging ordeal. For those that are interested, graphs from our monitoring server are available here:

Smokeping (latency graphs) http://monitor.sudomesh.org/smokeping/smokeping.cgi?target=Mesh

and

Cacti (traffic and some hardware measurements): http://monitor.sudomesh.org/cacti/graph_view.php?action=tree&tree_id=1&leaf_id=45

[[File:Sudomesh cacti 10.26.15.png|framed|Cacti Graph of PeoplesOpen.net traffic for 10/26/2015]]
[[File:Sudomesh_cacti_graph_sept-oct.2015.png|framed|Cacti Graph of PeoplesOpen.net traffic for Sept-Oct 2015]]

We've been uploading the latest versions of our firmware as binaries to:

http://builds.sudomesh.org/builds

Home Node firmwares are for TP-Link wdr3500, 3600, and 4300 as well as MyNet N600 and N750 routers.
Extender Node firmwares are known to mostly work for Ubiquiti Picostation M2, Bullet M2 and M5, Powerbridge M2 and M5, and Nanostation M2 and M5.

We're in need of a handful of new folks to host home nodes and possibly also extender nodes. To be a good home node host, we ask that you be:
* Willing to share some amount of your bandwidth. It doesn't have to be a lot, but 1-2mbps can go a long way for someone who doesn't otherwise have any connectivity.
* Reliably in contact so that we can ask you to do simple things like reboot the router (hopefully rarely if at all), and check connectivity
* Interested in providing some feedback as to how you think the experience is and how it could be improved

To be an extender node host we ask that you be all those things and also have access to your roof and/or another high point on your house/building/etc and be willing to mount a (pretty small) antenna there and run an ethernet cable from your home node (probably near your router) to that roof location.

If that sounds like you, get in touch: https://sudoroom.org/wiki/Mesh#Join_Us

At the moment, we're providing the hardware, so you'll be hosting $50-$150 worth of equipment which in many cases can significantly improve coverage in your own home!

=Building out our backbone...=

After a dark fall of struggling with various issues with batman-adv and our tunnels, our coding crew decided to switch to [http://en.wikipedia.org/wiki/Babel_%28protocol%29 Babel]. While integrating the new protocol into our firmware, we've been actively researching potential sources of bandwidth to feed the network and [[Rooftop_Dish_Antenna_Mount|mounting rooftop nodes]] in strategic locations. Every Sunday, we've been building out the backbone of our network from Kensington to West Oakland - contact us if you've got a spot with great line-of-sight!

Our first major node in Kensington has excellent line-of-sight to both Oakland and Richmond:

[[File:20141130 160516.jpg|thumb|center| 400px | Sudomesh dish mount with Oakland in the distance]]

[[File:20141130 160446.jpg|thumb|center| 400px |Sudomesh dish with Richmond in the distance]]

If you're interested in helping out, we're always looking for [[Mesh/Wishlist|donations]] of gear and equipment, as well as committed volunteers and [https://gratipay.com/sudomesh financial support] (even 25 cents a week adds up as we prepare to launch).

[[File:20141130 160500.jpg|thumb| center | 500px |Sudomesh dish mount and happy ethernet wire/RJ45 termination.]]

Here's to growing a network from the ground up, together!

=We're meshing at the Omni!=

It's been a crazily active summer - apologies for the lack of updates! Sudo Room (and by extension, Sudo Mesh) has relocated to the [http://omni-oakland.org Omni Oakland Commons] at 4799 Shattuck. We're excited to be a founding member collective among an array of groups that have moved in together to create a radical commons in Oakland.

[[File:Omnicoversm.png|framed|center|The Omni building and logo]]

If you've been wanting to plug in and help out, or simply reconnect to the group, tonight is a great night to come by and check out the new space!

'''Announcements'''
* We'll be having our monthly general meeting today, starting at 7:30pm at Sudo Room. Please add to the agenda! - https://pad.riseup.net/p/sudomesh
* Juul, MaxB and Alex have been working hard on crushing bugs and levelling up our mesh firmware. We've deployed a test network within the Omni building and they are successfully meshing as I type! \o/
* We've procured a 75 foot antenna tower that will be mounted in West Oakland to become a core relay spot for routing traffic on the mesh.
* Noemie has put together a fantastic sudomesh / people's open net video and is currently soliciting feedback. Check it out @ https://www.youtube.com/watch?v=qva1SQSBDyE
* Paige made a rad flyer design and two versions of the flyer for a) general ways to participate in the project and b) promoting upcoming info sessions. Check them out here: https://sudoroom.org/wiki/Mesh/Flyers
* Stickers!! The round 'Mesh the Planet' and rectangular PeoplesOpen.Net stickers have been printed and can be procured at sudoroom (atio the white shelves next to the staircase) and/or one of our Tuesday/Thursday meetups!

'''Code - so much code this summer!!'''
* Juul created ipk-builder: https://github.com/sudomesh/ipk-builder
* MaxB, Ron, and Juul have been updating the service browser: https://github.com/sudomesh/service-browser
* Juul, MaxB, and Alex reengineered the node-configurator: https://github.com/sudomesh/makenode
* MaxB, Alex and Matt fixed the exitnode
* MaxB created sudowrt-firmware-images for temporary storage of firmware builds
* Matt added a patch to sudowrt-firmware
* Alex and MaxB have been fixing our fork of tunneldigger
* MaxB fixed sudowrt-packages
* Juul updated ubi-flasher
* Juul added fixes to meshnode-database
* Matt created svg-animations for mesh presentations

'''Wiki'''
* Tunabananas created [[Mesh/Flyers]] and uploaded Paige's flyers
* ChrisJ updated [[Mesh/Monitoring]] and created [[Mesh/Icinga]]
* Matt added instructions to [[Mesh/Firmware/Flash]]
* Jul added to [[Mesh/Hardware]] Support
* GMeader created the page [[Mesh/San Francisco]] and added to [[Mesh/Marketing]]
* MaxB added sticker images to [[Mesh/Stickers]]
* ChrisJ created [[Mesh/Sensu]]
* Tunabananas added recent research on broadband access in Oakland to [[Mesh/Oakland]]
* Tunabananas added some months worth of meeting minutes to [[Mesh/Minutes]]
* Jwentwistle added a bunch of documentation to [[Mesh/BATMAN-adv]]
* Jwentwistle and Tunabananas cleaned up the main [[Mesh]] page!
* Jwentwistle moved Mesh/MeshApps primarily to [[Mesh/Distributed Services]]
* Jwentwistle created and added slides to [[Mesh/Presentation]]
* Jwentwistle created [[Mesh/User Guide]]
* Jwentwistle created [[Mesh/Technical Overview]]
* MaxB checked some stuff out
* Matt added some diagrams to [[Mesh/Diagrams]]
* Jwentwistle added bandwidth shaping details to [[Mesh/Firmware]]
* MaxB added some ideas for our box of crappy routers to [[Mesh/Inventory]]
* Tunabananas wrote a new post on [[Mesh/Blog]]
* Aep added to [[Mesh/MeshApps]]

'''To Dos:'''
* Test current mesh setup in the Omni building
* Create online ordering system and shipping label automation
* Create 'How to Care for Your Node' guides
* Outreach to spaces that can host info sessions and presentations
* Work on local apps and services that will run on the mesh!
* More at: https://sudoroom.org/wiki/Mesh/ToDos
** Please update the list above with specific tasks!

'''Help Out!'''
* Come by our weekly hacknights, Tuesdays and Thursdays starting at 7:30pm at Sudo Room <https://sudoroom.org>
* Contribute research, ideas, designs to our wiki: https://sudomesh.org
* Contribute to the code: https://github.com/sudomesh
* Donate hardware and equipment! <https://sudoroom.org/wiki/Mesh/Wishlist>
* Give a small weekly donation: https://www.gittip.com/sudomesh

'''Recommended Reading'''
* Oakland's Sudo Mesh looks to counter censorship and the digital divide with a mesh network: http://techpresident.com/news/25200/oakland-sudo-mesh-counter-censorship-digital-divide-mesh-net
* It's Time for Open, Shared Home Wi-Fi (Re/Code): http://recode.net/2014/08/05/its-time-for-shared-open-home-wi-fi/

=Mesh Hackathon @ The Omni, July 5-7!=
This weekend, Sudo Mesh is having our first mesh hackathon at sudo room's new location in the Omni! Join us at 4799 at any point this weekend, starting at noon until we tire today[1], and noon on Sunday and Monday. We'll have rotating orientation sessions every hour on the hour both Sunday and Monday, so feel free to come by even if you're brand new to the project!

[[File:Sudoroomfirstallnighter.jpg|center|First all-nighter in the new sudo room!]]

Here are some of the things we plan to work on:
* Designing [[Mesh/Diagrams|network diagrams]] and educational curricula.
* Debugging exit node issues.
* Setting up [[Network/Reboot|our network at the Omni]], the new home of sudo room!
* [[Mesh/Communities|Outreach]] to various community stakeholders and interest groups relevant to the mesh (eg; rock climbers! Ham radio enthusiasts! Librarians!)
* Research and test deployment of [[Mesh/MeshApps|mesh apps]].
* Getting our books in order (finances, [[Mesh/Blog|blog]], calendar, 501c3 app, etc;)
* Making [[Mesh/Swag|swag]] ([[Mesh/Stickers|stickers]]! buttons! whatever you can think of!).

Whether you're a core team member, an occasional collaborator, or just interested in learning more about the mesh, you are welcome!

[1] We are being powered by [[Sudomate]].

--[[User:Tunabananas|Tunabananas]]

=Developer Launch!=
As of last night, we've officially launched version 0.1.0 of the mesh firmware, a.k.a. Snow Crash.

[[File:Snowcrash.png|center|Snow Crash login screen]]

The plan is to have ~20 people with networking skills run nodes from their homes for 1-2 months and report any remaining issues. We'll then fix those bugs and do a wider release of ~60 more nodes.

What's currently working:

1. Sharing limited Internet bandwidth with peoplesopen.net
2. Private access point with no bandwidth limit and mesh access
3. Automatic node meshing with batman-adv
4. Simplified web admin interface that lets node-owners change bandwidth sharing settings and passwords.
5. Automated configuration of new nodes using easy web interface.
6. Automatic printing of stickers with instructions and default generated passwords.

To those of you who have already taken nodes home, here are a few notes:

1. sudo mesh has root access to your nodes since we manage updates per default. If you want to manage your own node and don't want sudo mesh to have access, you can disable our root access by removing /etc/dropbear/authorized_keys on your node.

2. Please report any bugs on our github. If you know which repository the bug pertains to, then go to the issue tracker for that repository. If you aren't sure, then just add the bug here: https://github.com/sudomesh/sudowrt-firmware/issues

A compiled version of the firmware is available here: http://build.sudomesh.org:8080/latest_images/atheros/

Keep in mind that the nodes have to be configured using the node-configurator after being flashed with that firmware and that the firmware only trusts sudomesh SSL certificates. We'll release a less secure version for developers who just want to play around as soon as possible. For now you can configure your nodes at sudo room with the help of one of the core team.

In the following is a list of the repositories directly relevant to this release of the firmware. All of these repositories have been tagged with "sudowrt-0.1.0" so you can get the exact versions used in the release.

*The sudowrt firmware and build scripts (based on openwrt and the work of wlan slovenja): https://github.com/sudomesh/sudowrt-firmware
*The sudowrt packages repository: https://github.com/sudomesh/sudowrt-packages
*The web admin interface: https://github.com/sudomesh/luci-app-peopleswifi
*The mDNS and DNS-SD client: https://github.com/sudomesh/mdnssd-min
*The node database: https://github.com/sudomesh/node-database
*The node configurator: https://github.com/sudomesh/node-configurator
*Sticker printing support for the node configurator: https://github.com/sudomesh/ql570
*The node configurator client: https://github.com/sudomesh/node-configurator-client
*The wlan slovenja tunneldigger (very slightly modified): https://github.com/sudomesh/tunneldigger

Mesh the planet!

--via [[User:Juul|Juul]]

=How to Participate: All Hands on Deck!=
We are always excited to have new volunteers join the team! From designing flyers to developing software, doing research and documenting what you learn, fixing broken hardware to hitting the streets and spreading the word, there's something for everybody who wants to participate.

We meet weekly on Thursday evenings starting at 7:30pm at [https://sudoroom.org Sudo Room], your friendly neighborhood hackerspace. Come on by and jump in!

You can also participate online via [https://lists.sudoroom.org/listinfo/mesh our mailing list], our [http://webchat.freenode.net/?channels=peoplesopen.net chat room], contributing to [https://github.com/sudomesh our code on Github], and adding to this very wiki.

Donations are always appreciated and keep us sustainable. We accept donations [https://gittip.com/sudomesh via Gittip] (anonymous weekly micropayments), through [http://blockchain.info/address/12RxU4DpLpdWcmEBn7Tj325CCXBwt5i9Hc Bitcoin], and in-person at our weekly meetings. Sudo Mesh is currently in the process of acquiring non-profit status, so your donations will be retroactively tax-deductible. If you'd like to donate materials directly, [https://sudoroom.org/wiki/Mesh/Wishlist check here] for a list of hardware we'd love to have.

We also need gung ho folks to climb rooftops and mount nodes!

For press inquiries, please contact [mailto:info@sudomesh.org info (at) sudomesh (dot) org]!

--[[User:Tunabananas|Tunabananas]]

=Deployed our first node!=
[[File:FirstNode.JPG|right|350px|Sudo Mesh's first mesh node!]]
Today we finished installing our first backbone node! It's running [https://github.com/sudomesh Sudo Mesh v0.1 Snow Crash], and will soon be linking up with two neighboring hacker houses. :-)

Here's [[User:Juul|Juul's]] reportback:

<blockquote>Pete and myself installed a Nanostation M5 on a 20 foot aluminum flagpole in West Oakland. The node is about 14 feet above the roof of a two-story building. The total cost of this install ran to about $145 including all materials.

Bill of Materials:

* One Nanostation M5 loco
* One 4 foot wood beam of 3.5" by 3.5"
* Three 5" by 1/4" bolts
* Three 5/8" washers for bolts (optional)
* Three 1/2" washers for bolts (optional)
* Two 5" hose clamps
* 30+ feet of outdoor shielded ethernet cable
* Two shielded/groundable ethernet plugs
* A bunch of zip ties

The optional washers make it easier to tighten and untighten the bolts (otherwise they dig into the wood).

Material sources:

* Nanostation from Amazon
* Flag pole from Harbor Freight
* Everything else from Home Depot
</blockquote>

--[[User:Tunabananas|Tunabananas]] ([[User talk:Tunabananas|talk]]) 21:21, 31 December 2013 (PST)

=hello world!=
it's been [https://lists.sudoroom.org/pipermail/mesh/2013-January/000000.html nearly a year] since we first started meeting - our tiny group. so much learning, so much progress!

we've launched [http://peoplesopen.net the peoplesopen.net]!
&& [http://meshthepla.net meshthepla.net]!

check out our [https://github.com/sudomesh code] - namely forks of openwrt running batman-adv for routing and incorporating wlan-slovenia's tunneldigger for secure vpn connections, as well as an admin interface written in lua.

--[[User:Tunabananas|Tunabananas]] ([[User talk:Tunabananas|talk]]) 06:54, 28 December 2013 (PST)
<endfeed />

File:PeoplesOpen.net-Extender-Node-BulletM2-2.jpg

2016-01-26T22:31:51Z

Maxb: PeoplesOpen.net Extender Node Bullet M2 mounting

PeoplesOpen.net Extender Node Bullet M2 mounting

File:PeoplesOpen.net-Extender-Node-Bullet-M2-1.jpg

2016-01-26T22:31:22Z

Maxb: PeoplesOpen.net Extender Node Bullet M2 mounting

PeoplesOpen.net Extender Node Bullet M2 mounting

Mesh/Blog

2016-01-19T07:01:40Z

Maxb: /* Downtown Oakland Access Point */

<startfeed />
=Downtown Oakland Access Point=

We spent last Sunday installing a 2.4ghz AP pointing NW towards the street at 1212 Broadway in Downtown Oakland in the [https://getclef.com/ Clef] offices. They have a 1gbps connection in their 12th story office and they were willing to share, so we set up a Nanostation M2 pointing towards the street in an attempt to create an open AP. The tricky thing about setting up APs is that while our antenna is quite strong and has high gain, the majority of devices that would connect to it are weak and have low gain (mobile, laptops, etc). We're going to do some monitoring and testing of how usable the signal is on the street, and we may have to do some adjustments and add another antenna. It may be obvious, but one of our members is quite a cable management specialist :)

<gallery>
PeoplesOpen.net-Clef-Installation-1.jpeg|Showing off work
PeoplesOpen.net-Clef-Installation-2.jpeg|Cable Management
PeoplesOpen.net-Clef-Installation-3.jpeg|Aiming towards the street
</gallery>

=Alpha Testing Network=
We've been doing alpha testing on our what's looking to be the network v0.2 for the last couple months. A lot of our firmware/etc code has been tightened up and we're starting to get good results. There are obviously a lot of metrics that are worth considering when evaluating the success of a network, but uptime is a good start, and we're finally getting 90%+ uptime on all of our nodes. That might not sound impressive, but these are pieces of hardware that are hosted at various folks houses, so coordinating the reboot of a router that's in someone's living room can be a challenging ordeal. For those that are interested, graphs from our monitoring server are available here:

Smokeping (latency graphs) http://monitor.sudomesh.org/smokeping/smokeping.cgi?target=Mesh

and

Cacti (traffic and some hardware measurements): http://monitor.sudomesh.org/cacti/graph_view.php?action=tree&tree_id=1&leaf_id=45

[[File:Sudomesh cacti 10.26.15.png|framed|Cacti Graph of PeoplesOpen.net traffic for 10/26/2015]]
[[File:Sudomesh_cacti_graph_sept-oct.2015.png|framed|Cacti Graph of PeoplesOpen.net traffic for Sept-Oct 2015]]

We've been uploading the latest versions of our firmware as binaries to:

http://builds.sudomesh.org/builds

Home Node firmwares are for TP-Link wdr3500, 3600, and 4300 as well as MyNet N600 and N750 routers.
Extender Node firmwares are known to mostly work for Ubiquiti Picostation M2, Bullet M2 and M5, Powerbridge M2 and M5, and Nanostation M2 and M5.

We're in need of a handful of new folks to host home nodes and possibly also extender nodes. To be a good home node host, we ask that you be:
* Willing to share some amount of your bandwidth. It doesn't have to be a lot, but 1-2mbps can go a long way for someone who doesn't otherwise have any connectivity.
* Reliably in contact so that we can ask you to do simple things like reboot the router (hopefully rarely if at all), and check connectivity
* Interested in providing some feedback as to how you think the experience is and how it could be improved

To be an extender node host we ask that you be all those things and also have access to your roof and/or another high point on your house/building/etc and be willing to mount a (pretty small) antenna there and run an ethernet cable from your home node (probably near your router) to that roof location.

If that sounds like you, get in touch: https://sudoroom.org/wiki/Mesh#Join_Us

At the moment, we're providing the hardware, so you'll be hosting $50-$150 worth of equipment which in many cases can significantly improve coverage in your own home!

=Building out our backbone...=

After a dark fall of struggling with various issues with batman-adv and our tunnels, our coding crew decided to switch to [http://en.wikipedia.org/wiki/Babel_%28protocol%29 Babel]. While integrating the new protocol into our firmware, we've been actively researching potential sources of bandwidth to feed the network and [[Rooftop_Dish_Antenna_Mount|mounting rooftop nodes]] in strategic locations. Every Sunday, we've been building out the backbone of our network from Kensington to West Oakland - contact us if you've got a spot with great line-of-sight!

Our first major node in Kensington has excellent line-of-sight to both Oakland and Richmond:

[[File:20141130 160516.jpg|thumb|center| 400px | Sudomesh dish mount with Oakland in the distance]]

[[File:20141130 160446.jpg|thumb|center| 400px |Sudomesh dish with Richmond in the distance]]

If you're interested in helping out, we're always looking for [[Mesh/Wishlist|donations]] of gear and equipment, as well as committed volunteers and [https://gratipay.com/sudomesh financial support] (even 25 cents a week adds up as we prepare to launch).

[[File:20141130 160500.jpg|thumb| center | 500px |Sudomesh dish mount and happy ethernet wire/RJ45 termination.]]

Here's to growing a network from the ground up, together!

=We're meshing at the Omni!=

It's been a crazily active summer - apologies for the lack of updates! Sudo Room (and by extension, Sudo Mesh) has relocated to the [http://omni-oakland.org Omni Oakland Commons] at 4799 Shattuck. We're excited to be a founding member collective among an array of groups that have moved in together to create a radical commons in Oakland.

[[File:Omnicoversm.png|framed|center|The Omni building and logo]]

If you've been wanting to plug in and help out, or simply reconnect to the group, tonight is a great night to come by and check out the new space!

'''Announcements'''
* We'll be having our monthly general meeting today, starting at 7:30pm at Sudo Room. Please add to the agenda! - https://pad.riseup.net/p/sudomesh
* Juul, MaxB and Alex have been working hard on crushing bugs and levelling up our mesh firmware. We've deployed a test network within the Omni building and they are successfully meshing as I type! \o/
* We've procured a 75 foot antenna tower that will be mounted in West Oakland to become a core relay spot for routing traffic on the mesh.
* Noemie has put together a fantastic sudomesh / people's open net video and is currently soliciting feedback. Check it out @ https://www.youtube.com/watch?v=qva1SQSBDyE
* Paige made a rad flyer design and two versions of the flyer for a) general ways to participate in the project and b) promoting upcoming info sessions. Check them out here: https://sudoroom.org/wiki/Mesh/Flyers
* Stickers!! The round 'Mesh the Planet' and rectangular PeoplesOpen.Net stickers have been printed and can be procured at sudoroom (atio the white shelves next to the staircase) and/or one of our Tuesday/Thursday meetups!

'''Code - so much code this summer!!'''
* Juul created ipk-builder: https://github.com/sudomesh/ipk-builder
* MaxB, Ron, and Juul have been updating the service browser: https://github.com/sudomesh/service-browser
* Juul, MaxB, and Alex reengineered the node-configurator: https://github.com/sudomesh/makenode
* MaxB, Alex and Matt fixed the exitnode
* MaxB created sudowrt-firmware-images for temporary storage of firmware builds
* Matt added a patch to sudowrt-firmware
* Alex and MaxB have been fixing our fork of tunneldigger
* MaxB fixed sudowrt-packages
* Juul updated ubi-flasher
* Juul added fixes to meshnode-database
* Matt created svg-animations for mesh presentations

'''Wiki'''
* Tunabananas created [[Mesh/Flyers]] and uploaded Paige's flyers
* ChrisJ updated [[Mesh/Monitoring]] and created [[Mesh/Icinga]]
* Matt added instructions to [[Mesh/Firmware/Flash]]
* Jul added to [[Mesh/Hardware]] Support
* GMeader created the page [[Mesh/San Francisco]] and added to [[Mesh/Marketing]]
* MaxB added sticker images to [[Mesh/Stickers]]
* ChrisJ created [[Mesh/Sensu]]
* Tunabananas added recent research on broadband access in Oakland to [[Mesh/Oakland]]
* Tunabananas added some months worth of meeting minutes to [[Mesh/Minutes]]
* Jwentwistle added a bunch of documentation to [[Mesh/BATMAN-adv]]
* Jwentwistle and Tunabananas cleaned up the main [[Mesh]] page!
* Jwentwistle moved Mesh/MeshApps primarily to [[Mesh/Distributed Services]]
* Jwentwistle created and added slides to [[Mesh/Presentation]]
* Jwentwistle created [[Mesh/User Guide]]
* Jwentwistle created [[Mesh/Technical Overview]]
* MaxB checked some stuff out
* Matt added some diagrams to [[Mesh/Diagrams]]
* Jwentwistle added bandwidth shaping details to [[Mesh/Firmware]]
* MaxB added some ideas for our box of crappy routers to [[Mesh/Inventory]]
* Tunabananas wrote a new post on [[Mesh/Blog]]
* Aep added to [[Mesh/MeshApps]]

'''To Dos:'''
* Test current mesh setup in the Omni building
* Create online ordering system and shipping label automation
* Create 'How to Care for Your Node' guides
* Outreach to spaces that can host info sessions and presentations
* Work on local apps and services that will run on the mesh!
* More at: https://sudoroom.org/wiki/Mesh/ToDos
** Please update the list above with specific tasks!

'''Help Out!'''
* Come by our weekly hacknights, Tuesdays and Thursdays starting at 7:30pm at Sudo Room <https://sudoroom.org>
* Contribute research, ideas, designs to our wiki: https://sudomesh.org
* Contribute to the code: https://github.com/sudomesh
* Donate hardware and equipment! <https://sudoroom.org/wiki/Mesh/Wishlist>
* Give a small weekly donation: https://www.gittip.com/sudomesh

'''Recommended Reading'''
* Oakland's Sudo Mesh looks to counter censorship and the digital divide with a mesh network: http://techpresident.com/news/25200/oakland-sudo-mesh-counter-censorship-digital-divide-mesh-net
* It's Time for Open, Shared Home Wi-Fi (Re/Code): http://recode.net/2014/08/05/its-time-for-shared-open-home-wi-fi/

=Mesh Hackathon @ The Omni, July 5-7!=
This weekend, Sudo Mesh is having our first mesh hackathon at sudo room's new location in the Omni! Join us at 4799 at any point this weekend, starting at noon until we tire today[1], and noon on Sunday and Monday. We'll have rotating orientation sessions every hour on the hour both Sunday and Monday, so feel free to come by even if you're brand new to the project!

[[File:Sudoroomfirstallnighter.jpg|center|First all-nighter in the new sudo room!]]

Here are some of the things we plan to work on:
* Designing [[Mesh/Diagrams|network diagrams]] and educational curricula.
* Debugging exit node issues.
* Setting up [[Network/Reboot|our network at the Omni]], the new home of sudo room!
* [[Mesh/Communities|Outreach]] to various community stakeholders and interest groups relevant to the mesh (eg; rock climbers! Ham radio enthusiasts! Librarians!)
* Research and test deployment of [[Mesh/MeshApps|mesh apps]].
* Getting our books in order (finances, [[Mesh/Blog|blog]], calendar, 501c3 app, etc;)
* Making [[Mesh/Swag|swag]] ([[Mesh/Stickers|stickers]]! buttons! whatever you can think of!).

Whether you're a core team member, an occasional collaborator, or just interested in learning more about the mesh, you are welcome!

[1] We are being powered by [[Sudomate]].

--[[User:Tunabananas|Tunabananas]]

=Developer Launch!=
As of last night, we've officially launched version 0.1.0 of the mesh firmware, a.k.a. Snow Crash.

[[File:Snowcrash.png|center|Snow Crash login screen]]

The plan is to have ~20 people with networking skills run nodes from their homes for 1-2 months and report any remaining issues. We'll then fix those bugs and do a wider release of ~60 more nodes.

What's currently working:

1. Sharing limited Internet bandwidth with peoplesopen.net
2. Private access point with no bandwidth limit and mesh access
3. Automatic node meshing with batman-adv
4. Simplified web admin interface that lets node-owners change bandwidth sharing settings and passwords.
5. Automated configuration of new nodes using easy web interface.
6. Automatic printing of stickers with instructions and default generated passwords.

To those of you who have already taken nodes home, here are a few notes:

1. sudo mesh has root access to your nodes since we manage updates per default. If you want to manage your own node and don't want sudo mesh to have access, you can disable our root access by removing /etc/dropbear/authorized_keys on your node.

2. Please report any bugs on our github. If you know which repository the bug pertains to, then go to the issue tracker for that repository. If you aren't sure, then just add the bug here: https://github.com/sudomesh/sudowrt-firmware/issues

A compiled version of the firmware is available here: http://build.sudomesh.org:8080/latest_images/atheros/

Keep in mind that the nodes have to be configured using the node-configurator after being flashed with that firmware and that the firmware only trusts sudomesh SSL certificates. We'll release a less secure version for developers who just want to play around as soon as possible. For now you can configure your nodes at sudo room with the help of one of the core team.

In the following is a list of the repositories directly relevant to this release of the firmware. All of these repositories have been tagged with "sudowrt-0.1.0" so you can get the exact versions used in the release.

*The sudowrt firmware and build scripts (based on openwrt and the work of wlan slovenja): https://github.com/sudomesh/sudowrt-firmware
*The sudowrt packages repository: https://github.com/sudomesh/sudowrt-packages
*The web admin interface: https://github.com/sudomesh/luci-app-peopleswifi
*The mDNS and DNS-SD client: https://github.com/sudomesh/mdnssd-min
*The node database: https://github.com/sudomesh/node-database
*The node configurator: https://github.com/sudomesh/node-configurator
*Sticker printing support for the node configurator: https://github.com/sudomesh/ql570
*The node configurator client: https://github.com/sudomesh/node-configurator-client
*The wlan slovenja tunneldigger (very slightly modified): https://github.com/sudomesh/tunneldigger

Mesh the planet!

--via [[User:Juul|Juul]]

=How to Participate: All Hands on Deck!=
We are always excited to have new volunteers join the team! From designing flyers to developing software, doing research and documenting what you learn, fixing broken hardware to hitting the streets and spreading the word, there's something for everybody who wants to participate.

We meet weekly on Thursday evenings starting at 7:30pm at [https://sudoroom.org Sudo Room], your friendly neighborhood hackerspace. Come on by and jump in!

You can also participate online via [https://lists.sudoroom.org/listinfo/mesh our mailing list], our [http://webchat.freenode.net/?channels=peoplesopen.net chat room], contributing to [https://github.com/sudomesh our code on Github], and adding to this very wiki.

Donations are always appreciated and keep us sustainable. We accept donations [https://gittip.com/sudomesh via Gittip] (anonymous weekly micropayments), through [http://blockchain.info/address/12RxU4DpLpdWcmEBn7Tj325CCXBwt5i9Hc Bitcoin], and in-person at our weekly meetings. Sudo Mesh is currently in the process of acquiring non-profit status, so your donations will be retroactively tax-deductible. If you'd like to donate materials directly, [https://sudoroom.org/wiki/Mesh/Wishlist check here] for a list of hardware we'd love to have.

We also need gung ho folks to climb rooftops and mount nodes!

For press inquiries, please contact [mailto:info@sudomesh.org info (at) sudomesh (dot) org]!

--[[User:Tunabananas|Tunabananas]]

=Deployed our first node!=
[[File:FirstNode.JPG|right|350px|Sudo Mesh's first mesh node!]]
Today we finished installing our first backbone node! It's running [https://github.com/sudomesh Sudo Mesh v0.1 Snow Crash], and will soon be linking up with two neighboring hacker houses. :-)

Here's [[User:Juul|Juul's]] reportback:

<blockquote>Pete and myself installed a Nanostation M5 on a 20 foot aluminum flagpole in West Oakland. The node is about 14 feet above the roof of a two-story building. The total cost of this install ran to about $145 including all materials.

Bill of Materials:

* One Nanostation M5 loco
* One 4 foot wood beam of 3.5" by 3.5"
* Three 5" by 1/4" bolts
* Three 5/8" washers for bolts (optional)
* Three 1/2" washers for bolts (optional)
* Two 5" hose clamps
* 30+ feet of outdoor shielded ethernet cable
* Two shielded/groundable ethernet plugs
* A bunch of zip ties

The optional washers make it easier to tighten and untighten the bolts (otherwise they dig into the wood).

Material sources:

* Nanostation from Amazon
* Flag pole from Harbor Freight
* Everything else from Home Depot
</blockquote>

--[[User:Tunabananas|Tunabananas]] ([[User talk:Tunabananas|talk]]) 21:21, 31 December 2013 (PST)

=hello world!=
it's been [https://lists.sudoroom.org/pipermail/mesh/2013-January/000000.html nearly a year] since we first started meeting - our tiny group. so much learning, so much progress!

we've launched [http://peoplesopen.net the peoplesopen.net]!
&& [http://meshthepla.net meshthepla.net]!

check out our [https://github.com/sudomesh code] - namely forks of openwrt running batman-adv for routing and incorporating wlan-slovenia's tunneldigger for secure vpn connections, as well as an admin interface written in lua.

--[[User:Tunabananas|Tunabananas]] ([[User talk:Tunabananas|talk]]) 06:54, 28 December 2013 (PST)
<endfeed />

Mesh/Blog

2016-01-19T07:01:13Z

Maxb: Clef AP Install

<startfeed />
=Downtown Oakland Access Point=

We spent last Sunday installing a 2.4ghz AP pointing NW towards the street at 1212 Broadway in Downtown Oakland in the [https://getclef.com/ Clef] offices. They have a 1gbps connection in their 12th story office and they were willing to share, so we set up a Nanostation M2 pointing towards the street in an attempt to create an open AP. The tricky thing about setting up APs is that while our antenna is quite strong and has high gain, the majority of devices that would connect to it are weak and have low gain (mobile, laptops, etc). We're going to do some monitoring and testing of how usable the signal is on the street, and we may have to do some adjustments and add another antenna. It may be obvious, but one of our members is quite a cable management specialist :)

<gallery>
PeoplesOpen.net-Clef-Installation-1.jpeg|Showing off work
PeoplesOpen.net-Clef-Installation-2.jpeg|That Cable Management
PeoplesOpen.net-Clef-Installation-3.jpeg|Aiming towards the street
</gallery>

=Alpha Testing Network=
We've been doing alpha testing on our what's looking to be the network v0.2 for the last couple months. A lot of our firmware/etc code has been tightened up and we're starting to get good results. There are obviously a lot of metrics that are worth considering when evaluating the success of a network, but uptime is a good start, and we're finally getting 90%+ uptime on all of our nodes. That might not sound impressive, but these are pieces of hardware that are hosted at various folks houses, so coordinating the reboot of a router that's in someone's living room can be a challenging ordeal. For those that are interested, graphs from our monitoring server are available here:

Smokeping (latency graphs) http://monitor.sudomesh.org/smokeping/smokeping.cgi?target=Mesh

and

Cacti (traffic and some hardware measurements): http://monitor.sudomesh.org/cacti/graph_view.php?action=tree&tree_id=1&leaf_id=45

[[File:Sudomesh cacti 10.26.15.png|framed|Cacti Graph of PeoplesOpen.net traffic for 10/26/2015]]
[[File:Sudomesh_cacti_graph_sept-oct.2015.png|framed|Cacti Graph of PeoplesOpen.net traffic for Sept-Oct 2015]]

We've been uploading the latest versions of our firmware as binaries to:

http://builds.sudomesh.org/builds

Home Node firmwares are for TP-Link wdr3500, 3600, and 4300 as well as MyNet N600 and N750 routers.
Extender Node firmwares are known to mostly work for Ubiquiti Picostation M2, Bullet M2 and M5, Powerbridge M2 and M5, and Nanostation M2 and M5.

We're in need of a handful of new folks to host home nodes and possibly also extender nodes. To be a good home node host, we ask that you be:
* Willing to share some amount of your bandwidth. It doesn't have to be a lot, but 1-2mbps can go a long way for someone who doesn't otherwise have any connectivity.
* Reliably in contact so that we can ask you to do simple things like reboot the router (hopefully rarely if at all), and check connectivity
* Interested in providing some feedback as to how you think the experience is and how it could be improved

To be an extender node host we ask that you be all those things and also have access to your roof and/or another high point on your house/building/etc and be willing to mount a (pretty small) antenna there and run an ethernet cable from your home node (probably near your router) to that roof location.

If that sounds like you, get in touch: https://sudoroom.org/wiki/Mesh#Join_Us

At the moment, we're providing the hardware, so you'll be hosting $50-$150 worth of equipment which in many cases can significantly improve coverage in your own home!

=Building out our backbone...=

After a dark fall of struggling with various issues with batman-adv and our tunnels, our coding crew decided to switch to [http://en.wikipedia.org/wiki/Babel_%28protocol%29 Babel]. While integrating the new protocol into our firmware, we've been actively researching potential sources of bandwidth to feed the network and [[Rooftop_Dish_Antenna_Mount|mounting rooftop nodes]] in strategic locations. Every Sunday, we've been building out the backbone of our network from Kensington to West Oakland - contact us if you've got a spot with great line-of-sight!

Our first major node in Kensington has excellent line-of-sight to both Oakland and Richmond:

[[File:20141130 160516.jpg|thumb|center| 400px | Sudomesh dish mount with Oakland in the distance]]

[[File:20141130 160446.jpg|thumb|center| 400px |Sudomesh dish with Richmond in the distance]]

If you're interested in helping out, we're always looking for [[Mesh/Wishlist|donations]] of gear and equipment, as well as committed volunteers and [https://gratipay.com/sudomesh financial support] (even 25 cents a week adds up as we prepare to launch).

[[File:20141130 160500.jpg|thumb| center | 500px |Sudomesh dish mount and happy ethernet wire/RJ45 termination.]]

Here's to growing a network from the ground up, together!

=We're meshing at the Omni!=

It's been a crazily active summer - apologies for the lack of updates! Sudo Room (and by extension, Sudo Mesh) has relocated to the [http://omni-oakland.org Omni Oakland Commons] at 4799 Shattuck. We're excited to be a founding member collective among an array of groups that have moved in together to create a radical commons in Oakland.

[[File:Omnicoversm.png|framed|center|The Omni building and logo]]

If you've been wanting to plug in and help out, or simply reconnect to the group, tonight is a great night to come by and check out the new space!

'''Announcements'''
* We'll be having our monthly general meeting today, starting at 7:30pm at Sudo Room. Please add to the agenda! - https://pad.riseup.net/p/sudomesh
* Juul, MaxB and Alex have been working hard on crushing bugs and levelling up our mesh firmware. We've deployed a test network within the Omni building and they are successfully meshing as I type! \o/
* We've procured a 75 foot antenna tower that will be mounted in West Oakland to become a core relay spot for routing traffic on the mesh.
* Noemie has put together a fantastic sudomesh / people's open net video and is currently soliciting feedback. Check it out @ https://www.youtube.com/watch?v=qva1SQSBDyE
* Paige made a rad flyer design and two versions of the flyer for a) general ways to participate in the project and b) promoting upcoming info sessions. Check them out here: https://sudoroom.org/wiki/Mesh/Flyers
* Stickers!! The round 'Mesh the Planet' and rectangular PeoplesOpen.Net stickers have been printed and can be procured at sudoroom (atio the white shelves next to the staircase) and/or one of our Tuesday/Thursday meetups!

'''Code - so much code this summer!!'''
* Juul created ipk-builder: https://github.com/sudomesh/ipk-builder
* MaxB, Ron, and Juul have been updating the service browser: https://github.com/sudomesh/service-browser
* Juul, MaxB, and Alex reengineered the node-configurator: https://github.com/sudomesh/makenode
* MaxB, Alex and Matt fixed the exitnode
* MaxB created sudowrt-firmware-images for temporary storage of firmware builds
* Matt added a patch to sudowrt-firmware
* Alex and MaxB have been fixing our fork of tunneldigger
* MaxB fixed sudowrt-packages
* Juul updated ubi-flasher
* Juul added fixes to meshnode-database
* Matt created svg-animations for mesh presentations

'''Wiki'''
* Tunabananas created [[Mesh/Flyers]] and uploaded Paige's flyers
* ChrisJ updated [[Mesh/Monitoring]] and created [[Mesh/Icinga]]
* Matt added instructions to [[Mesh/Firmware/Flash]]
* Jul added to [[Mesh/Hardware]] Support
* GMeader created the page [[Mesh/San Francisco]] and added to [[Mesh/Marketing]]
* MaxB added sticker images to [[Mesh/Stickers]]
* ChrisJ created [[Mesh/Sensu]]
* Tunabananas added recent research on broadband access in Oakland to [[Mesh/Oakland]]
* Tunabananas added some months worth of meeting minutes to [[Mesh/Minutes]]
* Jwentwistle added a bunch of documentation to [[Mesh/BATMAN-adv]]
* Jwentwistle and Tunabananas cleaned up the main [[Mesh]] page!
* Jwentwistle moved Mesh/MeshApps primarily to [[Mesh/Distributed Services]]
* Jwentwistle created and added slides to [[Mesh/Presentation]]
* Jwentwistle created [[Mesh/User Guide]]
* Jwentwistle created [[Mesh/Technical Overview]]
* MaxB checked some stuff out
* Matt added some diagrams to [[Mesh/Diagrams]]
* Jwentwistle added bandwidth shaping details to [[Mesh/Firmware]]
* MaxB added some ideas for our box of crappy routers to [[Mesh/Inventory]]
* Tunabananas wrote a new post on [[Mesh/Blog]]
* Aep added to [[Mesh/MeshApps]]

'''To Dos:'''
* Test current mesh setup in the Omni building
* Create online ordering system and shipping label automation
* Create 'How to Care for Your Node' guides
* Outreach to spaces that can host info sessions and presentations
* Work on local apps and services that will run on the mesh!
* More at: https://sudoroom.org/wiki/Mesh/ToDos
** Please update the list above with specific tasks!

'''Help Out!'''
* Come by our weekly hacknights, Tuesdays and Thursdays starting at 7:30pm at Sudo Room <https://sudoroom.org>
* Contribute research, ideas, designs to our wiki: https://sudomesh.org
* Contribute to the code: https://github.com/sudomesh
* Donate hardware and equipment! <https://sudoroom.org/wiki/Mesh/Wishlist>
* Give a small weekly donation: https://www.gittip.com/sudomesh

'''Recommended Reading'''
* Oakland's Sudo Mesh looks to counter censorship and the digital divide with a mesh network: http://techpresident.com/news/25200/oakland-sudo-mesh-counter-censorship-digital-divide-mesh-net
* It's Time for Open, Shared Home Wi-Fi (Re/Code): http://recode.net/2014/08/05/its-time-for-shared-open-home-wi-fi/

=Mesh Hackathon @ The Omni, July 5-7!=
This weekend, Sudo Mesh is having our first mesh hackathon at sudo room's new location in the Omni! Join us at 4799 at any point this weekend, starting at noon until we tire today[1], and noon on Sunday and Monday. We'll have rotating orientation sessions every hour on the hour both Sunday and Monday, so feel free to come by even if you're brand new to the project!

[[File:Sudoroomfirstallnighter.jpg|center|First all-nighter in the new sudo room!]]

Here are some of the things we plan to work on:
* Designing [[Mesh/Diagrams|network diagrams]] and educational curricula.
* Debugging exit node issues.
* Setting up [[Network/Reboot|our network at the Omni]], the new home of sudo room!
* [[Mesh/Communities|Outreach]] to various community stakeholders and interest groups relevant to the mesh (eg; rock climbers! Ham radio enthusiasts! Librarians!)
* Research and test deployment of [[Mesh/MeshApps|mesh apps]].
* Getting our books in order (finances, [[Mesh/Blog|blog]], calendar, 501c3 app, etc;)
* Making [[Mesh/Swag|swag]] ([[Mesh/Stickers|stickers]]! buttons! whatever you can think of!).

Whether you're a core team member, an occasional collaborator, or just interested in learning more about the mesh, you are welcome!

[1] We are being powered by [[Sudomate]].

--[[User:Tunabananas|Tunabananas]]

=Developer Launch!=
As of last night, we've officially launched version 0.1.0 of the mesh firmware, a.k.a. Snow Crash.

[[File:Snowcrash.png|center|Snow Crash login screen]]

The plan is to have ~20 people with networking skills run nodes from their homes for 1-2 months and report any remaining issues. We'll then fix those bugs and do a wider release of ~60 more nodes.

What's currently working:

1. Sharing limited Internet bandwidth with peoplesopen.net
2. Private access point with no bandwidth limit and mesh access
3. Automatic node meshing with batman-adv
4. Simplified web admin interface that lets node-owners change bandwidth sharing settings and passwords.
5. Automated configuration of new nodes using easy web interface.
6. Automatic printing of stickers with instructions and default generated passwords.

To those of you who have already taken nodes home, here are a few notes:

1. sudo mesh has root access to your nodes since we manage updates per default. If you want to manage your own node and don't want sudo mesh to have access, you can disable our root access by removing /etc/dropbear/authorized_keys on your node.

2. Please report any bugs on our github. If you know which repository the bug pertains to, then go to the issue tracker for that repository. If you aren't sure, then just add the bug here: https://github.com/sudomesh/sudowrt-firmware/issues

A compiled version of the firmware is available here: http://build.sudomesh.org:8080/latest_images/atheros/

Keep in mind that the nodes have to be configured using the node-configurator after being flashed with that firmware and that the firmware only trusts sudomesh SSL certificates. We'll release a less secure version for developers who just want to play around as soon as possible. For now you can configure your nodes at sudo room with the help of one of the core team.

In the following is a list of the repositories directly relevant to this release of the firmware. All of these repositories have been tagged with "sudowrt-0.1.0" so you can get the exact versions used in the release.

*The sudowrt firmware and build scripts (based on openwrt and the work of wlan slovenja): https://github.com/sudomesh/sudowrt-firmware
*The sudowrt packages repository: https://github.com/sudomesh/sudowrt-packages
*The web admin interface: https://github.com/sudomesh/luci-app-peopleswifi
*The mDNS and DNS-SD client: https://github.com/sudomesh/mdnssd-min
*The node database: https://github.com/sudomesh/node-database
*The node configurator: https://github.com/sudomesh/node-configurator
*Sticker printing support for the node configurator: https://github.com/sudomesh/ql570
*The node configurator client: https://github.com/sudomesh/node-configurator-client
*The wlan slovenja tunneldigger (very slightly modified): https://github.com/sudomesh/tunneldigger

Mesh the planet!

--via [[User:Juul|Juul]]

=How to Participate: All Hands on Deck!=
We are always excited to have new volunteers join the team! From designing flyers to developing software, doing research and documenting what you learn, fixing broken hardware to hitting the streets and spreading the word, there's something for everybody who wants to participate.

We meet weekly on Thursday evenings starting at 7:30pm at [https://sudoroom.org Sudo Room], your friendly neighborhood hackerspace. Come on by and jump in!

You can also participate online via [https://lists.sudoroom.org/listinfo/mesh our mailing list], our [http://webchat.freenode.net/?channels=peoplesopen.net chat room], contributing to [https://github.com/sudomesh our code on Github], and adding to this very wiki.

Donations are always appreciated and keep us sustainable. We accept donations [https://gittip.com/sudomesh via Gittip] (anonymous weekly micropayments), through [http://blockchain.info/address/12RxU4DpLpdWcmEBn7Tj325CCXBwt5i9Hc Bitcoin], and in-person at our weekly meetings. Sudo Mesh is currently in the process of acquiring non-profit status, so your donations will be retroactively tax-deductible. If you'd like to donate materials directly, [https://sudoroom.org/wiki/Mesh/Wishlist check here] for a list of hardware we'd love to have.

We also need gung ho folks to climb rooftops and mount nodes!

For press inquiries, please contact [mailto:info@sudomesh.org info (at) sudomesh (dot) org]!

--[[User:Tunabananas|Tunabananas]]

=Deployed our first node!=
[[File:FirstNode.JPG|right|350px|Sudo Mesh's first mesh node!]]
Today we finished installing our first backbone node! It's running [https://github.com/sudomesh Sudo Mesh v0.1 Snow Crash], and will soon be linking up with two neighboring hacker houses. :-)

Here's [[User:Juul|Juul's]] reportback:

<blockquote>Pete and myself installed a Nanostation M5 on a 20 foot aluminum flagpole in West Oakland. The node is about 14 feet above the roof of a two-story building. The total cost of this install ran to about $145 including all materials.

Bill of Materials:

* One Nanostation M5 loco
* One 4 foot wood beam of 3.5" by 3.5"
* Three 5" by 1/4" bolts
* Three 5/8" washers for bolts (optional)
* Three 1/2" washers for bolts (optional)
* Two 5" hose clamps
* 30+ feet of outdoor shielded ethernet cable
* Two shielded/groundable ethernet plugs
* A bunch of zip ties

The optional washers make it easier to tighten and untighten the bolts (otherwise they dig into the wood).

Material sources:

* Nanostation from Amazon
* Flag pole from Harbor Freight
* Everything else from Home Depot
</blockquote>

--[[User:Tunabananas|Tunabananas]] ([[User talk:Tunabananas|talk]]) 21:21, 31 December 2013 (PST)

=hello world!=
it's been [https://lists.sudoroom.org/pipermail/mesh/2013-January/000000.html nearly a year] since we first started meeting - our tiny group. so much learning, so much progress!

we've launched [http://peoplesopen.net the peoplesopen.net]!
&& [http://meshthepla.net meshthepla.net]!

check out our [https://github.com/sudomesh code] - namely forks of openwrt running batman-adv for routing and incorporating wlan-slovenia's tunneldigger for secure vpn connections, as well as an admin interface written in lua.

--[[User:Tunabananas|Tunabananas]] ([[User talk:Tunabananas|talk]]) 06:54, 28 December 2013 (PST)
<endfeed />

File:PeoplesOpen.net-Clef-Installation-3.jpeg

2016-01-19T06:59:32Z

Maxb: PeoplesOpen.net Installation at Clef in Downtown Oakland.

PeoplesOpen.net Installation at Clef in Downtown Oakland.

File:PeoplesOpen.net-Clef-Installation-2.jpeg

2016-01-19T06:59:09Z

Maxb: PeoplesOpen.net Installation at Clef in Downtown Oakland.

PeoplesOpen.net Installation at Clef in Downtown Oakland.

File:PeoplesOpen.net-Clef-Installation-1.jpeg

2016-01-19T06:58:13Z

Maxb: PeoplesOpen.net Installation at Clef in Downtown Oakland.

PeoplesOpen.net Installation at Clef in Downtown Oakland.

Mesh/Home and extender nodes

2016-01-07T21:07:11Z

Maxb: /* Extender nodes */ Supported hardware

There are two types of nodes in the mesh:

[[File:Sudomesh home and extender node illustration extra-simplified.png|thumb|Illustration showing how a sudomesh home node can connect to a window-mounted extender node. The device with two antennas is the home node and the device on the outside of the window is an extender node.]]

[[File:Sudomesh home and extender node illustration.png|thumb|Illustration showing a more complicated setup. Here the node operator has connected their personal computer, a small Raspberry Pi computer and two extender nodes: One on the outside of the window and one on the roof (not shown but a can be seen going up and out of the frame). This is definitely an advanced node operator.]]

[[File:Sudomesh home node ethernet ports.png|thumb|A close-up of the wired network ports on the home node and their use.]]

= Home nodes =

Every node operator has a home node. The home node does everything you need for the mesh. It must be kept indoors since home nodes don't like rain or sun. Each home node has two wifi radios and two antennas so they can talk to other mesh nodes on both the 2.4 and 5 gigaherz frequencies. Home nodes also have one wired network port for connecting to your existing internet connection (if you have one), two wired network ports to connect to any of your computers that don't have wifi and two wired network ports for connecting extender nodes (see next section).

== Supported Hardware ==

At the moment, we are supporting the following routers for home nodes:
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 TP-Link WDR3500]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 TP-Link WDR3600]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 TP-Link WDR4300]
* [https://wiki.openwrt.org/toh/wd/n600 Western Digital MyNet N600]
* [https://wiki.openwrt.org/toh/wd/n750 Western Digital MyNet N750]

== Setup ==
Instructions for flashing and configuring home nodes are at our [[Mesh/WalkThrough|walkthrough page]].

== Info ==

=== Wifi Signals/SSIDs ===
Home nodes broadcast 3 SSIDs (these are the wifi names that you can connect to):
* `peoplesopen.net` - the public network that anyone can connect to and that connects to the rest of the mesh
* `pplsopen.net-node2node` - the "adhoc" network that the node will use to connect to other routers
* (Your private SSID Name) - you can set a private ssid name and a wpa2 password to connect to the node. When you're connected to this network, you won't be connected to the rest of the mesh, and your traffic will not be routed through the mesh exit server. You can connect to this ssid to use the web admin to make basic config changes.

=== Admin Access ===
Administrative tasks can be done with the web ui. You must be connected to the router via the "private" wifi signal/ssid. When connected over the private network, you can visit http://privatenode.sudomesh.org or http://172.30.0.1

In that web ui you can change the amount of bandwidth you'd like to share, the private ssid and wpa passwords, and the admin password.

=== Root Login ===
When the node is originally configured, it is set with a root password. If you want shell access to the device, you can use this password to login as root. It's sort of generally preferable that you use ssh keys, which are stored on the node in `/etc/dropbear/authorized_keys`.
During alpha testing there will be three developer keys stored there so that our dev volunteers can access the devices for maintenance and diagnostics. If you want to remove access, feel free to comment out those lines, but please keep in mind that this limits our effectiveness to troubleshoot and upgrade during this period.

=== Ethernet Ports ===
As of 1/6/2016, home nodes are being configured with 1 WAN (internet port), 2 "peoplesopen.net" ports, and 2 "extender node" ports.

The WAN port will be labeled "internet" and will be a different color than the rest. If you have a home internet connection that you'd like to share, connect this port to your upstream router or cable box from your ISP.

The "peoplesopen.net" ports function as LAN ports on the network. They are assigned a DHCP lease/ip within the peoplesopen.net subnet and can access (and be accessed by) all of the other computers on the mesh. They are functionally equivalent to connecting to the "peoplesopen.net" ssid.

The "extender node" ports are for connecting extender nodes, whose functions are detailed below. The home node will be running a `notdhcpserver` daemon listening on those ports, so if you connect an extender node to them, the two devices **should** automatically negotiate the correct ip address and additional parameters for the extender node.

Unfortunately, the different hardwares have different numbering for the non "internet" ports, so which ports are for extenders and which are "peoplesopen.net lan" ports will not always be the same from device to device. It's fairly easy to test, though. Simply connect a laptop or other computer to one. If it receives a DHCP lease/ip address within the mesh subnet (100.64.0.0/10), then it is a "peoplesopen.net" port. If not, then it is an extender port.

= Extender nodes =

Extender nodes are optional add-ons to your home node. They plug into your home node with a cable and act as a sort of extra antenna that extends the signal of your home node to reach mesh nodes that are further away. Extender nodes come in different shapes and sizes. You can get extender nodes that look like little parabolic dishes and these are suitable for mounting on your roof and making connections to other nodes several miles away! Or you can get ones that are flat and tall that are good for extending the signal out your window and to your close neighbours or maybe to a nearby park. Most extender nodes can be mounted outside and only need one cable that carries both data and power.

To tell you the truth, each extender node isn't really just an antenna: They each have their own computers and wifi radios so they can talk on different wifi channels at the same time as your home node without causing interference.

The extender nodes that we currently support are:
* [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 Ubiquiti Nanostation M5]
* [https://wiki.openwrt.org/toh/ubiquiti/nanostationm2 Ubiquiti Nanostation M2]
* [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 Ubiquiti Picostation M2]
* [https://wiki.openwrt.org/toh/ubiquiti/nanobeam Ubiquiti Nanobeam M2 and M5]
* [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 Ubiquiti Picostation M2]
* [https://wiki.openwrt.org/toh/ubiquiti/picostation2 Ubiquiti Picostation 2]
* [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 Ubiquiti Picostation M2]
* [https://wiki.openwrt.org/toh/ubiquiti/bullet Ubiquiti Bullet M2 and M5]

Mesh/Home and extender nodes

2016-01-07T20:46:17Z

Maxb: /* Info */ Info about home nodes admin and ethernet ports

Mesh/WalkThrough

2016-01-07T20:34:49Z

Maxb: /* Running */ Adding bit about root password

Mesh/WalkThrough

2016-01-07T20:28:21Z

Maxb: /* Setup */

This a walkthrough for flashing a node with the sudomesh firmware and then configuring it with makenode. At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish (OSX should mostly work) OS and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The basic idea of getting a node (router) on the mesh consists of flashing (copying files to [https://en.wikipedia.org/wiki/Flash_memory flash memory]) an operating system to the node and then using a software configurator finish setup .

To build an OpenWRT image from scratch, visit this How To: [[Mesh/Build An OpenWRT Image]]

= Build Environment =

The directions that follow assume you are runing a linux-ish distro (OSX should work). Many of the quoted commands listed below may need `sudo` prepended to them. For the moment, Windows users will have to figure out some of these steps on their own. Sorry :/

=Installing OpenWRT=

==Supported Hardware==
At the moment, we are supporting the following routers for home nodes:
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 TP-Link WDR3500] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 TP-Link WDR3600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 TP-Link WDR4300] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n600 Western Digital MyNet N600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n750 Western Digital MyNet N750] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin firmware image]

==Images==
Sudomesh firmware images can be found here:
[https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/ https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/]

Download the image according to your hardware. For example, if you have a Western Digital MyNet N600, download the image named: openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin, or use the links above

==Flashing==
There are different techniques for flashing each of the routers. Use the links above to the openwrt wiki and follow the instructions there to flash the router with the firmware you've downloaded.

==Confirm Installation==
In order to confirm that the installation has proceeded correctly, use an ethernet cable to connect your computer to the "internet/WAN" port of your router and set your IP address to an address on the 172.22.0.0/24 subnet:
<code>$ ip addr add 172.22.0.9/24 dev IF_NAME</code>
(where IF_NAME is the name of your ethernet interface)
You ''may'' want to stop network-manager (not all distros use this, but Ubuntu does):
<code>$ /etc/init.d/network-manager stop</code>

You can also assign yourself the address via a network manager, both in linux and OSX.

<code>$ ssh root@172.22.0.1</code>

The default password will be: `meshtheplanet`

You ''may'' need to restart the router, but be careful not to restart it while it's in the process of flashing.

=Configuring=
These are the steps for configuring your newly flashed router. It will retrieve hardware information about the node, prompt you for a few config settings, and then query the meshnode database to get an available IP address and subnet.

==Prerequisites==
You'll need:
* A newish version of nodejs and npm. Follow the recommended instructions at [https://docs.npmjs.com/getting-started/installing-node npmjs.com].
* Git. In Debian based distros you can do: <code>$ apt-get install git</code>. For OSX you can probably use homebrew or your preferred package manager.

==Setup==
Download [https://github.com/sudomesh/makenode makenode]. The easiest way to do this will likely be with git:
<code>$ git clone https://github.com/sudomesh/makenode.git</code>

Then you need to install nodejs/npm packages:
* <code>$ cd makenode</code>
* <code>$ npm install</code>
* <code>$ cp settings.js.example settings.js</code>

The default settings in `settings.js` should suffice in most cases, but if you need to make changes, do them there.

If you'd like to add your ssh key to the router, add it to the `configs/authorized_keys` file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.

==Running==
You should now be able to run makenode:
<code>$ ./makenode.js</code>

Makenode will detect the hardware on the router and ask you to input some data about the node. Some notes:
* Set the "txpower" to 20. This should be set in the code, but hasn't been just yet.
* The password for the private ssid should be at least 8 characters or you will not be able to connect
* For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* The max downstream and upstream bandwidth are the maximum amount of bandwidth you want to share on the "peoplesopen.net" network. They are measured in kbps (kilobits per second), so if you'd like to share 10mbps (megabits per second), enter 10000. You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.

==What now?==

If configuration proceeded correctly, you should see the 'peoplesopen.net' and 'pplsopen.net-node2node' wifi interfaces when running `sudo iwlist wlan0 scan` or when looking at available wifi networks.

It's recommended that you read the [[Home and extender nodes#Home_nodes|Home node info]] to find out more about the way that your new mesh node works.

Mesh/WalkThrough

2016-01-07T20:19:40Z

Maxb: Adding link to home node info in mesh walkthrough

This a walkthrough for flashing a node with the sudomesh firmware and then configuring it with makenode. At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish (OSX should mostly work) OS and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The basic idea of getting a node (router) on the mesh consists of flashing (copying files to [https://en.wikipedia.org/wiki/Flash_memory flash memory]) an operating system to the node and then using a software configurator finish setup .

To build an OpenWRT image from scratch, visit this How To: [[Mesh/Build An OpenWRT Image]]

= Build Environment =

The directions that follow assume you are runing a linux-ish distro (OSX should work). Many of the quoted commands listed below may need `sudo` prepended to them. For the moment, Windows users will have to figure out some of these steps on their own. Sorry :/

=Installing OpenWRT=

==Supported Hardware==
At the moment, we are supporting the following routers for home nodes:
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 TP-Link WDR3500] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 TP-Link WDR3600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 TP-Link WDR4300] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n600 Western Digital MyNet N600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n750 Western Digital MyNet N750] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin firmware image]

==Images==
Sudomesh firmware images can be found here:
[https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/ https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/]

Download the image according to your hardware. For example, if you have a Western Digital MyNet N600, download the image named: openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin, or use the links above

==Flashing==
There are different techniques for flashing each of the routers. Use the links above to the openwrt wiki and follow the instructions there to flash the router with the firmware you've downloaded.

==Confirm Installation==
In order to confirm that the installation has proceeded correctly, use an ethernet cable to connect your computer to the "internet/WAN" port of your router and set your IP address to an address on the 172.22.0.0/24 subnet:
<code>$ ip addr add 172.22.0.9/24 dev IF_NAME</code>
(where IF_NAME is the name of your ethernet interface)
You ''may'' want to stop network-manager (not all distros use this, but Ubuntu does):
<code>$ /etc/init.d/network-manager stop</code>

You can also assign yourself the address via a network manager, both in linux and OSX.

<code>$ ssh root@172.22.0.1</code>

The default password will be: `meshtheplanet`

You ''may'' need to restart the router, but be careful not to restart it while it's in the process of flashing.

=Configuring=
These are the steps for configuring your newly flashed router. It will retrieve hardware information about the node, prompt you for a few config settings, and then query the meshnode database to get an available IP address and subnet.

==Prerequisites==
You'll need:
* A newish version of nodejs and npm. Follow the recommended instructions at [https://docs.npmjs.com/getting-started/installing-node npmjs.com].
* Git. In Debian based distros you can do: <code>$ apt-get install git</code>. For OSX you can probably use homebrew or your preferred package manager.

==Setup==
Download [https://github.com/sudomesh/makenode makenode]. The easiest way to do this will likely be with git:
<code>$ git clone https://github.com/sudomesh/makenode.git</code>

Then you need to install nodejs/npm packages:
<code>$ cd makenode</code>
<code>$ npm install</code>
<code>$ cp settings.js.example settings.js</code>

The default settings in `settings.js` should suffice in most cases, but if you need to make changes, do them there.

If you'd like to add your ssh key to the router, add it to the `configs/authorized_keys` file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.

==Running==
You should now be able to run makenode:
<code>$ ./makenode.js</code>

Makenode will detect the hardware on the router and ask you to input some data about the node. Some notes:
* Set the "txpower" to 20. This should be set in the code, but hasn't been just yet.
* The password for the private ssid should be at least 8 characters or you will not be able to connect
* For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* The max downstream and upstream bandwidth are the maximum amount of bandwidth you want to share on the "peoplesopen.net" network. They are measured in kbps (kilobits per second), so if you'd like to share 10mbps (megabits per second), enter 10000. You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.

==What now?==

If configuration proceeded correctly, you should see the 'peoplesopen.net' and 'pplsopen.net-node2node' wifi interfaces when running `sudo iwlist wlan0 scan` or when looking at available wifi networks.

It's recommended that you read the [[Home and extender nodes#Home_nodes|Home node info]] to find out more about the way that your new mesh node works.

Mesh/Home and extender nodes

2016-01-07T20:16:41Z

Maxb: /* Supported Hardware */

Mesh/WalkThrough

2016-01-06T06:00:05Z

Maxb:

This a walkthrough for flashing a node with the sudomesh firmware and then configuring it with makenode. At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish (OSX should mostly work) OS and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The basic idea of getting a node (router) on the mesh consists of flashing (copying files to [https://en.wikipedia.org/wiki/Flash_memory flash memory]) an operating system to the node and then using a software configurator finish setup .

To build an OpenWRT image from scratch, visit this How To: [[Mesh/Build An OpenWRT Image]]

= Build Environment =

The directions that follow assume you are runing a linux-ish distro (OSX should work). Many of the quoted commands listed below may need `sudo` prepended to them. For the moment, Windows users will have to figure out some of these steps on their own. Sorry :/

=Installing OpenWRT=

==Supported Hardware==
At the moment, we are supporting the following routers for home nodes:
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 TP-Link WDR3500] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 TP-Link WDR3600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 TP-Link WDR4300] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n600 Western Digital MyNet N600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n750 Western Digital MyNet N750] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin firmware image]

==Images==
Sudomesh firmware images can be found here:
[https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/ https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/]

Download the image according to your hardware. For example, if you have a Western Digital MyNet N600, download the image named: openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin, or use the links above

==Flashing==
There are different techniques for flashing each of the routers. Use the links above to the openwrt wiki and follow the instructions there to flash the router with the firmware you've downloaded.

==Confirm Installation==
In order to confirm that the installation has proceeded correctly, use an ethernet cable to connect your computer to the "internet/WAN" port of your router and set your IP address to an address on the 172.22.0.0/24 subnet:

<code>$ ip addr add 172.22.0.9/24 dev IF_NAME</code>
(where IF_NAME is the name of your ethernet interface)

You ''may'' want to stop network-manager (not all distros use this, but Ubuntu does):

<code>$ /etc/init.d/network-manager stop</code>

You can also assign yourself the address via a network manager, both in linux and OSX.

<code>$ ssh root@172.22.0.1</code>

The default password will be: `meshtheplanet`

You ''may'' need to restart the router, but be careful not to restart it while it's in the process of flashing.

=Configuring=
These are the steps for configuring your newly flashed router. It will retrieve hardware information about the node, prompt you for a few config settings, and then query the meshnode database to get an available IP address and subnet.

==Prerequisites==
You'll need:
* A newish version of nodejs and npm. Follow the recommended instructions at [https://docs.npmjs.com/getting-started/installing-node npmjs.com].
* Git. In Debian based distros you can do: <code>$ apt-get install git</code>. For OSX you can probably use homebrew or your preferred package manager.

==Setup==
Download [https://github.com/sudomesh/makenode makenode]. The easiest way to do this will likely be with git:
<code>$ git clone https://github.com/sudomesh/makenode.git</code>

Then you need to install nodejs/npm packages:

<code>$ cd makenode</code>

<code>$ npm install</code>

<code>$ cp settings.js.example settings.js</code>

The default settings in `settings.js` should suffice in most cases, but if you need to make changes, do them there.

If you'd like to add your ssh key to the router, add it to the `configs/authorized_keys` file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.

==Running==
You should now be able to run makenode:
<code>$ ./makenode.js</code>

Makenode will detect the hardware on the router and ask you to input some data about the node. Some notes:
* Set the "txpower" to 20. This should be set in the code, but hasn't been just yet.
* The password for the private ssid should be at least 8 characters or you will not be able to connect
* For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* The max downstream and upstream bandwidth are the maximum amount of bandwidth you want to share on the "peoplesopen.net" network. They are measured in kbps (kilobits per second), so if you'd like to share 10mbps (megabits per second), enter 10000. You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.

==Step Five: Testing ==

You should see the 'peoplesopen.net' and 'pplsopen.net-node2node' wifi interfaces when running `sudo iwlist wlan0 scan` or when looking at available wifi networks.

Mesh/WalkThrough

2016-01-06T05:53:52Z

Maxb: /* Installing OpenWRT */

This a walkthrough for flashing a node with the sudomesh firmware and then configuring it with makenode. At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish (OSX should mostly work) OS and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The basic idea of getting a node (router) on the mesh consists of flashing (copying files to [https://en.wikipedia.org/wiki/Flash_memory flash memory]) an operating system to the node and then using a software configurator finish setup .

To build an OpenWRT image from scratch, visit this How To: [[Mesh/Build An OpenWRT Image]]

= Build Environment =

The directions that follow assume you are runing a linux-ish distro (OSX should work). Many of the quoted commands listed below may need `sudo` prepended to them. For the moment, Windows users will have to figure out some of these steps on their own. Sorry :/

=Installing OpenWRT=

==Supported Hardware==
At the moment, we are supporting the following routers for home nodes:
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 TP-Link WDR3500] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 TP-Link WDR3600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 TP-Link WDR4300] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n600 Western Digital MyNet N600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n750 Western Digital MyNet N750] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin firmware image]

==Images==
Sudomesh firmware images can be found here:
[https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/ https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/]

Download the image according to your hardware. For example, if you have a Western Digital MyNet N600, download the image named: openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin, or use the links above

==Flashing==
There are different techniques for flashing each of the routers. Use the links above to the openwrt wiki and follow the instructions there to flash the router with the firmware you've downloaded.

==Confirm Installation==
In order to confirm that the installation has proceeded correctly, use an ethernet cable to connect your computer to the "internet/WAN" port of your router and set your IP address to an address on the 172.22.0.0/24 subnet:

<code>$ ip addr add 172.22.0.9/24 dev IF_NAME</code>
(where IF_NAME is the name of your ethernet interface)

You ''may'' want to stop network-manager (not all distros use this, but Ubuntu does):

<code>$ /etc/init.d/network-manager stop</code>

You can also assign yourself the address via a network manager, both in linux and OSX.

<code>$ ssh root@172.22.0.1</code>

The default password will be: `meshtheplanet`

You ''may'' need to restart the router, but be careful not to restart it while it's in the process of flashing.

=Configuring=
These are the steps for configuring your newly flashed router. It will retrieve hardware information about the node, prompt you for a few config settings, and then query the meshnode database to get an available IP address and subnet.

==Prerequisites==
You'll need:
* A newish version of nodejs and npm. Follow the recommended instructions at [https://docs.npmjs.com/getting-started/installing-node npmjs.com].
* Git. In Debian based distros you can do: <code>$ apt-get install git</code>. For OSX you can probably use homebrew or your preferred package manager.

==Setup==
Download [https://github.com/sudomesh/makenode makenode]. The easiest way to do this will likely be with git:
<code>$ git clone https://github.com/sudomesh/makenode.git</code>

Then you need to install nodejs/npm packages:
<code>$ cd makenode</code>
<code>$ npm install</code>
<code>$ cp settings.js.example settings.js</code>

The default settings in `settings.js` should suffice in most cases, but if you need to make changes, do them there.

If you'd like to add your ssh key to the router, add it to the `configs/authorized_keys` file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.

==Running==
You should now be able to run makenode:
<code>$ ./makenode.js</code>

Makenode will detect the hardware on the router and ask you to input some data about the node. Some notes:
* Set the "txpower" to 20. This should be set in the code, but hasn't been just yet.
* The password for the private ssid should be at least 8 characters or you will not be able to connect
* For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* The max downstream and upstream bandwidth are the maximum amount of bandwidth you want to share on the "peoplesopen.net" network. They are measured in kbps (kilobits per second), so if you'd like to share 10mbps (megabits per second), enter 10000. You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.

==Step Five: Testing ==

You should see the 'peoplesopen.net' and 'pplsopen.net-node2node' wifi interfaces when running `sudo iwlist wlan0 scan` or when looking at available wifi networks.

Mesh/WalkThrough

2016-01-06T05:53:01Z

Maxb: /* Installing OpenWRT */

This a walkthrough for flashing a node with the sudomesh firmware and then configuring it with makenode. At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish (OSX should mostly work) OS and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The basic idea of getting a node (router) on the mesh consists of flashing (copying files to [https://en.wikipedia.org/wiki/Flash_memory flash memory]) an operating system to the node and then using a software configurator finish setup .

To build an OpenWRT image from scratch, visit this How To: [[Mesh/Build An OpenWRT Image]]

= Build Environment =

The directions that follow assume you are runing a linux-ish distro (OSX should work). Many of the quoted commands listed below may need `sudo` prepended to them. For the moment, Windows users will have to figure out some of these steps on their own. Sorry :/

=Installing OpenWRT=

==Supported Hardware==
At the moment, we are supporting the following routers for home nodes:
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 TP-Link WDR3500] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 TP-Link WDR3600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 TP-Link WDR4300] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n600 Western Digital MyNet N600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n750 Western Digital MyNet N750] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin firmware image]

==Images==
Sudomesh firmware images can be found here:
[https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/ https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/]

Download the image according to your hardware. For example, if you have a Western Digital MyNet N600, download the image named: openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin, or use the links above

==Flashing==
There are different techniques for flashing each of the routers. Use the links above to the openwrt wiki and follow the instructions there to flash the router with the firmware you've downloaded.

==Confirm Installation==
In order to confirm that the installation has proceeded correctly, use an ethernet cable to connect your computer to the "internet/WAN" port of your router and set your IP address to an address on the 172.22.0.0/24 subnet:
<code>$ ip addr add 172.22.0.9/24 dev IF_NAME</code>
(where IF_NAME is the name of your ethernet interface)

You ''may'' want to stop network-manager (not all distros use this, but Ubuntu does):

<code>$ /etc/init.d/network-manager stop</code>

You can also assign yourself the address via a network manager, both in linux and OSX.

<code>$ ssh root@172.22.0.1</code>

The default password will be: `meshtheplanet`

You ''may'' need to restart the router, but be careful not to restart it while it's in the process of flashing.

=Configuring=
These are the steps for configuring your newly flashed router. It will retrieve hardware information about the node, prompt you for a few config settings, and then query the meshnode database to get an available IP address and subnet.

==Prerequisites==
You'll need:
* A newish version of nodejs and npm. Follow the recommended instructions at [https://docs.npmjs.com/getting-started/installing-node npmjs.com].
* Git. In Debian based distros you can do: <code>$ apt-get install git</code>. For OSX you can probably use homebrew or your preferred package manager.

==Setup==
Download [https://github.com/sudomesh/makenode makenode]. The easiest way to do this will likely be with git:
<code>$ git clone https://github.com/sudomesh/makenode.git</code>

Then you need to install nodejs/npm packages:
<code>$ cd makenode</code>
<code>$ npm install</code>
<code>$ cp settings.js.example settings.js</code>

The default settings in `settings.js` should suffice in most cases, but if you need to make changes, do them there.

If you'd like to add your ssh key to the router, add it to the `configs/authorized_keys` file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.

==Running==
You should now be able to run makenode:
<code>$ ./makenode.js</code>

Makenode will detect the hardware on the router and ask you to input some data about the node. Some notes:
* Set the "txpower" to 20. This should be set in the code, but hasn't been just yet.
* The password for the private ssid should be at least 8 characters or you will not be able to connect
* For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* The max downstream and upstream bandwidth are the maximum amount of bandwidth you want to share on the "peoplesopen.net" network. They are measured in kbps (kilobits per second), so if you'd like to share 10mbps (megabits per second), enter 10000. You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.

==Step Five: Testing ==

You should see the 'peoplesopen.net' and 'pplsopen.net-node2node' wifi interfaces when running `sudo iwlist wlan0 scan` or when looking at available wifi networks.

Mesh/Home and extender nodes

2016-01-06T01:30:40Z

Maxb: /* Home nodes */ Adding info about broadcasted ssids

Mesh/Home and extender nodes

2016-01-06T01:25:08Z

Maxb: /* Setup */ fixing walkthrough page link.

Mesh/Home and extender nodes

2016-01-06T01:23:46Z

Maxb: /* Home nodes */ Adding supported hardware info and link to walkthrough

Template:Mesh nav

2016-01-06T01:21:29Z

Maxb:

{|style="border-style: solid; border-width: 10px; border-color: #20b24b; background-color: #ffffcc; width: 70%; text-align: center;"
|+ '''''Quick Links''' (see below for more details)''
|-
!Documentation
!Technical
!Outreach
!Operations
!Help
!External Links
|-
|[[Mesh/Blog|Blog]]
|[[Mesh/Home_and_extender_nodes|Home and Extender Nodes]]
|[[Mesh/Website|Website]]
|[[Mesh/Minutes|Minutes]]
|[[Mesh/FAQ|FAQ]]
|[http://peoplesopen.net peoplesopen.net]
|-
|[[Mesh/Oakland|Oakland]]
|[[Mesh/WalkThrough|Walkthrough]]
|[[Mesh/Meetings|Meetings]]
|[[Mesh/Legal|Legal]]
|[[Mesh/How_to_help|How to Help]]
|[http://meshmap.sudoroom.org sudo mesh map]
|-
|[[Mesh/Interviews with other meshers|Interviews]]
|[[Mesh/Firmware|Firmware]]
|[[Mesh/Stickers|Stickers]]
|[[Mesh/Hosting|Hosting]]
|[[Mesh/ToDos|To-Do's]]
|[https://github.com/sudomesh code on github]
|-
|[[Mesh/Other mesh projects|Other meshes]]
|[[Mesh/MeshApps|MeshApps]]
|[[Mesh/Presentations|Presentations]]
|[[Mesh/Backup|Backup]]
|[[Mesh/Wishlist|Wishlist]]
|[http://meshthepla.net meshthepla.net!]
|-
|[[Mesh/Documentation|Documentation]]
|[[Mesh/Network topology|Network topology]]
|[[Mesh/Swag|Swag]]
|[[Mesh/Server security|Server security]]
|
|
|-
|
|[[Mesh/Specs|Specs]]
|[[Ascii Art]]
|[[Mesh/Naming|Naming]]
|
|
|-
|
|[[Mesh/Frequencies|Frequencies]]
|[[Mesh/Communities|Communities]]
|[[Mesh/Marketing|Marketing]]
|
|
|-
|
|[[Mesh/Software tools|Software tools]]
|[[Mesh/Press|Press]]
|[[Mesh/Purchases|Purchases]]
|
|
|-
|
||[[Mesh/Terms|Terms]]
|[[Mesh/Design|Design]]
|[[Mesh/Inventory|Inventory]]
|
|
|-
|
|[[Mesh/Power|Power]]
|
|[[Mesh/Donations|Donations]]
|
|
|-
|
||[[Mesh/Monitoring|Monitoring]]
|
|[[Mesh/Decisions|Decisions]]
|
|
|-
|
||[[Mesh/Freifunk|Freifunk]]
|
|[[Mesh/Challenges|Challenges]]
|
|
|-
|
||[[Mesh/Commotion|Commotion]]
|
|[[Mesh/Checkouts|Checkouts]]
|
|
|-
|
|[[Mesh/Diagrams|Diagrams]]
|
|[[Mesh/Funding|Funding]]
|
|}

Template:Mesh nav

2016-01-06T01:20:24Z

Maxb:

{|style="border-style: solid; border-width: 10px; border-color: #20b24b; background-color: #ffffcc; width: 70%; text-align: center;"
|+ '''''Quick Links''' (see below for more details)''
|-
!Documentation
!Technical
!Outreach
!Operations
!Help
!External Links
|-
|[[Mesh/Blog|Blog]]
|[[Mesh/Tracking|Tracking]]
|[[Mesh/Website|Website]]
|[[Mesh/Minutes|Minutes]]
|[[Mesh/FAQ|FAQ]]
|[http://peoplesopen.net peoplesopen.net]
|-
|[[Mesh/Oakland|Oakland]]
|[[Mesh/WalkThrough|Walkthrough]]
|[[Mesh/Meetings|Meetings]]
|[[Mesh/Legal|Legal]]
|[[Mesh/How_to_help|How to Help]]
|[http://meshmap.sudoroom.org sudo mesh map]
|-
|[[Mesh/Interviews with other meshers|Interviews]]
|[[Mesh/Firmware|Firmware]]
|[[Mesh/Home_and_extender_nodes|Home and Extender Nodes]]
|[[Mesh/Stickers|Stickers]]
|[[Mesh/Hosting|Hosting]]
|[[Mesh/ToDos|To-Do's]]
|[https://github.com/sudomesh code on github]
|-
|[[Mesh/Other mesh projects|Other meshes]]
|[[Mesh/MeshApps|MeshApps]]
|[[Mesh/Presentations|Presentations]]
|[[Mesh/Backup|Backup]]
|[[Mesh/Wishlist|Wishlist]]
|[http://meshthepla.net meshthepla.net!]
|-
|[[Mesh/Documentation|Documentation]]
|[[Mesh/Network topology|Network topology]]
|[[Mesh/Swag|Swag]]
|[[Mesh/Server security|Server security]]
|
|
|-
|
|[[Mesh/Specs|Specs]]
|[[Ascii Art]]
|[[Mesh/Naming|Naming]]
|
|
|-
|
|[[Mesh/Frequencies|Frequencies]]
|[[Mesh/Communities|Communities]]
|[[Mesh/Marketing|Marketing]]
|
|
|-
|
|[[Mesh/Software tools|Software tools]]
|[[Mesh/Press|Press]]
|[[Mesh/Purchases|Purchases]]
|
|
|-
|
||[[Mesh/Terms|Terms]]
|[[Mesh/Design|Design]]
|[[Mesh/Inventory|Inventory]]
|
|
|-
|
|[[Mesh/Power|Power]]
|
|[[Mesh/Donations|Donations]]
|
|
|-
|
||[[Mesh/Monitoring|Monitoring]]
|
|[[Mesh/Decisions|Decisions]]
|
|
|-
|
||[[Mesh/Freifunk|Freifunk]]
|
|[[Mesh/Challenges|Challenges]]
|
|
|-
|
||[[Mesh/Commotion|Commotion]]
|
|[[Mesh/Checkouts|Checkouts]]
|
|
|-
|
|[[Mesh/Diagrams|Diagrams]]
|
|[[Mesh/Funding|Funding]]
|
|}

Mesh/WalkThrough

2016-01-06T01:15:55Z

Maxb: Mesh Walkthrough - Updating to reflect all the new changes

This a walkthrough for flashing a node with the sudomesh firmware and then configuring it with makenode. At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish (OSX should mostly work) OS and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The basic idea of getting a node (router) on the mesh consists of flashing (copying files to [https://en.wikipedia.org/wiki/Flash_memory flash memory]) an operating system to the node and then using a software configurator finish setup .

To build an OpenWRT image from scratch, visit this How To: [[Mesh/Build An OpenWRT Image]]

= Build Environment =

The directions that follow assume you are runing a linux-ish distro (OSX should work). Many of the quoted commands listed below may need `sudo` prepended to them. For the moment, Windows users will have to figure out some of these steps on their own. Sorry :/

=Installing OpenWRT=

==Supported Hardware==
At the moment, we are supporting the following routers for home nodes:
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 TP-Link WDR3500] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 TP-Link WDR3600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 TP-Link WDR4300] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n600 Western Digital MyNet N600] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/wd/n750 Western Digital MyNet N750] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin firmware image]

==Images==
Sudomesh firmware images can be found here:
[https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/ https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/]

Download the image according to your hardware. For example, if you have a Western Digital MyNet N600, download the image named: openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin, or use the links above

==Flashing==
There are different techniques for flashing each of the routers. Use the links above to the openwrt wiki and follow the instructions there to flash the router with the firmware you've downloaded.

==Confirm Installation==
In order to confirm that the installation has proceeded correctly, use an ethernet cable to connect your computer to the "internet/WAN" port of your router and set your IP address to an address on the 172.22.0.0/24 subnet:
<code>$ ip addr add 172.22.0.9/24 dev IF_NAME</code>
(where IF_NAME is the name of your ethernet interface)
You ''may'' want to stop network-manager (not all distros use this, but Ubuntu does):
<code>$ /etc/init.d/network-manager stop</code>

You can also assign yourself the address via a network manager, both in linux and OSX.

<code>$ ssh root@172.22.0.1</code>

The default password will be: `meshtheplanet`

You ''may'' need to restart the router, but be careful not to restart it while it's in the process of flashing.

=Configuring=
These are the steps for configuring your newly flashed router. It will retrieve hardware information about the node, prompt you for a few config settings, and then query the meshnode database to get an available IP address and subnet.

==Prerequisites==
You'll need:
* A newish version of nodejs and npm. Follow the recommended instructions at [https://docs.npmjs.com/getting-started/installing-node npmjs.com].
* Git. In Debian based distros you can do: <code>$ apt-get install git</code>. For OSX you can probably use homebrew or your preferred package manager.

==Setup==
Download [https://github.com/sudomesh/makenode makenode]. The easiest way to do this will likely be with git:
<code>$ git clone https://github.com/sudomesh/makenode.git</code>

Then you need to install nodejs/npm packages:
<code>$ cd makenode</code>
<code>$ npm install</code>
<code>$ cp settings.js.example settings.js</code>

The default settings in `settings.js` should suffice in most cases, but if you need to make changes, do them there.

If you'd like to add your ssh key to the router, add it to the `configs/authorized_keys` file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.

==Running==
You should now be able to run makenode:
<code>$ ./makenode.js</code>

Makenode will detect the hardware on the router and ask you to input some data about the node. Some notes:
* Set the "txpower" to 20. This should be set in the code, but hasn't been just yet.
* The password for the private ssid should be at least 8 characters or you will not be able to connect
* For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* The max downstream and upstream bandwidth are the maximum amount of bandwidth you want to share on the "peoplesopen.net" network. They are measured in kbps (kilobits per second), so if you'd like to share 10mbps (megabits per second), enter 10000. You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.

==Step Five: Testing ==

You should see the 'peoplesopen.net' and 'pplsopen.net-node2node' wifi interfaces when running `sudo iwlist wlan0 scan` or when looking at available wifi networks.

Mesh/Monitoring

2015-12-30T20:36:09Z

Maxb: /* The Basics */

See Also: [[Mesh#Technical_Documentation | Technical Documentation]], [[Mesh/Bandwidth Quotas | Bandwidth Quotas]]

[[Category:Monitoring]]
[[Category:Technical]]

This is all currently out of date. The currently implemented monitor server is running on VPS, which is tunneled into the network.
It's running [https://monitor.sudomesh.org/cacti/graph_view.php?action=tree&tree_id=1&leaf_id=45 Cacti] and [https://monitor.sudomesh.org/smokeping/smokeping.cgi?target=Mesh Smokeping] as well as gathering logs.

When I have the time, I'll update the details here, but I've documented the setup as provisioning code here: https://github.com/max-b/mesh-playbooks - [[User:Maxb]]

== The Basics ==
See Also: [[Mesh/Icinga 2]]

=== The Hardware ===
Small frame Dell PC, service tag: 2FDSGC1, green tape with info on the front.

=== The Software ===
* OS: Linux monitor 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux

=== Use It ===

ssh to:
* monitor or monitor.local - (as of 10.30.2014, not accessible by this host name, perhaps dns is not correctly defined)
* 192.168.50.15
* login: sudoroom:sudomesh

Icinga web UI:
* http://192.168.50.15/icinga2-classicui (login: icingaadmin:mojave)

Charting:
* Graphite - http://192.168.50.15/
* Grafana - http://192.168.50.15/grafana
* Mesh Charts - http://192.168.50.15/grafana/#/dashboard/db/sudomesh (works best in firefox)

Github repo:
* https://github.com/TinajaLabs/sudomesh_icinga

== List of hosts ==
Run nmap (09.18.2014) to see a list of hosts which we might want to monitor...

Most of these are probably laptops connected to the internet.
nmap -sn 192.168.50.0/24

* 192.168.50.15 - monitoring server
*

== Icinga ==
Interesting article: [http://www.smallbusinesstech.net/more-complicated-instructions/nagios/setting-up-nagios-on-a-debian-server-to-remotely-monitor-an-openwrt-router Setting up Icinga on a Debian Server to Remotely Monitor an OpenWrt Router]

Icinga is a Nagios fork which, as of Fall 2013, has more development involvement. Icinga is the central system that pings other systems like openWRT. Icinga gathers the data and can track and send notifications when values drift beyond normal tolerances. On the remote hosts it is required to install '''nrpe''' and a basic set of '''nrpe plugins'''. The article referenced above shows how it is possible to install nrpe on openwrt through the openwrt web interface. After that one can ssh into the router and configure it.

Once the router is configured it is necessary to configure the central Icinga server with:
* the IP address of each node it will track
* the host groups
* the services that are to be monitored.

== Icinga 2 ==
Icinga 2 is a rewrite of Icinga with a cleaner implementation and configuration structure. It will be able to run SNMP calls to nodes which run mini-snmpd and be able to send performance data to charting apps like graphite.

See Install notes at: [[Icinga 2]]

== Access to remote hosts ==
Icinga can use various methods to monitor remote hosts, NRPE, SNMP, etc.

=== IMCP ===
The ping service; for determining if the host is reachable

=== SNMP ===
We will probably start off with simple SNMP monitoring. It return very basic info but it does not require too much setup on the remote hosts.

=== OpenWRT Package: nrpe ===
NRPE requires a daemon running on the remote host and a number of mostly bash scripts for specialized info. Bash scripts can be developed to read disk stats, memory usage, etc. There are about 30 scripts which come with NRPE.
<pre>
Package: nrpe
Version: 2.12-4
Depends: libc, librt, libpthread, libopenssl, libwrap
Source: feeds/packages/admin/nrpe
SourceFile: nrpe-2.12.tar.gz
SourceURL: @SF/nagios
Section: admin
Architecture: ib42x0
Installed-Size: 19018
Filename: nrpe_2.12-4_ib42x0.ipk
Size: 19801
MD5Sum: f36019344c747a1e88f5aab50776bd4e
Description: The NRPE addon is designed to allow you to execute Nagios plugins on
remote Linux/Unix machines. The main reason for doing this is to allow
Nagios to monitor "local" resources (like CPU load, memory usage, etc.)
on remote machines. Since these public resources are not usually
exposed to external machines, an agent like NRPE must be installed on
the remote Linux/Unix machines.
</pre>

== Alternative tools ==

=== RRD ===
* http://oss.oetiker.ch/rrdtool/
* also look at whisper, a light weight rrd - http://graphite.wikidot.com/whisper
*

=== collectd ===
* http://collectd.org/

=== Sensu - Deprecated ===
See our notes about the Sensu install: [[Mesh/Sensu_Page | Sensu Page]]

'''Requires a client application service and not useful for our needs for monitoring mesh nodes...'''

* The sensu web page can be accessed internally at:
** http://192.168.42.65:8080/# (as of 2014.07.25 no services defined)
** user: admin
** pw: secret

==== About Sensu - From Sensu site ====

Sensu is often described as the "monitoring router". Essentially, Sensu takes the results of "check" scripts run across many systems, and if certain conditions are met; passes their information to one or more "handlers". Checks are used, for example, to determine if a service like Apache is up or down. Checks can also be used to collect data, such as MySQL query statistics or Rails application metrics. Handlers take actions, using result information, such as sending an email, messaging a chat room, or adding a data point to a graph. There are several types of handlers, but the most common and most powerful is "pipe", a script that receives data via standard input. Check and handler scripts can be written in any language, and the community repository continues to grow!

Fun Sensu facts:

* Written in Ruby, using EventMachine.
* Has great test coverage with continuous integration via Travis CI.
* Can use existing Nagios plugins.
* Configuration is all in JSON.
* Has a message-oriented architecture, using RabbitMQ and JSON payloads.
* Packages are "omnibus", for consistency, isolation, and low-friction deployment.
* Sensu is designed for modern infrastructures and to be driven by configuration management tools, designed for the "cloud".

== Charting ==

=== Graphite ===
* http://www.slideshare.net/reyjrar/graphite-overview
* http://graphite.wikidot.com/whisper
* http://graphite.wikidot.com/
* http://graphite.readthedocs.org/en/latest/config-local-settings.html
* graphite admin: http://192.168.50.15/admin - sudomesh:sudomesh

* 09.18.2014, ChrisJ started installing this on the monitor server. Not finished...
* 10.02.2014 - another night... continuing.

* installed on host: monitor:/opt/graphite/

* install tutorial: https://tipstricks.itmatrix.eu/installing-icinga2-in-debian-wheezy/

==== Sample live charts rendered from Graphite ====
http://192.168.50.15/render?width=400&from=-2hours&until=now&height=250&target=icinga.localhost.ping4.rta&_uniq=0.43809576937928796&title=icinga.localhost.ping4.rta&.png
 Round trip average ping over the last 2 hours:

=== Grafana ===
http://grafana.org/

* a cool dashboard that you can install under apache (maybe ngnx) and crete a dashboard of data streamed from graphite
* limited to line charts, no meters, gauges, etc.

Installed in: /opt/grafana

As of 10.30.2014 - net yet working... has an issue connecting to Elasticsearch to save settings in grafana.
https://github.com/grafana/grafana/issues/330

==== Setup ====
http://192.168.50.15/grafana

http://192.168.50.15/grafana/#/dashboard/db/sudomesh - works best in firefox...

==== Elasticsearch ====
* requires elasticsearch - https://xenforo.com/community/threads/how-to-basic-elasticsearch-installation-debian-ubuntu.26163/

http://192.168.50.15:9200 - returns something like this:
<pre>
{
"status" : 200,
"name" : "Exterminator",
"version" : {
"number" : "1.0.3",
"build_hash" : "61bfb72d845a59a58cd9910e47515665f6478a5c",
"build_timestamp" : "2014-04-16T14:43:11Z",
"build_snapshot" : false,
"lucene_version" : "4.6"
},
"tagline" : "You Know, for Search"
}
</pre>

=== Graphene ===
* https://github.com/jondot/graphene
* http://jondot.github.io/graphene - demo

=== Cricket ===
* http://cricket.sourceforge.net/
*

== motd ==
We can set a boot message for the /etc/motd file.

These samples from http://patorjk.com/software/taag/#p=testall&h=0&v=0&f=Mer&t=SudoMesh

<pre>

____ __ __ ___ __
/ __/ __ __ ___/ / ___ / |/ / ___ ___ / /
_\ \ / // // _ / / _ \ / /|_/ / / -_) (_-< / _ \
/___/ \_,_/ \_,_/ \___//_/ /_/ \__/ /___//_//_/
______________________________________________________
SudoMesh Monitoring Server - Fall, 2014

_______ __ _______ __
| __|.--.--..--| |.-----.| | |.-----..-----.| |--.
|__ || | || _ || _ || || -__||__ --|| |
|_______||_____||_____||_____||__|_|__||_____||_____||__|__|
SudoMesh Monitoring Server - Fall, 2014

____ __ __
/\ _`\ /\ \ /'\_/`\ /\ \
\ \,\L\_\ __ __ \_\ \ ___ /\ \ __ ____ \ \ \___
\/_\__ \ /\ \/\ \ /'_` \ / __`\ \ \ \__\ \ /'__`\ /',__\ \ \ _ `\
/\ \L\ \ \ \ \_\ \/\ \L\ \ /\ \L\ \ \ \ \_/\ \ /\ __/ /\__, `\ \ \ \ \ \
\ `\____\ \ \____/\ \___,_\\ \____/ \ \_\\ \_\\ \____\\/\____/ \ \_\ \_\
\/_____/ \/___/ \/__,_ / \/___/ \/_/ \/_/ \/____/ \/___/ \/_/\/_/
SudoMesh Monitoring Server - Fall, 2014

____ _ __ __ _
/ ___| _ _ __| | ___ | \/ | ___ ___ | |__
\___ \ | | | | / _` | / _ \ | |\/| | / _ \ / __| | '_ \
___) | | |_| | | (_| | | (_) | | | | | | __/ \__ \ | | | |
|____/ \__,_| \__,_| \___/ |_| |_| \___| |___/ |_| |_|
SudoMesh Monitoring Server - Fall, 2014

</pre>

Mesh

2015-12-24T19:48:07Z

Maxb:

[[File:SudoMesh Node.png|frameless|right|300px]]

You can read about our progress on our [[Mesh/Blog|blog]]. We're in an alpha testing phase, and our monitoring results can be seen on [https://monitor.sudomesh.org/smokeping/smokeping.cgi?target=Mesh smokeping] or [https://monitor.sudomesh.org/cacti/graph.php?action=view&local_graph_id=217&rra_id=all cacti].
 Check out the Join Us section below for opportunities to help out!
([[User:Maxb|Maxb]] December 22nd 2015)
 
<hr>
'''We are an all-volunteer organization building the People's Open Network, a community-owned and operated non-profit internet infrastructure in Oakland.'''

People's Open Network is a [http://en.wikipedia.org/wiki/Mesh_networking mesh network] based out of Oakland, California.

Imagine if the wifi router in your home connected to the wifi routers in your neighbourâ€™s homes and they again connected to their neighbours to form a huge free wireless network spanning the city! That's exactly what a mesh network is, or at least what it can be. Roads and telephone poles are owned government or private interests and laying down cable is expensive but by using wireless signals that hop from building to building we can create a community owned and operated free-as-in-freedom alternative to corporate Internet Service Providers! Community wireless mesh networks are growing around the world, creating local 'internets' that support Net Neutrality and community control of critical infrastructure.

sudo mesh is a non-profit organization consisting of a group of unpaid volunteers who are building People's Open Network. Our mission in building the network is to connect our neighbors, support local businesses, and enable community collaboration and cultural production. In the event of disaster or censorship, a mesh network can be a resilient means of communication and sharing of information.

We are spending a lot of time developing [https://github.com/sudomesh/ software] to make it cheap and easy for anyone to be part of People's Open Network, regardless of technical skill.

[[File:Mesh_Oakland_High_Res.png|225px|right]]

= Join Us =

* Join the [http://lists.sudoroom.org/listinfo/mesh email list]
* Follow us on [https://twitter.com/sudomesh twitter] and like us on [https://www.facebook.com/sudomesh facebook].
* Learn more at our general meetings, which are the last Tuesdays of every month at [[Getting_there|sudo room]]. We have focus groups and we collaborate on different parts of the project - from design to software development, documentation to community outreach and of course, community outreach and climbing rooftops to mount nodes!
* We have '''weekly meetings'' on Tuesdays and '''weekly hacknights''' on Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]], but at these events we do not spend time introducing new people to the project. If you do not feel ready to jump right in and start contributing, please show up for our general meetings (mentioned above) where we specifically take time to intro new volunteers and answer questions :D
* Chat with us on [http://www.irchelp.org/irchelp/irctutorial.html IRC]: [http://webchat.freenode.net/?channels=peoplesopen.net #peoplesopen.net]
* We generally collaborate on [https://pad.riseup.net/p/sudomesh meeting notes] at each meeting. Look at our archive of past [[Mesh/Minutes|meeting minutes]]!

= How to Help =

We need more people on the network to improve the quality of the service. When you setup a node, you improve the service for everybody on the network and give more access to your community. We encourage participants to ask their communities to join their networks and create distributed services for them. We have a [[Mesh/User_Guide|user guide]] to help you get on the network!

*Check out our [[Mesh/ToDos|action items]]
*Support us with a small weekly donation on [https://www.gittip.com/sudomesh/ gittip], here's [[Mesh/Purchases|how we spend it]].
*Send bitcoins to our wallet address: {{bitcoin wallet}}
*Check out our [[Mesh/Wishlist|wishlist]], we have requests!
*Come to our meetings in Oakland! (listed above)
*Improve our documentation
*Talk to your community about joining the mesh

== Developers ==

We need hardware and software engineers to help us with our code. We have an overview of [[Mesh/Technical_Overview|technical documentation]] that will be helpful in understanding the network.

If you want to immediately help, check out [https://github.com/sudomesh our code] or [https://github.com/sudomesh/sudowrt-firmware/milestones look at our remaining issues for upcoming milestones].

Here are some of the projects that need attention:

* [[Mesh/Firmware|Firmware]] - The sudowrt firmware
* [https://github.com/sudomesh/sudowrt-web-ui sudowrt-web-ui] - The new and improved web admin UI for sudowrt nodes
* [https://github.com/sudomesh/ubus-https-forwarder ubus-https-forwarder] - Allow management of extender nodes from home node web UI
* [https://github.com/sudomesh/service-browser The Service Browser] - Web UI for browsing mesh services
* [[Mesh/Distributed Services|Mesh Services]] - Which services should we provide?

== Designers ==

We need artists and designers to make things look nice! We have [[Mesh/Design|design schemes]] we already use, but we're always looking to improve it. We need to improve our presentation content and [[Mesh/Diagrams|diagrams]] too! We've been focused on these areas:

* [[Mesh/Presentation|Presentation]]
* [[Mesh/Diagrams|Diagrams]]
* Tutorials and Videos

= Frequently Asked Questions (FAQs)=
*[[Mesh/Challenges|Challenges]] - What sort of challenges and problems do we face?
*[[Mesh/Decisions|Decisions]] - What decisions have we made, and why?
*[[Mesh/Funding|Funding]] - How the heck do we fund this thing?
*[[Mesh/Legal|Legal]] - How do we use exit nodes, relays and legal structures to protect node owners and ourselves?
*[[Mesh/Hosting|Hosting]] - How are we hosting and what does it cost?
*[[Mesh/Backup|Backup]] - How do we handle backups?
*[[Mesh/Server security|Server security]] - How do we ensure server security?

=Logistics=
*[[Mesh/Checkouts|Checkouts]] - Who took what gear home.
*[[Mesh/Inventory|Inventory]] - Continually-updated inventory of our hardware and gear.
*[[Mesh/Marketing|Marketing]] - Inspiration and links to marketing materials in progress.
*[[Mesh/Naming|Naming]] - What do we call ourselves? A lineage of bikeshedding.
*[[Mesh/Purchases|Purchases]] - Details on our purchases, made by either individuals or through our crowdfunded money.
*[[Mesh/Taxes|Taxes]] - Filed taxes for the sudo mesh non-profit

= Research =
We need help improving our documentation about the area and other legalities.

*[[Mesh/Legal|Legal]] - we are becoming a 501(c)3 and there are other legalities of wireless networks
*[[Mesh/Interviews with other meshers|Interviews]] - we interviewed other experienced meshers
*[[Mesh/Documentation|Other documentation]] - books, articles, wikis, blog posts.
*[[Mesh/Oakland|Oakland]] - information and resources pertaining to Oakland community organizations, wireless initiatives, policy and research initiatives
*[[Mesh/Other muni networking projects|Municipal projects]] - examples of progressive uses of municipal networks.
*[[Mesh/Decentralized FM/AM radio|Decentralized FM/AM radio]] - Bit of research on adding legal FM/AM transmitters to nodes.

= Other Firmware and Networks =

There are [[Mesh/Other mesh projects|other meshes]] around the world that have inspired us to make our own network! They use software from these projects:

*[[Mesh/Freifunk]] (germany) - the creators of batman-adv (routing protocol we use) and one of the longest-running mesh networks in the world.
*[[Mesh/Commotion]] - a very well-documented project from the Open Technology Institute creating a simple-to-deploy mesh firmware and setup for small community meshes around the world.
* [[Mesh/San Francisco]] Mesh projects in San Francisco

=Web Resources=
*[http://510pen.org 510pen] - East Bay community wireless mesh network spawned in 2009 by [[User:mfb|Mark Burdett]]
*[http://wiki.tidepools.com Tidepools] - [[User:tunabananas|Jenny Ryan]] designed local use cases for a community mobile mapping application built to run on mesh networks.
*[https://wiki.projectmeshnet.org/Main_Page Project Meshnet] - Extensive wiki on the /r/darknet project, including extensive list of [https://wiki.projectmeshnet.org/Projects projects coordinating with them].
*[http://en.wikipedia.org/wiki/Long-range_Wi-Fi#Notable_links Long Range Wifi] - Info on the longest-range wifi connections ever made.
*[https://github.com/adafruit/Adafruit-WebIDE Adafruit's Web IDE built for Raspberry Pi] but probably good for editing code on any device and ensuring it is managed with a code repo. By default it uses [https://bitbucket.org bitbucket.org] but it could probably be configured for Github.

=All Sudo Mesh Wiki Pages=
<center>{{Mesh nav}}</center>

''Please note that all contributions to Sudo Room may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here. You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Sudo Room:Copyrights for details). Do not submit copyrighted work without permission!''

[[Category:Projects]][[Category:Mesh]]

Mesh

2015-12-23T01:45:42Z

Maxb: /* Developers */

[[File:SudoMesh Node.png|frameless|right|300px]]

You can usually read about our progress on our [[Mesh/Blog|blog]] or by perusing our [[Mesh/Minutes|meeting minutes]] but we've been in ''deep development mode'' for a few months and are just now emerging. The 0.2 firmware release is very imminent and we will resume our regularly scheduled meetings and blog updates post release :-) ([[User:Juul|Juul]] July 2nd 2015)
 

'''We are an all-volunteer organization building the People's Open Network, a community-owned and operated non-profit internet infrastructure in Oakland.'''

People's Open Network is a [http://en.wikipedia.org/wiki/Mesh_networking mesh network] based out of Oakland, California.

Imagine if the wifi router in your home connected to the wifi routers in your neighbourâ€™s homes and they again connected to their neighbours to form a huge free wireless network spanning the city! That's exactly what a mesh network is, or at least what it can be. Roads and telephone poles are owned government or private interests and laying down cable is expensive but by using wireless signals that hop from building to building we can create a community owned and operated free-as-in-freedom alternative to corporate Internet Service Providers! Community wireless mesh networks are growing around the world, creating local 'internets' that support Net Neutrality and community control of critical infrastructure.

sudo mesh is a non-profit organization consisting of a group of unpaid volunteers who are building People's Open Network. Our mission in building the network is to connect our neighbors, support local businesses, and enable community collaboration and cultural production. In the event of disaster or censorship, a mesh network can be a resilient means of communication and sharing of information.

We are spending a lot of time developing [https://github.com/sudomesh/ software] to make it cheap and easy for anyone to be part of People's Open Network, regardless of technical skill.

[[File:Mesh_Oakland_High_Res.png|225px|right]]

= Join Us =

* Join the [http://lists.sudoroom.org/listinfo/mesh email list]
* Follow us on [https://twitter.com/sudomesh twitter] and like us on [https://www.facebook.com/sudomesh facebook].
* Learn more at our general meetings, which are the last Tuesdays of every month at [[Getting_there|sudo room]]. We have focus groups and we collaborate on different parts of the project - from design to software development, documentation to community outreach and of course, community outreach and climbing rooftops to mount nodes!
* We have '''weekly meetings'' on Tuesdays and '''weekly hacknights''' on Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]], but at these events we do not spend time introducing new people to the project. If you do not feel ready to jump right in and start contributing, please show up for our general meetings (mentioned above) where we specifically take time to intro new volunteers and answer questions :D
* Chat with us on [http://www.irchelp.org/irchelp/irctutorial.html IRC]: [http://webchat.freenode.net/?channels=peoplesopen.net #peoplesopen.net]
* We generally collaborate on [https://pad.riseup.net/p/sudomesh meeting notes] at each meeting. Look at our archive of past [[Mesh/Minutes|meeting minutes]]!

= How to Help =

We need more people on the network to improve the quality of the service. When you setup a node, you improve the service for everybody on the network and give more access to your community. We encourage participants to ask their communities to join their networks and create distributed services for them. We have a [[Mesh/User_Guide|user guide]] to help you get on the network!

*Check out our [[Mesh/ToDos|action items]]
*Support us with a small weekly donation on [https://www.gittip.com/sudomesh/ gittip], here's [[Mesh/Purchases|how we spend it]].
*Send bitcoins to our wallet address: {{bitcoin wallet}}
*Check out our [[Mesh/Wishlist|wishlist]], we have requests!
*Come to our meetings in Oakland! (listed above)
*Improve our documentation
*Talk to your community about joining the mesh

== Developers ==

We need hardware and software engineers to help us with our code. We have an overview of [[Mesh/Technical_Overview|technical documentation]] that will be helpful in understanding the network.

If you want to immediately help, check out [https://github.com/sudomesh our code] or [https://github.com/sudomesh/sudowrt-firmware/milestones look at our remaining issues for upcoming milestones].

Here are some of the projects that need attention:

* [[Mesh/Firmware|Firmware]] - The sudowrt firmware
* [https://github.com/sudomesh/sudowrt-web-ui sudowrt-web-ui] - The new and improved web admin UI for sudowrt nodes
* [https://github.com/sudomesh/ubus-https-forwarder ubus-https-forwarder] - Allow management of extender nodes from home node web UI
* [https://github.com/sudomesh/service-browser The Service Browser] - Web UI for browsing mesh services
* [[Mesh/Distributed Services|Mesh Services]] - Which services should we provide?

== Designers ==

We need artists and designers to make things look nice! We have [[Mesh/Design|design schemes]] we already use, but we're always looking to improve it. We need to improve our presentation content and [[Mesh/Diagrams|diagrams]] too! We've been focused on these areas:

* [[Mesh/Presentation|Presentation]]
* [[Mesh/Diagrams|Diagrams]]
* Tutorials and Videos

= Frequently Asked Questions (FAQs)=
*[[Mesh/Challenges|Challenges]] - What sort of challenges and problems do we face?
*[[Mesh/Decisions|Decisions]] - What decisions have we made, and why?
*[[Mesh/Funding|Funding]] - How the heck do we fund this thing?
*[[Mesh/Legal|Legal]] - How do we use exit nodes, relays and legal structures to protect node owners and ourselves?
*[[Mesh/Hosting|Hosting]] - How are we hosting and what does it cost?
*[[Mesh/Backup|Backup]] - How do we handle backups?
*[[Mesh/Server security|Server security]] - How do we ensure server security?

=Logistics=
*[[Mesh/Checkouts|Checkouts]] - Who took what gear home.
*[[Mesh/Inventory|Inventory]] - Continually-updated inventory of our hardware and gear.
*[[Mesh/Marketing|Marketing]] - Inspiration and links to marketing materials in progress.
*[[Mesh/Naming|Naming]] - What do we call ourselves? A lineage of bikeshedding.
*[[Mesh/Purchases|Purchases]] - Details on our purchases, made by either individuals or through our crowdfunded money.
*[[Mesh/Taxes|Taxes]] - Filed taxes for the sudo mesh non-profit

= Research =
We need help improving our documentation about the area and other legalities.

*[[Mesh/Legal|Legal]] - we are becoming a 501(c)3 and there are other legalities of wireless networks
*[[Mesh/Interviews with other meshers|Interviews]] - we interviewed other experienced meshers
*[[Mesh/Documentation|Other documentation]] - books, articles, wikis, blog posts.
*[[Mesh/Oakland|Oakland]] - information and resources pertaining to Oakland community organizations, wireless initiatives, policy and research initiatives
*[[Mesh/Other muni networking projects|Municipal projects]] - examples of progressive uses of municipal networks.
*[[Mesh/Decentralized FM/AM radio|Decentralized FM/AM radio]] - Bit of research on adding legal FM/AM transmitters to nodes.

= Other Firmware and Networks =

There are [[Mesh/Other mesh projects|other meshes]] around the world that have inspired us to make our own network! They use software from these projects:

*[[Mesh/Freifunk]] (germany) - the creators of batman-adv (routing protocol we use) and one of the longest-running mesh networks in the world.
*[[Mesh/Commotion]] - a very well-documented project from the Open Technology Institute creating a simple-to-deploy mesh firmware and setup for small community meshes around the world.
* [[Mesh/San Francisco]] Mesh projects in San Francisco

=Web Resources=
*[http://510pen.org 510pen] - East Bay community wireless mesh network spawned in 2009 by [[User:mfb|Mark Burdett]]
*[http://wiki.tidepools.com Tidepools] - [[User:tunabananas|Jenny Ryan]] designed local use cases for a community mobile mapping application built to run on mesh networks.
*[https://wiki.projectmeshnet.org/Main_Page Project Meshnet] - Extensive wiki on the /r/darknet project, including extensive list of [https://wiki.projectmeshnet.org/Projects projects coordinating with them].
*[http://en.wikipedia.org/wiki/Long-range_Wi-Fi#Notable_links Long Range Wifi] - Info on the longest-range wifi connections ever made.
*[https://github.com/adafruit/Adafruit-WebIDE Adafruit's Web IDE built for Raspberry Pi] but probably good for editing code on any device and ensuring it is managed with a code repo. By default it uses [https://bitbucket.org bitbucket.org] but it could probably be configured for Github.

=All Sudo Mesh Wiki Pages=
<center>{{Mesh nav}}</center>

''Please note that all contributions to Sudo Room may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here. You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Sudo Room:Copyrights for details). Do not submit copyrighted work without permission!''

[[Category:Projects]][[Category:Mesh]]

Mesh

2015-12-23T01:44:07Z

Maxb: /* Logistics */

[[File:SudoMesh Node.png|frameless|right|300px]]

You can usually read about our progress on our [[Mesh/Blog|blog]] or by perusing our [[Mesh/Minutes|meeting minutes]] but we've been in ''deep development mode'' for a few months and are just now emerging. The 0.2 firmware release is very imminent and we will resume our regularly scheduled meetings and blog updates post release :-) ([[User:Juul|Juul]] July 2nd 2015)
 

'''We are an all-volunteer organization building the People's Open Network, a community-owned and operated non-profit internet infrastructure in Oakland.'''

People's Open Network is a [http://en.wikipedia.org/wiki/Mesh_networking mesh network] based out of Oakland, California.

Imagine if the wifi router in your home connected to the wifi routers in your neighbourâ€™s homes and they again connected to their neighbours to form a huge free wireless network spanning the city! That's exactly what a mesh network is, or at least what it can be. Roads and telephone poles are owned government or private interests and laying down cable is expensive but by using wireless signals that hop from building to building we can create a community owned and operated free-as-in-freedom alternative to corporate Internet Service Providers! Community wireless mesh networks are growing around the world, creating local 'internets' that support Net Neutrality and community control of critical infrastructure.

sudo mesh is a non-profit organization consisting of a group of unpaid volunteers who are building People's Open Network. Our mission in building the network is to connect our neighbors, support local businesses, and enable community collaboration and cultural production. In the event of disaster or censorship, a mesh network can be a resilient means of communication and sharing of information.

We are spending a lot of time developing [https://github.com/sudomesh/ software] to make it cheap and easy for anyone to be part of People's Open Network, regardless of technical skill.

[[File:Mesh_Oakland_High_Res.png|225px|right]]

= Join Us =

* Join the [http://lists.sudoroom.org/listinfo/mesh email list]
* Follow us on [https://twitter.com/sudomesh twitter] and like us on [https://www.facebook.com/sudomesh facebook].
* Learn more at our general meetings, which are the last Tuesdays of every month at [[Getting_there|sudo room]]. We have focus groups and we collaborate on different parts of the project - from design to software development, documentation to community outreach and of course, community outreach and climbing rooftops to mount nodes!
* We have '''weekly meetings'' on Tuesdays and '''weekly hacknights''' on Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]], but at these events we do not spend time introducing new people to the project. If you do not feel ready to jump right in and start contributing, please show up for our general meetings (mentioned above) where we specifically take time to intro new volunteers and answer questions :D
* Chat with us on [http://www.irchelp.org/irchelp/irctutorial.html IRC]: [http://webchat.freenode.net/?channels=peoplesopen.net #peoplesopen.net]
* We generally collaborate on [https://pad.riseup.net/p/sudomesh meeting notes] at each meeting. Look at our archive of past [[Mesh/Minutes|meeting minutes]]!

= How to Help =

We need more people on the network to improve the quality of the service. When you setup a node, you improve the service for everybody on the network and give more access to your community. We encourage participants to ask their communities to join their networks and create distributed services for them. We have a [[Mesh/User_Guide|user guide]] to help you get on the network!

*Check out our [[Mesh/ToDos|action items]]
*Support us with a small weekly donation on [https://www.gittip.com/sudomesh/ gittip], here's [[Mesh/Purchases|how we spend it]].
*Send bitcoins to our wallet address: {{bitcoin wallet}}
*Check out our [[Mesh/Wishlist|wishlist]], we have requests!
*Come to our meetings in Oakland! (listed above)
*Improve our documentation
*Talk to your community about joining the mesh

== Developers ==

We need hardware and software engineers to help us with our code. We have an overview of [[Mesh/Technical_Overview|technical documentation]] that will be helpful in understanding the network.

If you want to immediately help, check out [https://github.com/sudomesh our code] or [https://github.com/sudomesh/sudowrt-firmware/milestones look at our remaining issues for upcoming milestones].

Here are some of the projects that need attention:

* [[Mesh/Firmware|Firmware]] - The sudowrt firmware
* [https://github.com/sudomesh/sudowrt-web-ui] - The new and improved web admin UI for sudowrt nodes
* [https://github.com/sudomesh/ubus-https-forwarder ubus-https-forwarder] - Allow management of extender nodes from home node web UI
* [https://github.com/sudomesh/service-browser The Service Browser] - Web UI for browsing mesh services
* [[Mesh/Distributed Services|Mesh Services]] - Which services should we provide?

== Designers ==

We need artists and designers to make things look nice! We have [[Mesh/Design|design schemes]] we already use, but we're always looking to improve it. We need to improve our presentation content and [[Mesh/Diagrams|diagrams]] too! We've been focused on these areas:

* [[Mesh/Presentation|Presentation]]
* [[Mesh/Diagrams|Diagrams]]
* Tutorials and Videos

= Frequently Asked Questions (FAQs)=
*[[Mesh/Challenges|Challenges]] - What sort of challenges and problems do we face?
*[[Mesh/Decisions|Decisions]] - What decisions have we made, and why?
*[[Mesh/Funding|Funding]] - How the heck do we fund this thing?
*[[Mesh/Legal|Legal]] - How do we use exit nodes, relays and legal structures to protect node owners and ourselves?
*[[Mesh/Hosting|Hosting]] - How are we hosting and what does it cost?
*[[Mesh/Backup|Backup]] - How do we handle backups?
*[[Mesh/Server security|Server security]] - How do we ensure server security?

=Logistics=
*[[Mesh/Checkouts|Checkouts]] - Who took what gear home.
*[[Mesh/Inventory|Inventory]] - Continually-updated inventory of our hardware and gear.
*[[Mesh/Marketing|Marketing]] - Inspiration and links to marketing materials in progress.
*[[Mesh/Naming|Naming]] - What do we call ourselves? A lineage of bikeshedding.
*[[Mesh/Purchases|Purchases]] - Details on our purchases, made by either individuals or through our crowdfunded money.
*[[Mesh/Taxes|Taxes]] - Filed taxes for the sudo mesh non-profit

= Research =
We need help improving our documentation about the area and other legalities.

*[[Mesh/Legal|Legal]] - we are becoming a 501(c)3 and there are other legalities of wireless networks
*[[Mesh/Interviews with other meshers|Interviews]] - we interviewed other experienced meshers
*[[Mesh/Documentation|Other documentation]] - books, articles, wikis, blog posts.
*[[Mesh/Oakland|Oakland]] - information and resources pertaining to Oakland community organizations, wireless initiatives, policy and research initiatives
*[[Mesh/Other muni networking projects|Municipal projects]] - examples of progressive uses of municipal networks.
*[[Mesh/Decentralized FM/AM radio|Decentralized FM/AM radio]] - Bit of research on adding legal FM/AM transmitters to nodes.

= Other Firmware and Networks =

There are [[Mesh/Other mesh projects|other meshes]] around the world that have inspired us to make our own network! They use software from these projects:

*[[Mesh/Freifunk]] (germany) - the creators of batman-adv (routing protocol we use) and one of the longest-running mesh networks in the world.
*[[Mesh/Commotion]] - a very well-documented project from the Open Technology Institute creating a simple-to-deploy mesh firmware and setup for small community meshes around the world.
* [[Mesh/San Francisco]] Mesh projects in San Francisco

=Web Resources=
*[http://510pen.org 510pen] - East Bay community wireless mesh network spawned in 2009 by [[User:mfb|Mark Burdett]]
*[http://wiki.tidepools.com Tidepools] - [[User:tunabananas|Jenny Ryan]] designed local use cases for a community mobile mapping application built to run on mesh networks.
*[https://wiki.projectmeshnet.org/Main_Page Project Meshnet] - Extensive wiki on the /r/darknet project, including extensive list of [https://wiki.projectmeshnet.org/Projects projects coordinating with them].
*[http://en.wikipedia.org/wiki/Long-range_Wi-Fi#Notable_links Long Range Wifi] - Info on the longest-range wifi connections ever made.
*[https://github.com/adafruit/Adafruit-WebIDE Adafruit's Web IDE built for Raspberry Pi] but probably good for editing code on any device and ensuring it is managed with a code repo. By default it uses [https://bitbucket.org bitbucket.org] but it could probably be configured for Github.

=All Sudo Mesh Wiki Pages=
<center>{{Mesh nav}}</center>

''Please note that all contributions to Sudo Room may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here. You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Sudo Room:Copyrights for details). Do not submit copyrighted work without permission!''

[[Category:Projects]][[Category:Mesh]]

Mesh/Hosting

2015-12-23T01:41:09Z

Maxb:

This page details current and future hosting solutions used by sudomesh.

= Production =

== Exit nodes ==

We have no production exit nodes yet. The exit nodes must live up the the following requirements:

*Minimum 100 mbit unmetered bandwidth
*A processor fast enough to saturate 100 mbit with NAT'ed tunneled traffic
*A subnet or IP that lists sudomesh as the abuse contact
*Tor-friendly or Tor-agnostic provider
*Location close to bay area
*Co-located (optional, but we want this in the long term)

=== Possible providers ===

[http://www.oplink.net/colocation.html Oplink]:

*Location: Texas
*Bandwidth: Unmetered 100 mbit
*Tor-friendliness: Unknown
*Will let us be the abuse contact: Unknown
*Price: $80 per month

== Relay nodes ==

The relay node requirements:

*Minimum 100 mbit unmetered bandwidth
*Ability to saturate 100 mbit with tunnneled traffic
*Location close to bay area

=== Possible providers ===

[http://www.vpscheap.net/enterprise-vds.aspx vpscheap] have virtual servers with the following specs:

*VM technology: Xen
*Bandwidth: Unmetered 100 mbit
*Ram: 1 GB
*Dual CPU
*Disk space: 50 GB
*Location: Chicago
*Price: $16.99 per month

== SSL ==

We use free [http://startssl.com/ StartSSL] certificates.

== DNS ==

Our DNS hosting is via namecheap.com. We own the following domains:

*peoplesopen.net (primary, use this in communications)
*pplsopen.net
*peoplesopennetwork.com
*peoplesopennetwork.net
*peoplesopennetwork.org
*sudomesh.org (primary, use this in communications)
*sudomesh.net
*sudomesh.com
*meshthepla.net
*meshtheplanet.net
*meshtheplanet.org
*meshtheplanet.com

== Web and email ==

We currently have a VPS from vpscheap.com. It is hosting web and email for the following domains:

*peoplesopen.net (and variations)
*sudomesh.org (and variations)

The VPS specs are:

*VM technology: OpenVZ
*Ram: 512 MB
*Swap: 1 GB
*Disk space: 50 GB
*Bandwidth: 20 mbit/sec unmetered
*Operating system: Ubuntu
*Cost: $6 a month

== Backup ==

We currently have a VPS from backupsy.com. The domain backup.sudomesh.org points to the server. All sudomesh servers back up to this server using [http://duplicity.nongnu.org/â€Ž Duplicity] once every 24 hours. The backups are incremental so we can restore to any point in time. We do not yet have a policy for how far back we keep backups. The backups are encrypted and the backups cannot be deleted by anyone other than root on the backup server, so gaining access to a sudomesh server does not mean gaining access to deletion of backups.

The specs for the VPS are:

*VM technology: KVM
*Disk space: 250 GB
*Ram: 512 MB
*Bandwidth: 1000 GB per month
*Operating system: Ubuntu
*Cost: $6 a month
*Note: The ToS only let us use this for backup unless we upgrade our plan.

= Development =

== Exit node ==

We have one exit node for development use. Its hostname is exit1.sudomesh.org.

VPS specs:

*Provider: digitalocean.com
*VM technology: KVM
*Ram: 4G
*Bandwidth: 1Gbps with 4TB transfer limit/month
*IP address: 104.236.181.226
*OS: Debian
*Price: $40 per month

Mesh/Hosting

2015-12-23T01:40:10Z

Maxb: /* Development */

This page details current and future hosting solutions used by sudomesh.

sudomesh's recurring hosting-related costs are currently $37.28.

Here is [https://docs.google.com/spreadsheet/ccc?key=0Akog0JI0-bB9dEtTOU41Q0NxZnQ3SVctY0tXWmZIWEE#gid=0 a spreadsheet with the hosting-related recurring expenses].

= Production =

== Exit nodes ==

We have no production exit nodes yet. The exit nodes must live up the the following requirements:

*Minimum 100 mbit unmetered bandwidth
*A processor fast enough to saturate 100 mbit with NAT'ed tunneled traffic
*A subnet or IP that lists sudomesh as the abuse contact
*Tor-friendly or Tor-agnostic provider
*Location close to bay area
*Co-located (optional, but we want this in the long term)

=== Possible providers ===

[http://www.oplink.net/colocation.html Oplink]:

*Location: Texas
*Bandwidth: Unmetered 100 mbit
*Tor-friendliness: Unknown
*Will let us be the abuse contact: Unknown
*Price: $80 per month

== Relay nodes ==

The relay node requirements:

*Minimum 100 mbit unmetered bandwidth
*Ability to saturate 100 mbit with tunnneled traffic
*Location close to bay area

=== Possible providers ===

[http://www.vpscheap.net/enterprise-vds.aspx vpscheap] have virtual servers with the following specs:

*VM technology: Xen
*Bandwidth: Unmetered 100 mbit
*Ram: 1 GB
*Dual CPU
*Disk space: 50 GB
*Location: Chicago
*Price: $16.99 per month

== SSL ==

We use free [http://startssl.com/ StartSSL] certificates.

== DNS ==

Our DNS hosting is via namecheap.com. We own the following domains:

*peoplesopen.net (primary, use this in communications)
*pplsopen.net
*peoplesopennetwork.com
*peoplesopennetwork.net
*peoplesopennetwork.org
*sudomesh.org (primary, use this in communications)
*sudomesh.net
*sudomesh.com
*meshthepla.net
*meshtheplanet.net
*meshtheplanet.org
*meshtheplanet.com

== Web and email ==

We currently have a VPS from vpscheap.com. It is hosting web and email for the following domains:

*peoplesopen.net (and variations)
*sudomesh.org (and variations)

The VPS specs are:

*VM technology: OpenVZ
*Ram: 512 MB
*Swap: 1 GB
*Disk space: 50 GB
*Bandwidth: 20 mbit/sec unmetered
*Operating system: Ubuntu
*Cost: $6 a month

== Backup ==

We currently have a VPS from backupsy.com. The domain backup.sudomesh.org points to the server. All sudomesh servers back up to this server using [http://duplicity.nongnu.org/â€Ž Duplicity] once every 24 hours. The backups are incremental so we can restore to any point in time. We do not yet have a policy for how far back we keep backups. The backups are encrypted and the backups cannot be deleted by anyone other than root on the backup server, so gaining access to a sudomesh server does not mean gaining access to deletion of backups.

The specs for the VPS are:

*VM technology: KVM
*Disk space: 250 GB
*Ram: 512 MB
*Bandwidth: 1000 GB per month
*Operating system: Ubuntu
*Cost: $6 a month
*Note: The ToS only let us use this for backup unless we upgrade our plan.

= Development =

== Exit node ==

We have one exit node for development use. Its hostname is exit1.sudomesh.org.

VPS specs:

*Provider: digitalocean.com
*VM technology: KVM
*Ram: 4G
*Bandwidth: 1Gbps with 4TB transfer limit/month
*IP address: 104.236.181.226
*OS: Debian
*Price: $40 per month

Mesh/Hosting

2015-12-23T01:39:52Z

Maxb: /* Exit node */

This page details current and future hosting solutions used by sudomesh.

sudomesh's recurring hosting-related costs are currently $37.28.

Here is [https://docs.google.com/spreadsheet/ccc?key=0Akog0JI0-bB9dEtTOU41Q0NxZnQ3SVctY0tXWmZIWEE#gid=0 a spreadsheet with the hosting-related recurring expenses].

= Production =

== Exit nodes ==

We have no production exit nodes yet. The exit nodes must live up the the following requirements:

*Minimum 100 mbit unmetered bandwidth
*A processor fast enough to saturate 100 mbit with NAT'ed tunneled traffic
*A subnet or IP that lists sudomesh as the abuse contact
*Tor-friendly or Tor-agnostic provider
*Location close to bay area
*Co-located (optional, but we want this in the long term)

=== Possible providers ===

[http://www.oplink.net/colocation.html Oplink]:

*Location: Texas
*Bandwidth: Unmetered 100 mbit
*Tor-friendliness: Unknown
*Will let us be the abuse contact: Unknown
*Price: $80 per month

== Relay nodes ==

The relay node requirements:

*Minimum 100 mbit unmetered bandwidth
*Ability to saturate 100 mbit with tunnneled traffic
*Location close to bay area

=== Possible providers ===

[http://www.vpscheap.net/enterprise-vds.aspx vpscheap] have virtual servers with the following specs:

*VM technology: Xen
*Bandwidth: Unmetered 100 mbit
*Ram: 1 GB
*Dual CPU
*Disk space: 50 GB
*Location: Chicago
*Price: $16.99 per month

== SSL ==

We use free [http://startssl.com/ StartSSL] certificates.

== DNS ==

Our DNS hosting is via namecheap.com. We own the following domains:

*peoplesopen.net (primary, use this in communications)
*pplsopen.net
*peoplesopennetwork.com
*peoplesopennetwork.net
*peoplesopennetwork.org
*sudomesh.org (primary, use this in communications)
*sudomesh.net
*sudomesh.com
*meshthepla.net
*meshtheplanet.net
*meshtheplanet.org
*meshtheplanet.com

== Web and email ==

We currently have a VPS from vpscheap.com. It is hosting web and email for the following domains:

*peoplesopen.net (and variations)
*sudomesh.org (and variations)

The VPS specs are:

*VM technology: OpenVZ
*Ram: 512 MB
*Swap: 1 GB
*Disk space: 50 GB
*Bandwidth: 20 mbit/sec unmetered
*Operating system: Ubuntu
*Cost: $6 a month

== Backup ==

We currently have a VPS from backupsy.com. The domain backup.sudomesh.org points to the server. All sudomesh servers back up to this server using [http://duplicity.nongnu.org/â€Ž Duplicity] once every 24 hours. The backups are incremental so we can restore to any point in time. We do not yet have a policy for how far back we keep backups. The backups are encrypted and the backups cannot be deleted by anyone other than root on the backup server, so gaining access to a sudomesh server does not mean gaining access to deletion of backups.

The specs for the VPS are:

*VM technology: KVM
*Disk space: 250 GB
*Ram: 512 MB
*Bandwidth: 1000 GB per month
*Operating system: Ubuntu
*Cost: $6 a month
*Note: The ToS only let us use this for backup unless we upgrade our plan.

= Development =

== Relay node ==

We have one relay node for development use. Its hostname is relay1.sudomesh.org.

VPS specs:

*Provider: budgetvm.com
*VM technology: Xen
*Ram: 768 MB
*Swap: 1536 MB
*Bandwidth: 2500 GB per month
*IP addresses: 2
*OS: Debian
*Price: $6.99 per month

== Exit node ==

We have one exit node for development use. Its hostname is exit1.sudomesh.org.

VPS specs:

*Provider: digitalocean.com
*VM technology: KVM
*Ram: 4G
*Bandwidth: 1Gbps with 4TB transfer limit/month
*IP address: 104.236.181.226
*OS: Debian
*Price: $40 per month

Mesh/Distributed Services

2015-12-20T23:14:54Z

Maxb: /* Maxb's Debian Server on Banana Pi - maxb-banana-pi.sudomesh.org */

The [[mesh]] network should provide communication services, so that it offers value to its users beyond mere connectivity to the Internet. What can be done to help it strengthen ties among Oakland residents, and to benefit the community? This wiki page is here to collect ideas about what services could/should be offered.

Services (such as file sharing, email, contacts, calendar, and phone) should be provided based on existing free/open source software. Orientation & setup could be built into the introductory process for new mesh users.

Some general aspects worth considering:
* Security
* Integration into a user account distributed database with master-master replication and low latency (ex. [http://www.datastax.com/resources/whitepapers/benchmarking-top-nosql-databases Cassandra]).

== Active Services ==
The service browser is unfinished, but as we're working on building out the network and setting up services on the network, we can document what we currently have running here for now:

=== Maxb's Debian Server on Banana Pi - maxb-banana-pi.sudomesh.org ===
* Only accessible when connected to peoplesopen.net
* Owncloud: https://owncloud.maxb-banana-pi.sudomesh.org
** guest username: thepasswordispassword
** guest password: password
* Etherpad: https://pad.maxb-banana-pi.sudomesh.org

== Architecture: Centralized & decentralized services ==
A central philosophical and practical consideration is how services will be provided. Do we fundamentally want the mesh to be a centralized entity which offers certain services to all members? Or a platform on which individual members can offer services? Or a hybrid?

As it stands now (summer 2015), the mesh offers some opportunity for individual members to offer services. For instance, it's possible for anybody on the mesh to offer services that are accessible elsewhere on the mesh. Should there be (for instance) a central, community-curated file server? Or should it just be up to anybody who wants to, to offer up file shares?

Are there certain kinds of sharing we want to discourage or prohibit, and if so, what will be the social and technical means for enforcement? How will we respond if people start openly sharing copyrighted music and movies? Proprietary software? Child porn? It's worthwhile to think through these scenarios, as a successful network that lacks any kind of governance would become an attractive resource for those whose illegal activities cannot be pursued in the open on the Internet. (An example of this dynamic: [http://www.seattletimes.com/seattle-news/crime/state-supreme-court-rules-against-backpagecom-in-sex-trafficking-suit/ State Supreme Court rules against Backpage.com in sex-trafficking suit], Seattle Times, Sept. 2015)

==Storage / File Systems==

There are several options for a distributed file system and each have there advantages and disadvantages. The distributed file system can be used to offer file storage or reduce latency across the network.

* [http://opensfs.org/lustre/ Lustre] - Used by sixty percent of the top 100 websites.
** Performance: Amazingly fast! I can assert that Lustre can serve a lot of streams and that encoding speed is not affected by accessing files via Lustre.
** [http://en.wikipedia.org/wiki/POSIX POSIX] compatibility: Very good!. No need to modify applications to use luster.
** Replication, Load Balancing and Fail Over: Very bad!. For replication load balancing we and fail over we need to rely on other software such as virtual IPs and DRDB.
** Installation: The worst!. Impossible to install by mere mortals. Requires a very specific combination of kernel, lustre patches and tweaks to get it working. And current luster patches usually work with old kernels that are incompatible with new hardware/software.

* [https://code.google.com/p/mogilefs/ MogileFS]
** Performance: Good for small files but not usable for medium to large files. This is mostly due to HTTP overhead since all files are send/receive via HTTP requests that encode all data in base64 adding a 33% overhead to each file.
** POXIS compatibility: Non existent. All applications require to be modified to use MogileFS that renders it useless for streaming/encoding since most streaming servers and encoding tools do not understand the protocol.
** Replication and failover out of the box and load balancing can be implemented in the application by accessing more than one tracker at a time.
** Installation: Relatively easy and ready to use packages exist in most distributions. The only difficulty I found was setting the database master-slave to eliminate the single point of failure.

* [http://www.gluster.org/ GlusterFS]
** Performance: Very bad for streaming. I cannot reach more than a few Mbps in a 10Gbps network. Clients and Server CPU skyrockets on heavy writes. For encoding works because the CPU is saturated before the network and I/O.
** POXIS: Almost compatible. The tools I use can access gluster mounts as normal folders in disk but in some edge cases things start causing problems. Check gluster mailing lists and you will see there are a lot of problems.
** Replication, Failover and Load balancing: The best! if they actually worked. Gluster is very new and it has a lot of bugs and performance problems.
** Installation is too easy. The management command line is amazing and setting replicated, striped and distributed volumes among several servers can not be any easier.

([http://stackoverflow.com/questions/916902/lustre-gluster-or-mogilefs-for-video-storage-encoding-and-streaming source of above information])

* [http://hadoop.apache.org/ Hadoop] (HDFS) - slow and has a lot of proprietary derivatives (MapR, GPFS, and [http://gigaom.com/2012/07/11/because-hadoop-isnt-perfect-8-ways-to-replace-hdfs/ other alternatives])
* [http://www.xtreemfs.org/ XtreemFS] - slow and we need more research on it.
* Cassandra File System (CFS) - proprietary software made by DataStax and included in the Enterprise Edition of their software.
* [http://en.wikipedia.org/wiki/Network_File_System Network File Sytem] (NFS) - comparable to Lustre, but the [http://wiki.lustre.org/index.php/NFS_vs._Lustre IO bandwidth doesn't scale].

'''Non-distributed file systems'''
There's the option to use a modern file system with [http://en.wikipedia.org/wiki/Rsync rsync].
[http://rudd-o.com/linux-and-free-software/ways-in-which-zfs-is-better-than-btrfs Comparison of ZFS and BTRFS]
[http://porky.linuxjournal.com:8080/LJ/218/11250.html A Quick Introduction to Modern Filesystems]

==Databases and Servers==

These are decentralized databases and servers that could ultimately be optimized to store data nearest to where people access it. A significant factors with mesh networks, that as "size and complexity continues to grow, mesh networks that contain multiple hops become increasingly vulnerable to problems such as bandwidth degradation, radio interference and network latency.<ref>[http://www.strixsystems.com/products/datasheets/strixwhitepaper_multihop.pdf Solving the Wireless Mesh Multi-Hop Dilemma]</ref>" There are several other methods of improving network latency, but all means should be tested and implemented to improve services.

* [https://cassandra.apache.org/ cassandra] - a decentralized database with asynchronous masterless replication allowing low latency operations for all clients. Cassandra has [http://en.wikipedia.org/wiki/Hadoop Hadoop] integration, with MapReduce support.
* [https://couchdb.apache.org/ CouchDB] - I can tell you that it quickly becomes complicated to write multi-user app with CouchDB. Decent access control means that you need a database per user and likely a few extra databases. You then have to set all of these databases up to synchronize between each other which is further complicated by the limitations on what information is available by the limitations on how synchronization rules and filters can be written. There seem to be no good tools for managing/visualizing these complex relationships so you end up having to roll your own.
* [https://github.com/mirage/irmin irmin] - a distributed database with built-in snapshot, branch and revert mechanisms. (similar to git)
* [http://code.google.com/p/leveldb/ levelDB] - a fast and lightweight key/value database library.
* [http://www.mongodb.org/ mongoDB] - an open-source document database, a NoSQL database. Written in C++.
* [http://nodejs.org/ node.js] - an HTTP server written in javascript.
* [http://pouchdb.com/ PouchDB] - a javascript based couchDB.
* [https://github.com/dominictarr/scuttlebutt scuttlebutt] - a data synchronization protocol, or a peer-to-peer replicable data structure.
* [https://tahoe-lafs.org/trac/tahoe-lafs tahoe-lafs] - a decentralized database.

==Communications==

*[http://radicale.org/ radicale] - a CalDAV (calendar) and CardDAV (contacts) server.
*[http://keithp.com/blogs/calypso/ calypso] - Radicale fork with a git back-end (by Keith Packard of X11 fame)
*[http://villagetelco.org Village telco] - an initiative to build low-cost community telephone network hardware and software that can be set up in minutes anywhere in the world. No mobile phone towers or land lines are required, it uses the internet. It has a Simple Unified Dashboard (SPUD) for mesh networks.
*[https://ripple.com/currency/ Ripple] (XRP) - a math-based crypto-currency designed to work seamlessly with the Internet. Powered by a global network of computers; a fast, direct, and secure way to send payments on the web. '''It can be used to prevent malious attacks on servers.'''
*[http://openbts.org/ OpenBTS] - open source cell phone tower software.
*[http://www.openmama.org/what-is-openmama OpenMAMA] - a high performance middleware agnostic messaging API that interfaces with a variety of message oriented middleware systems
*an encrypted asynchronous messaging system to replace email
*a module to have collaborative documents, voting, and groups (ie. [http://en.wikipedia.org/wiki/Collaborative_software groupware])
** Read information about the [http://mitar.tnode.com/post/73983101095/peer-to-peer-voting-scheme peer-to-peer voting scheme].
*a module for peer to peer file sharing.
*a module for object-orientated tagging, shareable feeds.
*a module for feeds and posts, such as [http://www.trsst.com/ Trsst].
* [http://www.frontlinesms.com/ Frontline SMS] - a free, open-source desktop application that allows you to send texts.

==Mapping==

* [http://nodewatcher.readthedocs.org/en/latest/installation.html NodeWatcher] - an open source network planning, deployment, monitoring and maintanance platform.
* [http://wiki.ninux.org/InstallNodeshot NodeShot] - an easy to use wireless community map server.
* [https://github.com/freifunk/openwifimap-html5 OpenWiFiMap] - a database and map for free network WiFi routers (freifunk and others, too!).
* [https://github.com/libremap LibreMap] - a scalable, global and decentralized router database and map visualization for community networks, such as guifi, ninux, etc.
* [http://tidepools.co Tidepools] - collaborative local mapping software
* [http://ediblecities.org/ Edible Cities] - a food mapping project
* Bulletin Board / Local Classified Ads
** Community Asset Mapping (ex. [http://thepyre.org/wiki/Mycelia Mycelia])

== Protocols ==
* [https://tent.io/ Tent] - a method to store all your data in one place that you control. Instead of your digital life being spread across many services.
* [https://www.docker.io/ Docker] - an open-source project to easily create lightweight, portable, self-sufficient containers from any application.
* [http://maidsafe.net/ MaidSafe] - an encrypted, fully distributed data management service. This network manages static and dynamic data as well as communications. (charges money)
* [https://github.com/telehash/telehash.org/blob/master/v3/intro.md Telehash] - "Telehash is a 100% open, secure mesh networking technology with these design principles: full end-to-end encryption, all the time; strict privacy: no content, identity, or metadata is ever revealed to third parties; maximum app/device compatibility: suitable for embedded, mobile, and web usage; making privacy the easy choice for developers; flexible transport protocols, for compatibility with existing layers; native implementations for the widest possible variety of languages/platforms. The telehash team includes collaborators from around the world, many of whom were the principal architects of XMPP. It is intended as a next-generation protocol advancing the original goals of Jabber."

== Social Platforms ==
* [https://joindiaspora.com/ Diaspora] - a decentralized social network
* [https://identi.ca/ Identi.ca] - a high-performance Open Source social engine.
* [http://pump.io/ Pump] - a stream server that does most of what people really want from a social network.
* [http://twister.net.co/ Twister] - a decentralized, peer to peer microblogging platform

==Utilities and Misc.==
* [https://sudoroom.org/wiki/Mesh/Firmware/Zeroconf Avahi] - a mDNS responder that allows you to broadcast services
* [http://localwiki.org/ Local Wiki] - create a local wikipedia (eg; http://oaklandwiki.org)
* a module for sensor data (eg; Temperature, Seismic activity, air pollution)
* [http://dev.wlan-si.net/wiki/PiplMesh PiplMesh] - an open source social networking and info portal for wireless networks used as a welcome page when users connect to the network.
* [https://neocities.org/ Neocities] ([https://github.com/neocities/neocities git]) - create free user sites
* [http://crabgrass.riseuplabs.org/ Crabgrass] - a project out of riseup labs, a ruby rails application for community organizing. It's not the easiest to run your own instance, but very easy to sign up to their server ([https://we.riseup.net/ we.riseup.net])

= References =
<references/>

Mesh/Distributed Services

2015-12-11T06:44:12Z

Maxb: /* Protocols */

The [[mesh]] network should provide communication services, so that it offers value to its users beyond mere connectivity to the Internet. What can be done to help it strengthen ties among Oakland residents, and to benefit the community? This wiki page is here to collect ideas about what services could/should be offered.

Services (such as file sharing, email, contacts, calendar, and phone) should be provided based on existing free/open source software. Orientation & setup could be built into the introductory process for new mesh users.

Some general aspects worth considering:
* Security
* Integration into a user account distributed database with master-master replication and low latency (ex. [http://www.datastax.com/resources/whitepapers/benchmarking-top-nosql-databases Cassandra]).

== Active Services ==
The service browser is unfinished, but as we're working on building out the network and setting up services on the network, we can document what we currently have running here for now:

=== Maxb's Debian Server on Banana Pi - maxb-banana-pi.sudomesh.org ===
* Only accessible when connected to peoplesopen.net
* Owncloud: http://maxb-banana-pi.sudomesh.org:8081/
** guest username: thepasswordispassword
** guest password: password
* Etherpad: http://maxb-banana-pi.sudomesh.org:8082/

== Architecture: Centralized & decentralized services ==
A central philosophical and practical consideration is how services will be provided. Do we fundamentally want the mesh to be a centralized entity which offers certain services to all members? Or a platform on which individual members can offer services? Or a hybrid?

As it stands now (summer 2015), the mesh offers some opportunity for individual members to offer services. For instance, it's possible for anybody on the mesh to offer services that are accessible elsewhere on the mesh. Should there be (for instance) a central, community-curated file server? Or should it just be up to anybody who wants to, to offer up file shares?

Are there certain kinds of sharing we want to discourage or prohibit, and if so, what will be the social and technical means for enforcement? How will we respond if people start openly sharing copyrighted music and movies? Proprietary software? Child porn? It's worthwhile to think through these scenarios, as a successful network that lacks any kind of governance would become an attractive resource for those whose illegal activities cannot be pursued in the open on the Internet. (An example of this dynamic: [http://www.seattletimes.com/seattle-news/crime/state-supreme-court-rules-against-backpagecom-in-sex-trafficking-suit/ State Supreme Court rules against Backpage.com in sex-trafficking suit], Seattle Times, Sept. 2015)

==Storage / File Systems==

There are several options for a distributed file system and each have there advantages and disadvantages. The distributed file system can be used to offer file storage or reduce latency across the network.

* [http://opensfs.org/lustre/ Lustre] - Used by sixty percent of the top 100 websites.
** Performance: Amazingly fast! I can assert that Lustre can serve a lot of streams and that encoding speed is not affected by accessing files via Lustre.
** [http://en.wikipedia.org/wiki/POSIX POSIX] compatibility: Very good!. No need to modify applications to use luster.
** Replication, Load Balancing and Fail Over: Very bad!. For replication load balancing we and fail over we need to rely on other software such as virtual IPs and DRDB.
** Installation: The worst!. Impossible to install by mere mortals. Requires a very specific combination of kernel, lustre patches and tweaks to get it working. And current luster patches usually work with old kernels that are incompatible with new hardware/software.

* [https://code.google.com/p/mogilefs/ MogileFS]
** Performance: Good for small files but not usable for medium to large files. This is mostly due to HTTP overhead since all files are send/receive via HTTP requests that encode all data in base64 adding a 33% overhead to each file.
** POXIS compatibility: Non existent. All applications require to be modified to use MogileFS that renders it useless for streaming/encoding since most streaming servers and encoding tools do not understand the protocol.
** Replication and failover out of the box and load balancing can be implemented in the application by accessing more than one tracker at a time.
** Installation: Relatively easy and ready to use packages exist in most distributions. The only difficulty I found was setting the database master-slave to eliminate the single point of failure.

* [http://www.gluster.org/ GlusterFS]
** Performance: Very bad for streaming. I cannot reach more than a few Mbps in a 10Gbps network. Clients and Server CPU skyrockets on heavy writes. For encoding works because the CPU is saturated before the network and I/O.
** POXIS: Almost compatible. The tools I use can access gluster mounts as normal folders in disk but in some edge cases things start causing problems. Check gluster mailing lists and you will see there are a lot of problems.
** Replication, Failover and Load balancing: The best! if they actually worked. Gluster is very new and it has a lot of bugs and performance problems.
** Installation is too easy. The management command line is amazing and setting replicated, striped and distributed volumes among several servers can not be any easier.

([http://stackoverflow.com/questions/916902/lustre-gluster-or-mogilefs-for-video-storage-encoding-and-streaming source of above information])

* [http://hadoop.apache.org/ Hadoop] (HDFS) - slow and has a lot of proprietary derivatives (MapR, GPFS, and [http://gigaom.com/2012/07/11/because-hadoop-isnt-perfect-8-ways-to-replace-hdfs/ other alternatives])
* [http://www.xtreemfs.org/ XtreemFS] - slow and we need more research on it.
* Cassandra File System (CFS) - proprietary software made by DataStax and included in the Enterprise Edition of their software.
* [http://en.wikipedia.org/wiki/Network_File_System Network File Sytem] (NFS) - comparable to Lustre, but the [http://wiki.lustre.org/index.php/NFS_vs._Lustre IO bandwidth doesn't scale].

'''Non-distributed file systems'''
There's the option to use a modern file system with [http://en.wikipedia.org/wiki/Rsync rsync].
[http://rudd-o.com/linux-and-free-software/ways-in-which-zfs-is-better-than-btrfs Comparison of ZFS and BTRFS]
[http://porky.linuxjournal.com:8080/LJ/218/11250.html A Quick Introduction to Modern Filesystems]

==Databases and Servers==

These are decentralized databases and servers that could ultimately be optimized to store data nearest to where people access it. A significant factors with mesh networks, that as "size and complexity continues to grow, mesh networks that contain multiple hops become increasingly vulnerable to problems such as bandwidth degradation, radio interference and network latency.<ref>[http://www.strixsystems.com/products/datasheets/strixwhitepaper_multihop.pdf Solving the Wireless Mesh Multi-Hop Dilemma]</ref>" There are several other methods of improving network latency, but all means should be tested and implemented to improve services.

* [https://cassandra.apache.org/ cassandra] - a decentralized database with asynchronous masterless replication allowing low latency operations for all clients. Cassandra has [http://en.wikipedia.org/wiki/Hadoop Hadoop] integration, with MapReduce support.
* [https://couchdb.apache.org/ CouchDB] - I can tell you that it quickly becomes complicated to write multi-user app with CouchDB. Decent access control means that you need a database per user and likely a few extra databases. You then have to set all of these databases up to synchronize between each other which is further complicated by the limitations on what information is available by the limitations on how synchronization rules and filters can be written. There seem to be no good tools for managing/visualizing these complex relationships so you end up having to roll your own.
* [https://github.com/mirage/irmin irmin] - a distributed database with built-in snapshot, branch and revert mechanisms. (similar to git)
* [http://code.google.com/p/leveldb/ levelDB] - a fast and lightweight key/value database library.
* [http://www.mongodb.org/ mongoDB] - an open-source document database, a NoSQL database. Written in C++.
* [http://nodejs.org/ node.js] - an HTTP server written in javascript.
* [http://pouchdb.com/ PouchDB] - a javascript based couchDB.
* [https://github.com/dominictarr/scuttlebutt scuttlebutt] - a data synchronization protocol, or a peer-to-peer replicable data structure.
* [https://tahoe-lafs.org/trac/tahoe-lafs tahoe-lafs] - a decentralized database.

==Communications==

*[http://radicale.org/ radicale] - a CalDAV (calendar) and CardDAV (contacts) server.
*[http://keithp.com/blogs/calypso/ calypso] - Radicale fork with a git back-end (by Keith Packard of X11 fame)
*[http://villagetelco.org Village telco] - an initiative to build low-cost community telephone network hardware and software that can be set up in minutes anywhere in the world. No mobile phone towers or land lines are required, it uses the internet. It has a Simple Unified Dashboard (SPUD) for mesh networks.
*[https://ripple.com/currency/ Ripple] (XRP) - a math-based crypto-currency designed to work seamlessly with the Internet. Powered by a global network of computers; a fast, direct, and secure way to send payments on the web. '''It can be used to prevent malious attacks on servers.'''
*[http://openbts.org/ OpenBTS] - open source cell phone tower software.
*[http://www.openmama.org/what-is-openmama OpenMAMA] - a high performance middleware agnostic messaging API that interfaces with a variety of message oriented middleware systems
*an encrypted asynchronous messaging system to replace email
*a module to have collaborative documents, voting, and groups (ie. [http://en.wikipedia.org/wiki/Collaborative_software groupware])
** Read information about the [http://mitar.tnode.com/post/73983101095/peer-to-peer-voting-scheme peer-to-peer voting scheme].
*a module for peer to peer file sharing.
*a module for object-orientated tagging, shareable feeds.
*a module for feeds and posts, such as [http://www.trsst.com/ Trsst].
* [http://www.frontlinesms.com/ Frontline SMS] - a free, open-source desktop application that allows you to send texts.

==Mapping==

* [http://nodewatcher.readthedocs.org/en/latest/installation.html NodeWatcher] - an open source network planning, deployment, monitoring and maintanance platform.
* [http://wiki.ninux.org/InstallNodeshot NodeShot] - an easy to use wireless community map server.
* [https://github.com/freifunk/openwifimap-html5 OpenWiFiMap] - a database and map for free network WiFi routers (freifunk and others, too!).
* [https://github.com/libremap LibreMap] - a scalable, global and decentralized router database and map visualization for community networks, such as guifi, ninux, etc.
* [http://tidepools.co Tidepools] - collaborative local mapping software
* [http://ediblecities.org/ Edible Cities] - a food mapping project
* Bulletin Board / Local Classified Ads
** Community Asset Mapping (ex. [http://thepyre.org/wiki/Mycelia Mycelia])

== Protocols ==
* [https://tent.io/ Tent] - a method to store all your data in one place that you control. Instead of your digital life being spread across many services.
* [https://www.docker.io/ Docker] - an open-source project to easily create lightweight, portable, self-sufficient containers from any application.
* [http://maidsafe.net/ MaidSafe] - an encrypted, fully distributed data management service. This network manages static and dynamic data as well as communications. (charges money)
* [https://github.com/telehash/telehash.org/blob/master/v3/intro.md Telehash] - "Telehash is a 100% open, secure mesh networking technology with these design principles: full end-to-end encryption, all the time; strict privacy: no content, identity, or metadata is ever revealed to third parties; maximum app/device compatibility: suitable for embedded, mobile, and web usage; making privacy the easy choice for developers; flexible transport protocols, for compatibility with existing layers; native implementations for the widest possible variety of languages/platforms. The telehash team includes collaborators from around the world, many of whom were the principal architects of XMPP. It is intended as a next-generation protocol advancing the original goals of Jabber."

== Social Platforms ==
* [https://joindiaspora.com/ Diaspora] - a decentralized social network
* [https://identi.ca/ Identi.ca] - a high-performance Open Source social engine.
* [http://pump.io/ Pump] - a stream server that does most of what people really want from a social network.
* [http://twister.net.co/ Twister] - a decentralized, peer to peer microblogging platform

==Utilities and Misc.==
* [https://sudoroom.org/wiki/Mesh/Firmware/Zeroconf Avahi] - a mDNS responder that allows you to broadcast services
* [http://localwiki.org/ Local Wiki] - create a local wikipedia (eg; http://oaklandwiki.org)
* a module for sensor data (eg; Temperature, Seismic activity, air pollution)
* [http://dev.wlan-si.net/wiki/PiplMesh PiplMesh] - an open source social networking and info portal for wireless networks used as a welcome page when users connect to the network.
* [https://neocities.org/ Neocities] ([https://github.com/neocities/neocities git]) - create free user sites
* [http://crabgrass.riseuplabs.org/ Crabgrass] - a project out of riseup labs, a ruby rails application for community organizing. It's not the easiest to run your own instance, but very easy to sign up to their server ([https://we.riseup.net/ we.riseup.net])

= References =
<references/>

Mesh/Distributed Services

2015-12-11T06:43:53Z

Maxb: /* Protocols */ Adding telehash

The [[mesh]] network should provide communication services, so that it offers value to its users beyond mere connectivity to the Internet. What can be done to help it strengthen ties among Oakland residents, and to benefit the community? This wiki page is here to collect ideas about what services could/should be offered.

Services (such as file sharing, email, contacts, calendar, and phone) should be provided based on existing free/open source software. Orientation & setup could be built into the introductory process for new mesh users.

Some general aspects worth considering:
* Security
* Integration into a user account distributed database with master-master replication and low latency (ex. [http://www.datastax.com/resources/whitepapers/benchmarking-top-nosql-databases Cassandra]).

== Active Services ==
The service browser is unfinished, but as we're working on building out the network and setting up services on the network, we can document what we currently have running here for now:

=== Maxb's Debian Server on Banana Pi - maxb-banana-pi.sudomesh.org ===
* Only accessible when connected to peoplesopen.net
* Owncloud: http://maxb-banana-pi.sudomesh.org:8081/
** guest username: thepasswordispassword
** guest password: password
* Etherpad: http://maxb-banana-pi.sudomesh.org:8082/

== Architecture: Centralized & decentralized services ==
A central philosophical and practical consideration is how services will be provided. Do we fundamentally want the mesh to be a centralized entity which offers certain services to all members? Or a platform on which individual members can offer services? Or a hybrid?

As it stands now (summer 2015), the mesh offers some opportunity for individual members to offer services. For instance, it's possible for anybody on the mesh to offer services that are accessible elsewhere on the mesh. Should there be (for instance) a central, community-curated file server? Or should it just be up to anybody who wants to, to offer up file shares?

Are there certain kinds of sharing we want to discourage or prohibit, and if so, what will be the social and technical means for enforcement? How will we respond if people start openly sharing copyrighted music and movies? Proprietary software? Child porn? It's worthwhile to think through these scenarios, as a successful network that lacks any kind of governance would become an attractive resource for those whose illegal activities cannot be pursued in the open on the Internet. (An example of this dynamic: [http://www.seattletimes.com/seattle-news/crime/state-supreme-court-rules-against-backpagecom-in-sex-trafficking-suit/ State Supreme Court rules against Backpage.com in sex-trafficking suit], Seattle Times, Sept. 2015)

==Storage / File Systems==

There are several options for a distributed file system and each have there advantages and disadvantages. The distributed file system can be used to offer file storage or reduce latency across the network.

* [http://opensfs.org/lustre/ Lustre] - Used by sixty percent of the top 100 websites.
** Performance: Amazingly fast! I can assert that Lustre can serve a lot of streams and that encoding speed is not affected by accessing files via Lustre.
** [http://en.wikipedia.org/wiki/POSIX POSIX] compatibility: Very good!. No need to modify applications to use luster.
** Replication, Load Balancing and Fail Over: Very bad!. For replication load balancing we and fail over we need to rely on other software such as virtual IPs and DRDB.
** Installation: The worst!. Impossible to install by mere mortals. Requires a very specific combination of kernel, lustre patches and tweaks to get it working. And current luster patches usually work with old kernels that are incompatible with new hardware/software.

* [https://code.google.com/p/mogilefs/ MogileFS]
** Performance: Good for small files but not usable for medium to large files. This is mostly due to HTTP overhead since all files are send/receive via HTTP requests that encode all data in base64 adding a 33% overhead to each file.
** POXIS compatibility: Non existent. All applications require to be modified to use MogileFS that renders it useless for streaming/encoding since most streaming servers and encoding tools do not understand the protocol.
** Replication and failover out of the box and load balancing can be implemented in the application by accessing more than one tracker at a time.
** Installation: Relatively easy and ready to use packages exist in most distributions. The only difficulty I found was setting the database master-slave to eliminate the single point of failure.

* [http://www.gluster.org/ GlusterFS]
** Performance: Very bad for streaming. I cannot reach more than a few Mbps in a 10Gbps network. Clients and Server CPU skyrockets on heavy writes. For encoding works because the CPU is saturated before the network and I/O.
** POXIS: Almost compatible. The tools I use can access gluster mounts as normal folders in disk but in some edge cases things start causing problems. Check gluster mailing lists and you will see there are a lot of problems.
** Replication, Failover and Load balancing: The best! if they actually worked. Gluster is very new and it has a lot of bugs and performance problems.
** Installation is too easy. The management command line is amazing and setting replicated, striped and distributed volumes among several servers can not be any easier.

([http://stackoverflow.com/questions/916902/lustre-gluster-or-mogilefs-for-video-storage-encoding-and-streaming source of above information])

* [http://hadoop.apache.org/ Hadoop] (HDFS) - slow and has a lot of proprietary derivatives (MapR, GPFS, and [http://gigaom.com/2012/07/11/because-hadoop-isnt-perfect-8-ways-to-replace-hdfs/ other alternatives])
* [http://www.xtreemfs.org/ XtreemFS] - slow and we need more research on it.
* Cassandra File System (CFS) - proprietary software made by DataStax and included in the Enterprise Edition of their software.
* [http://en.wikipedia.org/wiki/Network_File_System Network File Sytem] (NFS) - comparable to Lustre, but the [http://wiki.lustre.org/index.php/NFS_vs._Lustre IO bandwidth doesn't scale].

'''Non-distributed file systems'''
There's the option to use a modern file system with [http://en.wikipedia.org/wiki/Rsync rsync].
[http://rudd-o.com/linux-and-free-software/ways-in-which-zfs-is-better-than-btrfs Comparison of ZFS and BTRFS]
[http://porky.linuxjournal.com:8080/LJ/218/11250.html A Quick Introduction to Modern Filesystems]

==Databases and Servers==

These are decentralized databases and servers that could ultimately be optimized to store data nearest to where people access it. A significant factors with mesh networks, that as "size and complexity continues to grow, mesh networks that contain multiple hops become increasingly vulnerable to problems such as bandwidth degradation, radio interference and network latency.<ref>[http://www.strixsystems.com/products/datasheets/strixwhitepaper_multihop.pdf Solving the Wireless Mesh Multi-Hop Dilemma]</ref>" There are several other methods of improving network latency, but all means should be tested and implemented to improve services.

* [https://cassandra.apache.org/ cassandra] - a decentralized database with asynchronous masterless replication allowing low latency operations for all clients. Cassandra has [http://en.wikipedia.org/wiki/Hadoop Hadoop] integration, with MapReduce support.
* [https://couchdb.apache.org/ CouchDB] - I can tell you that it quickly becomes complicated to write multi-user app with CouchDB. Decent access control means that you need a database per user and likely a few extra databases. You then have to set all of these databases up to synchronize between each other which is further complicated by the limitations on what information is available by the limitations on how synchronization rules and filters can be written. There seem to be no good tools for managing/visualizing these complex relationships so you end up having to roll your own.
* [https://github.com/mirage/irmin irmin] - a distributed database with built-in snapshot, branch and revert mechanisms. (similar to git)
* [http://code.google.com/p/leveldb/ levelDB] - a fast and lightweight key/value database library.
* [http://www.mongodb.org/ mongoDB] - an open-source document database, a NoSQL database. Written in C++.
* [http://nodejs.org/ node.js] - an HTTP server written in javascript.
* [http://pouchdb.com/ PouchDB] - a javascript based couchDB.
* [https://github.com/dominictarr/scuttlebutt scuttlebutt] - a data synchronization protocol, or a peer-to-peer replicable data structure.
* [https://tahoe-lafs.org/trac/tahoe-lafs tahoe-lafs] - a decentralized database.

==Communications==

*[http://radicale.org/ radicale] - a CalDAV (calendar) and CardDAV (contacts) server.
*[http://keithp.com/blogs/calypso/ calypso] - Radicale fork with a git back-end (by Keith Packard of X11 fame)
*[http://villagetelco.org Village telco] - an initiative to build low-cost community telephone network hardware and software that can be set up in minutes anywhere in the world. No mobile phone towers or land lines are required, it uses the internet. It has a Simple Unified Dashboard (SPUD) for mesh networks.
*[https://ripple.com/currency/ Ripple] (XRP) - a math-based crypto-currency designed to work seamlessly with the Internet. Powered by a global network of computers; a fast, direct, and secure way to send payments on the web. '''It can be used to prevent malious attacks on servers.'''
*[http://openbts.org/ OpenBTS] - open source cell phone tower software.
*[http://www.openmama.org/what-is-openmama OpenMAMA] - a high performance middleware agnostic messaging API that interfaces with a variety of message oriented middleware systems
*an encrypted asynchronous messaging system to replace email
*a module to have collaborative documents, voting, and groups (ie. [http://en.wikipedia.org/wiki/Collaborative_software groupware])
** Read information about the [http://mitar.tnode.com/post/73983101095/peer-to-peer-voting-scheme peer-to-peer voting scheme].
*a module for peer to peer file sharing.
*a module for object-orientated tagging, shareable feeds.
*a module for feeds and posts, such as [http://www.trsst.com/ Trsst].
* [http://www.frontlinesms.com/ Frontline SMS] - a free, open-source desktop application that allows you to send texts.

==Mapping==

* [http://nodewatcher.readthedocs.org/en/latest/installation.html NodeWatcher] - an open source network planning, deployment, monitoring and maintanance platform.
* [http://wiki.ninux.org/InstallNodeshot NodeShot] - an easy to use wireless community map server.
* [https://github.com/freifunk/openwifimap-html5 OpenWiFiMap] - a database and map for free network WiFi routers (freifunk and others, too!).
* [https://github.com/libremap LibreMap] - a scalable, global and decentralized router database and map visualization for community networks, such as guifi, ninux, etc.
* [http://tidepools.co Tidepools] - collaborative local mapping software
* [http://ediblecities.org/ Edible Cities] - a food mapping project
* Bulletin Board / Local Classified Ads
** Community Asset Mapping (ex. [http://thepyre.org/wiki/Mycelia Mycelia])

== Protocols ==
* [https://tent.io/ Tent] - a method to store all your data in one place that you control. Instead of your digital life being spread across many services.
* [https://www.docker.io/ Docker] - an open-source project to easily create lightweight, portable, self-sufficient containers from any application.
* [http://maidsafe.net/ MaidSafe] - an encrypted, fully distributed data management service. This network manages static and dynamic data as well as communications. (charges money)
* [https://github.com/telehash/telehash.org/blob/master/v3/intro.md Telehash] - "Telehash is a 100% open, secure mesh networking technology with these design principles: full end-to-end encryption, all the time; strict privacy: no content, identity, or metadata is ever revealed to third parties; maximum app/device compatibility: suitable for embedded, mobile, and web usage; making privacy the easy choice for developers; flexible transport protocols, for compatibility with existing layers; native implementations for the widest possible variety of languages/platforms. The telehash team includes collaborators from around the world, many of whom were the principal architects of XMPP. It is intended as a next-generation protocol advancing the original goals of Jabber.

== Social Platforms ==
* [https://joindiaspora.com/ Diaspora] - a decentralized social network
* [https://identi.ca/ Identi.ca] - a high-performance Open Source social engine.
* [http://pump.io/ Pump] - a stream server that does most of what people really want from a social network.
* [http://twister.net.co/ Twister] - a decentralized, peer to peer microblogging platform

==Utilities and Misc.==
* [https://sudoroom.org/wiki/Mesh/Firmware/Zeroconf Avahi] - a mDNS responder that allows you to broadcast services
* [http://localwiki.org/ Local Wiki] - create a local wikipedia (eg; http://oaklandwiki.org)
* a module for sensor data (eg; Temperature, Seismic activity, air pollution)
* [http://dev.wlan-si.net/wiki/PiplMesh PiplMesh] - an open source social networking and info portal for wireless networks used as a welcome page when users connect to the network.
* [https://neocities.org/ Neocities] ([https://github.com/neocities/neocities git]) - create free user sites
* [http://crabgrass.riseuplabs.org/ Crabgrass] - a project out of riseup labs, a ruby rails application for community organizing. It's not the easiest to run your own instance, but very easy to sign up to their server ([https://we.riseup.net/ we.riseup.net])

= References =
<references/>

Mesh/Distributed Services

2015-10-26T22:15:24Z

Maxb: Adding active services section

The [[mesh]] network should provide communication services, so that it offers value to its users beyond mere connectivity to the Internet. What can be done to help it strengthen ties among Oakland residents, and to benefit the community? This wiki page is here to collect ideas about what services could/should be offered.

Services (such as file sharing, email, contacts, calendar, and phone) should be provided based on existing free/open source software. Orientation & setup could be built into the introductory process for new mesh users.

Some general aspects worth considering:
* Security
* Integration into a user account distributed database with master-master replication and low latency (ex. [http://www.datastax.com/resources/whitepapers/benchmarking-top-nosql-databases Cassandra]).

== Active Services ==
The service browser is unfinished, but as we're working on building out the network and setting up services on the network, we can document what we currently have running here for now:

=== Maxb's Debian Server on Banana Pi - maxb-banana-pi.sudomesh.org ===
* Only accessible when connected to peoplesopen.net
* Owncloud: http://maxb-banana-pi.sudomesh.org:8081/
** guest username: thepasswordispassword
** guest password: password
* Etherpad: http://maxb-banana-pi.sudomesh.org:8082/

== Architecture: Centralized & decentralized services ==
A central philosophical and practical consideration is how services will be provided. Do we fundamentally want the mesh to be a centralized entity which offers certain services to all members? Or a platform on which individual members can offer services? Or a hybrid?

As it stands now (summer 2015), the mesh offers some opportunity for individual members to offer services. For instance, it's possible for anybody on the mesh to offer services that are accessible elsewhere on the mesh. Should there be (for instance) a central, community-curated file server? Or should it just be up to anybody who wants to, to offer up file shares?

Are there certain kinds of sharing we want to discourage or prohibit, and if so, what will be the social and technical means for enforcement? How will we respond if people start openly sharing copyrighted music and movies? Proprietary software? Child porn? It's worthwhile to think through these scenarios, as a successful network that lacks any kind of governance would become an attractive resource for those whose illegal activities cannot be pursued in the open on the Internet. (An example of this dynamic: [http://www.seattletimes.com/seattle-news/crime/state-supreme-court-rules-against-backpagecom-in-sex-trafficking-suit/ State Supreme Court rules against Backpage.com in sex-trafficking suit], Seattle Times, Sept. 2015)

==Storage / File Systems==

There are several options for a distributed file system and each have there advantages and disadvantages. The distributed file system can be used to offer file storage or reduce latency across the network.

* [http://opensfs.org/lustre/ Lustre] - Used by sixty percent of the top 100 websites.
** Performance: Amazingly fast! I can assert that Lustre can serve a lot of streams and that encoding speed is not affected by accessing files via Lustre.
** [http://en.wikipedia.org/wiki/POSIX POSIX] compatibility: Very good!. No need to modify applications to use luster.
** Replication, Load Balancing and Fail Over: Very bad!. For replication load balancing we and fail over we need to rely on other software such as virtual IPs and DRDB.
** Installation: The worst!. Impossible to install by mere mortals. Requires a very specific combination of kernel, lustre patches and tweaks to get it working. And current luster patches usually work with old kernels that are incompatible with new hardware/software.

* [https://code.google.com/p/mogilefs/ MogileFS]
** Performance: Good for small files but not usable for medium to large files. This is mostly due to HTTP overhead since all files are send/receive via HTTP requests that encode all data in base64 adding a 33% overhead to each file.
** POXIS compatibility: Non existent. All applications require to be modified to use MogileFS that renders it useless for streaming/encoding since most streaming servers and encoding tools do not understand the protocol.
** Replication and failover out of the box and load balancing can be implemented in the application by accessing more than one tracker at a time.
** Installation: Relatively easy and ready to use packages exist in most distributions. The only difficulty I found was setting the database master-slave to eliminate the single point of failure.

* [http://www.gluster.org/ GlusterFS]
** Performance: Very bad for streaming. I cannot reach more than a few Mbps in a 10Gbps network. Clients and Server CPU skyrockets on heavy writes. For encoding works because the CPU is saturated before the network and I/O.
** POXIS: Almost compatible. The tools I use can access gluster mounts as normal folders in disk but in some edge cases things start causing problems. Check gluster mailing lists and you will see there are a lot of problems.
** Replication, Failover and Load balancing: The best! if they actually worked. Gluster is very new and it has a lot of bugs and performance problems.
** Installation is too easy. The management command line is amazing and setting replicated, striped and distributed volumes among several servers can not be any easier.

([http://stackoverflow.com/questions/916902/lustre-gluster-or-mogilefs-for-video-storage-encoding-and-streaming source of above information])

* [http://hadoop.apache.org/ Hadoop] (HDFS) - slow and has a lot of proprietary derivatives (MapR, GPFS, and [http://gigaom.com/2012/07/11/because-hadoop-isnt-perfect-8-ways-to-replace-hdfs/ other alternatives])
* [http://www.xtreemfs.org/ XtreemFS] - slow and we need more research on it.
* Cassandra File System (CFS) - proprietary software made by DataStax and included in the Enterprise Edition of their software.
* [http://en.wikipedia.org/wiki/Network_File_System Network File Sytem] (NFS) - comparable to Lustre, but the [http://wiki.lustre.org/index.php/NFS_vs._Lustre IO bandwidth doesn't scale].

'''Non-distributed file systems'''
There's the option to use a modern file system with [http://en.wikipedia.org/wiki/Rsync rsync].
[http://rudd-o.com/linux-and-free-software/ways-in-which-zfs-is-better-than-btrfs Comparison of ZFS and BTRFS]
[http://porky.linuxjournal.com:8080/LJ/218/11250.html A Quick Introduction to Modern Filesystems]

==Databases and Servers==

These are decentralized databases and servers that could ultimately be optimized to store data nearest to where people access it. A significant factors with mesh networks, that as "size and complexity continues to grow, mesh networks that contain multiple hops become increasingly vulnerable to problems such as bandwidth degradation, radio interference and network latency.<ref>[http://www.strixsystems.com/products/datasheets/strixwhitepaper_multihop.pdf Solving the Wireless Mesh Multi-Hop Dilemma]</ref>" There are several other methods of improving network latency, but all means should be tested and implemented to improve services.

* [https://cassandra.apache.org/ cassandra] - a decentralized database with asynchronous masterless replication allowing low latency operations for all clients. Cassandra has [http://en.wikipedia.org/wiki/Hadoop Hadoop] integration, with MapReduce support.
* [https://couchdb.apache.org/ CouchDB] - I can tell you that it quickly becomes complicated to write multi-user app with CouchDB. Decent access control means that you need a database per user and likely a few extra databases. You then have to set all of these databases up to synchronize between each other which is further complicated by the limitations on what information is available by the limitations on how synchronization rules and filters can be written. There seem to be no good tools for managing/visualizing these complex relationships so you end up having to roll your own.
* [https://github.com/mirage/irmin irmin] - a distributed database with built-in snapshot, branch and revert mechanisms. (similar to git)
* [http://code.google.com/p/leveldb/ levelDB] - a fast and lightweight key/value database library.
* [http://www.mongodb.org/ mongoDB] - an open-source document database, a NoSQL database. Written in C++.
* [http://nodejs.org/ node.js] - an HTTP server written in javascript.
* [http://pouchdb.com/ PouchDB] - a javascript based couchDB.
* [https://github.com/dominictarr/scuttlebutt scuttlebutt] - a data synchronization protocol, or a peer-to-peer replicable data structure.
* [https://tahoe-lafs.org/trac/tahoe-lafs tahoe-lafs] - a decentralized database.

==Communications==

*[http://radicale.org/ radicale] - a CalDAV (calendar) and CardDAV (contacts) server.
*[http://keithp.com/blogs/calypso/ calypso] - Radicale fork with a git back-end (by Keith Packard of X11 fame)
*[http://villagetelco.org Village telco] - an initiative to build low-cost community telephone network hardware and software that can be set up in minutes anywhere in the world. No mobile phone towers or land lines are required, it uses the internet. It has a Simple Unified Dashboard (SPUD) for mesh networks.
*[https://ripple.com/currency/ Ripple] (XRP) - a math-based crypto-currency designed to work seamlessly with the Internet. Powered by a global network of computers; a fast, direct, and secure way to send payments on the web. '''It can be used to prevent malious attacks on servers.'''
*[http://openbts.org/ OpenBTS] - open source cell phone tower software.
*[http://www.openmama.org/what-is-openmama OpenMAMA] - a high performance middleware agnostic messaging API that interfaces with a variety of message oriented middleware systems
*an encrypted asynchronous messaging system to replace email
*a module to have collaborative documents, voting, and groups (ie. [http://en.wikipedia.org/wiki/Collaborative_software groupware])
** Read information about the [http://mitar.tnode.com/post/73983101095/peer-to-peer-voting-scheme peer-to-peer voting scheme].
*a module for peer to peer file sharing.
*a module for object-orientated tagging, shareable feeds.
*a module for feeds and posts, such as [http://www.trsst.com/ Trsst].
* [http://www.frontlinesms.com/ Frontline SMS] - a free, open-source desktop application that allows you to send texts.

==Mapping==

* [http://nodewatcher.readthedocs.org/en/latest/installation.html NodeWatcher] - an open source network planning, deployment, monitoring and maintanance platform.
* [http://wiki.ninux.org/InstallNodeshot NodeShot] - an easy to use wireless community map server.
* [https://github.com/freifunk/openwifimap-html5 OpenWiFiMap] - a database and map for free network WiFi routers (freifunk and others, too!).
* [https://github.com/libremap LibreMap] - a scalable, global and decentralized router database and map visualization for community networks, such as guifi, ninux, etc.
* [http://tidepools.co Tidepools] - collaborative local mapping software
* [http://ediblecities.org/ Edible Cities] - a food mapping project
* Bulletin Board / Local Classified Ads
** Community Asset Mapping (ex. [http://thepyre.org/wiki/Mycelia Mycelia])

== Protocols ==
* [https://tent.io/ Tent] - a method to store all your data in one place that you control. Instead of your digital life being spread across many services.
* [https://www.docker.io/ Docker] - an open-source project to easily create lightweight, portable, self-sufficient containers from any application.
* [http://maidsafe.net/ MaidSafe] - an encrypted, fully distributed data management service. This network manages static and dynamic data as well as communications. (charges money)

== Social Platforms ==
* [https://joindiaspora.com/ Diaspora] - a decentralized social network
* [https://identi.ca/ Identi.ca] - a high-performance Open Source social engine.
* [http://pump.io/ Pump] - a stream server that does most of what people really want from a social network.
* [http://twister.net.co/ Twister] - a decentralized, peer to peer microblogging platform

==Utilities and Misc.==
* [https://sudoroom.org/wiki/Mesh/Firmware/Zeroconf Avahi] - a mDNS responder that allows you to broadcast services
* [http://localwiki.org/ Local Wiki] - create a local wikipedia (eg; http://oaklandwiki.org)
* a module for sensor data (eg; Temperature, Seismic activity, air pollution)
* [http://dev.wlan-si.net/wiki/PiplMesh PiplMesh] - an open source social networking and info portal for wireless networks used as a welcome page when users connect to the network.
* [https://neocities.org/ Neocities] ([https://github.com/neocities/neocities git]) - create free user sites
* [http://crabgrass.riseuplabs.org/ Crabgrass] - a project out of riseup labs, a ruby rails application for community organizing. It's not the easiest to run your own instance, but very easy to sign up to their server ([https://we.riseup.net/ we.riseup.net])

= References =
<references/>

Mesh/Blog

2015-10-26T19:33:10Z

Maxb: /* Alpha Testing Network */

<startfeed />
=Alpha Testing Network=
We've been doing alpha testing on our what's looking to be the network v0.2 for the last couple months. A lot of our firmware/etc code has been tightened up and we're starting to get good results. There are obviously a lot of metrics that are worth considering when evaluating the success of a network, but uptime is a good start, and we're finally getting 90%+ uptime on all of our nodes. That might not sound impressive, but these are pieces of hardware that are hosted at various folks houses, so coordinating the reboot of a router that's in someone's living room can be a challenging ordeal. For those that are interested, graphs from our monitoring server are available here:

Smokeping (latency graphs) http://monitor.sudomesh.org/smokeping/smokeping.cgi?target=Mesh

and

Cacti (traffic and some hardware measurements): http://monitor.sudomesh.org/cacti/graph_view.php?action=tree&tree_id=1&leaf_id=45

[[File:Sudomesh cacti 10.26.15.png|framed|Cacti Graph of PeoplesOpen.net traffic for 10/26/2015]]
[[File:Sudomesh_cacti_graph_sept-oct.2015.png|framed|Cacti Graph of PeoplesOpen.net traffic for Sept-Oct 2015]]

We've been uploading the latest versions of our firmware as binaries to:

http://builds.sudomesh.org/builds

Home Node firmwares are for TP-Link wdr3500, 3600, and 4300 as well as MyNet N600 and N750 routers.
Extender Node firmwares are known to mostly work for Ubiquiti Picostation M2, Bullet M2 and M5, Powerbridge M2 and M5, and Nanostation M2 and M5.

We're in need of a handful of new folks to host home nodes and possibly also extender nodes. To be a good home node host, we ask that you be:
* Willing to share some amount of your bandwidth. It doesn't have to be a lot, but 1-2mbps can go a long way for someone who doesn't otherwise have any connectivity.
* Reliably in contact so that we can ask you to do simple things like reboot the router (hopefully rarely if at all), and check connectivity
* Interested in providing some feedback as to how you think the experience is and how it could be improved

To be an extender node host we ask that you be all those things and also have access to your roof and/or another high point on your house/building/etc and be willing to mount a (pretty small) antenna there and run an ethernet cable from your home node (probably near your router) to that roof location.

If that sounds like you, get in touch: https://sudoroom.org/wiki/Mesh#Join_Us

At the moment, we're providing the hardware, so you'll be hosting $50-$150 worth of equipment which in many cases can significantly improve coverage in your own home!

=Building out our backbone...=

After a dark fall of struggling with various issues with batman-adv and our tunnels, our coding crew decided to switch to [http://en.wikipedia.org/wiki/Babel_%28protocol%29 Babel]. While integrating the new protocol into our firmware, we've been actively researching potential sources of bandwidth to feed the network and [[Rooftop_Dish_Antenna_Mount|mounting rooftop nodes]] in strategic locations. Every Sunday, we've been building out the backbone of our network from Kensington to West Oakland - contact us if you've got a spot with great line-of-sight!

Our first major node in Kensington has excellent line-of-sight to both Oakland and Richmond:

[[File:20141130 160516.jpg|thumb|center| 400px | Sudomesh dish mount with Oakland in the distance]]

[[File:20141130 160446.jpg|thumb|center| 400px |Sudomesh dish with Richmond in the distance]]

If you're interested in helping out, we're always looking for [[Mesh/Wishlist|donations]] of gear and equipment, as well as committed volunteers and [https://gratipay.com/sudomesh financial support] (even 25 cents a week adds up as we prepare to launch).

[[File:20141130 160500.jpg|thumb| center | 500px |Sudomesh dish mount and happy ethernet wire/RJ45 termination.]]

Here's to growing a network from the ground up, together!

=We're meshing at the Omni!=

It's been a crazily active summer - apologies for the lack of updates! Sudo Room (and by extension, Sudo Mesh) has relocated to the [http://omni-oakland.org Omni Oakland Commons] at 4799 Shattuck. We're excited to be a founding member collective among an array of groups that have moved in together to create a radical commons in Oakland.

[[File:Omnicoversm.png|framed|center|The Omni building and logo]]

If you've been wanting to plug in and help out, or simply reconnect to the group, tonight is a great night to come by and check out the new space!

'''Announcements'''
* We'll be having our monthly general meeting today, starting at 7:30pm at Sudo Room. Please add to the agenda! - https://pad.riseup.net/p/sudomesh
* Juul, MaxB and Alex have been working hard on crushing bugs and levelling up our mesh firmware. We've deployed a test network within the Omni building and they are successfully meshing as I type! \o/
* We've procured a 75 foot antenna tower that will be mounted in West Oakland to become a core relay spot for routing traffic on the mesh.
* Noemie has put together a fantastic sudomesh / people's open net video and is currently soliciting feedback. Check it out @ https://www.youtube.com/watch?v=qva1SQSBDyE
* Paige made a rad flyer design and two versions of the flyer for a) general ways to participate in the project and b) promoting upcoming info sessions. Check them out here: https://sudoroom.org/wiki/Mesh/Flyers
* Stickers!! The round 'Mesh the Planet' and rectangular PeoplesOpen.Net stickers have been printed and can be procured at sudoroom (atio the white shelves next to the staircase) and/or one of our Tuesday/Thursday meetups!

'''Code - so much code this summer!!'''
* Juul created ipk-builder: https://github.com/sudomesh/ipk-builder
* MaxB, Ron, and Juul have been updating the service browser: https://github.com/sudomesh/service-browser
* Juul, MaxB, and Alex reengineered the node-configurator: https://github.com/sudomesh/makenode
* MaxB, Alex and Matt fixed the exitnode
* MaxB created sudowrt-firmware-images for temporary storage of firmware builds
* Matt added a patch to sudowrt-firmware
* Alex and MaxB have been fixing our fork of tunneldigger
* MaxB fixed sudowrt-packages
* Juul updated ubi-flasher
* Juul added fixes to meshnode-database
* Matt created svg-animations for mesh presentations

'''Wiki'''
* Tunabananas created [[Mesh/Flyers]] and uploaded Paige's flyers
* ChrisJ updated [[Mesh/Monitoring]] and created [[Mesh/Icinga]]
* Matt added instructions to [[Mesh/Firmware/Flash]]
* Jul added to [[Mesh/Hardware]] Support
* GMeader created the page [[Mesh/San Francisco]] and added to [[Mesh/Marketing]]
* MaxB added sticker images to [[Mesh/Stickers]]
* ChrisJ created [[Mesh/Sensu]]
* Tunabananas added recent research on broadband access in Oakland to [[Mesh/Oakland]]
* Tunabananas added some months worth of meeting minutes to [[Mesh/Minutes]]
* Jwentwistle added a bunch of documentation to [[Mesh/BATMAN-adv]]
* Jwentwistle and Tunabananas cleaned up the main [[Mesh]] page!
* Jwentwistle moved Mesh/MeshApps primarily to [[Mesh/Distributed Services]]
* Jwentwistle created and added slides to [[Mesh/Presentation]]
* Jwentwistle created [[Mesh/User Guide]]
* Jwentwistle created [[Mesh/Technical Overview]]
* MaxB checked some stuff out
* Matt added some diagrams to [[Mesh/Diagrams]]
* Jwentwistle added bandwidth shaping details to [[Mesh/Firmware]]
* MaxB added some ideas for our box of crappy routers to [[Mesh/Inventory]]
* Tunabananas wrote a new post on [[Mesh/Blog]]
* Aep added to [[Mesh/MeshApps]]

'''To Dos:'''
* Test current mesh setup in the Omni building
* Create online ordering system and shipping label automation
* Create 'How to Care for Your Node' guides
* Outreach to spaces that can host info sessions and presentations
* Work on local apps and services that will run on the mesh!
* More at: https://sudoroom.org/wiki/Mesh/ToDos
** Please update the list above with specific tasks!

'''Help Out!'''
* Come by our weekly hacknights, Tuesdays and Thursdays starting at 7:30pm at Sudo Room <https://sudoroom.org>
* Contribute research, ideas, designs to our wiki: https://sudomesh.org
* Contribute to the code: https://github.com/sudomesh
* Donate hardware and equipment! <https://sudoroom.org/wiki/Mesh/Wishlist>
* Give a small weekly donation: https://www.gittip.com/sudomesh

'''Recommended Reading'''
* Oakland's Sudo Mesh looks to counter censorship and the digital divide with a mesh network: http://techpresident.com/news/25200/oakland-sudo-mesh-counter-censorship-digital-divide-mesh-net
* It's Time for Open, Shared Home Wi-Fi (Re/Code): http://recode.net/2014/08/05/its-time-for-shared-open-home-wi-fi/

=Mesh Hackathon @ The Omni, July 5-7!=
This weekend, Sudo Mesh is having our first mesh hackathon at sudo room's new location in the Omni! Join us at 4799 at any point this weekend, starting at noon until we tire today[1], and noon on Sunday and Monday. We'll have rotating orientation sessions every hour on the hour both Sunday and Monday, so feel free to come by even if you're brand new to the project!

[[File:Sudoroomfirstallnighter.jpg|center|First all-nighter in the new sudo room!]]

Here are some of the things we plan to work on:
* Designing [[Mesh/Diagrams|network diagrams]] and educational curricula.
* Debugging exit node issues.
* Setting up [[Network/Reboot|our network at the Omni]], the new home of sudo room!
* [[Mesh/Communities|Outreach]] to various community stakeholders and interest groups relevant to the mesh (eg; rock climbers! Ham radio enthusiasts! Librarians!)
* Research and test deployment of [[Mesh/MeshApps|mesh apps]].
* Getting our books in order (finances, [[Mesh/Blog|blog]], calendar, 501c3 app, etc;)
* Making [[Mesh/Swag|swag]] ([[Mesh/Stickers|stickers]]! buttons! whatever you can think of!).

Whether you're a core team member, an occasional collaborator, or just interested in learning more about the mesh, you are welcome!

[1] We are being powered by [[Sudomate]].

--[[User:Tunabananas|Tunabananas]]

=Developer Launch!=
As of last night, we've officially launched version 0.1.0 of the mesh firmware, a.k.a. Snow Crash.

[[File:Snowcrash.png|center|Snow Crash login screen]]

The plan is to have ~20 people with networking skills run nodes from their homes for 1-2 months and report any remaining issues. We'll then fix those bugs and do a wider release of ~60 more nodes.

What's currently working:

1. Sharing limited Internet bandwidth with peoplesopen.net
2. Private access point with no bandwidth limit and mesh access
3. Automatic node meshing with batman-adv
4. Simplified web admin interface that lets node-owners change bandwidth sharing settings and passwords.
5. Automated configuration of new nodes using easy web interface.
6. Automatic printing of stickers with instructions and default generated passwords.

To those of you who have already taken nodes home, here are a few notes:

1. sudo mesh has root access to your nodes since we manage updates per default. If you want to manage your own node and don't want sudo mesh to have access, you can disable our root access by removing /etc/dropbear/authorized_keys on your node.

2. Please report any bugs on our github. If you know which repository the bug pertains to, then go to the issue tracker for that repository. If you aren't sure, then just add the bug here: https://github.com/sudomesh/sudowrt-firmware/issues

A compiled version of the firmware is available here: http://build.sudomesh.org:8080/latest_images/atheros/

Keep in mind that the nodes have to be configured using the node-configurator after being flashed with that firmware and that the firmware only trusts sudomesh SSL certificates. We'll release a less secure version for developers who just want to play around as soon as possible. For now you can configure your nodes at sudo room with the help of one of the core team.

In the following is a list of the repositories directly relevant to this release of the firmware. All of these repositories have been tagged with "sudowrt-0.1.0" so you can get the exact versions used in the release.

*The sudowrt firmware and build scripts (based on openwrt and the work of wlan slovenja): https://github.com/sudomesh/sudowrt-firmware
*The sudowrt packages repository: https://github.com/sudomesh/sudowrt-packages
*The web admin interface: https://github.com/sudomesh/luci-app-peopleswifi
*The mDNS and DNS-SD client: https://github.com/sudomesh/mdnssd-min
*The node database: https://github.com/sudomesh/node-database
*The node configurator: https://github.com/sudomesh/node-configurator
*Sticker printing support for the node configurator: https://github.com/sudomesh/ql570
*The node configurator client: https://github.com/sudomesh/node-configurator-client
*The wlan slovenja tunneldigger (very slightly modified): https://github.com/sudomesh/tunneldigger

Mesh the planet!

--via [[User:Juul|Juul]]

=How to Participate: All Hands on Deck!=
We are always excited to have new volunteers join the team! From designing flyers to developing software, doing research and documenting what you learn, fixing broken hardware to hitting the streets and spreading the word, there's something for everybody who wants to participate.

We meet weekly on Thursday evenings starting at 7:30pm at [https://sudoroom.org Sudo Room], your friendly neighborhood hackerspace. Come on by and jump in!

You can also participate online via [https://lists.sudoroom.org/listinfo/mesh our mailing list], our [http://webchat.freenode.net/?channels=peoplesopen.net chat room], contributing to [https://github.com/sudomesh our code on Github], and adding to this very wiki.

Donations are always appreciated and keep us sustainable. We accept donations [https://gittip.com/sudomesh via Gittip] (anonymous weekly micropayments), through [http://blockchain.info/address/12RxU4DpLpdWcmEBn7Tj325CCXBwt5i9Hc Bitcoin], and in-person at our weekly meetings. Sudo Mesh is currently in the process of acquiring non-profit status, so your donations will be retroactively tax-deductible. If you'd like to donate materials directly, [https://sudoroom.org/wiki/Mesh/Wishlist check here] for a list of hardware we'd love to have.

We also need gung ho folks to climb rooftops and mount nodes!

For press inquiries, please contact [mailto:info@sudomesh.org info (at) sudomesh (dot) org]!

--[[User:Tunabananas|Tunabananas]]

=Deployed our first node!=
[[File:FirstNode.JPG|right|350px|Sudo Mesh's first mesh node!]]
Today we finished installing our first backbone node! It's running [https://github.com/sudomesh Sudo Mesh v0.1 Snow Crash], and will soon be linking up with two neighboring hacker houses. :-)

Here's [[User:Juul|Juul's]] reportback:

<blockquote>Pete and myself installed a Nanostation M5 on a 20 foot aluminum flagpole in West Oakland. The node is about 14 feet above the roof of a two-story building. The total cost of this install ran to about $145 including all materials.

Bill of Materials:

* One Nanostation M5 loco
* One 4 foot wood beam of 3.5" by 3.5"
* Three 5" by 1/4" bolts
* Three 5/8" washers for bolts (optional)
* Three 1/2" washers for bolts (optional)
* Two 5" hose clamps
* 30+ feet of outdoor shielded ethernet cable
* Two shielded/groundable ethernet plugs
* A bunch of zip ties

The optional washers make it easier to tighten and untighten the bolts (otherwise they dig into the wood).

Material sources:

* Nanostation from Amazon
* Flag pole from Harbor Freight
* Everything else from Home Depot
</blockquote>

--[[User:Tunabananas|Tunabananas]] ([[User talk:Tunabananas|talk]]) 21:21, 31 December 2013 (PST)

=hello world!=
it's been [https://lists.sudoroom.org/pipermail/mesh/2013-January/000000.html nearly a year] since we first started meeting - our tiny group. so much learning, so much progress!

we've launched [http://peoplesopen.net the peoplesopen.net]!
&& [http://meshthepla.net meshthepla.net]!

check out our [https://github.com/sudomesh code] - namely forks of openwrt running batman-adv for routing and incorporating wlan-slovenia's tunneldigger for secure vpn connections, as well as an admin interface written in lua.

--[[User:Tunabananas|Tunabananas]] ([[User talk:Tunabananas|talk]]) 06:54, 28 December 2013 (PST)
<endfeed />

File:Sudomesh cacti graph sept-oct.2015.png

2015-10-26T19:32:31Z

Maxb: Sudomesh Cacti graph of peoplesopen.net traffic for months of Sept and Oct 2015

Sudomesh Cacti graph of peoplesopen.net traffic for months of Sept and Oct 2015

Mesh/Blog

2015-10-26T19:11:01Z

Maxb: /* Alpha Testing Network */ Formatting

<startfeed />
=Alpha Testing Network=
We've been doing alpha testing on our what's looking to be the network v0.2 for the last couple months. A lot of our firmware/etc code has been tightened up and we're starting to get good results. There are obviously a lot of metrics that are worth considering when evaluating the success of a network, but uptime is a good start, and we're finally getting 90%+ uptime on all of our nodes. That might not sound impressive, but these are pieces of hardware that are hosted at various folks houses, so coordinating the reboot of a router that's in someone's living room can be a challenging ordeal. For those that are interested, graphs from our monitoring server are available here:

Smokeping (latency graphs) http://monitor.sudomesh.org/smokeping/smokeping.cgi?target=Mesh

and

Cacti (traffic and some hardware measurements): http://monitor.sudomesh.org/cacti/graph_view.php?action=tree&tree_id=1&leaf_id=45

[[File:Sudomesh cacti 10.26.15.png|framed|Cacti Graph of PeoplesOpen.net traffic for 10/26/2015]]

We've been uploading the latest versions of our firmware as binaries to:

http://builds.sudomesh.org/builds

Home Node firmwares are for TP-Link wdr3500, 3600, and 4300 as well as MyNet N600 and N750 routers.
Extender Node firmwares are known to mostly work for Ubiquiti Picostation M2, Bullet M2 and M5, Powerbridge M2 and M5, and Nanostation M2 and M5.

We're in need of a handful of new folks to host home nodes and possibly also extender nodes. To be a good home node host, we ask that you be:
* Willing to share some amount of your bandwidth. It doesn't have to be a lot, but 1-2mbps can go a long way for someone who doesn't otherwise have any connectivity.
* Reliably in contact so that we can ask you to do simple things like reboot the router (hopefully rarely if at all), and check connectivity
* Interested in providing some feedback as to how you think the experience is and how it could be improved

To be an extender node host we ask that you be all those things and also have access to your roof and/or another high point on your house/building/etc and be willing to mount a (pretty small) antenna there and run an ethernet cable from your home node (probably near your router) to that roof location.

If that sounds like you, get in touch: https://sudoroom.org/wiki/Mesh#Join_Us

At the moment, we're providing the hardware, so you'll be hosting $50-$150 worth of equipment which in many cases can significantly improve coverage in your own home!

=Building out our backbone...=

After a dark fall of struggling with various issues with batman-adv and our tunnels, our coding crew decided to switch to [http://en.wikipedia.org/wiki/Babel_%28protocol%29 Babel]. While integrating the new protocol into our firmware, we've been actively researching potential sources of bandwidth to feed the network and [[Rooftop_Dish_Antenna_Mount|mounting rooftop nodes]] in strategic locations. Every Sunday, we've been building out the backbone of our network from Kensington to West Oakland - contact us if you've got a spot with great line-of-sight!

Our first major node in Kensington has excellent line-of-sight to both Oakland and Richmond:

[[File:20141130 160516.jpg|thumb|center| 400px | Sudomesh dish mount with Oakland in the distance]]

[[File:20141130 160446.jpg|thumb|center| 400px |Sudomesh dish with Richmond in the distance]]

If you're interested in helping out, we're always looking for [[Mesh/Wishlist|donations]] of gear and equipment, as well as committed volunteers and [https://gratipay.com/sudomesh financial support] (even 25 cents a week adds up as we prepare to launch).

[[File:20141130 160500.jpg|thumb| center | 500px |Sudomesh dish mount and happy ethernet wire/RJ45 termination.]]

Here's to growing a network from the ground up, together!

=We're meshing at the Omni!=

It's been a crazily active summer - apologies for the lack of updates! Sudo Room (and by extension, Sudo Mesh) has relocated to the [http://omni-oakland.org Omni Oakland Commons] at 4799 Shattuck. We're excited to be a founding member collective among an array of groups that have moved in together to create a radical commons in Oakland.

[[File:Omnicoversm.png|framed|center|The Omni building and logo]]

If you've been wanting to plug in and help out, or simply reconnect to the group, tonight is a great night to come by and check out the new space!

'''Announcements'''
* We'll be having our monthly general meeting today, starting at 7:30pm at Sudo Room. Please add to the agenda! - https://pad.riseup.net/p/sudomesh
* Juul, MaxB and Alex have been working hard on crushing bugs and levelling up our mesh firmware. We've deployed a test network within the Omni building and they are successfully meshing as I type! \o/
* We've procured a 75 foot antenna tower that will be mounted in West Oakland to become a core relay spot for routing traffic on the mesh.
* Noemie has put together a fantastic sudomesh / people's open net video and is currently soliciting feedback. Check it out @ https://www.youtube.com/watch?v=qva1SQSBDyE
* Paige made a rad flyer design and two versions of the flyer for a) general ways to participate in the project and b) promoting upcoming info sessions. Check them out here: https://sudoroom.org/wiki/Mesh/Flyers
* Stickers!! The round 'Mesh the Planet' and rectangular PeoplesOpen.Net stickers have been printed and can be procured at sudoroom (atio the white shelves next to the staircase) and/or one of our Tuesday/Thursday meetups!

'''Code - so much code this summer!!'''
* Juul created ipk-builder: https://github.com/sudomesh/ipk-builder
* MaxB, Ron, and Juul have been updating the service browser: https://github.com/sudomesh/service-browser
* Juul, MaxB, and Alex reengineered the node-configurator: https://github.com/sudomesh/makenode
* MaxB, Alex and Matt fixed the exitnode
* MaxB created sudowrt-firmware-images for temporary storage of firmware builds
* Matt added a patch to sudowrt-firmware
* Alex and MaxB have been fixing our fork of tunneldigger
* MaxB fixed sudowrt-packages
* Juul updated ubi-flasher
* Juul added fixes to meshnode-database
* Matt created svg-animations for mesh presentations

'''Wiki'''
* Tunabananas created [[Mesh/Flyers]] and uploaded Paige's flyers
* ChrisJ updated [[Mesh/Monitoring]] and created [[Mesh/Icinga]]
* Matt added instructions to [[Mesh/Firmware/Flash]]
* Jul added to [[Mesh/Hardware]] Support
* GMeader created the page [[Mesh/San Francisco]] and added to [[Mesh/Marketing]]
* MaxB added sticker images to [[Mesh/Stickers]]
* ChrisJ created [[Mesh/Sensu]]
* Tunabananas added recent research on broadband access in Oakland to [[Mesh/Oakland]]
* Tunabananas added some months worth of meeting minutes to [[Mesh/Minutes]]
* Jwentwistle added a bunch of documentation to [[Mesh/BATMAN-adv]]
* Jwentwistle and Tunabananas cleaned up the main [[Mesh]] page!
* Jwentwistle moved Mesh/MeshApps primarily to [[Mesh/Distributed Services]]
* Jwentwistle created and added slides to [[Mesh/Presentation]]
* Jwentwistle created [[Mesh/User Guide]]
* Jwentwistle created [[Mesh/Technical Overview]]
* MaxB checked some stuff out
* Matt added some diagrams to [[Mesh/Diagrams]]
* Jwentwistle added bandwidth shaping details to [[Mesh/Firmware]]
* MaxB added some ideas for our box of crappy routers to [[Mesh/Inventory]]
* Tunabananas wrote a new post on [[Mesh/Blog]]
* Aep added to [[Mesh/MeshApps]]

'''To Dos:'''
* Test current mesh setup in the Omni building
* Create online ordering system and shipping label automation
* Create 'How to Care for Your Node' guides
* Outreach to spaces that can host info sessions and presentations
* Work on local apps and services that will run on the mesh!
* More at: https://sudoroom.org/wiki/Mesh/ToDos
** Please update the list above with specific tasks!

'''Help Out!'''
* Come by our weekly hacknights, Tuesdays and Thursdays starting at 7:30pm at Sudo Room <https://sudoroom.org>
* Contribute research, ideas, designs to our wiki: https://sudomesh.org
* Contribute to the code: https://github.com/sudomesh
* Donate hardware and equipment! <https://sudoroom.org/wiki/Mesh/Wishlist>
* Give a small weekly donation: https://www.gittip.com/sudomesh

'''Recommended Reading'''
* Oakland's Sudo Mesh looks to counter censorship and the digital divide with a mesh network: http://techpresident.com/news/25200/oakland-sudo-mesh-counter-censorship-digital-divide-mesh-net
* It's Time for Open, Shared Home Wi-Fi (Re/Code): http://recode.net/2014/08/05/its-time-for-shared-open-home-wi-fi/

=Mesh Hackathon @ The Omni, July 5-7!=
This weekend, Sudo Mesh is having our first mesh hackathon at sudo room's new location in the Omni! Join us at 4799 at any point this weekend, starting at noon until we tire today[1], and noon on Sunday and Monday. We'll have rotating orientation sessions every hour on the hour both Sunday and Monday, so feel free to come by even if you're brand new to the project!

[[File:Sudoroomfirstallnighter.jpg|center|First all-nighter in the new sudo room!]]

Here are some of the things we plan to work on:
* Designing [[Mesh/Diagrams|network diagrams]] and educational curricula.
* Debugging exit node issues.
* Setting up [[Network/Reboot|our network at the Omni]], the new home of sudo room!
* [[Mesh/Communities|Outreach]] to various community stakeholders and interest groups relevant to the mesh (eg; rock climbers! Ham radio enthusiasts! Librarians!)
* Research and test deployment of [[Mesh/MeshApps|mesh apps]].
* Getting our books in order (finances, [[Mesh/Blog|blog]], calendar, 501c3 app, etc;)
* Making [[Mesh/Swag|swag]] ([[Mesh/Stickers|stickers]]! buttons! whatever you can think of!).

Whether you're a core team member, an occasional collaborator, or just interested in learning more about the mesh, you are welcome!

[1] We are being powered by [[Sudomate]].

--[[User:Tunabananas|Tunabananas]]

=Developer Launch!=
As of last night, we've officially launched version 0.1.0 of the mesh firmware, a.k.a. Snow Crash.

[[File:Snowcrash.png|center|Snow Crash login screen]]

The plan is to have ~20 people with networking skills run nodes from their homes for 1-2 months and report any remaining issues. We'll then fix those bugs and do a wider release of ~60 more nodes.

What's currently working:

1. Sharing limited Internet bandwidth with peoplesopen.net
2. Private access point with no bandwidth limit and mesh access
3. Automatic node meshing with batman-adv
4. Simplified web admin interface that lets node-owners change bandwidth sharing settings and passwords.
5. Automated configuration of new nodes using easy web interface.
6. Automatic printing of stickers with instructions and default generated passwords.

To those of you who have already taken nodes home, here are a few notes:

1. sudo mesh has root access to your nodes since we manage updates per default. If you want to manage your own node and don't want sudo mesh to have access, you can disable our root access by removing /etc/dropbear/authorized_keys on your node.

2. Please report any bugs on our github. If you know which repository the bug pertains to, then go to the issue tracker for that repository. If you aren't sure, then just add the bug here: https://github.com/sudomesh/sudowrt-firmware/issues

A compiled version of the firmware is available here: http://build.sudomesh.org:8080/latest_images/atheros/

Keep in mind that the nodes have to be configured using the node-configurator after being flashed with that firmware and that the firmware only trusts sudomesh SSL certificates. We'll release a less secure version for developers who just want to play around as soon as possible. For now you can configure your nodes at sudo room with the help of one of the core team.

In the following is a list of the repositories directly relevant to this release of the firmware. All of these repositories have been tagged with "sudowrt-0.1.0" so you can get the exact versions used in the release.

*The sudowrt firmware and build scripts (based on openwrt and the work of wlan slovenja): https://github.com/sudomesh/sudowrt-firmware
*The sudowrt packages repository: https://github.com/sudomesh/sudowrt-packages
*The web admin interface: https://github.com/sudomesh/luci-app-peopleswifi
*The mDNS and DNS-SD client: https://github.com/sudomesh/mdnssd-min
*The node database: https://github.com/sudomesh/node-database
*The node configurator: https://github.com/sudomesh/node-configurator
*Sticker printing support for the node configurator: https://github.com/sudomesh/ql570
*The node configurator client: https://github.com/sudomesh/node-configurator-client
*The wlan slovenja tunneldigger (very slightly modified): https://github.com/sudomesh/tunneldigger

Mesh the planet!

--via [[User:Juul|Juul]]

=How to Participate: All Hands on Deck!=
We are always excited to have new volunteers join the team! From designing flyers to developing software, doing research and documenting what you learn, fixing broken hardware to hitting the streets and spreading the word, there's something for everybody who wants to participate.

We meet weekly on Thursday evenings starting at 7:30pm at [https://sudoroom.org Sudo Room], your friendly neighborhood hackerspace. Come on by and jump in!

You can also participate online via [https://lists.sudoroom.org/listinfo/mesh our mailing list], our [http://webchat.freenode.net/?channels=peoplesopen.net chat room], contributing to [https://github.com/sudomesh our code on Github], and adding to this very wiki.

Donations are always appreciated and keep us sustainable. We accept donations [https://gittip.com/sudomesh via Gittip] (anonymous weekly micropayments), through [http://blockchain.info/address/12RxU4DpLpdWcmEBn7Tj325CCXBwt5i9Hc Bitcoin], and in-person at our weekly meetings. Sudo Mesh is currently in the process of acquiring non-profit status, so your donations will be retroactively tax-deductible. If you'd like to donate materials directly, [https://sudoroom.org/wiki/Mesh/Wishlist check here] for a list of hardware we'd love to have.

We also need gung ho folks to climb rooftops and mount nodes!

For press inquiries, please contact [mailto:info@sudomesh.org info (at) sudomesh (dot) org]!

--[[User:Tunabananas|Tunabananas]]

=Deployed our first node!=
[[File:FirstNode.JPG|right|350px|Sudo Mesh's first mesh node!]]
Today we finished installing our first backbone node! It's running [https://github.com/sudomesh Sudo Mesh v0.1 Snow Crash], and will soon be linking up with two neighboring hacker houses. :-)

Here's [[User:Juul|Juul's]] reportback:

<blockquote>Pete and myself installed a Nanostation M5 on a 20 foot aluminum flagpole in West Oakland. The node is about 14 feet above the roof of a two-story building. The total cost of this install ran to about $145 including all materials.

Bill of Materials:

* One Nanostation M5 loco
* One 4 foot wood beam of 3.5" by 3.5"
* Three 5" by 1/4" bolts
* Three 5/8" washers for bolts (optional)
* Three 1/2" washers for bolts (optional)
* Two 5" hose clamps
* 30+ feet of outdoor shielded ethernet cable
* Two shielded/groundable ethernet plugs
* A bunch of zip ties

The optional washers make it easier to tighten and untighten the bolts (otherwise they dig into the wood).

Material sources:

* Nanostation from Amazon
* Flag pole from Harbor Freight
* Everything else from Home Depot
</blockquote>

--[[User:Tunabananas|Tunabananas]] ([[User talk:Tunabananas|talk]]) 21:21, 31 December 2013 (PST)

=hello world!=
it's been [https://lists.sudoroom.org/pipermail/mesh/2013-January/000000.html nearly a year] since we first started meeting - our tiny group. so much learning, so much progress!

we've launched [http://peoplesopen.net the peoplesopen.net]!
&& [http://meshthepla.net meshthepla.net]!

check out our [https://github.com/sudomesh code] - namely forks of openwrt running batman-adv for routing and incorporating wlan-slovenia's tunneldigger for secure vpn connections, as well as an admin interface written in lua.

--[[User:Tunabananas|Tunabananas]] ([[User talk:Tunabananas|talk]]) 06:54, 28 December 2013 (PST)
<endfeed />

Mesh/Blog

2015-10-26T19:10:40Z

Maxb: /* Alpha Testing Network */ Formatting

<startfeed />
=Alpha Testing Network=
We've been doing alpha testing on our what's looking to be the network v0.2 for the last couple months. A lot of our firmware/etc code has been tightened up and we're starting to get good results. There are obviously a lot of metrics that are worth considering when evaluating the success of a network, but uptime is a good start, and we're finally getting 90%+ uptime on all of our nodes. That might not sound impressive, but these are pieces of hardware that are hosted at various folks houses, so coordinating the reboot of a router that's in someone's living room can be a challenging ordeal. For those that are interested, graphs from our monitoring server are available here:

Smokeping (latency graphs) http://monitor.sudomesh.org/smokeping/smokeping.cgi?target=Mesh

and

Cacti (traffic and some hardware measurements): http://monitor.sudomesh.org/cacti/graph_view.php?action=tree&tree_id=1&leaf_id=45

[[File:Sudomesh cacti 10.26.15.png|framed|Cacti Graph of PeoplesOpen.net traffic for 10/26/2015]]

We've been uploading the latest versions of our firmware as binaries to:

http://builds.sudomesh.org/builds

Home Node firmwares are for TP-Link wdr3500, 3600, and 4300 as well as MyNet N600 and N750 routers.
Extender Node firmwares are known to mostly work for Ubiquiti Picostation M2, Bullet M2 and M5, Powerbridge M2 and M5, and Nanostation M2 and M5.

We're in need of a handful of new folks to host home nodes and possibly also extender nodes. To be a good home node host, we ask that you be:
* Willing to share some amount of your bandwidth. It doesn't have to be a lot, but 1-2mbps can go a long way for someone who doesn't otherwise have any connectivity.
* Reliably in contact so that we can ask you to do simple things like reboot the router (hopefully rarely if at all), and check connectivity
* Interested in providing some feedback as to how you think the experience is and how it could be improved

To be an extender node host we ask that you be all those things and also have access to your roof and/or another high point on your house/building/etc and be willing to mount a (pretty small) antenna there and run an ethernet cable from your home node (probably near your router) to that roof location.

If that sounds like you, get in touch: https://sudoroom.org/wiki/Mesh#Join_Us

At the moment, we're providing the hardware, so you'll be hosting $50-$150 worth of equipment which in many cases can significantly improve coverage in your own home!

=Building out our backbone...=

After a dark fall of struggling with various issues with batman-adv and our tunnels, our coding crew decided to switch to [http://en.wikipedia.org/wiki/Babel_%28protocol%29 Babel]. While integrating the new protocol into our firmware, we've been actively researching potential sources of bandwidth to feed the network and [[Rooftop_Dish_Antenna_Mount|mounting rooftop nodes]] in strategic locations. Every Sunday, we've been building out the backbone of our network from Kensington to West Oakland - contact us if you've got a spot with great line-of-sight!

Our first major node in Kensington has excellent line-of-sight to both Oakland and Richmond:

[[File:20141130 160516.jpg|thumb|center| 400px | Sudomesh dish mount with Oakland in the distance]]

[[File:20141130 160446.jpg|thumb|center| 400px |Sudomesh dish with Richmond in the distance]]

If you're interested in helping out, we're always looking for [[Mesh/Wishlist|donations]] of gear and equipment, as well as committed volunteers and [https://gratipay.com/sudomesh financial support] (even 25 cents a week adds up as we prepare to launch).

[[File:20141130 160500.jpg|thumb| center | 500px |Sudomesh dish mount and happy ethernet wire/RJ45 termination.]]

Here's to growing a network from the ground up, together!

=We're meshing at the Omni!=

It's been a crazily active summer - apologies for the lack of updates! Sudo Room (and by extension, Sudo Mesh) has relocated to the [http://omni-oakland.org Omni Oakland Commons] at 4799 Shattuck. We're excited to be a founding member collective among an array of groups that have moved in together to create a radical commons in Oakland.

[[File:Omnicoversm.png|framed|center|The Omni building and logo]]

If you've been wanting to plug in and help out, or simply reconnect to the group, tonight is a great night to come by and check out the new space!

'''Announcements'''
* We'll be having our monthly general meeting today, starting at 7:30pm at Sudo Room. Please add to the agenda! - https://pad.riseup.net/p/sudomesh
* Juul, MaxB and Alex have been working hard on crushing bugs and levelling up our mesh firmware. We've deployed a test network within the Omni building and they are successfully meshing as I type! \o/
* We've procured a 75 foot antenna tower that will be mounted in West Oakland to become a core relay spot for routing traffic on the mesh.
* Noemie has put together a fantastic sudomesh / people's open net video and is currently soliciting feedback. Check it out @ https://www.youtube.com/watch?v=qva1SQSBDyE
* Paige made a rad flyer design and two versions of the flyer for a) general ways to participate in the project and b) promoting upcoming info sessions. Check them out here: https://sudoroom.org/wiki/Mesh/Flyers
* Stickers!! The round 'Mesh the Planet' and rectangular PeoplesOpen.Net stickers have been printed and can be procured at sudoroom (atio the white shelves next to the staircase) and/or one of our Tuesday/Thursday meetups!

'''Code - so much code this summer!!'''
* Juul created ipk-builder: https://github.com/sudomesh/ipk-builder
* MaxB, Ron, and Juul have been updating the service browser: https://github.com/sudomesh/service-browser
* Juul, MaxB, and Alex reengineered the node-configurator: https://github.com/sudomesh/makenode
* MaxB, Alex and Matt fixed the exitnode
* MaxB created sudowrt-firmware-images for temporary storage of firmware builds
* Matt added a patch to sudowrt-firmware
* Alex and MaxB have been fixing our fork of tunneldigger
* MaxB fixed sudowrt-packages
* Juul updated ubi-flasher
* Juul added fixes to meshnode-database
* Matt created svg-animations for mesh presentations

'''Wiki'''
* Tunabananas created [[Mesh/Flyers]] and uploaded Paige's flyers
* ChrisJ updated [[Mesh/Monitoring]] and created [[Mesh/Icinga]]
* Matt added instructions to [[Mesh/Firmware/Flash]]
* Jul added to [[Mesh/Hardware]] Support
* GMeader created the page [[Mesh/San Francisco]] and added to [[Mesh/Marketing]]
* MaxB added sticker images to [[Mesh/Stickers]]
* ChrisJ created [[Mesh/Sensu]]
* Tunabananas added recent research on broadband access in Oakland to [[Mesh/Oakland]]
* Tunabananas added some months worth of meeting minutes to [[Mesh/Minutes]]
* Jwentwistle added a bunch of documentation to [[Mesh/BATMAN-adv]]
* Jwentwistle and Tunabananas cleaned up the main [[Mesh]] page!
* Jwentwistle moved Mesh/MeshApps primarily to [[Mesh/Distributed Services]]
* Jwentwistle created and added slides to [[Mesh/Presentation]]
* Jwentwistle created [[Mesh/User Guide]]
* Jwentwistle created [[Mesh/Technical Overview]]
* MaxB checked some stuff out
* Matt added some diagrams to [[Mesh/Diagrams]]
* Jwentwistle added bandwidth shaping details to [[Mesh/Firmware]]
* MaxB added some ideas for our box of crappy routers to [[Mesh/Inventory]]
* Tunabananas wrote a new post on [[Mesh/Blog]]
* Aep added to [[Mesh/MeshApps]]

'''To Dos:'''
* Test current mesh setup in the Omni building
* Create online ordering system and shipping label automation
* Create 'How to Care for Your Node' guides
* Outreach to spaces that can host info sessions and presentations
* Work on local apps and services that will run on the mesh!
* More at: https://sudoroom.org/wiki/Mesh/ToDos
** Please update the list above with specific tasks!

'''Help Out!'''
* Come by our weekly hacknights, Tuesdays and Thursdays starting at 7:30pm at Sudo Room <https://sudoroom.org>
* Contribute research, ideas, designs to our wiki: https://sudomesh.org
* Contribute to the code: https://github.com/sudomesh
* Donate hardware and equipment! <https://sudoroom.org/wiki/Mesh/Wishlist>
* Give a small weekly donation: https://www.gittip.com/sudomesh

'''Recommended Reading'''
* Oakland's Sudo Mesh looks to counter censorship and the digital divide with a mesh network: http://techpresident.com/news/25200/oakland-sudo-mesh-counter-censorship-digital-divide-mesh-net
* It's Time for Open, Shared Home Wi-Fi (Re/Code): http://recode.net/2014/08/05/its-time-for-shared-open-home-wi-fi/

=Mesh Hackathon @ The Omni, July 5-7!=
This weekend, Sudo Mesh is having our first mesh hackathon at sudo room's new location in the Omni! Join us at 4799 at any point this weekend, starting at noon until we tire today[1], and noon on Sunday and Monday. We'll have rotating orientation sessions every hour on the hour both Sunday and Monday, so feel free to come by even if you're brand new to the project!

[[File:Sudoroomfirstallnighter.jpg|center|First all-nighter in the new sudo room!]]

Here are some of the things we plan to work on:
* Designing [[Mesh/Diagrams|network diagrams]] and educational curricula.
* Debugging exit node issues.
* Setting up [[Network/Reboot|our network at the Omni]], the new home of sudo room!
* [[Mesh/Communities|Outreach]] to various community stakeholders and interest groups relevant to the mesh (eg; rock climbers! Ham radio enthusiasts! Librarians!)
* Research and test deployment of [[Mesh/MeshApps|mesh apps]].
* Getting our books in order (finances, [[Mesh/Blog|blog]], calendar, 501c3 app, etc;)
* Making [[Mesh/Swag|swag]] ([[Mesh/Stickers|stickers]]! buttons! whatever you can think of!).

Whether you're a core team member, an occasional collaborator, or just interested in learning more about the mesh, you are welcome!

[1] We are being powered by [[Sudomate]].

--[[User:Tunabananas|Tunabananas]]

=Developer Launch!=
As of last night, we've officially launched version 0.1.0 of the mesh firmware, a.k.a. Snow Crash.

[[File:Snowcrash.png|center|Snow Crash login screen]]

The plan is to have ~20 people with networking skills run nodes from their homes for 1-2 months and report any remaining issues. We'll then fix those bugs and do a wider release of ~60 more nodes.

What's currently working:

1. Sharing limited Internet bandwidth with peoplesopen.net
2. Private access point with no bandwidth limit and mesh access
3. Automatic node meshing with batman-adv
4. Simplified web admin interface that lets node-owners change bandwidth sharing settings and passwords.
5. Automated configuration of new nodes using easy web interface.
6. Automatic printing of stickers with instructions and default generated passwords.

To those of you who have already taken nodes home, here are a few notes:

1. sudo mesh has root access to your nodes since we manage updates per default. If you want to manage your own node and don't want sudo mesh to have access, you can disable our root access by removing /etc/dropbear/authorized_keys on your node.

2. Please report any bugs on our github. If you know which repository the bug pertains to, then go to the issue tracker for that repository. If you aren't sure, then just add the bug here: https://github.com/sudomesh/sudowrt-firmware/issues

A compiled version of the firmware is available here: http://build.sudomesh.org:8080/latest_images/atheros/

Keep in mind that the nodes have to be configured using the node-configurator after being flashed with that firmware and that the firmware only trusts sudomesh SSL certificates. We'll release a less secure version for developers who just want to play around as soon as possible. For now you can configure your nodes at sudo room with the help of one of the core team.

In the following is a list of the repositories directly relevant to this release of the firmware. All of these repositories have been tagged with "sudowrt-0.1.0" so you can get the exact versions used in the release.

*The sudowrt firmware and build scripts (based on openwrt and the work of wlan slovenja): https://github.com/sudomesh/sudowrt-firmware
*The sudowrt packages repository: https://github.com/sudomesh/sudowrt-packages
*The web admin interface: https://github.com/sudomesh/luci-app-peopleswifi
*The mDNS and DNS-SD client: https://github.com/sudomesh/mdnssd-min
*The node database: https://github.com/sudomesh/node-database
*The node configurator: https://github.com/sudomesh/node-configurator
*Sticker printing support for the node configurator: https://github.com/sudomesh/ql570
*The node configurator client: https://github.com/sudomesh/node-configurator-client
*The wlan slovenja tunneldigger (very slightly modified): https://github.com/sudomesh/tunneldigger

Mesh the planet!

--via [[User:Juul|Juul]]

=How to Participate: All Hands on Deck!=
We are always excited to have new volunteers join the team! From designing flyers to developing software, doing research and documenting what you learn, fixing broken hardware to hitting the streets and spreading the word, there's something for everybody who wants to participate.

We meet weekly on Thursday evenings starting at 7:30pm at [https://sudoroom.org Sudo Room], your friendly neighborhood hackerspace. Come on by and jump in!

You can also participate online via [https://lists.sudoroom.org/listinfo/mesh our mailing list], our [http://webchat.freenode.net/?channels=peoplesopen.net chat room], contributing to [https://github.com/sudomesh our code on Github], and adding to this very wiki.

Donations are always appreciated and keep us sustainable. We accept donations [https://gittip.com/sudomesh via Gittip] (anonymous weekly micropayments), through [http://blockchain.info/address/12RxU4DpLpdWcmEBn7Tj325CCXBwt5i9Hc Bitcoin], and in-person at our weekly meetings. Sudo Mesh is currently in the process of acquiring non-profit status, so your donations will be retroactively tax-deductible. If you'd like to donate materials directly, [https://sudoroom.org/wiki/Mesh/Wishlist check here] for a list of hardware we'd love to have.

We also need gung ho folks to climb rooftops and mount nodes!

For press inquiries, please contact [mailto:info@sudomesh.org info (at) sudomesh (dot) org]!

--[[User:Tunabananas|Tunabananas]]

=Deployed our first node!=
[[File:FirstNode.JPG|right|350px|Sudo Mesh's first mesh node!]]
Today we finished installing our first backbone node! It's running [https://github.com/sudomesh Sudo Mesh v0.1 Snow Crash], and will soon be linking up with two neighboring hacker houses. :-)

Here's [[User:Juul|Juul's]] reportback:

<blockquote>Pete and myself installed a Nanostation M5 on a 20 foot aluminum flagpole in West Oakland. The node is about 14 feet above the roof of a two-story building. The total cost of this install ran to about $145 including all materials.

Bill of Materials:

* One Nanostation M5 loco
* One 4 foot wood beam of 3.5" by 3.5"
* Three 5" by 1/4" bolts
* Three 5/8" washers for bolts (optional)
* Three 1/2" washers for bolts (optional)
* Two 5" hose clamps
* 30+ feet of outdoor shielded ethernet cable
* Two shielded/groundable ethernet plugs
* A bunch of zip ties

The optional washers make it easier to tighten and untighten the bolts (otherwise they dig into the wood).

Material sources:

* Nanostation from Amazon
* Flag pole from Harbor Freight
* Everything else from Home Depot
</blockquote>

--[[User:Tunabananas|Tunabananas]] ([[User talk:Tunabananas|talk]]) 21:21, 31 December 2013 (PST)

=hello world!=
it's been [https://lists.sudoroom.org/pipermail/mesh/2013-January/000000.html nearly a year] since we first started meeting - our tiny group. so much learning, so much progress!

we've launched [http://peoplesopen.net the peoplesopen.net]!
&& [http://meshthepla.net meshthepla.net]!

check out our [https://github.com/sudomesh code] - namely forks of openwrt running batman-adv for routing and incorporating wlan-slovenia's tunneldigger for secure vpn connections, as well as an admin interface written in lua.

--[[User:Tunabananas|Tunabananas]] ([[User talk:Tunabananas|talk]]) 06:54, 28 December 2013 (PST)
<endfeed />

Mesh/Blog

2015-10-26T19:10:09Z

Maxb: /* Alpha Testing Network */

<startfeed />
=Alpha Testing Network=
We've been doing alpha testing on our what's looking to be the network v0.2 for the last couple months. A lot of our firmware/etc code has been tightened up and we're starting to get good results. There are obviously a lot of metrics that are worth considering when evaluating the success of a network, but uptime is a good start, and we're finally getting 90%+ uptime on all of our nodes. That might not sound impressive, but these are pieces of hardware that are hosted at various folks houses, so coordinating the reboot of a router that's in someone's living room can be a challenging ordeal. For those that are interested, graphs from our monitoring server are available here:

Smokeping (latency graphs) http://monitor.sudomesh.org/smokeping/smokeping.cgi?target=Mesh

and

Cacti (traffic and some hardware measurements): http://monitor.sudomesh.org/cacti/graph_view.php?action=tree&tree_id=1&leaf_id=45

[[File:Sudomesh cacti 10.26.15.png|framed|Cacti Graph of PeoplesOpen.net traffic for 10/26/2015]]

We've been uploading the latest versions of our firmware as binaries to:

http://builds.sudomesh.org/builds

Home Node firmwares are for TP-Link wdr3500, 3600, and 4300 as well as MyNet N600 and N750 routers.
Extender Node firmwares are known to mostly work for Ubiquiti Picostation M2, Bullet M2 and M5, Powerbridge M2 and M5, and Nanostation M2 and M5.

We're in need of a handful of new folks to host home nodes and possibly also extender nodes. To be a good home node host, we ask that you be:
- Willing to share some amount of your bandwidth. It doesn't have to be a lot, but 1-2mbps can go a long way for someone who doesn't otherwise have any connectivity.
- Reliably in contact so that we can ask you to do simple things like reboot the router (hopefully rarely if at all), and check connectivity
- Interested in providing some feedback as to how you think the experience is and how it could be improved

To be an extender node host we ask that you be all those things and also have access to your roof and/or another high point on your house/building/etc and be willing to mount a (pretty small) antenna there and run an ethernet cable from your home node (probably near your router) to that roof location.

If that sounds like you, get in touch: https://sudoroom.org/wiki/Mesh#Join_Us

At the moment, we're providing the hardware, so you'll be hosting $50-$150 worth of equipment which in many cases can significantly improve coverage in your own home!

=Building out our backbone...=

After a dark fall of struggling with various issues with batman-adv and our tunnels, our coding crew decided to switch to [http://en.wikipedia.org/wiki/Babel_%28protocol%29 Babel]. While integrating the new protocol into our firmware, we've been actively researching potential sources of bandwidth to feed the network and [[Rooftop_Dish_Antenna_Mount|mounting rooftop nodes]] in strategic locations. Every Sunday, we've been building out the backbone of our network from Kensington to West Oakland - contact us if you've got a spot with great line-of-sight!

Our first major node in Kensington has excellent line-of-sight to both Oakland and Richmond:

[[File:20141130 160516.jpg|thumb|center| 400px | Sudomesh dish mount with Oakland in the distance]]

[[File:20141130 160446.jpg|thumb|center| 400px |Sudomesh dish with Richmond in the distance]]

If you're interested in helping out, we're always looking for [[Mesh/Wishlist|donations]] of gear and equipment, as well as committed volunteers and [https://gratipay.com/sudomesh financial support] (even 25 cents a week adds up as we prepare to launch).

[[File:20141130 160500.jpg|thumb| center | 500px |Sudomesh dish mount and happy ethernet wire/RJ45 termination.]]

Here's to growing a network from the ground up, together!

=We're meshing at the Omni!=

It's been a crazily active summer - apologies for the lack of updates! Sudo Room (and by extension, Sudo Mesh) has relocated to the [http://omni-oakland.org Omni Oakland Commons] at 4799 Shattuck. We're excited to be a founding member collective among an array of groups that have moved in together to create a radical commons in Oakland.

[[File:Omnicoversm.png|framed|center|The Omni building and logo]]

If you've been wanting to plug in and help out, or simply reconnect to the group, tonight is a great night to come by and check out the new space!

'''Announcements'''
* We'll be having our monthly general meeting today, starting at 7:30pm at Sudo Room. Please add to the agenda! - https://pad.riseup.net/p/sudomesh
* Juul, MaxB and Alex have been working hard on crushing bugs and levelling up our mesh firmware. We've deployed a test network within the Omni building and they are successfully meshing as I type! \o/
* We've procured a 75 foot antenna tower that will be mounted in West Oakland to become a core relay spot for routing traffic on the mesh.
* Noemie has put together a fantastic sudomesh / people's open net video and is currently soliciting feedback. Check it out @ https://www.youtube.com/watch?v=qva1SQSBDyE
* Paige made a rad flyer design and two versions of the flyer for a) general ways to participate in the project and b) promoting upcoming info sessions. Check them out here: https://sudoroom.org/wiki/Mesh/Flyers
* Stickers!! The round 'Mesh the Planet' and rectangular PeoplesOpen.Net stickers have been printed and can be procured at sudoroom (atio the white shelves next to the staircase) and/or one of our Tuesday/Thursday meetups!

'''Code - so much code this summer!!'''
* Juul created ipk-builder: https://github.com/sudomesh/ipk-builder
* MaxB, Ron, and Juul have been updating the service browser: https://github.com/sudomesh/service-browser
* Juul, MaxB, and Alex reengineered the node-configurator: https://github.com/sudomesh/makenode
* MaxB, Alex and Matt fixed the exitnode
* MaxB created sudowrt-firmware-images for temporary storage of firmware builds
* Matt added a patch to sudowrt-firmware
* Alex and MaxB have been fixing our fork of tunneldigger
* MaxB fixed sudowrt-packages
* Juul updated ubi-flasher
* Juul added fixes to meshnode-database
* Matt created svg-animations for mesh presentations

'''Wiki'''
* Tunabananas created [[Mesh/Flyers]] and uploaded Paige's flyers
* ChrisJ updated [[Mesh/Monitoring]] and created [[Mesh/Icinga]]
* Matt added instructions to [[Mesh/Firmware/Flash]]
* Jul added to [[Mesh/Hardware]] Support
* GMeader created the page [[Mesh/San Francisco]] and added to [[Mesh/Marketing]]
* MaxB added sticker images to [[Mesh/Stickers]]
* ChrisJ created [[Mesh/Sensu]]
* Tunabananas added recent research on broadband access in Oakland to [[Mesh/Oakland]]
* Tunabananas added some months worth of meeting minutes to [[Mesh/Minutes]]
* Jwentwistle added a bunch of documentation to [[Mesh/BATMAN-adv]]
* Jwentwistle and Tunabananas cleaned up the main [[Mesh]] page!
* Jwentwistle moved Mesh/MeshApps primarily to [[Mesh/Distributed Services]]
* Jwentwistle created and added slides to [[Mesh/Presentation]]
* Jwentwistle created [[Mesh/User Guide]]
* Jwentwistle created [[Mesh/Technical Overview]]
* MaxB checked some stuff out
* Matt added some diagrams to [[Mesh/Diagrams]]
* Jwentwistle added bandwidth shaping details to [[Mesh/Firmware]]
* MaxB added some ideas for our box of crappy routers to [[Mesh/Inventory]]
* Tunabananas wrote a new post on [[Mesh/Blog]]
* Aep added to [[Mesh/MeshApps]]

'''To Dos:'''
* Test current mesh setup in the Omni building
* Create online ordering system and shipping label automation
* Create 'How to Care for Your Node' guides
* Outreach to spaces that can host info sessions and presentations
* Work on local apps and services that will run on the mesh!
* More at: https://sudoroom.org/wiki/Mesh/ToDos
** Please update the list above with specific tasks!

'''Help Out!'''
* Come by our weekly hacknights, Tuesdays and Thursdays starting at 7:30pm at Sudo Room <https://sudoroom.org>
* Contribute research, ideas, designs to our wiki: https://sudomesh.org
* Contribute to the code: https://github.com/sudomesh
* Donate hardware and equipment! <https://sudoroom.org/wiki/Mesh/Wishlist>
* Give a small weekly donation: https://www.gittip.com/sudomesh

'''Recommended Reading'''
* Oakland's Sudo Mesh looks to counter censorship and the digital divide with a mesh network: http://techpresident.com/news/25200/oakland-sudo-mesh-counter-censorship-digital-divide-mesh-net
* It's Time for Open, Shared Home Wi-Fi (Re/Code): http://recode.net/2014/08/05/its-time-for-shared-open-home-wi-fi/

=Mesh Hackathon @ The Omni, July 5-7!=
This weekend, Sudo Mesh is having our first mesh hackathon at sudo room's new location in the Omni! Join us at 4799 at any point this weekend, starting at noon until we tire today[1], and noon on Sunday and Monday. We'll have rotating orientation sessions every hour on the hour both Sunday and Monday, so feel free to come by even if you're brand new to the project!

[[File:Sudoroomfirstallnighter.jpg|center|First all-nighter in the new sudo room!]]

Here are some of the things we plan to work on:
* Designing [[Mesh/Diagrams|network diagrams]] and educational curricula.
* Debugging exit node issues.
* Setting up [[Network/Reboot|our network at the Omni]], the new home of sudo room!
* [[Mesh/Communities|Outreach]] to various community stakeholders and interest groups relevant to the mesh (eg; rock climbers! Ham radio enthusiasts! Librarians!)
* Research and test deployment of [[Mesh/MeshApps|mesh apps]].
* Getting our books in order (finances, [[Mesh/Blog|blog]], calendar, 501c3 app, etc;)
* Making [[Mesh/Swag|swag]] ([[Mesh/Stickers|stickers]]! buttons! whatever you can think of!).

Whether you're a core team member, an occasional collaborator, or just interested in learning more about the mesh, you are welcome!

[1] We are being powered by [[Sudomate]].

--[[User:Tunabananas|Tunabananas]]

=Developer Launch!=
As of last night, we've officially launched version 0.1.0 of the mesh firmware, a.k.a. Snow Crash.

[[File:Snowcrash.png|center|Snow Crash login screen]]

The plan is to have ~20 people with networking skills run nodes from their homes for 1-2 months and report any remaining issues. We'll then fix those bugs and do a wider release of ~60 more nodes.

What's currently working:

1. Sharing limited Internet bandwidth with peoplesopen.net
2. Private access point with no bandwidth limit and mesh access
3. Automatic node meshing with batman-adv
4. Simplified web admin interface that lets node-owners change bandwidth sharing settings and passwords.
5. Automated configuration of new nodes using easy web interface.
6. Automatic printing of stickers with instructions and default generated passwords.

To those of you who have already taken nodes home, here are a few notes:

1. sudo mesh has root access to your nodes since we manage updates per default. If you want to manage your own node and don't want sudo mesh to have access, you can disable our root access by removing /etc/dropbear/authorized_keys on your node.

2. Please report any bugs on our github. If you know which repository the bug pertains to, then go to the issue tracker for that repository. If you aren't sure, then just add the bug here: https://github.com/sudomesh/sudowrt-firmware/issues

A compiled version of the firmware is available here: http://build.sudomesh.org:8080/latest_images/atheros/

Keep in mind that the nodes have to be configured using the node-configurator after being flashed with that firmware and that the firmware only trusts sudomesh SSL certificates. We'll release a less secure version for developers who just want to play around as soon as possible. For now you can configure your nodes at sudo room with the help of one of the core team.

In the following is a list of the repositories directly relevant to this release of the firmware. All of these repositories have been tagged with "sudowrt-0.1.0" so you can get the exact versions used in the release.

*The sudowrt firmware and build scripts (based on openwrt and the work of wlan slovenja): https://github.com/sudomesh/sudowrt-firmware
*The sudowrt packages repository: https://github.com/sudomesh/sudowrt-packages
*The web admin interface: https://github.com/sudomesh/luci-app-peopleswifi
*The mDNS and DNS-SD client: https://github.com/sudomesh/mdnssd-min
*The node database: https://github.com/sudomesh/node-database
*The node configurator: https://github.com/sudomesh/node-configurator
*Sticker printing support for the node configurator: https://github.com/sudomesh/ql570
*The node configurator client: https://github.com/sudomesh/node-configurator-client
*The wlan slovenja tunneldigger (very slightly modified): https://github.com/sudomesh/tunneldigger

Mesh the planet!

--via [[User:Juul|Juul]]

=How to Participate: All Hands on Deck!=
We are always excited to have new volunteers join the team! From designing flyers to developing software, doing research and documenting what you learn, fixing broken hardware to hitting the streets and spreading the word, there's something for everybody who wants to participate.

We meet weekly on Thursday evenings starting at 7:30pm at [https://sudoroom.org Sudo Room], your friendly neighborhood hackerspace. Come on by and jump in!

You can also participate online via [https://lists.sudoroom.org/listinfo/mesh our mailing list], our [http://webchat.freenode.net/?channels=peoplesopen.net chat room], contributing to [https://github.com/sudomesh our code on Github], and adding to this very wiki.

Donations are always appreciated and keep us sustainable. We accept donations [https://gittip.com/sudomesh via Gittip] (anonymous weekly micropayments), through [http://blockchain.info/address/12RxU4DpLpdWcmEBn7Tj325CCXBwt5i9Hc Bitcoin], and in-person at our weekly meetings. Sudo Mesh is currently in the process of acquiring non-profit status, so your donations will be retroactively tax-deductible. If you'd like to donate materials directly, [https://sudoroom.org/wiki/Mesh/Wishlist check here] for a list of hardware we'd love to have.

We also need gung ho folks to climb rooftops and mount nodes!

For press inquiries, please contact [mailto:info@sudomesh.org info (at) sudomesh (dot) org]!

--[[User:Tunabananas|Tunabananas]]

=Deployed our first node!=
[[File:FirstNode.JPG|right|350px|Sudo Mesh's first mesh node!]]
Today we finished installing our first backbone node! It's running [https://github.com/sudomesh Sudo Mesh v0.1 Snow Crash], and will soon be linking up with two neighboring hacker houses. :-)

Here's [[User:Juul|Juul's]] reportback:

<blockquote>Pete and myself installed a Nanostation M5 on a 20 foot aluminum flagpole in West Oakland. The node is about 14 feet above the roof of a two-story building. The total cost of this install ran to about $145 including all materials.

Bill of Materials:

* One Nanostation M5 loco
* One 4 foot wood beam of 3.5" by 3.5"
* Three 5" by 1/4" bolts
* Three 5/8" washers for bolts (optional)
* Three 1/2" washers for bolts (optional)
* Two 5" hose clamps
* 30+ feet of outdoor shielded ethernet cable
* Two shielded/groundable ethernet plugs
* A bunch of zip ties

The optional washers make it easier to tighten and untighten the bolts (otherwise they dig into the wood).

Material sources:

* Nanostation from Amazon
* Flag pole from Harbor Freight
* Everything else from Home Depot
</blockquote>

--[[User:Tunabananas|Tunabananas]] ([[User talk:Tunabananas|talk]]) 21:21, 31 December 2013 (PST)

=hello world!=
it's been [https://lists.sudoroom.org/pipermail/mesh/2013-January/000000.html nearly a year] since we first started meeting - our tiny group. so much learning, so much progress!

we've launched [http://peoplesopen.net the peoplesopen.net]!
&& [http://meshthepla.net meshthepla.net]!

check out our [https://github.com/sudomesh code] - namely forks of openwrt running batman-adv for routing and incorporating wlan-slovenia's tunneldigger for secure vpn connections, as well as an admin interface written in lua.

--[[User:Tunabananas|Tunabananas]] ([[User talk:Tunabananas|talk]]) 06:54, 28 December 2013 (PST)
<endfeed />