makenode is a script that finishes the configuration for People's Open nodes flashed with the sudowrt firmware, see https://github.com/sudomesh/makenode.

This script is in the process of being deprecated, below is ongoing documentation this deprecation.

"Early alpha status. Things may break."

= makenode theory =
There are two interconnected theories that govern the implementation, usage, and deprecation of the makenode script

== theory for implementation ==
The story goes that makenode was created to solve a few problems with the sudowrt firmware. Mainly, it was much quicker to implement changes in makenode rather than rebuilding the firmware. This way patches could be rapidly deployed with out a full rebuild and reflash of the firmware (however this is ignoring the existence of a lot of already "made nodes"). This use case of triaging patches before integrating them into a new build of the firmware devolved into using makenode to do perform almost all node configurations. While these configurations are mostly "per-node"

1. To retrieve an IP from secrets.peoplesopen.net (our meshnode-database) and then copy it into a lot of config files

2. To set a root password other per-node configs, such as hostname, private SSID, etc.

3. To perform hardware detection to select which config files to copy onto node

== theory for deprecation ==
While makenode does work, it presents a large barrier to inclusion (e.g. doesn't work on Windows, have to be relatively comfortable with terminal) as well as limiting our ability to quickly configure "blank" routers that can be handed out to anyone. Instead, it would be preferable to have a version of the firmware that requires "zero configurations", aka zeroconf. To do this, we first need to address the three main reasons for implementation.

1. retrieving a mesh IP:
* this can be done shortly after boot by making a POST request to secrets.peoplesopen.net using curl, the IP can then be then be parse from the json response and inserted into the correct config files using OpenWRT's build UCI configuration tool.

2. setting a root password:
* the quick (but insecure) solution is to set a default root password. The better solution is to limit the access of the root user to only the hardwired interface and/or disable the password after a certain period of time and/or on second boot
* any other non-security-related, per-node configurations could and should be set through the admin dashboard

3. hardware detection:
* an example of this can already be seen for extender nodes in the [https://github.com/paidforby/sudowrt-firmware/blob/master/files_extender-node/etc/uci-defaults/99_wireless 99_wireless script]
* at boot OpenWrt needs to detect number of antennas and ports,
* currently we find ourselves flashing almost exclusively one model of router

However, before tackling these concerns, all the configurations made by makenode must be moved back to the firmware and adapted to be somewhat configurable. To do this, we will create a uci-defaults script that does exactly what make makenode previously did...copy a lot of IP addresses into different config files.

== What does makenode change? ==

=== configs/templates/files/opt/mesh/ ===
* tunnelhook -> callback called by config_load tunneldigger

=== configs/templates/files/etc/ ===

dropbear/
* authorized keys, i.e. adds developer keys -> remove? or add more people? opt-in option in dashboard

config/
* dhcp -> dnsmasq, mesh pool, private pool
* network -> loopback, lan, adhoc, open, priv
* notdhcpserver -> extender node static ips
* polipo -> daemonised caching web proxy
* rpcd, -> sets ubus username and pass (from where?)
* snmpd -> managment/monitoring, pulls in operator email/name, presumably from makenode.js
* system -> sets hostname and log ip? from makenode.js?
* tunneldigger- > sets tunnel broker ip, l2tp interface, upstream, downstream bandwidth (related to bug #2), and tunnel hook callback script
* uhttpd -> http server, sets index directory, ubus, cgi-bin, locale

init.d/
* log -> copied from openwrt? purpose?

iproute2/
* rt_tables -> moved to makenode by MaxB, unclear purpose? reverses values for ...?

babeld.conf -> allows babel to run on l2tp, adhoc, and open interface, (could address bug #13 here)

banner -> presents version info, move back to firmware

dnsmasq.conf -> excepts interfaces l2tp0, adhoc0, eth0, why?

Mesh/Makenode

2018-03-07T21:37:19Z

Gcg:

Gcg: Gcg moved page Makenode to Mesh/Makenode: forgot mesh slash

2018-02-11T22:46:10Z

Gcg:

{{#setlogo:Meshlogo.png}}
[[File:Sudomesh.jpg|350px]]
[[File:SudoMesh Node.png|frameless|right|300px]]

'''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're 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/sudmesh software], fixing hardware, [https://sudoroom.org/wiki/Mesh/WalkThrough setting up a node], [https://peoplesopen.net/blog/downtown-oakland-access-point/ 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 :)

You can read about our progress on our [https://peoplesopen.net/blog/ blog].

'''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!
<center>{{Mesh nav}}</center>

[[File:Mesh_Oakland_High_Res.png|225px|right]]
----
= Intro =
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.

sudo mesh is a non-profit organization consisting of a group of unpaid volunteers who are building the People's Open Network. Our mission is 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, a community mesh network can be a resilient means of communication and sharing of information.

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

= Join Us =

Ways to participate:

* 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 Tuesday of every month at [[Getting_there|sudo room]] at 7:30 pm. We have focus groups and collaborate on different parts of the project - from design to software development, documentation to hardware hacking, community outreach and climbing rooftops to mount nodes!
* We have '''weekly hacknights''' on the Tuesdays that are not general meetings, 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] (see also [[IRC | IRC Intro]])
* 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]]!
* 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").

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 show up at our monthly general meeting as described above :)

= 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|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!
*Come to our meetings in Oakland! (listed above)
*Improve our documentation
*Talk to your community about joining the mesh - here are some [[Mesh/Outreach|resources]] for doing so!

== Developers ==

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

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

Here are some of the projects that need attention:

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

== Designers ==

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

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

= Logistics =
* [[Mesh/Minutes|Meeting Minutes]] - Notes from our weekly meetings dating back to January 2013.
* [[Mesh/Inventory|Inventory]] - Continually-updated inventory of our hardware and gear.
* [[Mesh/Taxes|Taxes]] - Filed taxes for the sudo mesh non-profit

= Research =
We need help improving our documentation about the area and other legalities.
* [[Mesh/Interviews with other meshers|Interviews]] - we interviewed other experienced meshers
* [[Mesh/Documentation|Other documentation]] - books, articles, wikis, blog posts.
* [[Mesh/Oakland|Oakland]] - information and resources pertaining to Oakland community organizations, wireless initiatives, policy and research initiatives
* [[Mesh/Other muni networking projects|Municipal projects]] - examples of progressive uses of municipal networks.
* [[Mesh/Decentralized FM/AM radio|Decentralized FM/AM radio]] - Bit of research on adding legal FM/AM transmitters to nodes.

= Other Firmware and Networks =

There are [[Mesh/Other mesh projects|other meshes]] around the world that have inspired us to make our own network!
* [[Mesh/wlan-slovenia]] (slovenia) - mesh network in Slovenia with the first cross-country links to Austria and Croatia! wlan-sl developers have been incredibly helpful mentors since the beginning of the sudomesh project, and are the founders of the Nodewatcher admin database as well as the Koruza wireless optical link project.
* [[Mesh/Freifunk]] (germany) - the creators of batman-adv and one of the longest-running mesh networks in the world.
* [http://guifi.net/en Guifi] (catalonia) - largest community network (using a variety of topologies) in the world - spanning upwards of 22,000 nodes across catalonia and spain. Guifi folks have also been incredibly supportive of sudo mesh and helpful in guiding the international movement toward community wireless networks.
* [[Mesh/Altermundi]] (argentina) - Connecting rural communities in Argentina to the Internet using long range point-to-point links connecting community mesh networks. Developers from Altermundi also contribute extensively to the Libremesh firmware and Librerouter, an open hardware mesh router in development.
* [[Mesh/Funkfeur]] (austria) - another old-school mesh network
* [[Mesh/Ninux]] (italy) - Spanning several cities across Italy, Ninux developers also contribute extensively to research on community networks, the dashboard admin interface NodeShot, and LibreMesh / Librerouter
* [[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]][[Category:Mesh]]