Sudo Room - User contributions [en]

Mesh/BATMAN-adv

2014-07-22T08:50:40Z

Jwentwistle: change the wording

The [http://www.open-mesh.org/projects/batman-adv/wiki batman-adv] is an implementation of the [http://en.wikipedia.org/wiki/B.A.T.M.A.N. BATMAN routing protocol]. The protocol is configured with a file, but these settings can be changed with [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl]. The advantage of routing using batman-adv, rather than [https://github.com/cjdelisle/cjdns cjdns], is its a layer two protocol, which can send all types of layers three packets (udp, tcp/ip, etc). The protocol "forwards all traffic until it reaches the destination, hence emulating a virtual network switch of all nodes participating. Therefore all nodes appear to be link local and are unaware of the network's topology as well as unaffected by any network changes.<ref>[http://www.open-mesh.org/projects/batman-adv/wiki/Wiki BATMAN advanced overview]</ref>"

= [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl] configuration=

These functions change BATMAN-adv configurations through batctl:

* [http://downloads.open-mesh.org/batman/manpages/alfred-gpsd.html alfred-gpsd] - a used to distribute GPS location information about your batman-adv mesh network. This information could be, for example, combined with [http://www.open-mesh.org/projects/batmand/wiki/VisualizeMesh vis] to visualize your mesh topology with true geographic layout. The server fetches the information from locals nodes serving data from [http://manpages.ubuntu.com/manpages/karmic/en/man8/gpsd.8.html gpsd].
* [http://downloads.open-mesh.org/batman/manpages/batadv-vis.html batadv-vis] - its a server that saves local client tables and distributes these tables via [http://www.open-mesh.org/projects/open-mesh/wiki/Alfred alfred]. These tables can be used to create network topology maps.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Multi-link-optimize bonding] - when there's multiple interfaces with similar throughput, bonding can be used to increase frame throughput. It uses [http://oit2.utk.edu/helpdesk/kb/entry/1699/ round robin load balancing] to evenly distribute frames.
* [http://www.open-mesh.org/projects/batman-adv/wiki/DistributedArpTable-technical dat] - a distributed arp table is a Distributed Hash Table aimed to store ARP entries and to allow nodes to perform fast lookup operations. All the operations in the DHT (get and store) are performed on a set of nodes computed by means of a distributed hash function which input value is an IPv4 address.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Fragmentation-technical fragmentation] - a driver that sets fragmentation, which sends frames in fragmented frames when a wireless interfaces can't send/receive packets more than 1500 bytes. The protocol adds its own header to existing frames, which makes the packets have 1528 bytes.
* gw_mode - a server is an internet gateway, a client sends and receives traffic to and from the gateway
* [http://www.open-mesh.org/projects/batman-adv/wiki/NetworkCoding nc] (network coding) - when forwarding packets in a wireless mesh network, bandwidth can be saved by exploiting the information already present at the destinations of a forward. One way of doing this is network coding, where two packets are combined before transmission.
* traceroute - tries to find the bat-host name if the given parameter was not a MAC address. It can also try to guess the MAC address using an IPv4/IPv6 address or a hostname when the IPv4/IPv6 address was configured on top of the batman-adv interface of the destination device and both source and destination devices are in the same IP subnet.

= [http://downloads.open-mesh.org/batman/manpages/batmand.8.html batmand] configuration =

There functions change BATMAN configurations through [http://downloads.open-mesh.org/batman/manpages/batmand.8.html batmand]:

* s (visualization server) - Batman daemons may send their local view about their single-hop neighbors to the vis server. It collects the information and provides data in a format similar to [http://www.olsr.org/ OLSR's topology] information output.
* o (originator interval in ms) - a node transmits broadcast messages (we call them [http://www.open-mesh.org/projects/batman-adv/wiki/OGM originator message or OGM], [http://www.open-mesh.org/projects/batman-adv/wiki/Ogm-v2 version 2]) to inform the neighboring does about it's existence. Originator interval is the time to wait after sending one message and before sending the next message. The default value is 1000 ms (1 second). In a mobile network, you may want to detect network changes very quickly, so you need to send message very often, for example, use a value of 500 ms. In a static network, you can save bandwidth by using a higher value.

= Configuration files =
== Device configuration ==

This configuration is valid for [http://wiki.openwrt.org/about/history OpenWRT 12.09] (Attitude Adjustment), which uses BATMAN 2012.4.0. In newer versions, the version of BATMAN used is 2013.0.0 and the configuration of BATMAN slightly differs.

In /etc/config/wireless:

<pre>
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11g'
option channel '3' # You may want another channel
option disabled '0'
option phy 'phy0'

# the interface where non-mesh nodes connect
config wifi-iface
option device 'radio0'
option ifname 'ap0'
option encryption 'none'
option network 'lan'
option mode 'ap'
option ssid 'sudomesh' # You should change the ssid to be unique for dev purposes

# the mesh interface
config wifi-iface
option device 'radio0'
option ifname 'adhoc0'
option encryption 'none'
option network 'mesh'
option mode 'adhoc'
option bssid 'CA:FE:C0:DE:F0:0D' # You should change this to be unique for development purposes, but for meshing this should be the same for all routers on the mesh
option ssid 'sudomesh-backchannel' # You should change the ssid to be unique for development purposes, but for meshing this should be the same for all routers on the mesh
</pre>

Write some of this stuff down for reference later! You might need it!

== Network configuration ==

In /etc/config/network:

<pre>
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

# set up ethernet bridging between eth0 and bat0
# this means that packets can move between the ethernet port
# and the wifi mesh
config interface 'lan'
option type 'bridge'
option proto 'static'
option ipaddr '10.42.10.11' # this should be a unique IP
option netmask '255.255.0.0'
option dns '208.67.222.222'
option gateway '192.168.1.1' # an internet gateway, not sure how to deal with multiple gateways yet
option ifname 'eth0 bat0'

# the mesh interface
config interface 'mesh'
option ifname 'adhoc0'
option proto 'none'
option mtu '1528'
</pre>

== BATMAN configuration ==

There are [http://www.open-mesh.org/projects/batman-adv/wiki/Tweaking other options], but these are the recommended settings in /etc/config/batman-adv:

<pre>
config mesh 'bat0'
option interfaces 'adhoc0' # the interface for which to enable batman0
option 'aggregated_ogms'
option 'ap_isolation'
</pre>

* [http://www.open-mesh.org/projects/batman-adv/wiki/Tweaking aggregated_ogms] - an option that combines the [http://www.open-mesh.org/projects/batman-adv/wiki/OGM originator messages] into a single packet instead of a lot of smaller packets.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Ap-isolation ap_isolation] - an option that prevents any communication between stations connected to the same access point. The clients of the access point won't be able to communicate to each other, which makes it more secure, but less efficient for networking. There's [http://www.open-mesh.org/projects/batman-adv/wiki/Extended-Isolation extended ap isolation], which prevents all the wirelsss-to-wireless traffic and at the same time marks clients as isolated based on the user configuration.
* multicast mode - an option that reduces unnecessary packet transmissions. This optimization announces multicast listeners via the translation table mechanism, thereby signaling interest in certain multicast traffic instead of all of it. If disabled multicast traffic is forwarded to the every node in the network (broadcast).
* [http://www.open-mesh.org/projects/batman-adv/wiki/Understand-your-batman-adv-network routing_algo] - an option to change the routing algorithm.

== System configuration ==

In /etc/config/system you can set hostname and timezone. This is not strictly necessary for BATMAN to work, but it should be set correctly. The below timezone is correct for the pacific U.S. timezone. The naming convention for hostnames is: <router-model-name>-<some-unique-name-you-choose>

<pre>
config system
option hostname tl-wr703n-foo
option timezone PST8PDT,M3.2.0,M11.1.0
</pre>

You may also have to turn off dnsmasq. (someone else can chime in if this contradicts their working knowledge)

<pre>
/etc/init.d/dnsmasq disable
</pre>

= Testing =

You should see the 'sudomesh' and 'sudomesh-backchannel' wifi interfaces when running `sudo iwlist wlan0 scan`

= References =
<references/>

Mesh

2014-07-21T00:03:38Z

Jwentwistle: /* How to Help */ added user guide page

'''<big>Feb 21: Launched [https://sudoroom.org/wiki/Mesh/Blog#Developer_Launch.21 "Snow Crash" release candidate v.0.1.0] - now deploying the first batch of experimental nodes!</big>'''
 

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

A [http://en.wikipedia.org/wiki/Mesh_networking mesh network] is a network that allows the participants to freely share internet connectivity and build their own community-owned communications. It consists of routers running software that allow them to communicate with other routers around them. People who join the network enable others to be on the network and support [http://en.wikipedia.org/wiki/Net_neutrality net neutrality]. Community wireless mesh networks are growing around the world as alternatives to the existing system, creating local 'internets' rather than being dependent on the infrastructure developed by large Internet Service Providers and companies that mine and sell your personal information.

The software we've created is [http://en.wikipedia.org/wiki/Open_source open source] and we're using it to develop free internet for Oakland and the surrounding areas. 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.

[[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].
* We have '''weekly hack nights''' on Tuesdays and Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]]. The first three Thursdays of the month are work nights -- help us change the internet!
* Learn more at our general meetings, which are the last Thursdays of every month. 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!
* 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]! We're focused on these areas:
* [https://sudoroom.org/wiki/Mesh/Firmware Firmware]
* [https://github.com/sudomesh/service-browser Service Browser]
* [https://sudoroom.org/wiki/Mesh/Distributed_Services Services]

== 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/Donations|Donations]] - What's been donated to the group.
*[[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.

= 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.

= 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.

=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.

{{Mesh nav}}

''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]]

Mesh/BATMAN-adv

2014-07-20T22:49:06Z

Jwentwistle: changed menu structure

The [http://www.open-mesh.org/projects/batman-adv/wiki batman-adv] is an implementation of the [http://en.wikipedia.org/wiki/B.A.T.M.A.N. BATMAN routing protocol]. The protocol is configured with a file, but these settings can be changed with [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl]. The advantage of routing using batman-adv, rather than [https://github.com/cjdelisle/cjdns cjdns], is its a layer two protocol, which can send all types of layers three packets (udp, tcp/ip, etc). The protocol "forwards all traffic until it reaches the destination, hence emulating a virtual network switch of all nodes participating. Therefore all nodes appear to be link local and are unaware of the network's topology as well as unaffected by any network changes.<ref>[http://www.open-mesh.org/projects/batman-adv/wiki/Wiki BATMAN advanced overview]</ref>"

= [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl] configuration=

These are the main functions that change the configuration or adds a monitor:

* [http://downloads.open-mesh.org/batman/manpages/alfred-gpsd.html alfred-gpsd] - a used to distribute GPS location information about your batman-adv mesh network. This information could be, for example, combined with [http://www.open-mesh.org/projects/batmand/wiki/VisualizeMesh vis] to visualize your mesh topology with true geographic layout. The server fetches the information from locals nodes serving data from [http://manpages.ubuntu.com/manpages/karmic/en/man8/gpsd.8.html gpsd].
* [http://downloads.open-mesh.org/batman/manpages/batadv-vis.html batadv-vis] - its a server that saves local client tables and distributes these tables via [http://www.open-mesh.org/projects/open-mesh/wiki/Alfred alfred]. These tables can be used to create network topology maps.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Multi-link-optimize bonding] - when there's multiple interfaces with similar throughput, bonding can be used to increase frame throughput. It uses [http://oit2.utk.edu/helpdesk/kb/entry/1699/ round robin load balancing] to evenly distribute frames.
* [http://www.open-mesh.org/projects/batman-adv/wiki/DistributedArpTable-technical dat] - a distributed arp table is a Distributed Hash Table aimed to store ARP entries and to allow nodes to perform fast lookup operations. All the operations in the DHT (get and store) are performed on a set of nodes computed by means of a distributed hash function which input value is an IPv4 address.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Fragmentation-technical fragmentation] - a driver that sets fragmentation, which sends frames in fragmented frames when a wireless interfaces can't send/receive packets more than 1500 bytes. The protocol adds its own header to existing frames, which makes the packets have 1528 bytes.
* gw_mode - a server is an internet gateway, a client sends and receives traffic to and from the gateway
* [http://www.open-mesh.org/projects/batman-adv/wiki/NetworkCoding nc] (network coding) - when forwarding packets in a wireless mesh network, bandwidth can be saved by exploiting the information already present at the destinations of a forward. One way of doing this is network coding, where two packets are combined before transmission.
* traceroute - tries to find the bat-host name if the given parameter was not a MAC address. It can also try to guess the MAC address using an IPv4/IPv6 address or a hostname when the IPv4/IPv6 address was configured on top of the batman-adv interface of the destination device and both source and destination devices are in the same IP subnet.

= [http://downloads.open-mesh.org/batman/manpages/batmand.8.html batmand] configuration =

There functions to change the BATMAN configurations through [http://downloads.open-mesh.org/batman/manpages/batmand.8.html batmand]:

* s (visualization server) - Batman daemons may send their local view about their single-hop neighbors to the vis server. It collects the information and provides data in a format similar to [http://www.olsr.org/ OLSR's topology] information output.
* o (originator interval in ms) - a node transmits broadcast messages (we call them [http://www.open-mesh.org/projects/batman-adv/wiki/OGM originator message or OGM], [http://www.open-mesh.org/projects/batman-adv/wiki/Ogm-v2 version 2]) to inform the neighboring does about it's existence. Originator interval is the time to wait after sending one message and before sending the next message. The default value is 1000 ms (1 second). In a mobile network, you may want to detect network changes very quickly, so you need to send message very often, for example, use a value of 500 ms. In a static network, you can save bandwidth by using a higher value.

= Configuration files =
== Device configuration ==

This configuration is valid for [http://wiki.openwrt.org/about/history OpenWRT 12.09] (Attitude Adjustment), which uses BATMAN 2012.4.0. In newer versions, the version of BATMAN used is 2013.0.0 and the configuration of BATMAN slightly differs.

In /etc/config/wireless:

<pre>
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11g'
option channel '3' # You may want another channel
option disabled '0'
option phy 'phy0'

# the interface where non-mesh nodes connect
config wifi-iface
option device 'radio0'
option ifname 'ap0'
option encryption 'none'
option network 'lan'
option mode 'ap'
option ssid 'sudomesh' # You should change the ssid to be unique for dev purposes

# the mesh interface
config wifi-iface
option device 'radio0'
option ifname 'adhoc0'
option encryption 'none'
option network 'mesh'
option mode 'adhoc'
option bssid 'CA:FE:C0:DE:F0:0D' # You should change this to be unique for development purposes, but for meshing this should be the same for all routers on the mesh
option ssid 'sudomesh-backchannel' # You should change the ssid to be unique for development purposes, but for meshing this should be the same for all routers on the mesh
</pre>

Write some of this stuff down for reference later! You might need it!

== Network configuration ==

In /etc/config/network:

<pre>
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

# set up ethernet bridging between eth0 and bat0
# this means that packets can move between the ethernet port
# and the wifi mesh
config interface 'lan'
option type 'bridge'
option proto 'static'
option ipaddr '10.42.10.11' # this should be a unique IP
option netmask '255.255.0.0'
option dns '208.67.222.222'
option gateway '192.168.1.1' # an internet gateway, not sure how to deal with multiple gateways yet
option ifname 'eth0 bat0'

# the mesh interface
config interface 'mesh'
option ifname 'adhoc0'
option proto 'none'
option mtu '1528'
</pre>

== BATMAN configuration ==

There are [http://www.open-mesh.org/projects/batman-adv/wiki/Tweaking other options], but these are the recommended settings in /etc/config/batman-adv:

<pre>
config mesh 'bat0'
option interfaces 'adhoc0' # the interface for which to enable batman0
option 'aggregated_ogms'
option 'ap_isolation'
</pre>

* [http://www.open-mesh.org/projects/batman-adv/wiki/Tweaking aggregated_ogms] - an option that combines the [http://www.open-mesh.org/projects/batman-adv/wiki/OGM originator messages] into a single packet instead of a lot of smaller packets.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Ap-isolation ap_isolation] - an option that prevents any communication between stations connected to the same access point. The clients of the access point won't be able to communicate to each other, which makes it more secure, but less efficient for networking. There's [http://www.open-mesh.org/projects/batman-adv/wiki/Extended-Isolation extended ap isolation], which prevents all the wirelsss-to-wireless traffic and at the same time marks clients as isolated based on the user configuration.
* multicast mode - an option that reduces unnecessary packet transmissions. This optimization announces multicast listeners via the translation table mechanism, thereby signaling interest in certain multicast traffic instead of all of it. If disabled multicast traffic is forwarded to the every node in the network (broadcast).
* [http://www.open-mesh.org/projects/batman-adv/wiki/Understand-your-batman-adv-network routing_algo] - an option to change the routing algorithm.

== System configuration ==

In /etc/config/system you can set hostname and timezone. This is not strictly necessary for BATMAN to work, but it should be set correctly. The below timezone is correct for the pacific U.S. timezone. The naming convention for hostnames is: <router-model-name>-<some-unique-name-you-choose>

<pre>
config system
option hostname tl-wr703n-foo
option timezone PST8PDT,M3.2.0,M11.1.0
</pre>

You may also have to turn off dnsmasq. (someone else can chime in if this contradicts their working knowledge)

<pre>
/etc/init.d/dnsmasq disable
</pre>

= Testing =

You should see the 'sudomesh' and 'sudomesh-backchannel' wifi interfaces when running `sudo iwlist wlan0 scan`

= References =
<references/>

Mesh/BATMAN-adv

2014-07-20T22:47:20Z

Jwentwistle: added more details about algorithms

The [http://www.open-mesh.org/projects/batman-adv/wiki batman-adv] is an implementation of the [http://en.wikipedia.org/wiki/B.A.T.M.A.N. BATMAN routing protocol]. The protocol is configured with a file, but these settings can be changed with [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl]. The advantage of routing using batman-adv, rather than [https://github.com/cjdelisle/cjdns cjdns], is its a layer two protocol, which can send all types of layers three packets (udp, tcp/ip, etc). The protocol "forwards all traffic until it reaches the destination, hence emulating a virtual network switch of all nodes participating. Therefore all nodes appear to be link local and are unaware of the network's topology as well as unaffected by any network changes.<ref>[http://www.open-mesh.org/projects/batman-adv/wiki/Wiki BATMAN advanced overview]</ref>"

= [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl] configuration=

These are the main functions that change the configuration or adds a monitor:

* [http://downloads.open-mesh.org/batman/manpages/alfred-gpsd.html alfred-gpsd] - a used to distribute GPS location information about your batman-adv mesh network. This information could be, for example, combined with [http://www.open-mesh.org/projects/batmand/wiki/VisualizeMesh vis] to visualize your mesh topology with true geographic layout. The server fetches the information from locals nodes serving data from [http://manpages.ubuntu.com/manpages/karmic/en/man8/gpsd.8.html gpsd].
* [http://downloads.open-mesh.org/batman/manpages/batadv-vis.html batadv-vis] - its a server that saves local client tables and distributes these tables via [http://www.open-mesh.org/projects/open-mesh/wiki/Alfred alfred]. These tables can be used to create network topology maps.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Multi-link-optimize bonding] - when there's multiple interfaces with similar throughput, bonding can be used to increase frame throughput. It uses [http://oit2.utk.edu/helpdesk/kb/entry/1699/ round robin load balancing] to evenly distribute frames.
* [http://www.open-mesh.org/projects/batman-adv/wiki/DistributedArpTable-technical dat] - a distributed arp table is a Distributed Hash Table aimed to store ARP entries and to allow nodes to perform fast lookup operations. All the operations in the DHT (get and store) are performed on a set of nodes computed by means of a distributed hash function which input value is an IPv4 address.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Fragmentation-technical fragmentation] - a driver that sets fragmentation, which sends frames in fragmented frames when a wireless interfaces can't send/receive packets more than 1500 bytes. The protocol adds its own header to existing frames, which makes the packets have 1528 bytes.
* gw_mode - a server is an internet gateway, a client sends and receives traffic to and from the gateway
* [http://www.open-mesh.org/projects/batman-adv/wiki/NetworkCoding nc] (network coding) - when forwarding packets in a wireless mesh network, bandwidth can be saved by exploiting the information already present at the destinations of a forward. One way of doing this is network coding, where two packets are combined before transmission.
* traceroute - tries to find the bat-host name if the given parameter was not a MAC address. It can also try to guess the MAC address using an IPv4/IPv6 address or a hostname when the IPv4/IPv6 address was configured on top of the batman-adv interface of the destination device and both source and destination devices are in the same IP subnet.

= [http://downloads.open-mesh.org/batman/manpages/batmand.8.html batmand] configuration =

There functions to change the BATMAN configurations through [http://downloads.open-mesh.org/batman/manpages/batmand.8.html batmand]:

* s (visualization server) - Batman daemons may send their local view about their single-hop neighbors to the vis server. It collects the information and provides data in a format similar to [http://www.olsr.org/ OLSR's topology] information output.
* o (originator interval in ms) - a node transmits broadcast messages (we call them [http://www.open-mesh.org/projects/batman-adv/wiki/OGM originator message or OGM], [http://www.open-mesh.org/projects/batman-adv/wiki/Ogm-v2 version 2]) to inform the neighboring does about it's existence. Originator interval is the time to wait after sending one message and before sending the next message. The default value is 1000 ms (1 second). In a mobile network, you may want to detect network changes very quickly, so you need to send message very often, for example, use a value of 500 ms. In a static network, you can save bandwidth by using a higher value.

= configuration files =

This configuration is valid for [http://wiki.openwrt.org/about/history OpenWRT 12.09] (Attitude Adjustment), which uses BATMAN 2012.4.0. In newer versions, the version of BATMAN used is 2013.0.0 and the configuration of BATMAN slightly differs.

In /etc/config/wireless:

<pre>
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11g'
option channel '3' # You may want another channel
option disabled '0'
option phy 'phy0'

# the interface where non-mesh nodes connect
config wifi-iface
option device 'radio0'
option ifname 'ap0'
option encryption 'none'
option network 'lan'
option mode 'ap'
option ssid 'sudomesh' # You should change the ssid to be unique for dev purposes

# the mesh interface
config wifi-iface
option device 'radio0'
option ifname 'adhoc0'
option encryption 'none'
option network 'mesh'
option mode 'adhoc'
option bssid 'CA:FE:C0:DE:F0:0D' # You should change this to be unique for development purposes, but for meshing this should be the same for all routers on the mesh
option ssid 'sudomesh-backchannel' # You should change the ssid to be unique for development purposes, but for meshing this should be the same for all routers on the mesh
</pre>

Write some of this stuff down for reference later! You might need it!

= Network configuration =

In /etc/config/network:

<pre>
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

# set up ethernet bridging between eth0 and bat0
# this means that packets can move between the ethernet port
# and the wifi mesh
config interface 'lan'
option type 'bridge'
option proto 'static'
option ipaddr '10.42.10.11' # this should be a unique IP
option netmask '255.255.0.0'
option dns '208.67.222.222'
option gateway '192.168.1.1' # an internet gateway, not sure how to deal with multiple gateways yet
option ifname 'eth0 bat0'

# the mesh interface
config interface 'mesh'
option ifname 'adhoc0'
option proto 'none'
option mtu '1528'
</pre>

= BATMAN configuration =

There are [http://www.open-mesh.org/projects/batman-adv/wiki/Tweaking other options], but these are the recommended settings in /etc/config/batman-adv:

<pre>
config mesh 'bat0'
option interfaces 'adhoc0' # the interface for which to enable batman0
option 'aggregated_ogms'
option 'ap_isolation'
</pre>

* [http://www.open-mesh.org/projects/batman-adv/wiki/Tweaking aggregated_ogms] - an option that combines the [http://www.open-mesh.org/projects/batman-adv/wiki/OGM originator messages] into a single packet instead of a lot of smaller packets.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Ap-isolation ap_isolation] - an option that prevents any communication between stations connected to the same access point. The clients of the access point won't be able to communicate to each other, which makes it more secure, but less efficient for networking. There's [http://www.open-mesh.org/projects/batman-adv/wiki/Extended-Isolation extended ap isolation], which prevents all the wirelsss-to-wireless traffic and at the same time marks clients as isolated based on the user configuration.
* multicast mode - an option that reduces unnecessary packet transmissions. This optimization announces multicast listeners via the translation table mechanism, thereby signaling interest in certain multicast traffic instead of all of it. If disabled multicast traffic is forwarded to the every node in the network (broadcast).
* [http://www.open-mesh.org/projects/batman-adv/wiki/Understand-your-batman-adv-network routing_algo] - an option to change the routing algorithm.

= System configuration =

In /etc/config/system you can set hostname and timezone. This is not strictly necessary for BATMAN to work, but it should be set correctly. The below timezone is correct for the pacific U.S. timezone. The naming convention for hostnames is: <router-model-name>-<some-unique-name-you-choose>

<pre>
config system
option hostname tl-wr703n-foo
option timezone PST8PDT,M3.2.0,M11.1.0
</pre>

You may also have to turn off dnsmasq. (someone else can chime in if this contradicts their working knowledge)

<pre>
/etc/init.d/dnsmasq disable
</pre>

= Testing =

You should see the 'sudomesh' and 'sudomesh-backchannel' wifi interfaces when running `sudo iwlist wlan0 scan`

= References =
<references/>

Mesh/BATMAN-adv

2014-07-20T21:49:40Z

Jwentwistle: added details about the BATMAN config file

The [http://www.open-mesh.org/projects/batman-adv/wiki batman-adv] is an implementation of the [http://en.wikipedia.org/wiki/B.A.T.M.A.N. BATMAN routing protocol]. The protocol is configured with a file, but these settings can be changed with [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl]. The advantage of routing using batman-adv, rather than [https://github.com/cjdelisle/cjdns cjdns], is its a layer two protocol, which can send all types of layers three packets (udp, tcp/ip, etc). The protocol "forwards all traffic until it reaches the destination, hence emulating a virtual network switch of all nodes participating. Therefore all nodes appear to be link local and are unaware of the network's topology as well as unaffected by any network changes.<ref>[http://www.open-mesh.org/projects/batman-adv/wiki/Wiki BATMAN advanced overview]</ref>"

= [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl] configuration=

These are the main functions that change the configuration or adds a monitor:

* [http://downloads.open-mesh.org/batman/manpages/alfred-gpsd.html alfred-gpsd] - a used to distribute GPS location information about your batman-adv mesh network. This information could be, for example, combined with [http://www.open-mesh.org/projects/batmand/wiki/VisualizeMesh vis] to visualize your mesh topology with true geographic layout. The server fetches the information from locals nodes serving data from [http://manpages.ubuntu.com/manpages/karmic/en/man8/gpsd.8.html gpsd].
* [http://downloads.open-mesh.org/batman/manpages/batadv-vis.html batadv-vis] - its a server that saves local client tables and distributes these tables via [http://www.open-mesh.org/projects/open-mesh/wiki/Alfred alfred]. These tables can be used to create network topology maps.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Multi-link-optimize bonding] - when there's multiple interfaces with similar throughput, bonding can be used to increase frame throughput. It uses [http://oit2.utk.edu/helpdesk/kb/entry/1699/ round robin load balancing] to evenly distribute frames.
* [http://www.open-mesh.org/projects/batman-adv/wiki/DistributedArpTable-technical dat] - a distributed arp table is a Distributed Hash Table aimed to store ARP entries and to allow nodes to perform fast lookup operations. All the operations in the DHT (get and store) are performed on a set of nodes computed by means of a distributed hash function which input value is an IPv4 address.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Fragmentation-technical fragmentation] - a driver that sets fragmentation, which sends frames in fragmented frames when a wireless interfaces can't send/receive packets more than 1500 bytes. The protocol adds its own header to existing frames, which makes the packets have 1528 bytes.
* gw_mode - a server is an internet gateway, a client sends and receives traffic to and from the gateway
* [http://www.open-mesh.org/projects/batman-adv/wiki/NetworkCoding nc] (network coding) - when forwarding packets in a wireless mesh network, bandwidth can be saved by exploiting the information already present at the destinations of a forward. One way of doing this is network coding, where two packets are combined before transmission.
* traceroute - tries to find the bat-host name if the given parameter was not a MAC address. It can also try to guess the MAC address using an IPv4/IPv6 address or a hostname when the IPv4/IPv6 address was configured on top of the batman-adv interface of the destination device and both source and destination devices are in the same IP subnet.

= [http://downloads.open-mesh.org/batman/manpages/batmand.8.html batmand] configuration =

There functions to change the BATMAN configurations through [http://downloads.open-mesh.org/batman/manpages/batmand.8.html batmand]:

* s (visualization server) - Batman daemons may send their local view about their single-hop neighbors to the vis server. It collects the information and provides data in a format similar to [http://www.olsr.org/ OLSR's topology] information output.
* o (originator interval in ms) - a node transmits broadcast messages (we call them [http://www.open-mesh.org/projects/batman-adv/wiki/OGM originator message or OGM], [http://www.open-mesh.org/projects/batman-adv/wiki/Ogm-v2 version 2]) to inform the neighboring does about it's existence. Originator interval is the time to wait after sending one message and before sending the next message. The default value is 1000 ms (1 second). In a mobile network, you may want to detect network changes very quickly, so you need to send message very often, for example, use a value of 500 ms. In a static network, you can save bandwidth by using a higher value.

= configuration files =

This configuration is valid for [http://wiki.openwrt.org/about/history OpenWRT 12.09] (Attitude Adjustment), which uses BATMAN 2012.4.0. In newer versions, the version of BATMAN used is 2013.0.0 and the configuration of BATMAN slightly differs.

In /etc/config/wireless:

<pre>
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11g'
option channel '3' # You may want another channel
option disabled '0'
option phy 'phy0'

# the interface where non-mesh nodes connect
config wifi-iface
option device 'radio0'
option ifname 'ap0'
option encryption 'none'
option network 'lan'
option mode 'ap'
option ssid 'sudomesh' # You should change the ssid to be unique for dev purposes

# the mesh interface
config wifi-iface
option device 'radio0'
option ifname 'adhoc0'
option encryption 'none'
option network 'mesh'
option mode 'adhoc'
option bssid 'CA:FE:C0:DE:F0:0D' # You should change this to be unique for development purposes, but for meshing this should be the same for all routers on the mesh
option ssid 'sudomesh-backchannel' # You should change the ssid to be unique for development purposes, but for meshing this should be the same for all routers on the mesh
</pre>

Write some of this stuff down for reference later! You might need it!

= Network configuration =

In /etc/config/network:

<pre>
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

# set up ethernet bridging between eth0 and bat0
# this means that packets can move between the ethernet port
# and the wifi mesh
config interface 'lan'
option type 'bridge'
option proto 'static'
option ipaddr '10.42.10.11' # this should be a unique IP
option netmask '255.255.0.0'
option dns '208.67.222.222'
option gateway '192.168.1.1' # an internet gateway, not sure how to deal with multiple gateways yet
option ifname 'eth0 bat0'

# the mesh interface
config interface 'mesh'
option ifname 'adhoc0'
option proto 'none'
option mtu '1528'
</pre>

= BATMAN configuration =

There are [http://www.open-mesh.org/projects/batman-adv/wiki/Tweaking other options], but these are the recommended settings in /etc/config/batman-adv:

<pre>
config mesh 'bat0'
option interfaces 'adhoc0' # the interface for which to enable batman0
option 'aggregated_ogms'
option 'ap_isolation'
</pre>

* [http://www.open-mesh.org/projects/batman-adv/wiki/Tweaking aggregated_ogms] - an option that combines the [http://www.open-mesh.org/projects/batman-adv/wiki/OGM originator messages] into a single packet instead of a lot of smaller packets.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Ap-isolation ap_isolation] - an option that prevents any communication between stations connected to the same access point. The clients of the access point won't be able to communicate to each other, which makes it more secure, but less efficient for networking. There's [http://www.open-mesh.org/projects/batman-adv/wiki/Extended-Isolation extended ap isolation], which prevents all the wirelsss-to-wireless traffic and at the same time marks clients as isolated based on the user configuration.
* multicast mode - an option that reduces unnecessary packet transmissions. This optimization announces multicast listeners via the translation table mechanism, thereby signaling interest in certain multicast traffic instead of all of it. If disabled multicast traffic is forwarded to the every node in the network (broadcast).

= System configuration =

In /etc/config/system you can set hostname and timezone. This is not strictly necessary for BATMAN to work, but it should be set correctly. The below timezone is correct for the pacific U.S. timezone. The naming convention for hostnames is: <router-model-name>-<some-unique-name-you-choose>

<pre>
config system
option hostname tl-wr703n-foo
option timezone PST8PDT,M3.2.0,M11.1.0
</pre>

You may also have to turn off dnsmasq. (someone else can chime in if this contradicts their working knowledge)

<pre>
/etc/init.d/dnsmasq disable
</pre>

= Testing =

You should see the 'sudomesh' and 'sudomesh-backchannel' wifi interfaces when running `sudo iwlist wlan0 scan`

= References =
<references/>

Mesh/BATMAN-adv

2014-07-19T10:01:02Z

Jwentwistle: added network coding

The [http://www.open-mesh.org/projects/batman-adv/wiki batman-adv] is an implementation of the [http://en.wikipedia.org/wiki/B.A.T.M.A.N. BATMAN routing protocol]. The protocol is configured with a file, but these settings can be changed with [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl]. The advantage of routing using batman-adv, rather than [https://github.com/cjdelisle/cjdns cjdns], is its a layer two protocol, which can send all types of layers three packets (udp, tcp/ip, etc). The protocol "forwards all traffic until it reaches the destination, hence emulating a virtual network switch of all nodes participating. Therefore all nodes appear to be link local and are unaware of the network's topology as well as unaffected by any network changes.<ref>[http://www.open-mesh.org/projects/batman-adv/wiki/Wiki BATMAN advanced overview]</ref>"

= [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl] configuration=

These are the main functions that change the configuration or adds a monitor:

* [http://downloads.open-mesh.org/batman/manpages/alfred-gpsd.html alfred-gpsd] - a used to distribute GPS location information about your batman-adv mesh network. This information could be, for example, combined with [http://www.open-mesh.org/projects/batmand/wiki/VisualizeMesh vis] to visualize your mesh topology with true geographic layout. The server fetches the information from locals nodes serving data from [http://manpages.ubuntu.com/manpages/karmic/en/man8/gpsd.8.html gpsd].
* [http://downloads.open-mesh.org/batman/manpages/batadv-vis.html batadv-vis] - its a server that saves local client tables and distributes these tables via [http://www.open-mesh.org/projects/open-mesh/wiki/Alfred alfred]. These tables can be used to create network topology maps.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Multi-link-optimize bonding] - when there's multiple interfaces with similar throughput, bonding can be used to increase frame throughput. It uses [http://oit2.utk.edu/helpdesk/kb/entry/1699/ round robin load balancing] to evenly distribute frames.
* [http://www.open-mesh.org/projects/batman-adv/wiki/DistributedArpTable-technical dat] - a distributed arp table is a Distributed Hash Table aimed to store ARP entries and to allow nodes to perform fast lookup operations. All the operations in the DHT (get and store) are performed on a set of nodes computed by means of a distributed hash function which input value is an IPv4 address.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Fragmentation-technical fragmentation] - a driver that sets fragmentation, which sends frames in fragmented frames when a wireless interfaces can't send/receive packets more than 1500 bytes. The protocol adds its own header to existing frames, which makes the packets have 1528 bytes.
* gw_mode - a server is an internet gateway, a client sends and receives traffic to and from the gateway
* [http://www.open-mesh.org/projects/batman-adv/wiki/NetworkCoding nc] (network coding) - when forwarding packets in a wireless mesh network, bandwidth can be saved by exploiting the information already present at the destinations of a forward. One way of doing this is network coding, where two packets are combined before transmission.
* traceroute - tries to find the bat-host name if the given parameter was not a MAC address. It can also try to guess the MAC address using an IPv4/IPv6 address or a hostname when the IPv4/IPv6 address was configured on top of the batman-adv interface of the destination device and both source and destination devices are in the same IP subnet.

= [http://downloads.open-mesh.org/batman/manpages/batmand.8.html batmand] configuration =

There functions to change the BATMAN configurations through [http://downloads.open-mesh.org/batman/manpages/batmand.8.html batmand]:

* s (visualization server) - Batman daemons may send their local view about their single-hop neighbors to the vis server. It collects the information and provides data in a format similar to [http://www.olsr.org/ OLSR's topology] information output.
* o (originator interval in ms) - a node transmits broadcast messages (we call them [http://www.open-mesh.org/projects/batman-adv/wiki/OGM originator message or OGM], [http://www.open-mesh.org/projects/batman-adv/wiki/Ogm-v2 version 2]) to inform the neighboring does about it's existence. Originator interval is the time to wait after sending one message and before sending the next message. The default value is 1000 ms (1 second). In a mobile network, you may want to detect network changes very quickly, so you need to send message very often, for example, use a value of 500 ms. In a static network, you can save bandwidth by using a higher value.

= configuration files =

This configuration is valid for [http://wiki.openwrt.org/about/history OpenWRT 12.09] (Attitude Adjustment), which uses BATMAN 2012.4.0. In newer versions, the version of BATMAN used is 2013.0.0 and the configuration of BATMAN slightly differs.

In /etc/config/wireless:

<pre>
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11g'
option channel '3' # You may want another channel
option disabled '0'
option phy 'phy0'

# the interface where non-mesh nodes connect
config wifi-iface
option device 'radio0'
option ifname 'ap0'
option encryption 'none'
option network 'lan'
option mode 'ap'
option ssid 'sudomesh' # You should change the ssid to be unique for dev purposes

# the mesh interface
config wifi-iface
option device 'radio0'
option ifname 'adhoc0'
option encryption 'none'
option network 'mesh'
option mode 'adhoc'
option bssid 'CA:FE:C0:DE:F0:0D' # You should change this to be unique for development purposes, but for meshing this should be the same for all routers on the mesh
option ssid 'sudomesh-backchannel' # You should change the ssid to be unique for development purposes, but for meshing this should be the same for all routers on the mesh
</pre>

Write some of this stuff down for reference later! You might need it!

= Network configuration =

In /etc/config/network:

<pre>
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

# set up ethernet bridging between eth0 and bat0
# this means that packets can move between the ethernet port
# and the wifi mesh
config interface 'lan'
option type 'bridge'
option proto 'static'
option ipaddr '10.42.10.11' # this should be a unique IP
option netmask '255.255.0.0'
option dns '208.67.222.222'
option gateway '192.168.1.1' # an internet gateway, not sure how to deal with multiple gateways yet
option ifname 'eth0 bat0'

# the mesh interface
config interface 'mesh'
option ifname 'adhoc0'
option proto 'none'
option mtu '1528'
</pre>

= BATMAN configuration =

In /etc/config/batman-adv:

<pre>
config mesh 'bat0'
option interfaces 'adhoc0' # the interface for which to enable batman0
option 'aggregated_ogms' # no idea what this means
option 'ap_isolation' # no idea what this means
</pre>

= System configuration =

In /etc/config/system you can set hostname and timezone. This is not strictly necessary for BATMAN to work, but it should be set correctly. The below timezone is correct for the pacific U.S. timezone. The naming convention for hostnames is: <router-model-name>-<some-unique-name-you-choose>

<pre>
config system
option hostname tl-wr703n-foo
option timezone PST8PDT,M3.2.0,M11.1.0
</pre>

You may also have to turn off dnsmasq. (someone else can chime in if this contradicts their working knowledge)

<pre>
/etc/init.d/dnsmasq disable
</pre>

= Testing =

You should see the 'sudomesh' and 'sudomesh-backchannel' wifi interfaces when running `sudo iwlist wlan0 scan`

= References =
<references/>

Mesh/BATMAN-adv

2014-07-19T09:53:42Z

Jwentwistle: /* batmand configuration */ added version two

The [http://www.open-mesh.org/projects/batman-adv/wiki batman-adv] is an implementation of the [http://en.wikipedia.org/wiki/B.A.T.M.A.N. BATMAN routing protocol]. The protocol is configured with a file, but these settings can be changed with [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl]. The advantage of routing using batman-adv, rather than [https://github.com/cjdelisle/cjdns cjdns], is its a layer two protocol, which can send all types of layers three packets (udp, tcp/ip, etc). The protocol "forwards all traffic until it reaches the destination, hence emulating a virtual network switch of all nodes participating. Therefore all nodes appear to be link local and are unaware of the network's topology as well as unaffected by any network changes.<ref>[http://www.open-mesh.org/projects/batman-adv/wiki/Wiki BATMAN advanced overview]</ref>"

= [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl] configuration=

These are the main functions that change the configuration or adds a monitor:

* [http://downloads.open-mesh.org/batman/manpages/alfred-gpsd.html alfred-gpsd] - a used to distribute GPS location information about your batman-adv mesh network. This information could be, for example, combined with [http://www.open-mesh.org/projects/batmand/wiki/VisualizeMesh vis] to visualize your mesh topology with true geographic layout. The server fetches the information from locals nodes serving data from [http://manpages.ubuntu.com/manpages/karmic/en/man8/gpsd.8.html gpsd].
* [http://downloads.open-mesh.org/batman/manpages/batadv-vis.html batadv-vis] - its a server that saves local client tables and distributes these tables via [http://www.open-mesh.org/projects/open-mesh/wiki/Alfred alfred]. These tables can be used to create network topology maps.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Multi-link-optimize bonding] - when there's multiple interfaces with similar throughput, bonding can be used to increase frame throughput. It uses [http://oit2.utk.edu/helpdesk/kb/entry/1699/ round robin load balancing] to evenly distribute frames.
* [http://www.open-mesh.org/projects/batman-adv/wiki/DistributedArpTable-technical dat] - a distributed arp table is a Distributed Hash Table aimed to store ARP entries and to allow nodes to perform fast lookup operations. All the operations in the DHT (get and store) are performed on a set of nodes computed by means of a distributed hash function which input value is an IPv4 address.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Fragmentation-technical fragmentation] - a driver that sets fragmentation, which sends frames in fragmented frames when a wireless interfaces can't send/receive packets more than 1500 bytes. The protocol adds its own header to existing frames, which makes the packets have 1528 bytes.
* gw_mode - a server is an internet gateway, a client sends and receives traffic to and from the gateway
* traceroute - tries to find the bat-host name if the given parameter was not a MAC address. It can also try to guess the MAC address using an IPv4/IPv6 address or a hostname when the IPv4/IPv6 address was configured on top of the batman-adv interface of the destination device and both source and destination devices are in the same IP subnet.

= [http://downloads.open-mesh.org/batman/manpages/batmand.8.html batmand] configuration =

There functions to change the BATMAN configurations through [http://downloads.open-mesh.org/batman/manpages/batmand.8.html batmand]:

* s (visualization server) - Batman daemons may send their local view about their single-hop neighbors to the vis server. It collects the information and provides data in a format similar to [http://www.olsr.org/ OLSR's topology] information output.
* o (originator interval in ms) - a node transmits broadcast messages (we call them [http://www.open-mesh.org/projects/batman-adv/wiki/OGM originator message or OGM], [http://www.open-mesh.org/projects/batman-adv/wiki/Ogm-v2 version 2]) to inform the neighboring does about it's existence. Originator interval is the time to wait after sending one message and before sending the next message. The default value is 1000 ms (1 second). In a mobile network, you may want to detect network changes very quickly, so you need to send message very often, for example, use a value of 500 ms. In a static network, you can save bandwidth by using a higher value.

= configuration files =

This configuration is valid for [http://wiki.openwrt.org/about/history OpenWRT 12.09] (Attitude Adjustment), which uses BATMAN 2012.4.0. In newer versions, the version of BATMAN used is 2013.0.0 and the configuration of BATMAN slightly differs.

In /etc/config/wireless:

<pre>
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11g'
option channel '3' # You may want another channel
option disabled '0'
option phy 'phy0'

# the interface where non-mesh nodes connect
config wifi-iface
option device 'radio0'
option ifname 'ap0'
option encryption 'none'
option network 'lan'
option mode 'ap'
option ssid 'sudomesh' # You should change the ssid to be unique for dev purposes

# the mesh interface
config wifi-iface
option device 'radio0'
option ifname 'adhoc0'
option encryption 'none'
option network 'mesh'
option mode 'adhoc'
option bssid 'CA:FE:C0:DE:F0:0D' # You should change this to be unique for development purposes, but for meshing this should be the same for all routers on the mesh
option ssid 'sudomesh-backchannel' # You should change the ssid to be unique for development purposes, but for meshing this should be the same for all routers on the mesh
</pre>

Write some of this stuff down for reference later! You might need it!

= Network configuration =

In /etc/config/network:

<pre>
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

# set up ethernet bridging between eth0 and bat0
# this means that packets can move between the ethernet port
# and the wifi mesh
config interface 'lan'
option type 'bridge'
option proto 'static'
option ipaddr '10.42.10.11' # this should be a unique IP
option netmask '255.255.0.0'
option dns '208.67.222.222'
option gateway '192.168.1.1' # an internet gateway, not sure how to deal with multiple gateways yet
option ifname 'eth0 bat0'

# the mesh interface
config interface 'mesh'
option ifname 'adhoc0'
option proto 'none'
option mtu '1528'
</pre>

= BATMAN configuration =

In /etc/config/batman-adv:

<pre>
config mesh 'bat0'
option interfaces 'adhoc0' # the interface for which to enable batman0
option 'aggregated_ogms' # no idea what this means
option 'ap_isolation' # no idea what this means
</pre>

= System configuration =

In /etc/config/system you can set hostname and timezone. This is not strictly necessary for BATMAN to work, but it should be set correctly. The below timezone is correct for the pacific U.S. timezone. The naming convention for hostnames is: <router-model-name>-<some-unique-name-you-choose>

<pre>
config system
option hostname tl-wr703n-foo
option timezone PST8PDT,M3.2.0,M11.1.0
</pre>

You may also have to turn off dnsmasq. (someone else can chime in if this contradicts their working knowledge)

<pre>
/etc/init.d/dnsmasq disable
</pre>

= Testing =

You should see the 'sudomesh' and 'sudomesh-backchannel' wifi interfaces when running `sudo iwlist wlan0 scan`

= References =
<references/>

Mesh/BATMAN-adv

2014-07-19T09:48:47Z

Jwentwistle: /* batmand configuration */ added originator messages link

The [http://www.open-mesh.org/projects/batman-adv/wiki batman-adv] is an implementation of the [http://en.wikipedia.org/wiki/B.A.T.M.A.N. BATMAN routing protocol]. The protocol is configured with a file, but these settings can be changed with [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl]. The advantage of routing using batman-adv, rather than [https://github.com/cjdelisle/cjdns cjdns], is its a layer two protocol, which can send all types of layers three packets (udp, tcp/ip, etc). The protocol "forwards all traffic until it reaches the destination, hence emulating a virtual network switch of all nodes participating. Therefore all nodes appear to be link local and are unaware of the network's topology as well as unaffected by any network changes.<ref>[http://www.open-mesh.org/projects/batman-adv/wiki/Wiki BATMAN advanced overview]</ref>"

= [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl] configuration=

These are the main functions that change the configuration or adds a monitor:

* [http://downloads.open-mesh.org/batman/manpages/alfred-gpsd.html alfred-gpsd] - a used to distribute GPS location information about your batman-adv mesh network. This information could be, for example, combined with [http://www.open-mesh.org/projects/batmand/wiki/VisualizeMesh vis] to visualize your mesh topology with true geographic layout. The server fetches the information from locals nodes serving data from [http://manpages.ubuntu.com/manpages/karmic/en/man8/gpsd.8.html gpsd].
* [http://downloads.open-mesh.org/batman/manpages/batadv-vis.html batadv-vis] - its a server that saves local client tables and distributes these tables via [http://www.open-mesh.org/projects/open-mesh/wiki/Alfred alfred]. These tables can be used to create network topology maps.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Multi-link-optimize bonding] - when there's multiple interfaces with similar throughput, bonding can be used to increase frame throughput. It uses [http://oit2.utk.edu/helpdesk/kb/entry/1699/ round robin load balancing] to evenly distribute frames.
* [http://www.open-mesh.org/projects/batman-adv/wiki/DistributedArpTable-technical dat] - a distributed arp table is a Distributed Hash Table aimed to store ARP entries and to allow nodes to perform fast lookup operations. All the operations in the DHT (get and store) are performed on a set of nodes computed by means of a distributed hash function which input value is an IPv4 address.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Fragmentation-technical fragmentation] - a driver that sets fragmentation, which sends frames in fragmented frames when a wireless interfaces can't send/receive packets more than 1500 bytes. The protocol adds its own header to existing frames, which makes the packets have 1528 bytes.
* gw_mode - a server is an internet gateway, a client sends and receives traffic to and from the gateway
* traceroute - tries to find the bat-host name if the given parameter was not a MAC address. It can also try to guess the MAC address using an IPv4/IPv6 address or a hostname when the IPv4/IPv6 address was configured on top of the batman-adv interface of the destination device and both source and destination devices are in the same IP subnet.

= [http://downloads.open-mesh.org/batman/manpages/batmand.8.html batmand] configuration =

There functions to change the BATMAN configurations through [http://downloads.open-mesh.org/batman/manpages/batmand.8.html batmand]:

* s (visualization server) - Batman daemons may send their local view about their single-hop neighbors to the vis server. It collects the information and provides data in a format similar to [http://www.olsr.org/ OLSR's topology] information output.
* o (originator interval in ms) - a node transmits broadcast messages (we call them [http://www.open-mesh.org/projects/batman-adv/wiki/OGM originator message or OGM]) to inform the neighboring does about it's existence. Originator interval is the time to wait after sending one message and before sending the next message. The default value is 1000 ms (1 second). In a mobile network, you may want to detect network changes very quickly, so you need to send message very often, for example, use a value of 500 ms. In a static network, you can save bandwidth by using a higher value.

= configuration files =

This configuration is valid for [http://wiki.openwrt.org/about/history OpenWRT 12.09] (Attitude Adjustment), which uses BATMAN 2012.4.0. In newer versions, the version of BATMAN used is 2013.0.0 and the configuration of BATMAN slightly differs.

In /etc/config/wireless:

<pre>
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11g'
option channel '3' # You may want another channel
option disabled '0'
option phy 'phy0'

# the interface where non-mesh nodes connect
config wifi-iface
option device 'radio0'
option ifname 'ap0'
option encryption 'none'
option network 'lan'
option mode 'ap'
option ssid 'sudomesh' # You should change the ssid to be unique for dev purposes

# the mesh interface
config wifi-iface
option device 'radio0'
option ifname 'adhoc0'
option encryption 'none'
option network 'mesh'
option mode 'adhoc'
option bssid 'CA:FE:C0:DE:F0:0D' # You should change this to be unique for development purposes, but for meshing this should be the same for all routers on the mesh
option ssid 'sudomesh-backchannel' # You should change the ssid to be unique for development purposes, but for meshing this should be the same for all routers on the mesh
</pre>

Write some of this stuff down for reference later! You might need it!

= Network configuration =

In /etc/config/network:

<pre>
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

# set up ethernet bridging between eth0 and bat0
# this means that packets can move between the ethernet port
# and the wifi mesh
config interface 'lan'
option type 'bridge'
option proto 'static'
option ipaddr '10.42.10.11' # this should be a unique IP
option netmask '255.255.0.0'
option dns '208.67.222.222'
option gateway '192.168.1.1' # an internet gateway, not sure how to deal with multiple gateways yet
option ifname 'eth0 bat0'

# the mesh interface
config interface 'mesh'
option ifname 'adhoc0'
option proto 'none'
option mtu '1528'
</pre>

= BATMAN configuration =

In /etc/config/batman-adv:

<pre>
config mesh 'bat0'
option interfaces 'adhoc0' # the interface for which to enable batman0
option 'aggregated_ogms' # no idea what this means
option 'ap_isolation' # no idea what this means
</pre>

= System configuration =

In /etc/config/system you can set hostname and timezone. This is not strictly necessary for BATMAN to work, but it should be set correctly. The below timezone is correct for the pacific U.S. timezone. The naming convention for hostnames is: <router-model-name>-<some-unique-name-you-choose>

<pre>
config system
option hostname tl-wr703n-foo
option timezone PST8PDT,M3.2.0,M11.1.0
</pre>

You may also have to turn off dnsmasq. (someone else can chime in if this contradicts their working knowledge)

<pre>
/etc/init.d/dnsmasq disable
</pre>

= Testing =

You should see the 'sudomesh' and 'sudomesh-backchannel' wifi interfaces when running `sudo iwlist wlan0 scan`

= References =
<references/>

Mesh/BATMAN-adv

2014-07-19T09:45:33Z

Jwentwistle: /* batmand configuration */

The [http://www.open-mesh.org/projects/batman-adv/wiki batman-adv] is an implementation of the [http://en.wikipedia.org/wiki/B.A.T.M.A.N. BATMAN routing protocol]. The protocol is configured with a file, but these settings can be changed with [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl]. The advantage of routing using batman-adv, rather than [https://github.com/cjdelisle/cjdns cjdns], is its a layer two protocol, which can send all types of layers three packets (udp, tcp/ip, etc). The protocol "forwards all traffic until it reaches the destination, hence emulating a virtual network switch of all nodes participating. Therefore all nodes appear to be link local and are unaware of the network's topology as well as unaffected by any network changes.<ref>[http://www.open-mesh.org/projects/batman-adv/wiki/Wiki BATMAN advanced overview]</ref>"

= [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl] configuration=

These are the main functions that change the configuration or adds a monitor:

* [http://downloads.open-mesh.org/batman/manpages/alfred-gpsd.html alfred-gpsd] - a used to distribute GPS location information about your batman-adv mesh network. This information could be, for example, combined with [http://www.open-mesh.org/projects/batmand/wiki/VisualizeMesh vis] to visualize your mesh topology with true geographic layout. The server fetches the information from locals nodes serving data from [http://manpages.ubuntu.com/manpages/karmic/en/man8/gpsd.8.html gpsd].
* [http://downloads.open-mesh.org/batman/manpages/batadv-vis.html batadv-vis] - its a server that saves local client tables and distributes these tables via [http://www.open-mesh.org/projects/open-mesh/wiki/Alfred alfred]. These tables can be used to create network topology maps.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Multi-link-optimize bonding] - when there's multiple interfaces with similar throughput, bonding can be used to increase frame throughput. It uses [http://oit2.utk.edu/helpdesk/kb/entry/1699/ round robin load balancing] to evenly distribute frames.
* [http://www.open-mesh.org/projects/batman-adv/wiki/DistributedArpTable-technical dat] - a distributed arp table is a Distributed Hash Table aimed to store ARP entries and to allow nodes to perform fast lookup operations. All the operations in the DHT (get and store) are performed on a set of nodes computed by means of a distributed hash function which input value is an IPv4 address.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Fragmentation-technical fragmentation] - a driver that sets fragmentation, which sends frames in fragmented frames when a wireless interfaces can't send/receive packets more than 1500 bytes. The protocol adds its own header to existing frames, which makes the packets have 1528 bytes.
* gw_mode - a server is an internet gateway, a client sends and receives traffic to and from the gateway
* traceroute - tries to find the bat-host name if the given parameter was not a MAC address. It can also try to guess the MAC address using an IPv4/IPv6 address or a hostname when the IPv4/IPv6 address was configured on top of the batman-adv interface of the destination device and both source and destination devices are in the same IP subnet.

= [http://downloads.open-mesh.org/batman/manpages/batmand.8.html batmand] configuration =

There functions to change the BATMAN configurations through [http://downloads.open-mesh.org/batman/manpages/batmand.8.html batmand]:

* s (visualization server) - Batman daemons may send their local view about their single-hop neighbors to the vis server. It collects the information and provides data in a format similar to [http://www.olsr.org/ OLSR's topology] information output.
* o (originator interval in ms) - a node transmits broadcast messages (we call them originator message or OGM) to inform the neighboring does about it's existence. Originator interval is the time to wait after sending one message and before sending the next message. The default value is 1000 ms (1 second). In a mobile network, you may want to detect network changes very quickly, so you need to send message very often, for example, use a value of 500 ms. In a static network, you can save bandwidth by using a higher value.

= configuration files =

This configuration is valid for [http://wiki.openwrt.org/about/history OpenWRT 12.09] (Attitude Adjustment), which uses BATMAN 2012.4.0. In newer versions, the version of BATMAN used is 2013.0.0 and the configuration of BATMAN slightly differs.

In /etc/config/wireless:

<pre>
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11g'
option channel '3' # You may want another channel
option disabled '0'
option phy 'phy0'

# the interface where non-mesh nodes connect
config wifi-iface
option device 'radio0'
option ifname 'ap0'
option encryption 'none'
option network 'lan'
option mode 'ap'
option ssid 'sudomesh' # You should change the ssid to be unique for dev purposes

# the mesh interface
config wifi-iface
option device 'radio0'
option ifname 'adhoc0'
option encryption 'none'
option network 'mesh'
option mode 'adhoc'
option bssid 'CA:FE:C0:DE:F0:0D' # You should change this to be unique for development purposes, but for meshing this should be the same for all routers on the mesh
option ssid 'sudomesh-backchannel' # You should change the ssid to be unique for development purposes, but for meshing this should be the same for all routers on the mesh
</pre>

Write some of this stuff down for reference later! You might need it!

= Network configuration =

In /etc/config/network:

<pre>
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

# set up ethernet bridging between eth0 and bat0
# this means that packets can move between the ethernet port
# and the wifi mesh
config interface 'lan'
option type 'bridge'
option proto 'static'
option ipaddr '10.42.10.11' # this should be a unique IP
option netmask '255.255.0.0'
option dns '208.67.222.222'
option gateway '192.168.1.1' # an internet gateway, not sure how to deal with multiple gateways yet
option ifname 'eth0 bat0'

# the mesh interface
config interface 'mesh'
option ifname 'adhoc0'
option proto 'none'
option mtu '1528'
</pre>

= BATMAN configuration =

In /etc/config/batman-adv:

<pre>
config mesh 'bat0'
option interfaces 'adhoc0' # the interface for which to enable batman0
option 'aggregated_ogms' # no idea what this means
option 'ap_isolation' # no idea what this means
</pre>

= System configuration =

In /etc/config/system you can set hostname and timezone. This is not strictly necessary for BATMAN to work, but it should be set correctly. The below timezone is correct for the pacific U.S. timezone. The naming convention for hostnames is: <router-model-name>-<some-unique-name-you-choose>

<pre>
config system
option hostname tl-wr703n-foo
option timezone PST8PDT,M3.2.0,M11.1.0
</pre>

You may also have to turn off dnsmasq. (someone else can chime in if this contradicts their working knowledge)

<pre>
/etc/init.d/dnsmasq disable
</pre>

= Testing =

You should see the 'sudomesh' and 'sudomesh-backchannel' wifi interfaces when running `sudo iwlist wlan0 scan`

= References =
<references/>

Mesh/BATMAN-adv

2014-07-19T09:43:50Z

Jwentwistle: updated batmand functions

The [http://www.open-mesh.org/projects/batman-adv/wiki batman-adv] is an implementation of the [http://en.wikipedia.org/wiki/B.A.T.M.A.N. BATMAN routing protocol]. The protocol is configured with a file, but these settings can be changed with [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl]. The advantage of routing using batman-adv, rather than [https://github.com/cjdelisle/cjdns cjdns], is its a layer two protocol, which can send all types of layers three packets (udp, tcp/ip, etc). The protocol "forwards all traffic until it reaches the destination, hence emulating a virtual network switch of all nodes participating. Therefore all nodes appear to be link local and are unaware of the network's topology as well as unaffected by any network changes.<ref>[http://www.open-mesh.org/projects/batman-adv/wiki/Wiki BATMAN advanced overview]</ref>"

= [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl] configuration=

These are the main functions that change the configuration or adds a monitor:

* [http://downloads.open-mesh.org/batman/manpages/alfred-gpsd.html alfred-gpsd] - a used to distribute GPS location information about your batman-adv mesh network. This information could be, for example, combined with [http://www.open-mesh.org/projects/batmand/wiki/VisualizeMesh vis] to visualize your mesh topology with true geographic layout. The server fetches the information from locals nodes serving data from [http://manpages.ubuntu.com/manpages/karmic/en/man8/gpsd.8.html gpsd].
* [http://downloads.open-mesh.org/batman/manpages/batadv-vis.html batadv-vis] - its a server that saves local client tables and distributes these tables via [http://www.open-mesh.org/projects/open-mesh/wiki/Alfred alfred]. These tables can be used to create network topology maps.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Multi-link-optimize bonding] - when there's multiple interfaces with similar throughput, bonding can be used to increase frame throughput. It uses [http://oit2.utk.edu/helpdesk/kb/entry/1699/ round robin load balancing] to evenly distribute frames.
* [http://www.open-mesh.org/projects/batman-adv/wiki/DistributedArpTable-technical dat] - a distributed arp table is a Distributed Hash Table aimed to store ARP entries and to allow nodes to perform fast lookup operations. All the operations in the DHT (get and store) are performed on a set of nodes computed by means of a distributed hash function which input value is an IPv4 address.
* [http://www.open-mesh.org/projects/batman-adv/wiki/Fragmentation-technical fragmentation] - a driver that sets fragmentation, which sends frames in fragmented frames when a wireless interfaces can't send/receive packets more than 1500 bytes. The protocol adds its own header to existing frames, which makes the packets have 1528 bytes.
* gw_mode - a server is an internet gateway, a client sends and receives traffic to and from the gateway
* traceroute - tries to find the bat-host name if the given parameter was not a MAC address. It can also try to guess the MAC address using an IPv4/IPv6 address or a hostname when the IPv4/IPv6 address was configured on top of the batman-adv interface of the destination device and both source and destination devices are in the same IP subnet.

= [http://downloads.open-mesh.org/batman/manpages/batmand.8.html batmand] configuration =

There functions to change the BATMAN configurations through [http://downloads.open-mesh.org/batman/manpages/batmand.8.html batmand]:

* s (visualization server) - Batman daemons may send their local view about their single-hop neighbors to the vis server. It collects the information and provides data in a format similar to [http://www.olsr.org/ OLSR's topology] information output.
* -o (originator interval in ms) - a node transmits broadcast messages (we call them originator message or OGM) to inform the neighboring does about it's existence. Originator interval is the time to wait after sending one message and before sending the next message. The default value is 1000 ms (1 second). In a mobile network, you may want to detect network changes very quickly, so you need to send message very often, for example, use a value of 500 ms. In a static network, you can save bandwidth by using a higher value.

= configuration files =

This configuration is valid for [http://wiki.openwrt.org/about/history OpenWRT 12.09] (Attitude Adjustment), which uses BATMAN 2012.4.0. In newer versions, the version of BATMAN used is 2013.0.0 and the configuration of BATMAN slightly differs.

In /etc/config/wireless:

<pre>
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11g'
option channel '3' # You may want another channel
option disabled '0'
option phy 'phy0'

# the interface where non-mesh nodes connect
config wifi-iface
option device 'radio0'
option ifname 'ap0'
option encryption 'none'
option network 'lan'
option mode 'ap'
option ssid 'sudomesh' # You should change the ssid to be unique for dev purposes

# the mesh interface
config wifi-iface
option device 'radio0'
option ifname 'adhoc0'
option encryption 'none'
option network 'mesh'
option mode 'adhoc'
option bssid 'CA:FE:C0:DE:F0:0D' # You should change this to be unique for development purposes, but for meshing this should be the same for all routers on the mesh
option ssid 'sudomesh-backchannel' # You should change the ssid to be unique for development purposes, but for meshing this should be the same for all routers on the mesh
</pre>

Write some of this stuff down for reference later! You might need it!

= Network configuration =

In /etc/config/network:

<pre>
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

# set up ethernet bridging between eth0 and bat0
# this means that packets can move between the ethernet port
# and the wifi mesh
config interface 'lan'
option type 'bridge'
option proto 'static'
option ipaddr '10.42.10.11' # this should be a unique IP
option netmask '255.255.0.0'
option dns '208.67.222.222'
option gateway '192.168.1.1' # an internet gateway, not sure how to deal with multiple gateways yet
option ifname 'eth0 bat0'

# the mesh interface
config interface 'mesh'
option ifname 'adhoc0'
option proto 'none'
option mtu '1528'
</pre>

= BATMAN configuration =

In /etc/config/batman-adv:

<pre>
config mesh 'bat0'
option interfaces 'adhoc0' # the interface for which to enable batman0
option 'aggregated_ogms' # no idea what this means
option 'ap_isolation' # no idea what this means
</pre>

= System configuration =

In /etc/config/system you can set hostname and timezone. This is not strictly necessary for BATMAN to work, but it should be set correctly. The below timezone is correct for the pacific U.S. timezone. The naming convention for hostnames is: <router-model-name>-<some-unique-name-you-choose>

<pre>
config system
option hostname tl-wr703n-foo
option timezone PST8PDT,M3.2.0,M11.1.0
</pre>

You may also have to turn off dnsmasq. (someone else can chime in if this contradicts their working knowledge)

<pre>
/etc/init.d/dnsmasq disable
</pre>

= Testing =

You should see the 'sudomesh' and 'sudomesh-backchannel' wifi interfaces when running `sudo iwlist wlan0 scan`

= References =
<references/>

Mesh/BATMAN-adv

2014-07-19T09:29:49Z

Jwentwistle: /* Configure batctl */ changed header

Mesh/BATMAN-adv

2014-07-19T09:28:51Z

Jwentwistle: /* Configure batctl */ added a link

Mesh/BATMAN-adv

2014-07-19T07:57:50Z

Jwentwistle: updated but needs more

Mesh/BATMAN-adv

2014-07-19T06:07:28Z

Jwentwistle: added layer two information

Mesh/BATMAN-adv

2014-07-19T05:58:09Z

Jwentwistle: added batctl to description

Mesh

2014-07-19T05:38:20Z

Jwentwistle: changed the links

'''<big>Feb 21: Launched [https://sudoroom.org/wiki/Mesh/Blog#Developer_Launch.21 "Snow Crash" release candidate v.0.1.0] - now deploying the first batch of experimental nodes!</big>'''
 

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

A [http://en.wikipedia.org/wiki/Mesh_networking mesh network] is a network that allows the participants to freely share internet connectivity and build their own community-owned communications. It consists of routers running software that allow them to communicate with other routers around them. People who join the network enable others to be on the network and support [http://en.wikipedia.org/wiki/Net_neutrality net neutrality]. Community wireless mesh networks are growing around the world as alternatives to the existing system, creating local 'internets' rather than being dependent on the infrastructure developed by large Internet Service Providers and companies that mine and sell your personal information.

The software we've created is [http://en.wikipedia.org/wiki/Open_source open source] and we're using it to develop free internet for Oakland and the surrounding areas. 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.

[[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].
* We have '''weekly hack nights''' on Tuesdays and Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]]. The first three Thursdays of the month are work nights -- help us change the internet!
* Learn more at our general meetings, which are the last Thursdays of every month. 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!
* 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 user introduction to help you get involved!

*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]! We're focused on these areas:
* [https://sudoroom.org/wiki/Mesh/Firmware Firmware]
* [https://github.com/sudomesh/service-browser Service Browser]
* [https://sudoroom.org/wiki/Mesh/Distributed_Services Services]

== 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/Donations|Donations]] - What's been donated to the group.
*[[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.

= 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.

= 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.

=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.

{{Mesh nav}}

''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]]

Mesh

2014-07-19T05:33:53Z

Jwentwistle: /* Research */

'''<big>Feb 21: Launched [https://sudoroom.org/wiki/Mesh/Blog#Developer_Launch.21 "Snow Crash" release candidate v.0.1.0] - now deploying the first batch of experimental nodes!</big>'''
 

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

A [http://en.wikipedia.org/wiki/Mesh_networking mesh network] is a network that allows the participants to freely share internet connectivity and build their own community-owned communications. It consists of routers running software that allow them to communicate with other routers around them. People who join the network enable others to be on the network and support [http://en.wikipedia.org/wiki/Net_neutrality net neutrality]. Community wireless mesh networks are growing around the world as alternatives to the existing system, creating local 'internets' rather than being dependent on the infrastructure developed by large Internet Service Providers and companies that mine and sell your personal information.

The software we've created is [http://en.wikipedia.org/wiki/Open_source open source] and we're using it to develop free internet for Oakland and the surrounding areas. 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.

[[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].
* We have '''weekly hack nights''' on Tuesdays and Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]]. The first three Thursdays of the month are work nights -- help us change the internet!
* Learn more at our general meetings, which are the last Thursdays of every month. 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!
* 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 user introduction to help you get involved!

*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]! We're focused on these areas:
* [https://sudoroom.org/wiki/Mesh/Firmware Firmware]
* [https://github.com/sudomesh/service-browser Service Browser]
* [https://sudoroom.org/wiki/Mesh/Distributed_Services Services]

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

=Logistics=
*[[Mesh/Checkouts]] - Who took what gear home.
*[[Mesh/Donations]] - What's been donated to the group.
*[[Mesh/Inventory]] - Continually-updated inventory of our hardware and gear.
*[[Mesh/Marketing]] - Inspiration and links to marketing materials in progress.
*[[Mesh/Naming]] - What do we call ourselves? A lineage of bikeshedding.
*[[Mesh/Purchases]] - Details on our purchases, made by either individuals or through our crowdfunded money.

= 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.

= 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.

=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.

{{Mesh nav}}

''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]]

Mesh/Distributed Services

2014-07-19T05:02:25Z

Jwentwistle:

=Services=

The network ''should'' provide secure communication services (email, contacts, calendar, phone) to create more incentive to be on the network. The services can be integrated 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]). These services will use existing open source projects.

==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/Distributed Services

2014-07-19T05:01:54Z

Jwentwistle: added references tag

Mesh/Distributed Services

2014-07-19T05:00:37Z

Jwentwistle: added irmin, distributed database

Mesh

2014-07-19T01:57:43Z

Jwentwistle: changed layout of sitemap

'''<big>Feb 21: Launched [https://sudoroom.org/wiki/Mesh/Blog#Developer_Launch.21 "Snow Crash" release candidate v.0.1.0] - now deploying the first batch of experimental nodes!</big>'''
 

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

A [http://en.wikipedia.org/wiki/Mesh_networking mesh network] is a network that allows the participants to freely share internet connectivity and build their own community-owned communications. It consists of routers running software that allow them to communicate with other routers around them. People who join the network enable others to be on the network and support [http://en.wikipedia.org/wiki/Net_neutrality net neutrality]. Community wireless mesh networks are growing around the world as alternatives to the existing system, creating local 'internets' rather than being dependent on the infrastructure developed by large Internet Service Providers and companies that mine and sell your personal information.

The software we've created is [http://en.wikipedia.org/wiki/Open_source open source] and we're using it to develop free internet for Oakland and the surrounding areas. 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.

[[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].
* We have '''weekly hack nights''' on Tuesdays and Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]]. The first three Thursdays of the month are work nights -- help us change the internet!
* Learn more at our general meetings, which are the last Thursdays of every month. 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!
* 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 user introduction to help you get involved!

*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]! We're focused on these areas:
* [https://sudoroom.org/wiki/Mesh/Firmware Firmware]
* [https://github.com/sudomesh/service-browser Service Browser]
* [https://sudoroom.org/wiki/Mesh/Distributed_Services Services]

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

=Logistics=
*[[Mesh/Checkouts]] - Who took what gear home.
*[[Mesh/Donations]] - What's been donated to the group.
*[[Mesh/Inventory]] - Continually-updated inventory of our hardware and gear.
*[[Mesh/Marketing]] - Inspiration and links to marketing materials in progress.
*[[Mesh/Naming]] - What do we call ourselves? A lineage of bikeshedding.
*[[Mesh/Purchases]] - Details on our purchases, made by either individuals or through our crowdfunded money.

= 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.

= 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.

=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.

{{Mesh nav}}

''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]]

Mesh

2014-07-19T01:55:27Z

Jwentwistle: centered sitemap

'''<big>Feb 21: Launched [https://sudoroom.org/wiki/Mesh/Blog#Developer_Launch.21 "Snow Crash" release candidate v.0.1.0] - now deploying the first batch of experimental nodes!</big>'''
 

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

A [http://en.wikipedia.org/wiki/Mesh_networking mesh network] is a network that allows the participants to freely share internet connectivity and build their own community-owned communications. It consists of routers running software that allow them to communicate with other routers around them. People who join the network enable others to be on the network and support [http://en.wikipedia.org/wiki/Net_neutrality net neutrality]. Community wireless mesh networks are growing around the world as alternatives to the existing system, creating local 'internets' rather than being dependent on the infrastructure developed by large Internet Service Providers and companies that mine and sell your personal information.

The software we've created is [http://en.wikipedia.org/wiki/Open_source open source] and we're using it to develop free internet for Oakland and the surrounding areas. 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.

[[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].
* We have '''weekly hack nights''' on Tuesdays and Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]]. The first three Thursdays of the month are work nights -- help us change the internet!
* Learn more at our general meetings, which are the last Thursdays of every month. 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!
* 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 user introduction to help you get involved!

*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]! We're focused on these areas:
* [https://sudoroom.org/wiki/Mesh/Firmware Firmware]
* [https://github.com/sudomesh/service-browser Service Browser]
* [https://sudoroom.org/wiki/Mesh/Distributed_Services Services]

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

=Logistics=
*[[Mesh/Checkouts]] - Who took what gear home.
*[[Mesh/Donations]] - What's been donated to the group.
*[[Mesh/Inventory]] - Continually-updated inventory of our hardware and gear.
*[[Mesh/Marketing]] - Inspiration and links to marketing materials in progress.
*[[Mesh/Naming]] - What do we call ourselves? A lineage of bikeshedding.
*[[Mesh/Purchases]] - Details on our purchases, made by either individuals or through our crowdfunded money.

= 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.

= 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.

=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.

<div style="text-align: center;">
{{Mesh nav}}
</div>

''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]]

Mesh

2014-07-19T01:53:02Z

Jwentwistle: changed the layout

'''<big>Feb 21: Launched [https://sudoroom.org/wiki/Mesh/Blog#Developer_Launch.21 "Snow Crash" release candidate v.0.1.0] - now deploying the first batch of experimental nodes!</big>'''
 

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

A [http://en.wikipedia.org/wiki/Mesh_networking mesh network] is a network that allows the participants to freely share internet connectivity and build their own community-owned communications. It consists of routers running software that allow them to communicate with other routers around them. People who join the network enable others to be on the network and support [http://en.wikipedia.org/wiki/Net_neutrality net neutrality]. Community wireless mesh networks are growing around the world as alternatives to the existing system, creating local 'internets' rather than being dependent on the infrastructure developed by large Internet Service Providers and companies that mine and sell your personal information.

The software we've created is [http://en.wikipedia.org/wiki/Open_source open source] and we're using it to develop free internet for Oakland and the surrounding areas. 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.

[[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].
* We have '''weekly hack nights''' on Tuesdays and Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]]. The first three Thursdays of the month are work nights -- help us change the internet!
* Learn more at our general meetings, which are the last Thursdays of every month. 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!
* 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 user introduction to help you get involved!

*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]! We're focused on these areas:
* [https://sudoroom.org/wiki/Mesh/Firmware Firmware]
* [https://github.com/sudomesh/service-browser Service Browser]
* [https://sudoroom.org/wiki/Mesh/Distributed_Services Services]

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

=Logistics=
*[[Mesh/Checkouts]] - Who took what gear home.
*[[Mesh/Donations]] - What's been donated to the group.
*[[Mesh/Inventory]] - Continually-updated inventory of our hardware and gear.
*[[Mesh/Marketing]] - Inspiration and links to marketing materials in progress.
*[[Mesh/Naming]] - What do we call ourselves? A lineage of bikeshedding.
*[[Mesh/Purchases]] - Details on our purchases, made by either individuals or through our crowdfunded money.

= 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.

= 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.

=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.

{{Mesh nav}}

''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]]

Mesh

2014-07-19T01:49:02Z

Jwentwistle:

'''<big>Feb 21: Launched [https://sudoroom.org/wiki/Mesh/Blog#Developer_Launch.21 "Snow Crash" release candidate v.0.1.0] - now deploying the first batch of experimental nodes!</big>'''
 

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

A [http://en.wikipedia.org/wiki/Mesh_networking mesh network] is a network that allows the participants to freely share internet connectivity and build their own community-owned communications. It consists of routers running software that allow them to communicate with other routers around them. People who join the network enable others to be on the network and support [http://en.wikipedia.org/wiki/Net_neutrality net neutrality]. Community wireless mesh networks are growing around the world as alternatives to the existing system, creating local 'internets' rather than being dependent on the infrastructure developed by large Internet Service Providers and companies that mine and sell your personal information.

The software we've created is [http://en.wikipedia.org/wiki/Open_source open source] and we're using it to develop free internet for Oakland and the surrounding areas. 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.

[[File:Mesh_Oakland_High_Res.png|250px|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].
* We have '''weekly hack nights''' on Tuesdays and Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]]. The first three Thursdays of the month are work nights -- help us change the internet!
* Learn more at our general meetings, which are the last Thursdays of every month. 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!
* 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 user introduction to help you get involved!

*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]! We're focused on these areas:
* [https://sudoroom.org/wiki/Mesh/Firmware Firmware]
* [https://github.com/sudomesh/service-browser Service Browser]
* [https://sudoroom.org/wiki/Mesh/Distributed_Services Services]

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

=Logistics=
*[[Mesh/Checkouts]] - Who took what gear home.
*[[Mesh/Donations]] - What's been donated to the group.
*[[Mesh/Inventory]] - Continually-updated inventory of our hardware and gear.
*[[Mesh/Marketing]] - Inspiration and links to marketing materials in progress.
*[[Mesh/Naming]] - What do we call ourselves? A lineage of bikeshedding.
*[[Mesh/Purchases]] - Details on our purchases, made by either individuals or through our crowdfunded money.

= 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.

= 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.

=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.

{{Mesh nav}}

''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]]

Mesh

2014-07-19T01:48:11Z

Jwentwistle: the quick links is a site map, usually at the bottom, we shouldn't barrage our viewers with a lot of links at once

'''<big>Feb 21: Launched [https://sudoroom.org/wiki/Mesh/Blog#Developer_Launch.21 "Snow Crash" release candidate v.0.1.0] - now deploying the first batch of experimental nodes!</big>'''
 

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

A [http://en.wikipedia.org/wiki/Mesh_networking mesh network] is a network that allows the participants to freely share internet connectivity and build their own community-owned communications. It consists of routers running software that allow them to communicate with other routers around them. People who join the network enable others to be on the network and support [http://en.wikipedia.org/wiki/Net_neutrality net neutrality]. Community wireless mesh networks are growing around the world as alternatives to the existing system, creating local 'internets' rather than being dependent on the infrastructure developed by large Internet Service Providers and companies that mine and sell your personal information.

The software we've created is [http://en.wikipedia.org/wiki/Open_source open source] and we're using it to develop free internet for Oakland and the surrounding areas. 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.

[[File:Mesh_Oakland_High_Res.png|250px|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].
* We have '''weekly hack nights''' on Tuesdays and Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]]. The first three Thursdays of the month are work nights -- help us change the internet!
* Learn more at our general meetings, which are the last Thursdays of every month. 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!
* 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 user introduction to help you get involved!

*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]! We're focused on these areas:
* [https://sudoroom.org/wiki/Mesh/Firmware Firmware]
* [https://github.com/sudomesh/service-browser Service Browser]
* [https://sudoroom.org/wiki/Mesh/Distributed_Services Services]

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

=Logistics=
*[[Mesh/Checkouts]] - Who took what gear home.
*[[Mesh/Donations]] - What's been donated to the group.
*[[Mesh/Inventory]] - Continually-updated inventory of our hardware and gear.
*[[Mesh/Marketing]] - Inspiration and links to marketing materials in progress.
*[[Mesh/Naming]] - What do we call ourselves? A lineage of bikeshedding.
*[[Mesh/Purchases]] - Details on our purchases, made by either individuals or through our crowdfunded money.

= 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.

= 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.

=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.

{{Mesh nav}}

''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]]

Mesh

2014-07-19T01:46:03Z

Jwentwistle: /* Web Resources */

'''<big>Feb 21: Launched [https://sudoroom.org/wiki/Mesh/Blog#Developer_Launch.21 "Snow Crash" release candidate v.0.1.0] - now deploying the first batch of experimental nodes!</big>'''
 

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

A [http://en.wikipedia.org/wiki/Mesh_networking mesh network] is a network that allows the participants to freely share internet connectivity and build their own community-owned communications. It consists of routers running software that allow them to communicate with other routers around them. People who join the network enable others to be on the network and support [http://en.wikipedia.org/wiki/Net_neutrality net neutrality]. Community wireless mesh networks are growing around the world as alternatives to the existing system, creating local 'internets' rather than being dependent on the infrastructure developed by large Internet Service Providers and companies that mine and sell your personal information.

The software we've created is [http://en.wikipedia.org/wiki/Open_source open source] and we're using it to develop free internet for Oakland and the surrounding areas. 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.

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

{{Mesh nav}}

 

= 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].
* We have '''weekly hack nights''' on Tuesdays and Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]]. The first three Thursdays of the month are work nights -- help us change the internet!
* Learn more at our general meetings, which are the last Thursdays of every month. 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!
* 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 user introduction to help you get involved!

*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]! We're focused on these areas:
* [https://sudoroom.org/wiki/Mesh/Firmware Firmware]
* [https://github.com/sudomesh/service-browser Service Browser]
* [https://sudoroom.org/wiki/Mesh/Distributed_Services Services]

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

=Logistics=
*[[Mesh/Checkouts]] - Who took what gear home.
*[[Mesh/Donations]] - What's been donated to the group.
*[[Mesh/Inventory]] - Continually-updated inventory of our hardware and gear.
*[[Mesh/Marketing]] - Inspiration and links to marketing materials in progress.
*[[Mesh/Naming]] - What do we call ourselves? A lineage of bikeshedding.
*[[Mesh/Purchases]] - Details on our purchases, made by either individuals or through our crowdfunded money.

= 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.

= 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.

=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.

''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]]

Mesh/

2014-07-19T01:43:56Z

Jwentwistle: added redirect

#REDIRECT [[Mesh]]

Mesh

2014-07-19T01:12:07Z

Jwentwistle: improved many areas

'''<big>Feb 21: Launched [https://sudoroom.org/wiki/Mesh/Blog#Developer_Launch.21 "Snow Crash" release candidate v.0.1.0] - now deploying the first batch of experimental nodes!</big>'''
 

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

A [http://en.wikipedia.org/wiki/Mesh_networking mesh network] is a network that allows the participants to freely share internet connectivity and build their own community-owned communications. It consists of routers running software that allow them to communicate with other routers around them. People who join the network enable others to be on the network and support [http://en.wikipedia.org/wiki/Net_neutrality net neutrality]. Community wireless mesh networks are growing around the world as alternatives to the existing system, creating local 'internets' rather than being dependent on the infrastructure developed by large Internet Service Providers and companies that mine and sell your personal information.

The software we've created is [http://en.wikipedia.org/wiki/Open_source open source] and we're using it to develop free internet for Oakland and the surrounding areas. 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.

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

{{Mesh nav}}

 

= 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].
* We have '''weekly hack nights''' on Tuesdays and Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]]. The first three Thursdays of the month are work nights -- help us change the internet!
* Learn more at our general meetings, which are the last Thursdays of every month. 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!
* 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 user introduction to help you get involved!

*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]! We're focused on these areas:
* [https://sudoroom.org/wiki/Mesh/Firmware Firmware]
* [https://github.com/sudomesh/service-browser Service Browser]
* [https://sudoroom.org/wiki/Mesh/Distributed_Services Services]

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

=Logistics=
*[[Mesh/Checkouts]] - Who took what gear home.
*[[Mesh/Donations]] - What's been donated to the group.
*[[Mesh/Inventory]] - Continually-updated inventory of our hardware and gear.
*[[Mesh/Marketing]] - Inspiration and links to marketing materials in progress.
*[[Mesh/Naming]] - What do we call ourselves? A lineage of bikeshedding.
*[[Mesh/Purchases]] - Details on our purchases, made by either individuals or through our crowdfunded money.

= 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.

= 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.

=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.
Summary:
This is a minor edit Watch this page
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]] This is a minor edit Watch this page

Mesh

2014-07-19T00:58:33Z

Jwentwistle: /* Other Firmware and Networks */

'''<big>Feb 21: Launched [https://sudoroom.org/wiki/Mesh/Blog#Developer_Launch.21 "Snow Crash" release candidate v.0.1.0] - now deploying the first batch of experimental nodes!</big>'''
 

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

A [http://en.wikipedia.org/wiki/Mesh_networking mesh network] is a network that allows the participants to freely share internet connectivity and build their own community-owned communications. It consists of routers running software that allow them to communicate with other routers around them. People who join the network enable others to be on the network and support [http://en.wikipedia.org/wiki/Net_neutrality net neutrality]. Community wireless mesh networks are growing around the world as alternatives to the existing system, creating local 'internets' rather than being dependent on the infrastructure developed by large Internet Service Providers and companies that mine and sell your personal information.

The software we've created is [http://en.wikipedia.org/wiki/Open_source open source] and we're using it to develop free internet for Oakland and the surrounding areas. 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.

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

{{Mesh nav}}

 

= 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].
* We have '''weekly hack nights''' on Tuesdays and Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]]. The first three Thursdays of the month are work nights -- help us change the internet!
* Learn more at our general meetings, which are the last Thursdays of every month. 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!
* 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 user introduction to help you get involved!

*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]! We're focused on these areas:
* [https://sudoroom.org/wiki/Mesh/Firmware Firmware]
* [https://github.com/sudomesh/service-browser Service Browser]
* [https://sudoroom.org/wiki/Mesh/Distributed_Services Services]

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

=Logistics=
*[[Mesh/Checkouts]] - Who took what gear home.
*[[Mesh/Donations]] - What's been donated to the group.
*[[Mesh/Inventory]] - Continually-updated inventory of our hardware and gear.
*[[Mesh/Marketing]] - Inspiration and links to marketing materials in progress.
*[[Mesh/Naming]] - What do we call ourselves? A lineage of bikeshedding.
*[[Mesh/Purchases]] - Details on our purchases, made by either individuals or through our crowdfunded money.

= Research =
*[[Mesh/Interviews with other meshers]] - In which we attempt to extract the results of their hard-won experience.
*[[Mesh/Other mesh projects]] - List of active and inactive meshes we know about
*[[Mesh/Documentation]] - Books, articles, wikis, blog posts.
*[[Mesh/Oakland]] - Information and resources pertaining to Oakland community organizations, wireless initiatives, policy and research initiatives
*[[Mesh/Other muni networking projects]] - Examples of progressive uses of municipal networks.

= Other Firmware and Networks =

*[[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.

=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.

[[Category:Projects]]

Mesh

2014-07-19T00:56:38Z

Jwentwistle: /* Designers */

'''<big>Feb 21: Launched [https://sudoroom.org/wiki/Mesh/Blog#Developer_Launch.21 "Snow Crash" release candidate v.0.1.0] - now deploying the first batch of experimental nodes!</big>'''
 

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

A [http://en.wikipedia.org/wiki/Mesh_networking mesh network] is a network that allows the participants to freely share internet connectivity and build their own community-owned communications. It consists of routers running software that allow them to communicate with other routers around them. People who join the network enable others to be on the network and support [http://en.wikipedia.org/wiki/Net_neutrality net neutrality]. Community wireless mesh networks are growing around the world as alternatives to the existing system, creating local 'internets' rather than being dependent on the infrastructure developed by large Internet Service Providers and companies that mine and sell your personal information.

The software we've created is [http://en.wikipedia.org/wiki/Open_source open source] and we're using it to develop free internet for Oakland and the surrounding areas. 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.

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

{{Mesh nav}}

 

= 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].
* We have '''weekly hack nights''' on Tuesdays and Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]]. The first three Thursdays of the month are work nights -- help us change the internet!
* Learn more at our general meetings, which are the last Thursdays of every month. 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!
* 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 user introduction to help you get involved!

*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]! We're focused on these areas:
* [https://sudoroom.org/wiki/Mesh/Firmware Firmware]
* [https://github.com/sudomesh/service-browser Service Browser]
* [https://sudoroom.org/wiki/Mesh/Distributed_Services Services]

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

=Logistics=
*[[Mesh/Checkouts]] - Who took what gear home.
*[[Mesh/Donations]] - What's been donated to the group.
*[[Mesh/Inventory]] - Continually-updated inventory of our hardware and gear.
*[[Mesh/Marketing]] - Inspiration and links to marketing materials in progress.
*[[Mesh/Naming]] - What do we call ourselves? A lineage of bikeshedding.
*[[Mesh/Purchases]] - Details on our purchases, made by either individuals or through our crowdfunded money.

= Research =
*[[Mesh/Interviews with other meshers]] - In which we attempt to extract the results of their hard-won experience.
*[[Mesh/Other mesh projects]] - List of active and inactive meshes we know about
*[[Mesh/Documentation]] - Books, articles, wikis, blog posts.
*[[Mesh/Oakland]] - Information and resources pertaining to Oakland community organizations, wireless initiatives, policy and research initiatives
*[[Mesh/Other muni networking projects]] - Examples of progressive uses of municipal networks.

= Other Firmware and Networks =

*[[Mesh/Freifunk]] - Germany - Home of the creators of batman-adv (the 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.

=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.

[[Category:Projects]]

Mesh

2014-07-19T00:55:17Z

Jwentwistle: /* Designers */ added more details

'''<big>Feb 21: Launched [https://sudoroom.org/wiki/Mesh/Blog#Developer_Launch.21 "Snow Crash" release candidate v.0.1.0] - now deploying the first batch of experimental nodes!</big>'''
 

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

A [http://en.wikipedia.org/wiki/Mesh_networking mesh network] is a network that allows the participants to freely share internet connectivity and build their own community-owned communications. It consists of routers running software that allow them to communicate with other routers around them. People who join the network enable others to be on the network and support [http://en.wikipedia.org/wiki/Net_neutrality net neutrality]. Community wireless mesh networks are growing around the world as alternatives to the existing system, creating local 'internets' rather than being dependent on the infrastructure developed by large Internet Service Providers and companies that mine and sell your personal information.

The software we've created is [http://en.wikipedia.org/wiki/Open_source open source] and we're using it to develop free internet for Oakland and the surrounding areas. 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.

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

{{Mesh nav}}

 

= 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].
* We have '''weekly hack nights''' on Tuesdays and Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]]. The first three Thursdays of the month are work nights -- help us change the internet!
* Learn more at our general meetings, which are the last Thursdays of every month. 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!
* 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 user introduction to help you get involved!

*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]! We're focused on these areas:
* [https://sudoroom.org/wiki/Mesh/Firmware Firmware]
* [https://github.com/sudomesh/service-browser Service Browser]
* [https://sudoroom.org/wiki/Mesh/Distributed_Services Services]

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

=Logistics=
*[[Mesh/Checkouts]] - Who took what gear home.
*[[Mesh/Donations]] - What's been donated to the group.
*[[Mesh/Inventory]] - Continually-updated inventory of our hardware and gear.
*[[Mesh/Marketing]] - Inspiration and links to marketing materials in progress.
*[[Mesh/Naming]] - What do we call ourselves? A lineage of bikeshedding.
*[[Mesh/Purchases]] - Details on our purchases, made by either individuals or through our crowdfunded money.

= Research =
*[[Mesh/Interviews with other meshers]] - In which we attempt to extract the results of their hard-won experience.
*[[Mesh/Other mesh projects]] - List of active and inactive meshes we know about
*[[Mesh/Documentation]] - Books, articles, wikis, blog posts.
*[[Mesh/Oakland]] - Information and resources pertaining to Oakland community organizations, wireless initiatives, policy and research initiatives
*[[Mesh/Other muni networking projects]] - Examples of progressive uses of municipal networks.

= Other Firmware and Networks =

*[[Mesh/Freifunk]] - Germany - Home of the creators of batman-adv (the 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.

=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.

[[Category:Projects]]

File:Presentation-04.png

2014-07-19T00:37:42Z