Mesh/Network topology - Revision history

Eenblam: Drop images depicting relay nodes in network topology

2018-06-17T01:03:39Z

Drop images depicting relay nodes in network topology

← Older revision		Revision as of 18:03, 16 June 2018
Line 2:		Line 2:
	'''This page has been marked as [[:Category:Stale\|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''		'''This page has been marked as [[:Category:Stale\|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

	~~[[File:Network topology diagram-hi.png\|thumb\|png (hi), [[Mesh/Diagrams#Network Topology Diagram\|see more]]]]~~
	= Peoplesopen.net Topology =		= Peoplesopen.net Topology =
	For information about the people's open network topology, refer to this [[Mesh/Diagrams#Network Topology Diagram\|network topology diagram]].		For information about the people's open network topology, refer to this [[Mesh/Diagrams#Network Topology Diagram\|network topology diagram]].

	= WiFi Topology =		= WiFi Topology =

	~~[[File:Mesh topology diagram.png\|thumb]]~~

	We use 2.4 GHz 802.11g or 802.11n WiFi gear with omni or semi-directional antennas to provide connectivity to devices such as laptops and smartphones at street level and within buildings. We are currently using a variety of gear including Ubiquiti Picostation M2 HP and Ubiquiti Bullet M2 HP routers for outdoor APs.		We use 2.4 GHz 802.11g or 802.11n WiFi gear with omni or semi-directional antennas to provide connectivity to devices such as laptops and smartphones at street level and within buildings. We are currently using a variety of gear including Ubiquiti Picostation M2 HP and Ubiquiti Bullet M2 HP routers for outdoor APs.

Eenblam: Capitalize section headers

2018-06-17T01:02:40Z

Capitalize section headers

← Older revision		Revision as of 18:02, 16 June 2018
Line 3:		Line 3:

	[[File:Network topology diagram-hi.png\|thumb\|png (hi), [[Mesh/Diagrams#Network Topology Diagram\|see more]]]]		[[File:Network topology diagram-hi.png\|thumb\|png (hi), [[Mesh/Diagrams#Network Topology Diagram\|see more]]]]
	= ~~peoplesopen~~.net ~~topology~~ =		= Peoplesopen.net Topology =
	For information about the people's open network topology, refer to this [[Mesh/Diagrams#Network Topology Diagram\|network topology diagram]].		For information about the people's open network topology, refer to this [[Mesh/Diagrams#Network Topology Diagram\|network topology diagram]].

Line 18:		Line 18:
	All of the outdoor gear is Power over Ethernet (PoE), requiring only a single cable for network and power connectivity.		All of the outdoor gear is Power over Ethernet (PoE), requiring only a single cable for network and power connectivity.

	= ~~mesh topology~~ =		= Mesh Topology =

	All routers run the Babel mesh routing protocol. The street-level 2.4 ghz routers should ideally be able to function in the event that e.g. an earthquake takes out all of the point to point and point to multipoint rooftop nodes (more alignment sensitive) and the mesh should remain functional, though it could become segmented.		All routers run the Babel mesh routing protocol. The street-level 2.4 ghz routers should ideally be able to function in the event that e.g. an earthquake takes out all of the point to point and point to multipoint rooftop nodes (more alignment sensitive) and the mesh should remain functional, though it could become segmented.
Line 24:		Line 24:
	The relays / [[VPuN]] servers (see the internet connectivity section) also run Babel, so mesh traffic can flow from one part of the mesh, through the internet, through a relay, and into another part of the mesh if some of the mesh nodes are connected to the internet.		The relays / [[VPuN]] servers (see the internet connectivity section) also run Babel, so mesh traffic can flow from one part of the mesh, through the internet, through a relay, and into another part of the mesh if some of the mesh nodes are connected to the internet.

	= ~~internet connectivity~~ =		= Internet Connectivity =

	There are four primary types of devices in the mesh:		There are four primary types of devices in the mesh:

Eenblam: /* wifi topology */ Overhaul backbone section. Present tense - we have hardware. Capitalization. Oxford commas.

2018-06-17T01:02:00Z

wifi topology: Overhaul backbone section. Present tense - we have hardware. Capitalization. Oxford commas.

← Older revision		Revision as of 18:02, 16 June 2018
Line 6:		Line 6:
	For information about the people's open network topology, refer to this [[Mesh/Diagrams#Network Topology Diagram\|network topology diagram]].		For information about the people's open network topology, refer to this [[Mesh/Diagrams#Network Topology Diagram\|network topology diagram]].

	= ~~wifi topology~~ =		= WiFi Topology =

	[[File:Mesh topology diagram.png\|thumb]]		[[File:Mesh topology diagram.png\|thumb]]

	We use 2.4 ~~ghz~~ 802.11g or 802.11n ~~wifi~~ gear with omni or semi-directional antennas to provide connectivity to devices such as laptops and smartphones at street level and within buildings. We are currently using a variety of gear including Ubiquiti Picostation M2 HP and Ubiquiti Bullet M2 HP routers for ~~the~~ outdoor APs.		We use 2.4 GHz 802.11g or 802.11n WiFi gear with omni or semi-directional antennas to provide connectivity to devices such as laptops and smartphones at street level and within buildings. We are currently using a variety of gear including Ubiquiti Picostation M2 HP and Ubiquiti Bullet M2 HP routers for outdoor APs.

	~~A high-speed~~ wireless backbone ~~for the mesh will be provided by 5 ghz 802.11n hardware, usually with~~ point to point or point to multipoint ~~connections~~ mounted in high places such as on rooftops, flagpoles or antenna towers. We currently have a variety of Ubiquiti M5 routers such as ~~airgrids~~, ~~nanobridges~~, ~~nanostations~~ and ~~a rocket~~.		We're currently deploying a wireless backbone of point-to-point and point-to-multipoint links. These devices are mounted in high places such as on rooftops, flagpoles, or antenna towers. We currently have firmware support for a variety of Ubiquiti M5 (802.11n) routers, such as NanoBridges, NanoStations, and Rockets. As of June 2018, we're currently working to establish gigabit links with 5GHz and 24GHz Ubiquiti airFiber routers, as well as 60GHz Microtik wireless wires.

	See the [[Mesh/Home and extender nodes\|Home and extender nodes]] for more info about how these are setup.		See the [[Mesh/Home and extender nodes\|Home and extender nodes]] for more info about how these are setup.

	All of the outdoor gear ~~will be~~ Power over Ethernet (PoE), requiring only a single cable for network and power connectivity.		All of the outdoor gear is Power over Ethernet (PoE), requiring only a single cable for network and power connectivity.

	= mesh topology =		= mesh topology =

Eenblam: Fix link in stale message

2018-06-10T20:39:04Z

Fix link in stale message

← Older revision		Revision as of 13:39, 10 June 2018
Line 1:		Line 1:
	[[Category:Stale]]		[[Category:Stale]]
	'''This page is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''		'''This page has been marked as [[:Category:Stale\|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

	[[File:Network topology diagram-hi.png\|thumb\|png (hi), [[Mesh/Diagrams#Network Topology Diagram\|see more]]]]		[[File:Network topology diagram-hi.png\|thumb\|png (hi), [[Mesh/Diagrams#Network Topology Diagram\|see more]]]]

Eenblam: Move stale to top; add stale message

2018-06-10T20:36:31Z

Move stale to top; add stale message

← Older revision		Revision as of 13:36, 10 June 2018
Line 1:		Line 1:
			[[Category:Stale]]
			'''This page is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

	[[File:Network topology diagram-hi.png\|thumb\|png (hi), [[Mesh/Diagrams#Network Topology Diagram\|see more]]]]		[[File:Network topology diagram-hi.png\|thumb\|png (hi), [[Mesh/Diagrams#Network Topology Diagram\|see more]]]]
	= peoplesopen.net topology =		= peoplesopen.net topology =
Line 45:		Line 48:

	* We have the opportunity to establish a Gigabit link between Oakland and San Francisco, with a connection in San Francisco near the Western most part of 24th street in the [https://goo.gl/maps/TzMBTsadiCL2 Noe Valley] neighborhood. This location has great line of sight with many locations in the East Bay. We would like to establish a relationship with anyone that can grant permission to mount equipment on Laney Tower at [http://www.laney.edu/wp/ Laney College] in Oakland.		* We have the opportunity to establish a Gigabit link between Oakland and San Francisco, with a connection in San Francisco near the Western most part of 24th street in the [https://goo.gl/maps/TzMBTsadiCL2 Noe Valley] neighborhood. This location has great line of sight with many locations in the East Bay. We would like to establish a relationship with anyone that can grant permission to mount equipment on Laney Tower at [http://www.laney.edu/wp/ Laney College] in Oakland.

	~~[[Category:Stale]]~~

Eenblam: stale

2018-06-10T20:33:13Z

stale

← Older revision		Revision as of 13:33, 10 June 2018
Line 45:		Line 45:

	* We have the opportunity to establish a Gigabit link between Oakland and San Francisco, with a connection in San Francisco near the Western most part of 24th street in the [https://goo.gl/maps/TzMBTsadiCL2 Noe Valley] neighborhood. This location has great line of sight with many locations in the East Bay. We would like to establish a relationship with anyone that can grant permission to mount equipment on Laney Tower at [http://www.laney.edu/wp/ Laney College] in Oakland.		* We have the opportunity to establish a Gigabit link between Oakland and San Francisco, with a connection in San Francisco near the Western most part of 24th street in the [https://goo.gl/maps/TzMBTsadiCL2 Noe Valley] neighborhood. This location has great line of sight with many locations in the East Bay. We would like to establish a relationship with anyone that can grant permission to mount equipment on Laney Tower at [http://www.laney.edu/wp/ Laney College] in Oakland.

			[[Category:Stale]]

Redconfetti: added backbone connections section with note concerning SF and Laney College desired link

2016-07-06T04:19:17Z

added backbone connections section with note concerning SF and Laney College desired link

← Older revision		Revision as of 21:19, 5 July 2016
Line 39:		Line 39:
	:Until network has an AS, only one exit node should be made and multiple relay nodes should connect to that exit node (Tunneldigger software can be reused for that). Otherwise clients can have issues when routing protocol decides to move from one exit node to another.		:Until network has an AS, only one exit node should be made and multiple relay nodes should connect to that exit node (Tunneldigger software can be reused for that). Otherwise clients can have issues when routing protocol decides to move from one exit node to another.
	:It is important that nodes are connecting to relays and relays to exit nodes and that no IPs of those connecting to relays and exit nodes is stored.		:It is important that nodes are connecting to relays and relays to exit nodes and that no IPs of those connecting to relays and exit nodes is stored.

			= Backbone Connections =

			== Desired ==

			* We have the opportunity to establish a Gigabit link between Oakland and San Francisco, with a connection in San Francisco near the Western most part of 24th street in the [https://goo.gl/maps/TzMBTsadiCL2 Noe Valley] neighborhood. This location has great line of sight with many locations in the East Bay. We would like to establish a relationship with anyone that can grant permission to mount equipment on Laney Tower at [http://www.laney.edu/wp/ Laney College] in Oakland.

Maxb: /* wifi topology */

2016-02-05T23:55:52Z

wifi topology

← Older revision		Revision as of 16:55, 5 February 2016
Line 7:		Line 7:
	[[File:Mesh topology diagram.png\|thumb]]		[[File:Mesh topology diagram.png\|thumb]]

	We use 2.4 ghz 802.11g or 802.11n wifi gear with omni or semi-directional antennas to provide connectivity to devices such as laptops and smartphones at street level and within buildings. We are currently using ~~mostly~~ Ubiquiti Picostation 2 HP and Ubiquiti Bullet 2 HP routers for the ~~outdoors. For the indoors we will likely use TP-Link TL-WR703N routers~~.		We use 2.4 ghz 802.11g or 802.11n wifi gear with omni or semi-directional antennas to provide connectivity to devices such as laptops and smartphones at street level and within buildings. We are currently using a variety of gear including Ubiquiti Picostation M2 HP and Ubiquiti Bullet M2 HP routers for the outdoor APs.

	A high-speed wireless backbone for the mesh will be provided by 5 ghz 802.11n hardware, usually with point to point or point to multipoint connections mounted in high places such as on rooftops, flagpoles or antenna towers. We currently have a variety of Ubiquiti M5 routers such as airgrids, nanobridges, nanostations and a rocket.		A high-speed wireless backbone for the mesh will be provided by 5 ghz 802.11n hardware, usually with point to point or point to multipoint connections mounted in high places such as on rooftops, flagpoles or antenna towers. We currently have a variety of Ubiquiti M5 routers such as airgrids, nanobridges, nanostations and a rocket.

			See the [[Mesh/Home and extender nodes\|Home and extender nodes]] for more info about how these are setup.

	All of the outdoor gear will be Power over Ethernet (PoE), requiring only a single cable for network and power connectivity.		All of the outdoor gear will be Power over Ethernet (PoE), requiring only a single cable for network and power connectivity.

Juul: /* internet connectivity */

2015-07-02T14:42:30Z

internet connectivity

← Older revision		Revision as of 07:42, 2 July 2015
Line 35:		Line 35:

	Each relay is connected to one exit node (tunnel type not yet decided). It does NAT (IP Masquerading) on traffic coming from the mesh and headed for the internet. All traffic coming from the mesh and going to the wider internet goes through an exit node. The source IP of data coming from the mesh thus appears as the IP of one of the exit nodes. This provides a layer of protection such that e.g. abuse complaints will be sent to the mesh organization instead of the individuals who donate some of their internet bandwidth to the mesh.		Each relay is connected to one exit node (tunnel type not yet decided). It does NAT (IP Masquerading) on traffic coming from the mesh and headed for the internet. All traffic coming from the mesh and going to the wider internet goes through an exit node. The source IP of data coming from the mesh thus appears as the IP of one of the exit nodes. This provides a layer of protection such that e.g. abuse complaints will be sent to the mesh organization instead of the individuals who donate some of their internet bandwidth to the mesh.
	:Until network has an AS, only one exit node should be made and multiple relay nodes should connect to that exit node (Tunneldigger software can be reused for that). Otherwise clients can have issues when routing protocol decides to move from one exit node to another. ~~But it is true that batman-adv has some protection against that, so that once a client decides for a gateway, it should be more or less sticky, no?~~		:Until network has an AS, only one exit node should be made and multiple relay nodes should connect to that exit node (Tunneldigger software can be reused for that). Otherwise clients can have issues when routing protocol decides to move from one exit node to another.
	:It is important that nodes are connecting to relays and relays to exit nodes and that no IPs of those connecting to relays and exit nodes is stored.		:It is important that nodes are connecting to relays and relays to exit nodes and that no IPs of those connecting to relays and exit nodes is stored.

Juul: /* internet connectivity */

2015-07-02T14:41:20Z

internet connectivity

← Older revision		Revision as of 07:41, 2 July 2015
Line 26:		Line 26:
	:These do not run the meshing protocol.		:These do not run the meshing protocol.
	*Mesh nodes: Wifi routers running OpenWRT.		*Mesh nodes: Wifi routers running OpenWRT.
	:~~Some are rooftop backbone~~ nodes and ~~some are street-level or in-home~~ nodes.		:This includes home nodes and their extender nodes
	*Relays: Professionally hosted servers that relay mesh traffic over the internet.		*Relays / [[Mesh/VPuN\|VPuN servers]]: Professionally hosted servers that relay mesh traffic over the internet.
	:These run the meshing protocol. Mesh nodes are connected with L2TP tunnels ~~to them~~.		:These run the meshing protocol. Mesh nodes are connected to them with L2TP tunnels.
	*Exit nodes: Co-located servers that appear as the source IP for packets from mesh to internet.		*Exit nodes: Co-located servers that appear as the source IP for packets from mesh to internet.
	:Both relays and exit nodes serve as a layer of protection between people sharing their internet connections with the mesh.		:Both relays and exit nodes serve as a layer of protection between people sharing their internet connections with the mesh. A relay can also be an exit server and this may in fact end up being the case in most instances.

	Some mesh routers will be hosted in homes that already have internet connections. If an internet connection is available, a mesh router will open an L2TP tunnel (using the tunneldigger software) to several relay nodes over the internet connection. A relay could be e.g. a VPS without a bandwidth cap. The relays all run ~~batman-adv~~ and function as part of the mesh through the L2TP tunnels to the mesh nodes. Each relay will have a connection to an exit nodes. The relays allow segments of the mesh that are not connected with wifi to be connected over the internet.		Some mesh routers will be hosted in homes that already have internet connections. If an internet connection is available, a mesh router will open an L2TP tunnel (using the tunneldigger software) to several relay nodes over the internet connection. A relay could be e.g. a VPS without a bandwidth cap. The relays all run Babel and function as part of the mesh through the L2TP tunnels to the mesh nodes. Each relay will have a connection to an exit nodes. The relays allow segments of the mesh that are not connected with wifi to be connected over the internet.

	Each relay is connected to one exit node (tunnel type not yet decided). It does NAT (IP Masquerading) on traffic coming from the mesh and headed for the internet. All traffic coming from the mesh and going to the wider internet goes through an exit node. The source IP of data coming from the mesh thus appears as the IP of one of the exit nodes. This provides a layer of protection such that e.g. abuse complaints will be sent to the mesh organization instead of the individuals who donate some of their internet bandwidth to the mesh.		Each relay is connected to one exit node (tunnel type not yet decided). It does NAT (IP Masquerading) on traffic coming from the mesh and headed for the internet. All traffic coming from the mesh and going to the wider internet goes through an exit node. The source IP of data coming from the mesh thus appears as the IP of one of the exit nodes. This provides a layer of protection such that e.g. abuse complaints will be sent to the mesh organization instead of the individuals who donate some of their internet bandwidth to the mesh.
	:Until network has an AS, only one exit node should be made and multiple relay nodes should connect to that exit node (Tunneldigger software can be reused for that). Otherwise clients can have issues when routing protocol decides to move from one exit node to another. But it is true that batman-adv has some protection against that, so that once a client decides for a gateway, it should be more or less sticky, no?		:Until network has an AS, only one exit node should be made and multiple relay nodes should connect to that exit node (Tunneldigger software can be reused for that). Otherwise clients can have issues when routing protocol decides to move from one exit node to another. But it is true that batman-adv has some protection against that, so that once a client decides for a gateway, it should be more or less sticky, no?
	:It is important that nodes are connecting to relays and relays to exit nodes and that no IPs of those connecting to relays and exit nodes is stored.		:It is important that nodes are connecting to relays and relays to exit nodes and that no IPs of those connecting to relays and exit nodes is stored.