Difference between revisions of "Mesh/Diagrams"

Mesh/Diagrams (view source)

Revision as of 17:02, 23 June 2018

101 bytes removed , 17:02, 23 June 2018

updating netwrk topology diagram

Tunabananas

Bureaucrats, oversight, Administrators

1,196

edits

@@ Line 17: / Line 17: @@
 <gallery mode="nolines">
-File:Network topology diagram-lo.png|png (lo)
+File:Network_topology_diagram-2018-06-lo.png|png (lo)
-File:Network topology diagram-hi.png|png (hi)
+File:Network_topology_diagram-2018-06-hi.png|png (hi)
-File:Network topology diagram.pdf|pdf
+File:Network_topology_diagram-2018-06.pdf|pdf
-File:Network topology diagram svg.svg|svg
+File:Network_topology_diagram-2018-06.svg|svg
-File:Network topology diagram plain.svg|plain svg
 </gallery>
 The diagram's '''key''' includes the following types of items, which are also described in relation to one another below.
-* '''2.4ghz Node'''
+* '''Home Node'''
 ** Typical router running mesh firmware used in a node operator's home, office, public space, etc.
-* '''5ghz "Backbone" Point-to-Point Node'''
+* '''Extender Node'''
-** Special router running mesh firmware as well, but broadcasting and receiving on the 5ghz frequency that can travel longer distances than 2.4ghz, and is regulated by the [http://en.wikipedia.org/wiki/Federal_Communications_Commission FCC] for use in point-to-point connections only. These are therefore helpful to create a "backbone" on the network that can both:
+** Special router running mesh firmware as well, but broadcasting and receiving on the 5ghz frequency that can travel longer distances than 2.4ghz, and is regulated by the [http://en.wikipedia.org/wiki/Federal_Communications_Commission FCC] for use in point-to-point connections only. These are therefore helpful to create a "backbone" via rooftop-to-rooftop connections on the network that can both:
-**# connect neighborhoods to one another when reasonable connections with '''2.4ghz Nodes''' are not possible
+**# connect neighborhoods to one another when reasonable connections with '''Home Nodes''' are not possible
-**# ensure users of '''2.4ghz Nodes''' are within a few hops (through other nodes on a path) to strong and stable connections to the rest of the local network (peoplesopen.net) and substantive internet lines (e.g. a small ISP or donated line from the Internet Archive, etc).
+**# ensure users of '''Home Nodes''' are within a few hops (through other nodes on a path) to strong and stable connections to the rest of the local network (peoplesopen.net) and substantive internet lines (e.g. a small ISP or donated bandwidth from the Internet Archive, etc).
-* '''Relay Node''' "Virtual Public Network" (VPuN) Tunnel Server & Client
+* '''Exit Node''' "Virtual Public Network" (VPuN) Tunnel Server & Client
-** Server running linux and the TunnelDigger server and client software to create Virtual Public Network (VPuN) connections over generic internet connections. This tunnel software creates a connection using the internet underneath it, so at this point, traffic to '''Relay Nodes''' is considered public in the same way it is on the public global internet. Simply, the distinction is between passing purely local traffic, and traffic that is virtually local, but must use an internet connection to reach the necessary destinations.
+** Server running linux and the TunnelDigger server and client software to create Virtual Public Network (VPuN) connections over generic internet connections. This tunnel software creates a connection using the internet underneath it, so at this point, traffic to '''Exit Nodes''' is considered public in the same way it is on the public global internet. Simply, the distinction is between passing purely local traffic, and traffic that is virtually local, but must use an internet connection to reach the necessary destinations.
 **The term "Virtual Public Network" or VPuN has roots in GNUnet https://gnunet.org/gnunet-vpn and is situated in this historical piece http://www.isaca.org/Journal/Past-Issues/2001/Volume-3/Pages/Virtual-Private-Networking-Confidentiality-on-Public-Networks.aspx. TunnelDigger technically qualifies as "Virtual Private Network" software (with a major lapse in not actually providing access control mechanisms as is the point of most VPN software), but this "private" term is more generic than we can be (see https://en.wikipedia.org/wiki/VPN#Unencrypted_tunnels). Instead, we have opted for a socially and historically situated alternative that is both more descriptive and mission-consistent with sudo mesh's work and the values behind the People's Open Network: ''Virtual Public Network (VPuN)''.
-** Note: if, for instance, the '''5ghz Backbone Nodes''' in the diagram above are disconnected (maybe interference one day), then requests across the network (say from one neighborhood to another) can still pass virtually using the internet, out to '''Relay Nodes''' and back down.
+** Note: if, for instance, the '''Extender Nodes''' in the diagram above are disconnected (maybe interference one day), then requests across the network (say from one neighborhood to another) can still pass virtually using the internet, out to '''Exit Nodes''' and back down.
-* '''Exit Gateway'''
+* '''VPuN Tunnel'''
-** Same as '''Relay Node''' but designated as a ''gateway'' or the final stop between users on the ''peoplesopen.net'' network and out to the public internet (leaving the Virtual Public Network). The gateway is likely to communicate through '''Relay Nodes''' rather than directly with '''2.4ghz Nodes''' and '''Backbone Nodes'''.
+** The pathway between users on the ''peoplesopen.net'' network connecting to the public internet (leaving the Virtual Public Network). The tunnel connects directly to '''Exit Nodes''' rather than directly with '''Home''' and '''Extender Nodes'''.
 ===Node Traffic Diagram===