|
|
| (135 intermediate revisions by 16 users not shown) |
| Line 1: |
Line 1: |
| <span style="color:#20b24b;">'''<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>'''</span> | | <center>{{#setlogo:Meshlogo.png}} |
|
| | [[File:Sudomesh.jpg|350px]]</center> |
|
| |
|
| <span style="color:#20b24b;">'''<big>Oct 25: Launched [https://peoplesopen.net/ PeoplesOpen.net] our public project page!</big>'''</span>
| | Sudo Mesh is a people-powered project. That means that anyone can join the network if they're willing to contribute by [https://github.com/sudomesh/bugs/issues/new reporting bugs], improving [https://github.com/sudomesh software], fixing hardware, [https://sudoroom.org/wiki/Mesh/WalkThrough setting up a node], [https://peoplesopen.net/blog/new-node-in-the-berkeley-hills/ installing rooftop nodes], telling your friends about us, [https://peoplesopen.net/blog/build-your-own-internet-workshop/ joining for a workshop], bringing pizza to a hack session, donating [[Mesh/Wishlist|equipment]]/[https://www.patreon.com/peoplesopennet money]/[https://blockchain.info/address/12RxU4DpLpdWcmEBn7Tj325CCXBwt5i9Hc Bitcoin], learning with us about how the internet works, or just being patient if something is broken :) |
|
| |
|
| |
|
| '''''We are a group of volunteers building a community mesh network in Oakland, California.''''' | | '''Interested in learning more and exploring?''' Check out our [[#Join Us|Join Us]] section. You do not need to be technically skilled to be part of this project. We need people willing to mount gear on rooftops, folks who want to do public outreach, graphic design artists, film-makers, documentarians and so much more! Show up at a monthly general meeting and get involved! |
|
| |
|
| A mesh network is, in essence, free as in freedom alternative internet. Using low-cost routers mounted on rooftops and outside of homes, we're currently building the backbone of the mesh throughout the East Bay, from West Oakland to the Fruitvale BART and beyond!
| | ---- |
|
| |
|
| Mesh networks are awesome because they don't depend on the existing centralized Internet Service Providers to function. Though they can be connected to the Internet as we know it now, a mesh network provides a decentralized mode of communication with our local community. We view mesh networks as a means of connecting to our neighbors, supporting local businesses, and enabling grassroots community collaboration. In the event of disaster or government censorship, an active mesh network is a resilient means of communication and sharing of information. | | <center>{{Mesh nav}}</center> |
|
| |
|
|
| | ---- |
|
| |
|
| [[File:510NetworkDishes.jpg|200px|thumb|right|Dishes in Action]]
| | __NOTOC__ |
| | <div style="margin: 1em auto 1em auto; text-align: center; background: #ffffff; font-size: 10.5pt; padding: 10px; width: 96%; border: 0px solid #376a97;margin-center:10px;"> |
| | <!-- This is where the formatting for the 3 columns begins --> |
| | {| cellspacing="0" width="100%" style="clear: both;" |
| | |colspan="3" style=border: 0px solid black; float:left; padding-left:1em; padding-right:0.5em;"| |
| | {| cellspacing="5" cellpadding="10" width="100%" |
| | |- valign="top" |
| | |style="font-size:90%; padding:10px 10px; background: #FDF4F4; border: 0px solid black;padding-left:1em;padding-right:0.5em;" width="40%" align="left"| |
| | =What does it mean?!= |
| | Imagine if the wifi router in your home connected to the wifi routers in your neighbours' homes and they again connected to their neighbours to form a huge free wireless network spanning the city! That's exactly what a [https://en.wikipedia.org/wiki/Mesh_networking mesh network] is, or at least what it can be. Roads and telephone poles are owned by government or private interests and laying down cable is expensive, but by using wireless signals that hop from building to building we can create a community-owned and -operated, free-as-in-freedom alternative to corporate Internet Service Providers. Community wireless mesh networks are growing around the world, creating local 'internets' that support Net Neutrality and community control of critical infrastructure. |
|
| |
|
| {{Mesh nav}}
| | We are spending a lot of time developing [https://github.com/sudomesh/ software] to make it cheap and easy for anyone to be participate in cooperative communications infrastructure, regardless of technical skill. |
|
| |
|
|
| | = Who are you? = |
| | '''sudomesh is a group of volunteers operating out of the [https://sudoroom.org sudo room] hackerspace at the [https://omnicommons.org Omni Commons] - a collective of collectives stewarding a large community space in Oakland, California. We develop software and assemble hardware systems to help build open community networks like the [https://peoplesopen.net People's Open Network], a community-owned and -operated non-profit internet infrastructure in Oakland.''' We are all unpaid volunteers building open technology that helps to connect our neighbors, support local businesses, and enable community collaboration and cultural production. In the event of a natural disaster or state censorship, community mesh networks can be a resilient means of communication and sharing of information. |
|
| |
|
|
| | = Frequently Asked Questions (FAQs)= |
| | * [[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? |
|
| |
|
| = Meetup Info = | | = Logistics = |
| *Join the [http://lists.sudoroom.org/listinfo/mesh Mailing List!] | | * [[Mesh/Minutes|Meeting Minutes]] - Notes from our weekly meetings dating back to January 2013. |
| *We have weekly hack nights on Thursdays, 7:30-10pm at [[Getting_there|Sudo Room]]. The first three Thursdays of the month are work nights - so come by and jump in! General meetings for discussion and planning are Last Thursdays of every month. We plan to have local focus groups in the near future - watch this space or join the mailing list for details. | | * [[Mesh/Taxes|Taxes]] - Filed taxes for the sudo mesh non-profit |
| *Find us on IRC: #peoplesopen.net on [http://webchat.freenode.net/?channels=peoplesopen.net Freenode IRC]
| |
| *We generally take meeting notes at: https://pad.riseup.net/p/sudomesh
| |
|
| |
|
| = Crowdfunding campaign = | | = Research = |
| | * [[Mesh/Other mesh projects|Other mesh projects]] around the world that have inspired us to make our own network! |
| | * [[Mesh/Interviews with other meshers|Interviews]] - we interviewed other experienced meshers |
| | * [[Mesh/Documentation|Other documentation]] - books, articles, wikis, blog posts. |
| | * [[Mesh/Oakland|Oakland]] - information and resources pertaining to Oakland community organizations, wireless initiatives, policy and research initiatives |
| | * [[Mesh/Other muni networking projects|Municipal projects]] - examples of progressive uses of municipal networks. |
| | * [[Mesh/Decentralized FM/AM radio|Decentralized FM/AM radio]] - Bit of research on adding legal FM/AM transmitters to nodes. |
| | * [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. |
|
| |
|
| In July 2013, we successfully concluded our bootstrap crowdfunding campaign on WePay to buy the first 100 wifi routers for the mesh! Thanks to all who supported with a donation. See [[Mesh/Purchases]] for details on how much was raised, who contributed, and what we've procured thus far with the funds!
| | |style="font-size:90%; padding:10px 10px; background: #F4FDF6; border: 0px solid black;padding-left:1em;padding-right:0.5em;" width="20%"| |
| | <center> |
| | = Our Projects = |
| | [[File:Mesh_Oakland_High_Res.png|center|187px|thumb|Building a community-owned and -operated wireless mesh network in Oakland, California and beyond!|link=https://peoplesopen.net]]<br /> |
| | [[File:Disasterradio.png|center|187px|thumb|link=https://disaster.radio|Disaster-resilient communications network powered by the sun.]]<br /> |
| | [[File:Byoi.png|center|187px|thumb|link=https://buildyourowninter.net|Instructions for building your own internet, plus a global directory of community wireless mesh networks.]]</center><br /> |
| | [[File:Laptops4all.png|center|187px|thumb|link=https://laptopsforall.org|Upcycling retired/donated laptops to those who can't afford them.]]<br /> |
|
| |
|
| Here are some other ways you can help out:
| | |style="font-size:90%; padding:5px 10px; background:#F4F8FD;border: 0px solid black;padding-left:1em;padding-right:0.5em;" width="40%" align="left"| |
|
| |
|
| *Support us with a small weekly donation on [https://www.gittip.com/sudomesh/ Gittip]. | | <center> |
| *Send bitcoins to our wallet address: {{bitcoin wallet}} | | = How To Participate = |
| *Come to our work meetings in Oakland! (listed above). | | </center> |
| *Form a project and/or a neighborhood working group to create new and locally-relevant ways of plugging into the mesh. | | If you want to join the mesh you'll need a mesh router at your home! Currently the best way to get one is to [http://lists.sudoroom.org/listinfo/mesh join and send an email to the mailing list ]. 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! |
| | * Chat with us on the #peoplesopen channel in [https://www.scuttlebutt.nz/ Secure Scuttlebutt], or on [http://www.irchelp.org/irchelp/irctutorial.html IRC]: [http://webchat.freenode.net/?channels=peoplesopen.net #peoplesopen.net] (see also [[IRC | IRC Intro]]) |
| | * Join the [http://lists.sudoroom.org/listinfo/mesh email list] |
| | * We have focus groups and collaborate on different parts of the project - from [https://github.com/sudomesh/propaganda design] and events, to [https://github.com/sudomesh software development], documentation, hardware hacking, [https://sudorom.org/wiki/Mesh/SFBayArea community outreach] and [https://github.com/sudomesh/mounting/blob/master/PONIprogram.md climbing rooftops to mount nodes and distributing hotspots to encampments]! |
| | * We generally collaborate on [https://peoplesopen.net/notes notes] at each meeting (currently on hold as we regroup in 2024). Look at our archive of past [[Mesh/Minutes|meeting minutes]]! |
| | * Contribute to the network by installing a mesh node at your location using our handy [https://sudoroom.org/wiki/Mesh/WalkThrough Mesh Node Setup Walkthrough]. This is especially helpful for those who are within range of an existing node (seen as a wireless SSID named "peoplesopen.net"). |
| | * Check out our [[Mesh/ToDos|ToDo list]] |
| | * Support us with a small monthly donation on [https://www.patreon.com/peoplesopennet Patreon], 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! |
| | * Improve our documentation |
| | * Talk to your community about joining the mesh - here are some [https://github.com/sudomesh/propaganda resources] for doing so! |
| | * Follow us on [https://twitter.com/sudomesh twitter] and like us on [https://www.facebook.com/sudomesh facebook]. |
|
| |
|
| = Mesh pages = | | == Developers == |
| *[[Mesh/ToDos]] - Tangible To Dos! Add some on, take some on!
| |
| *[[Mesh/Wishlist]] - List of hardware we'd love to experiment with!
| |
|
| |
|
| ==Design==
| | 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. |
| *[http://meshmap.sudoroom.org Map] - of potential nodes.
| |
| *[[Mesh/Website]] - Notes and documentation for the design of peoplesopen.net and meshthepla.net.
| |
| *[[Mesh/MeshApps]] - Local applications to run on the mesh!
| |
| *[[Mesh/Swag]] - Research on custom-printed t-shirts and other swag.
| |
| *[[Mesh/Stickers]] - Sticker design
| |
| *[[Ascii Art]] - for linux logins
| |
|
| |
|
| ==Technical Documentation==
| | If you want to immediately help, check out [https://github.com/sudomesh our code], [https://github.com/sudomesh/sudowrt-firmware/milestones look at our remaining issues for upcoming milestones], report any [https://github.com/sudomesh/bugs bugs] or help us squish them! |
| *[[Mesh/Tracking]] - Problems and solutions related to tracking, logging and anonymity
| |
| *[[Mesh/WalkThrough]] - Easy how-to for setting up OpenWRT & BATMAN-adv on Ubiquiti routers
| |
| **[[Mesh/OpenWRT]] - Experiences with the OpenWRT router firmware
| |
| **[[Mesh/BATMAN-adv]] - Experiences with the batman-adv mesh protocol
| |
| *[[Mesh/Firmware]] - Everything related to our firmware
| |
| **[[Mesh/Firmware/Splash page]] - Splash page / Captive Portal
| |
| **[[Mesh/Firmware/Bandwidth shaping]] - QoS / Bandwidth shaping
| |
| **[[Mesh/Firmware/Zeroconf]] - Issues related to mDNS and DNS-SD
| |
| **[[Mesh/Firmware/MTU_issues]] - MTU issues
| |
| **[[Mesh/Firmware/Generating]] - How do we generate firmwares on demand
| |
| **[[Mesh/Firmware/Web Admin Development]] - Web admin development
| |
| *[[Mesh/Network topology]] - High-level explanation of the mesh network structure
| |
| *[[Mesh/Specs]] - Specs sheet on different access points
| |
| *[[Mesh/Frequencies]] - Information on different frequencies.
| |
| *[[Mesh/Software tools]] - List of useful mesh troubleshooting tools
| |
| *[[Mesh/Terms]] - Hidden Node, Fresnal zone, and other jargons
| |
| *[[Mesh/Power]] - Stuff about power usage, batteries and solar power.
| |
| *[[Mesh/Monitoring]] - notes about how to monitor systems
| |
| *[[Mesh/Spectrum]] - Different forms of spectral analysis
| |
| *[[Mesh/Hardware support]] - Officially and unofficially supported hardware / routers
| |
| *[[Mesh/Relay setup]] - Setting up a relay node
| |
| *[[Mesh/Exit setup]] - Setting up an exit node
| |
| *[[Mesh/Spectrum mapping]] - The setup we use for mapping local spectrum and wifi usage
| |
| **[[Mesh/Spectrum mapping/XO-1 Laptop]] - How to configure an XO-1 laptop for use with our spectrum mapping setup
| |
| * [[Mesh/Install]] - physical installation notes/stories
| |
| * [[Mesh/Diagrams]] - technical diagrams to support new outreach materials
| |
|
| |
|
| ==Operational==
| | Here are some of the projects that need attention: |
| *[[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?
| |
| *[[Mesh/Naming]] - What do we call ourselves?
| |
| *[[Mesh/Marketing]] - Inspiration and links to marketing materials in progress.
| |
| *[[Mesh/Purchases]] - Details on our purchases, made by either individuals or through our crowdfunded money.
| |
| *[[Mesh/Inventory]] - What we currently have.
| |
| *[[Mesh/Donations]] - List of donations
| |
| *[[Mesh/Decisions]] - Decisions on how to operate
| |
| *[[Mesh/Challenges]] - Challenges faced. Problems to be solved.
| |
| *[[Mesh/Checkouts]] - Who took what gear home
| |
| *[[Mesh/Funding]] - Ideas on funding structures and list of grants to apply for.
| |
|
| |
|
| ==Background Research==
| | * [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware] - The sudowrt firmware |
| *[[Mesh/Interviews with other meshers]] - In which we attempt to extract the results of their hard-won experience. | | * [https://github.com/sudomesh/sudowrt-web-ui sudowrt-web-ui] - The new and improved web admin UI for sudowrt nodes |
| *[[Mesh/Other mesh projects]] - List of active and inactive meshes we know about | | * [https://github.com/sudomesh/ubus-https-forwarder ubus-https-forwarder] - Allow management of extender nodes from home node web UI |
| *[[Mesh/Documentation]] - Books, articles, wikis, blog posts. | | * [https://github.com/sudomesh/service-browser The Service Browser] - Web UI for browsing mesh services |
| *[[Mesh/Oakland]] - Information and resources pertaining to Oakland community organizations, wireless initiatives, policy and research initiatives | | * [[Mesh/Distributed Services|Mesh Services]] - Which services should we provide? |
| *[[Mesh/Other muni networking projects]] - Examples of progressive uses of muni-networks | |
|
| |
|
| = Firmwares / groups = | | == Designers == |
|
| |
|
| *[[Mesh/Freifunk]] | | 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/Commotion]] | | * [[Mesh/Presentations]] - Past presentations, talks, workshops, tutorials and videos |
| | * [[Mesh/Diagrams|Diagrams]] - Diagrams outlining the network topology and technical stack |
| | * [[Mesh/Design|Design]] - Website & logo design; swag for enthusiasts; and marketing inspiration. |
| | |} |
|
| |
|
| = Technical overview =
| | ---- |
|
| |
|
| The mesh is made up mostly of wifi routers using Atheros chipsets and running [https://github.com/sudomesh/sudowrt-firmware our own firmware] based on [http://openwrt.org/ OpenWRT], [http://www.open-mesh.org/projects/batman-adv/wiki/ B.A.T.M.A.N. Advanced] and wlan slovenja's [https://github.com/sudomesh/tunneldigger tunneldigger]. We're using 2.4 GHz routers for indoor and street-level coverage and 5 GHz 802.11n routers for high-bandwidth and long distance roof to roof links. Most of our outdoor equipment is from Ubiquiti. We refer to the wifi routers as mesh nodes, or simply nodes.
| | ''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!'' |
|
| |
|
| Node-owners can choose to connect the nodes to their existing LAN using ethernet. If they have Internet access, they can share a portion of it with the mesh. The amount of bandwidth shared is limited with 'tc'. It is chosen at node-configuration time and can be changed using the simple built-in web admin interface.
| | [[Category:Projects]][[Category:Mesh]] |
| | |
| == Wifi networks and IP assignment ==
| |
| | |
| The nodes each run three wifi networks (three SSIDs on the same physical wifi interface):
| |
| | |
| * peoplesopen.net is an open access point. Most people will use the network by connecting to this.
| |
| * pplsopen.net-node2node is an ad-hoc network that the nodes use to mesh with each other
| |
| * A private wifi network is named by the node owner (or a name is generated) and uses WPA2-PSK.
| |
| | |
| If a node-owner is sharing internet, then the node will create a layer 2 (L2TP) tunnel to a VPN server on the Internet using tunneldigger. batman-adv will connect over this tunnel to other nodes on the mesh, so the mesh can route traffic over the internet if no wifi path to another node is available (e.g. other nodes are physically too far away). When people connect to the peoplesopen.net access point and try to access the Internet, the traffic will flow through the VPN, and the source IP of requests will appear to be the VPN with the sudo mesh organization listed as the abuse contact.
| |
| | |
| The nodes run DHCP servers and each have a /24 IPv4 subnet in the 10.0.0.0/8 range that is statically assigned by coordination between mesh groups and individuals hosting and administrating their own nodes on People's Open Network (currently only the sudo mesh organization). If a user connects to the peoplesopen.net access point on a node that isn't sharing internet, then batman-adv intercepts the DHCP request and forwards the request to another node on the network that has Internet connectivity (see the gw_mode option for batman-adv).
| |
| | |
| The private network does not limit bandwidth and provides access to both direct access to the Internet (if the node owner has hooked the node up to the Internet) and access to the mesh. Each node's private network runs on 172.30.0.0/16 and uses NAT between the private network and the mesh. It does not accept any new incoming connections from the mesh onto the 172.30.0.0/16 subnet.
| |
| | |
| == Node flashing and configuration ==
| |
| | |
| One of our medium-term goals is to be able to sell nodes on our website and minimize the amount of work required to re-flash/configure the nodes and provide documentation for the user. To facilitate this, our current process for new nodes is:
| |
| | |
| * A new node is flashed either automatically (using e.g. [https://github.com/sudomesh/ubiquiti-flasher ubiquiti-flasher] or [https://github.com/sudomesh/merakiflasher merakiflasher]) or manually with the [https://github.com/sudomesh/sudowrt-firmware sudowrt] firmware.
| |
| * The node is plugged into a server running our [https://github.com/sudomesh/node-configurator node-configurator] software.
| |
| * A sudo mesh volunteer pulls up https://nodeconf.local and uses a web interface to fill out contact info for the node owner, initial bandwidth sharing limits and private wifi SSID.
| |
| * The node-configurator generates SSH keys, SSH root password, web admin password and private wifi password, then it configures the node, saves the info in the [https://github.com/sudomesh/node-database node database] and shuts down the node.
| |
| * The node-configurator automatically [https://github.com/sudomesh/ql570 prints a sticker] containing some basic info including wifi and web admin passwords.
| |
| * The sudo mesh volunteer attaches the sticker to the nodes power supply and puts the node back in the box with a set of instructions for how to install and use the node.
| |
| * The node is shipped to the new node owner!
| |
| | |
| The node-configurator has both a [https://github.com/sudomesh/node-configurator server] and a [https://github.com/sudomesh/node-configurator-client client] component. The newly flashed sudowrt nodes automatically run the node-configurator client when they boot, and the client uses DNS-SD and mDNS to find node-configurator servers on the local network. The node then connects to the server using SSL and the server is ready to configure the node. The node-configurator server talks to Avahi using DBUS to announce itself using DNS-SD. The server is written in Python using Twisted and the client is written in Lua using luasec, and uses the [https://github.com/sudomesh/mdnssd-min mdnssd-min] utility to provide DNS-SD and mDNS.
| |
| | |
| The node-configurator includes a webserver and management web app. The web app talks to the server and connected nodes using websockets.
| |
| | |
| == Node management ==
| |
| | |
| All nodes set up by sudo mesh automatically allow root access using an SSH key held by a few trusted sudo mesh organizers. This is to allow us to update the firmware and troubleshoot network issues. We inform node-owners of this fact and tell them how to prevent sudo mesh from accessing their nodes, but also indicate that they should be ready to manage their own node if they choose to do this.
| |
| | |
| We don't yet have a solution for node monitoring but we're expecting to use the new version of wlan slovenja's nodewatcher software.
| |
| | |
| We don't yet have an automatic update solution in place, but it will work similarly to the node-configurator:
| |
| | |
| * Any number of node-updater servers announce themselves on the mesh and whether or not an update is available.
| |
| * The nodes run a future version of mdnssd-min as a daemon that keeps a currently list of node-updaters.
| |
| * Once every N hours +/- a random factor, if any node-updaters have updates available, all nodes connect to a randomly chosen node-updater and request an update.
| |
| * The node-updaters send the nodes an ipk file with the update and the nodes check the signature and install it if it's signed by a trusted authority.
| |
| | |
| == Minimum hardware specs ==
| |
| | |
| The sudowrt firmware minimally needs:
| |
| | |
| * Atheros chipset
| |
| * 32 MB ram
| |
| * 8 MB flash
| |
| **(or 4 MB flash and a USB port with a USB drive attached)
| |
| | |
| The firmware is currently only tested to be working on the older Atheros chipset (OpenWRT "atheros" architecture) but we're working on getting the newer Atheros chipsets working (OpenWRT "ar71xx" architecture).
| |
| | |
| We don't support less than 32 MB of ram because OpenWRT itself doesn't support less than 32 MB of ram as of the 12.09 "Attitude Adjustment" release.
| |
| | |
| We could probably squeeze the firmware into 4 MB flash, but we've decided it's not worth the trouble, and using jffs instead of squashfs simplifies some things.
| |
| | |
| == Internet bandwidth ==
| |
| | |
| We encourage node-owners to share their internet with the mesh, but on top of that we are talking to local non-profit organizations and ISPs about getting access to more cheap and free bandwidth.
| |
| | |
| =Social=
| |
| | |
| ==Community-Based Participatory Action Research in the San Antonio district of Oakland==
| |
| *We are currently researching existing community organizations in the San Antonio neighborhood for potential collaboration, and have established relationships with (and set up mesh nodes for) three grassroots organizations in the San Antonio neighborhood: Liberating Ourselves Locally (LOL), a makerspace run by and for people of color; Sustaining Ourselves Locally (SOL), a community garden and food justice advocacy and education space; and Cycles of Change, a community bike repair, advocacy and education space. Moving forward, we intend to expand the mesh through reaching out to grassroots organizations and local businesses, our process of designing and deploying mesh services guided by the needs and desires of existing community actors.
| |
| | |
| *The ethnographic research component of the project also involves interviewing local residents, designing and distributing community surveys, historical and political analysis, and asset mapping of existing and potential community resources.
| |
| | |
| ==Documentation of use cases and user stories==
| |
| *Articulating use cases for mesh networks involves the creation of user stories based on interviews with local residents and participatory engagement with existing community organizations and groups. The research process will be transparently documented on a research wiki, incorporating interview notes, meeting minutes, an annotated bibliography, written analysis and visual infographics (for an example, see Jenny's current research wiki here: http://wiki.tidepools.co).
| |
| | |
| *This documentation is intended to support a model of open source technology design that is bottom-up in nature, rooted in the interests of those who would receive the greatest humanitarian benefit from the technology and participate intimately with the development process.
| |
| | |
| ==Illustrated instructables for adapting recycled/reused items for DIY hardware==
| |
| *A major focus of the project is to experiment with recycled and donated hardware for the purposes of designing mesh solutions at minimal cost. Experimentation with various firmwares (eg; Commotion, Freifunk, Byzantium) and protocols (eg; OLSRd, batman-adv, Babel) using off-the-shelf and upcycled hardware (eg; donated routers and satellite dishes) will be extensively documented. Well-designed instructables/comics will incorporate use cases, user stories, and DIY building processes in an effort to engage everyday folks to experiment with mesh technology in their local neighborhoods.
| |
| | |
| ==Getting municipal actors to support the mesh==
| |
| *Over time, we expect municipal actors (people working for local governments, libraries, schools, etc.) to see the mesh as an ally in efforts to bridge the digital divide. We are creating a [[why municipal actors should care about the mesh|short introduction]] to the project explaining why municipal actors should care about the mesh what they can do to support it.
| |
| | |
| =Meeting Minutes=
| |
| See the [[Mesh/Minutes|Minutes]] page.
| |
| | |
| =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]] | |
