Difference between revisions of "Mesh/Decisions"

Jump to navigation Jump to search
2,081 bytes added ,  06:06, 2 July 2015
(Created page with "Each new community mesh project faces a set of decisions. This page contains a discussion of some of these decisions. = Mesh router as primary access point = Adding a WPA2-P...")
 
 
(8 intermediate revisions by 2 users not shown)
Line 4: Line 4:


Adding a WPA2-PSK encrypted virtal access point to the router would allow node-owners to use the mesh router either as their primary private access point, or as a secondary access point in places where their existing access point doesn't reach. This could be a nice added feature, but would require some more firmware work.
Adding a WPA2-PSK encrypted virtal access point to the router would allow node-owners to use the mesh router either as their primary private access point, or as a secondary access point in places where their existing access point doesn't reach. This could be a nice added feature, but would require some more firmware work.
:The issue with that is that primary access points are often optimally in the center of the house, while mesh nodes should be on the edge of the house.


== Decision ==
== Decision ==


We're already been working on this. The web admin interface will be fairly minimal, allowing changing the ssid and password of the private access point, as well as manual tcp/udp port forwarding. The nat-pmp and upnp daemons will also be installed and the gui will provide access to disable/enable them.
We're already implemented this. The web admin interface is fairly minimal, allowing changing the ssid and password of the private access point. We have solved the issue mentioned above (primary access point best located in center of house) by having optional [[extender-nodes]]. Node-owners can also just buy two nodes and put them in different locations.


= Commercial || non-commercial =
= Commercial || non-commercial =
Line 26: Line 28:
*Free for node-owners and they node-owners can sell access.
*Free for node-owners and they node-owners can sell access.
*Everyone has to pay.
*Everyone has to pay.
:What about paying in work? Time-banking?


== Decision ==
== Decision ==


I think we should stop right before the freemium model [[User:Juul|Juul]] ([[User talk:Juul|talk]]).
I think we should stop right before the freemium model [[User:Juul|Juul]] ([[User talk:Juul|talk]]). We are still discussing this.


= Internet =
= Internet =
Line 39: Line 43:
=== Decision ===
=== Decision ===


Our mesh will definitely be internet-connected.
Our mesh will definitely be internet-connected. It if wasn't then it would likely remain a curiosity for tech geeks and at best be useful in a disaster scenario unless someone can come up with a mesh service that's alluring enough to warrant disconnect from the internet and connecting to non-internet-enabled wifi (maybe really good pirate file sharing servers).


== Sharing of Internet by node-owners ==
== Sharing of Internet by node-owners ==
Line 117: Line 121:
== Decision ==
== Decision ==


We are currently leaning towards a 501c3 with the network being a separate thing.
sudo mesh is now a California non-profit. We should apply for federal 501(c)(3) non-profit status soon. The network itself is separate from sudo mesh and is called People's Open Network. sudo mesh will take incoming donations and develop the sudowrt firmware for connecting to People's Open Network, as well as other mesh services. sudo mesh will run [[VPuN]] servers and try its best to get fast internet piped into the network. sudo mesh will sell cheap pre-flashed routers and organize volunteers to assist with rooftop node installations. People's Open Network has no legal entity (but we may trademark the name to protect it from mis-use) and anyone can become part of (connect to) the network as long as they agree to a simple Free Network License (yet to be defined but likely based on the [https://commons.thefnf.org/index.php/Network_Commons_License Free Network Foundation's Network Common's License]).


= Ownership of and access to infrastructure =
= Ownership of and access to infrastructure =
Line 136: Line 140:


We haven't discussed this very much. I think we should let people own the nodes that they host and let the central organization manage the nodes unless the node-owner wants to manage their own node. We will have to have a clear strategy for who has access to privately owned nodes at any given time, and contracts/agreements about what they are allowed to do to them. We will have to make it very clear to the node-owners what letting us manage the nodes means (that, if obused, this power can be used to monitor their unencrypted traffic and phish ) and how we monitor and prevent abuse from the people in charge (though this is really no different from a normal ISP) [[User:Juul|Juul]] ([[User talk:Juul|talk]])
We haven't discussed this very much. I think we should let people own the nodes that they host and let the central organization manage the nodes unless the node-owner wants to manage their own node. We will have to have a clear strategy for who has access to privately owned nodes at any given time, and contracts/agreements about what they are allowed to do to them. We will have to make it very clear to the node-owners what letting us manage the nodes means (that, if obused, this power can be used to monitor their unencrypted traffic and phish ) and how we monitor and prevent abuse from the people in charge (though this is really no different from a normal ISP) [[User:Juul|Juul]] ([[User talk:Juul|talk]])
:There is as well a bit of difference if nodes are just mesh nodes or if they are being used for private SSID as well.


= Sensors / add-ons =
= Sensors / add-ons =
Line 176: Line 182:


To our knowledge, Ubuntu and other popular GNU/Linux systems do not support detection.
To our knowledge, Ubuntu and other popular GNU/Linux systems do not support detection.
:In talking with some other mesh people I learned that intercepting only first request is not useful because it is almost always some background service which tries that (eg. autoupdate) so user never really sees anything.
:Displaying things in OS detected captive portal window might be bad because this window is a special browser window, so user cannot really browse a lot there (no bookmarks for example). On Mac OS X, furthermore, window is automatically closed by OS when it is detected that connectivity is not limited anymore.


== No captive portal ==
== No captive portal ==

Navigation menu