Supernodes: Difference between revisions

From Bay Area Mesh
Jump to navigation Jump to search
No edit summary
 
(32 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
[[File:Essential Supernodes.png|none|thumb]]
  
[[File:Essential Supernodes.png|none|thumb]]
 
The basic idea behind a supernode connected mesh, is that each mesh is it's own self contained "zone", but these zones can communicate with each other by routing inter-zone traffic through a set of supernodes. Supernodes know about all the nodes in all the meshes and take care of routing traffic to where it needs to go, without burdening your average mesh node with this information.
  
The basic idea behind a supernode connected mesh, is that each mesh is it's own self contained "zone", but these zones can communicate with each other by routing inter-zone traffic through a set of supernodes. Supernodes know about all the nodes in all the meshes and take care of routing traffic to where it needs to go, without burdening your average mesh node with this information.
  +
  +
== Status ==
  +
The supernode infrastructure is supported in the nightly build series. It is not yet available as a release build.
  +
  +
To use the supernode infrastructure you must be running a nightly build (20230921 or later) on your localnode. Your localnode is the node you resolve if you type http://localnode.local.mesh info your web browser when connected to the mesh.
  +
  +
For a list of current supernode connected meshes see the list below. If you want to join this group, please contact KN6PLV (tim.j.wilkinson@gmail.com) or W6BI (orv.beach@gmail.com) who will help you with your supernode setup.
  +
  +
== Map of Connected Networks ==
  +
http://worldmap.arednmesh.org
  +
  +
== Traffic Monitoring ==
  +
https://grafana.xojs.org/d/slmVvAMSz/supernodes?orgId=1&from=now-6h&to=now&refresh=15m
  +
  +
== Current Supernodes ==
  +
  +
=== Bay Area Mesh ===
  +
  +
* KN6PLV-BAM-SUPERNODE
  +
  +
=== [[Oklahoma City Mesh]] ===
  +
  +
* KI5VMF-CLOUD-TUNNEL-SUPERNODE
  +
  +
=== [[Southern California Mesh]] ===
  +
  +
* W6BI-SoCal-SUPERNODE
  +
* KM6SLF-OC-SUPERNODE
  +
  +
=== [[Willamette Valley Mesh]] ===
  +
  +
* K1RKS-Supernode
  +
  +
=== Dayton Ohio Mesh ===
  +
  +
* NC8Q-SUPERNODE
  +
  +
=== Hawaii Mesh ===
  +
  +
* WH6AV-SUPERNODE
  +
  +
=== Arizona Mesh ===
  +
  +
* KI7LXY-AZ-SUPERNODE
  +
  +
=== Yakima Mesh ===
  +
  +
* KO7W-YAKIMA-SUPERNODE
  +
  +
=== Philadelphia Mesh ===
  +
  +
* W3EX-PHL-SUPERNODE
  +
* AA3JC-HAPAC3-SUPERNODE
  +
  +
=== Switzerland Mesh ===
  +
  +
* HB9FTS-SO-SUPERNODE
  +
  +
=== Anchorage Alaska Mesh ===
  +
  +
* KL7AA-AK-SUPERNODE
  +
  +
=== Florida Mesh ===
  +
  +
* KD4WLE-EASTFLORIDA-SUPERNODE
  +
* WT0F-NFL-SUPERNODE
  +
  +
=== South Texas Mesh ===
  +
  +
* N5MXI-STX-SUPERNODE
  +
  +
=== North Texas ===
  +
  +
* KE5YZP-NTX-SUPERNODE
  +
  +
== Alternate Approach ==
  +
Mark Herson N2HM has been operating an alternate supernode approach since 2016. He uses a Hub node which connects to many other meshes, but doesnt share any of the connected meshes data between each other. It's possible the browse these connected meshes by using a web proxy pointing at this hub.
  +
  +
It is not currently possible for one mesh node to connect directly to a node on another mesh. Redundant hubs are not currently provided.

Latest revision as of 16:57, 17 June 2024

Supernodes are a mechanism to connect multiple meshes together, without just making one giant mesh. The original proposal can be found here.

The Basic Idea

Essential Supernodes.png

The basic idea behind a supernode connected mesh, is that each mesh is it's own self contained "zone", but these zones can communicate with each other by routing inter-zone traffic through a set of supernodes. Supernodes know about all the nodes in all the meshes and take care of routing traffic to where it needs to go, without burdening your average mesh node with this information.

Status

The supernode infrastructure is supported in the nightly build series. It is not yet available as a release build.

To use the supernode infrastructure you must be running a nightly build (20230921 or later) on your localnode. Your localnode is the node you resolve if you type http://localnode.local.mesh info your web browser when connected to the mesh.

For a list of current supernode connected meshes see the list below. If you want to join this group, please contact KN6PLV (tim.j.wilkinson@gmail.com) or W6BI (orv.beach@gmail.com) who will help you with your supernode setup.

Map of Connected Networks

http://worldmap.arednmesh.org

Traffic Monitoring

https://grafana.xojs.org/d/slmVvAMSz/supernodes?orgId=1&from=now-6h&to=now&refresh=15m

Current Supernodes

Bay Area Mesh

  • KN6PLV-BAM-SUPERNODE

Oklahoma City Mesh

  • KI5VMF-CLOUD-TUNNEL-SUPERNODE

Southern California Mesh

  • W6BI-SoCal-SUPERNODE
  • KM6SLF-OC-SUPERNODE

Willamette Valley Mesh

  • K1RKS-Supernode

Dayton Ohio Mesh

  • NC8Q-SUPERNODE

Hawaii Mesh

  • WH6AV-SUPERNODE

Arizona Mesh

  • KI7LXY-AZ-SUPERNODE

Yakima Mesh

  • KO7W-YAKIMA-SUPERNODE

Philadelphia Mesh

  • W3EX-PHL-SUPERNODE
  • AA3JC-HAPAC3-SUPERNODE

Switzerland Mesh

  • HB9FTS-SO-SUPERNODE

Anchorage Alaska Mesh

  • KL7AA-AK-SUPERNODE

Florida Mesh

  • KD4WLE-EASTFLORIDA-SUPERNODE
  • WT0F-NFL-SUPERNODE

South Texas Mesh

  • N5MXI-STX-SUPERNODE

North Texas

  • KE5YZP-NTX-SUPERNODE

Alternate Approach

Mark Herson N2HM has been operating an alternate supernode approach since 2016. He uses a Hub node which connects to many other meshes, but doesnt share any of the connected meshes data between each other. It's possible the browse these connected meshes by using a web proxy pointing at this hub.

It is not currently possible for one mesh node to connect directly to a node on another mesh. Redundant hubs are not currently provided.

Retrieved from "https://wiki.bayareamesh.us/index.php?title=Supernodes&oldid=2927"