13
edits
Difference between revisions of "Mesh/Technical Overview"
Jump to navigation
Jump to search
→Node Monitoring
| (6 intermediate revisions by the same user not shown) | |||
| Line 14: | Line 14: | ||
Our mesh has two types of nodes: Home nodes and extender nodes. | Our mesh has two types of nodes: Home nodes and extender nodes. | ||
The home | The home node is a 5 ethernet port wifi router that runs the full sudowrt firmware. A network of home nodes can make a mesh network if they are within the same proximity e.g 200 meters and line-of-sight of each other. Beyond the home nodes broadcast area, an extender node needs to be connected to a home node to communicate to distant neighbours. An extender node runs a minimal firmware and does nothing on its own, but if its connected to a home node it will serve as an extra radio and extend the reach of the network. | ||
The node operator can choose to put a home node in their living room and if they decide they want a high speed directional link to a neighbour then they can put e.g. a Nanobridge M5 running the extender node firmware on their roof and connect it via ethernet to the home node. Or they could put a Nanostation M2 pointed out of their window and extend the signal further out into the street or to nearby neighbours. Each extender node extends all three networks (explained in the next section). | |||
For home nodes we are currently supporting these off-the-shelf router [https://sudoroom.org/wiki/Mesh/WalkThrough#Download.2FBuild models]. We are not planning to support anything else for the time being, though if you have a good reason please let us know. For extender nodes we are currently supporting the Ubiquiti M series [https://sudoroom.org/wiki/Mesh/Flashing_extender_nodes#Flash_the_Extender_Node routers]. | |||
Node-owners can choose to connect the nodes to their existing internet connection 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. | The mesh mainly uses wifi routers with Atheros chipsets and running [https://github.com/sudomesh/sudowrt-firmware our own firmware] based on [http://openwrt.org/ OpenWRT], [http://www.pps.univ-paris-diderot.fr/~jch/software/babel/ Babel] and wlan slovenja's [https://github.com/sudomesh/tunneldigger tunneldigger]. | ||
Node-owners can choose to connect the nodes to their existing internet connection 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 the tool 'tc'. It is chosen at node-configuration time and can be changed using the simple built-in web admin interface. | |||
== The three wifi networks and IP assignment == | == The three wifi networks and IP assignment == | ||
| Line 98: | Line 99: | ||
== Node Monitoring == | == Node Monitoring == | ||
Currently, the peoples open network can be monitored in real time with an [https://peoplesopen.herokuapp.com heroku app] | Currently, the peoples open network can be monitored in real time with an [https://peoplesopen.herokuapp.com heroku app]. | ||
Our exit nodes communicate to this URL using a monitor.sh script. This relays information about the number of active routes and number of active gateways. If the exit node doesn't check-in for longer than 2 minutes, it is assumed to be down. | Our exit nodes communicate to this URL using a monitor.sh script. This relays information about the number of active routes and number of active gateways. If the exit node doesn't check-in for longer than 2 minutes, it is assumed to be down. | ||
==Detailed Documentation== | ==Detailed Documentation== | ||