Difference between pages "Mesh/WalkThrough" and "Mesh"

From Sudo Room
(Difference between pages)
Jump to navigation Jump to search
m (modified to use preformatted for cmdline)
 
m (formatting)
 
Line 1: Line 1:
This a walkthrough for flashing a node with the sudomesh firmware and then configuring it with makenode. At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish (OSX should mostly work) OS and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The basic idea of getting a node (router) on the mesh consists of flashing (copying files to [https://en.wikipedia.org/wiki/Flash_memory flash memory]) an operating system to the node and then using a software configurator finish setup .
[[File:SudoMesh Node.png|frameless|right|300px]]


If you do not want to use a per-compiled OpenWRT image, you can build your own from scratch using this how to: [[Mesh/Build An OpenWRT Image]]
You can read about our progress on our [[Mesh/Blog|blog]]. We're in an alpha testing phase, and our monitoring results can be seen on [https://monitor.sudomesh.org/smokeping/smokeping.cgi?target=Mesh smokeping] or [https://monitor.sudomesh.org/cacti/graph.php?action=view&local_graph_id=217&rra_id=all cacti].


Before you flash your router it is recommended that you read the [[Home and extender nodes#Home_nodes|Home node info]] to find out the router works as a mesh node.
Check out the Join Us section below for opportunities to help out!


([[User:Maxb|Maxb]] December 22nd 2015)


= Preparing Your Laptop =
----


The directions that follow assume you are runing a linux-ish distro (OSX should work). Many of the quoted commands listed below may need `sudo` prepended to them. For the moment, Windows users will have to figure out some of these steps on their own. Sorry :/
'''We are an all-volunteer organization building the People's Open Network, a community-owned and operated non-profit internet infrastructure in Oakland.'''


If you are working with a fresh installation of Ubuntu linux, you will need to install a few pieces of software. Do install them, open your terminal and type the following:
People's Open Network is a [http://en.wikipedia.org/wiki/Mesh_networking mesh network] based out of Oakland, California.  


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


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


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


<code>sudo apt-get install dropbear</code>
[[File:Mesh_Oakland_High_Res.png|225px|right]]


= Join Us =


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


==Download the Sudomesh OpenWRT Image File For a Supported Router==
= How to Help =
Sudomesh firmware images can be found here:
[https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/ https://builds.sudomesh.org/builds/chaos_calmer/ar71xx/]


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


Download the image file for your supported router.
*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


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


For example, if you have a Western Digital MyNet N600, follow these instructions:<br>
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.
*Plug one end of the Ethernet cable into your laptop.<br>
*Plug the other end of the Ethernet cable into one of the normal ports on the router (not the Internet/WAN port).<br>
*With the router plugged in and power turned off, push a pin into the reset hole and hold it.<br>
*With the pin held down, turn on the router power button.<br>
*Watch the front blue light - they will flash on and off a few times.<br>
*Once the front blue is flashing, you can let go of the pin.<br>


On your laptop (instructions for ubuntu) edit your network settings by doing the following:<br>
If you want to immediately help, check out [https://github.com/sudomesh our code] or [https://github.com/sudomesh/sudowrt-firmware/milestones look at our remaining issues for upcoming milestones].
*Click on the network icon on the top right of the toolbar.<br>
*Click "Edit connections..."<br>
*Click on Ethernet connection "Wired connection 1" and click Edit<br>
*Click on the "IPv4 Settings" tab<br>
*Change method to "Manual"<br>
*Click Add<br>
*Under "Address" type "192.168.1.10"<br>
*Under "Netmask" type "255.255.255.0"<br>
*Under "Gateway" type "0.0.0.0"<br>
*Click Save<br>
*Click Close<br>


In your web browser:<br>
Here are some of the projects that need attention:
*Go to "192.168.1.1"<br>
*Click Browse and select the firmware you downloaded<br>
*Click Install<br>


=Configuring Your OpenWRT Router to Work on the Sudomesh Network=
* [[Mesh/Firmware|Firmware]] - The sudowrt firmware
These are the steps for configuring your newly flashed router. It will retrieve hardware information about the node, prompt you for a few config settings, and then query the meshnode database to get an available IP address and subnet.
* [https://github.com/sudomesh/sudowrt-web-ui sudowrt-web-ui] - The new and improved web admin UI for sudowrt nodes
* [https://github.com/sudomesh/ubus-https-forwarder ubus-https-forwarder] - Allow management of extender nodes from home node web UI
* [https://github.com/sudomesh/service-browser The Service Browser] - Web UI for browsing mesh services
* [[Mesh/Distributed Services|Mesh Services]] - Which services should we provide?


Open your terminal in Linux and type:<br>
== Designers ==


<code>git clone https://github.com/sudomesh/makenode.git</code>
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:


<code>cd makenode</code>
* [[Mesh/Presentation|Presentation]]
* [[Mesh/Diagrams|Diagrams]]
* Tutorials and Videos


<code>npm install</code>
= Frequently Asked Questions (FAQs)=


<code>cp settings.js.example settings.js</code>
* [[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?


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


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


= Research =


if you get the error "no such file or directory":<br>
We need help improving our documentation about the area and other legalities.
open a new terminal<br>
<code>sudo ln -s nodejs node</code>
(this will point node to nodejs)<br>
<code>npm install</code><br>
<code>./makenode.js</code>


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


Now the configuration wizard will ask you a number of questions:<br>
= Other Firmware and Networks =
*"enter valid hostname" - this is the host name when you SSH into the node - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
*"max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobytes per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
*"max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps
*"admin user password" - this is the password for for changing wifi settings on the node
*"root user password" - this is the root password for the router - Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device - see details below.
*"wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts)
*"operator name" - this is the name that the network admins can associate with the node - so use a unique name like your first name or location name
*"private wifi SSID" - this is the wireless SSID name for the private wireless network that will run on this router
*"private wifi password" - this is the password for the private wireless network that will run on this router - it must be at least 8 characters long


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:


In a separate terminal you will log into the node using these directions:<br>
* [[Mesh/Freifunk]] (germany) - the creators of batman-adv (routing protocol we use) and one of the longest-running mesh networks in the world.
To find the name of your ethernet port, type:<br>
* [[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.
<code>ifconfig</code><br>
* [[Mesh/San Francisco]] Mesh projects in San Francisco
In the example below, the wired Ethernet port was "eth0"<br>
In the terminal type the following, replacing "eth0" with the name of your Ethernet port:<br>
<code>sudo ip addr add 172.22.0.9/24 dev eth0</code>


Then type:<br>
= Web Resources =
<code>ssh root@172.22.0.1</code><br>
It will ask you for a password, which is "meshtheplanet"


If you'd like to add your ssh key to the router (instead of using a root password), add it to the `configs/authorized_keys` file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.
* [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.


==Confirm that the Node is Running==
= All Sudo Mesh Wiki Pages =
Click on the network icon on the top right of the toolbar to see the avaiable wireless networks (or run <code>sudo iwlist wlan0 scan</code> in your linux terminal)


If configuration proceeded correctly, you should see the 'peoplesopen.net' and 'pplsopen.net-node2node' wifi interfaces.
<center>{{Mesh nav}}</center>


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


=Flashing Extender Antennas=
[[Category:Projects]][[Category:Mesh]]
This step is optional.
 
==Download the Image File For a Extender Node==
The extender nodes that we currently support are:
* [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 Ubiquiti Nanostation M5] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/ubiquiti/nanostationm2 Ubiquiti Nanostation M2] - [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-om2p-squashfs-factory.bin firmware image]
* [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 Ubiquiti Picostation M2]
* [https://wiki.openwrt.org/toh/ubiquiti/nanobeam Ubiquiti Nanobeam M2 and M5]
* [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 Ubiquiti Picostation M2]
* [https://wiki.openwrt.org/toh/ubiquiti/picostation2 Ubiquiti Picostation 2] - [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
* [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 Ubiquiti Picostation M2]
* [https://wiki.openwrt.org/toh/ubiquiti/bullet Ubiquiti Bullet M2 and M5]
 
==Flash the Extender Node==
 
*Configure your wired internet settings to use Manual IPv4 settings with IP: 192.168.1.10, subnet: 255.255.255.0, gateway: 0.0.0.0
*Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.<br>
*Plug another Ethernet cable into your antenna on one end and into the "POE" port of the power-over-ethernet power supply on the other end.<br>
*Push a pin into the reset hole and hold it.<br>
*With the pin held down, plug in the power to the power-over-ethernet power supply.<br>
*Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.<br>
*Once the lights on the antenna are flashing up and down, you can let go of the pin.<br>
 
You should be able to ping the extender at 192.168.1.20.
<pre>
$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms
</pre>
 
In your linux terminal, type:<br>
<code>git clone https://github.com/sudomesh/ubi-flasher</code><br>
<code>cd ubi-flasher</code><br>
<code>npm install</code><br>
<code>./flasher.js '<path to firmware>'</code><br>
 
The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."<br>
Wait until the antenna has only the power LED lit and you're done.

Revision as of 20:50, 16 April 2016

SudoMesh Node.png

You can read about our progress on our blog. We're in an alpha testing phase, and our monitoring results can be seen on smokeping or cacti.

Check out the Join Us section below for opportunities to help out!

(Maxb December 22nd 2015)

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

People's Open Network is a mesh network based out of Oakland, California.

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

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

We are spending a lot of time developing software to make it cheap and easy for anyone to be part of People's Open Network, regardless of technical skill.

Mesh Oakland High Res.png

Join Us

  • Join the email list
  • Follow us on twitter and like us on facebook.
  • Learn more at our general meetings, which are the last Tuesdays of every month at sudo room. We have focus groups and we collaborate on different parts of the project - from design to software development, documentation to community outreach and of course, community outreach and climbing rooftops to mount nodes!
  • We have weekly meetings on Tuesdays and weekly hacknights' on Thursdays, 7:30-11:00pm at sudo room, but at these events we do not spend time introducing new people to the project. If you do not feel ready to jump right in and start contributing, please show up for our general meetings (mentioned above) where we specifically take time to intro new volunteers and answer questions :D
  • Chat with us on IRC: #peoplesopen.net
  • We generally collaborate on meeting notes at each meeting. Look at our archive of past meeting minutes!
  • If you are within range of an existing node (if you can access the internet through a connection with the SSID of "peoplesopen.net") contribute to the network by installing a mesh node at your location - Follow the walkthrough to build a new node

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 guide to help you get on the network!

  • Check out our action items
  • Support us with a small weekly donation on gittip, here's how we spend it.
  • Send bitcoins to our wallet address: 12RxU4DpLpdWcmEBn7Tj325CCXBwt5i9Hc
  • Check out our 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 technical documentation that will be helpful in understanding the network.

If you want to immediately help, check out our code or look at our remaining issues for upcoming milestones.

Here are some of the projects that need attention:

Designers

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

Frequently Asked Questions (FAQs)

  • Challenges - What sort of challenges and problems do we face?
  • Decisions - What decisions have we made, and why?
  • Funding - How the heck do we fund this thing?
  • Legal - How do we use exit nodes, relays and legal structures to protect node owners and ourselves?
  • Hosting - How are we hosting and what does it cost?
  • Backup - How do we handle backups?
  • Server security - How do we ensure server security?

Logistics

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

Research

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

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

Other Firmware and Networks

There are other meshes around the world that have inspired us to make our own network! They use software from these projects:

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

Web Resources

All Sudo Mesh Wiki Pages

Quick Links (see below for more details)
Documentation Technical Outreach Operations Research External Links
Install Instructions Overview FAQ Minutes User Research peoplesopen.net
Net Topology Hardware Blog To-Do's SF Bay Area network map
Presentations Power How to Help Legal Interviews code on github
History Security Wishlist Inventory Other Meshes DisasterRadio
Press Backup Website Meetings Software Tools BuildYourOwnInter.Net
Firmware Hosting Propaganda Funding Local Services
Mounting Decisions Self-Education
Next gen

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!

Retrieved from "https://sudoroom.org/mediawiki/index.php?title=Mesh/WalkThrough&oldid=10039"