Bay Area Backbone: Difference between revisions

From Bay Area Mesh
Jump to navigation Jump to search
No edit summary
No edit summary
Line 14: Line 14:
 
The current health of the backbone is monitored [http://kn6plv-backbone.local.mesh/ here] ([https://sfbackbone.xojs.org/ internet])
  
The current health of the backbone is monitored [http://kn6plv-backbone.local.mesh/ here] ([https://sfbackbone.xojs.org/ internet])
   
−
=== Management VLANs ===
 +
=== Hardware ===
  +
The mesh operates on the Backbone by creating point-to-point VLANs between mesh sites (these are called '''xlinks''' - see below). Mikrotik hAP ac2 nodes provide the the mesh endpoint hardware. The VLANs are passed across specific backbone links and traffic is not flooded across the backbone.
−
Each site manages its devices on a unique VLAN to isolate them from all other sites (the management VLAN is not passed across any links).
  
−
{| class="wikitable"
  
−
|+
  
−
!VLAN
  
−
!Site
  
−
!Notes
  
−
|-
  
−
|3
  
−
|Fish Ranch
  
−
|VLAN is not set on the AF radio
  
−
|-
  
−
|3
  
−
|ORCA
  
−
|
  
−
|-
  
−
|121
  
−
|Mount Diablo
  
−
|
  
−
|-
  
−
|100
  
−
|San Bruno (Building 4)
  
−
|
  
−
|-
  
−
|100
  
−
|San Bruno (Building 7)
  
−
|
  
−
|-
  
−
|110
  
−
|Oxford
  
−
|
  
−
|-
  
−
|122
  
−
|CCCC
  
−
|
  
−
|-
  
−
|1001
  
−
|San Carlos
  
−
|
  
−
|-
  
−
|1003
  
−
|San Pedro
  
−
|
  
−
|-
  
−
|1004
  
−
|Sunol Ridge
  
−
|
  
−
|-
  
−
| -
  
−
|Wolfback
  
−
|TODO
  
−
|}
  
   
 
=== XLINKS ===
  
=== XLINKS ===
Line 131: Line 81:
 
|
  
|
 
|}
  
|}
  ⚫
Backbone links appear in the mesh labeled as '''xlink''' but are no different from any other link in the network. We are not building a hierarchy with the backbone at the top and the rest of the mesh hanging below. But the nature of the backbone, how it connects, and the way the mesh routing protocol operates, these links will provide preferred pathways between physically distance locations.
   
 
== Backbone Links ==
  
== Backbone Links ==
Line 186: Line 137:
   
 
=== Physical ===
  
=== Physical ===
−
A minimal backbone endpoint consists of two pieces of hardware:
  
−  
−
* A non-AREDN radio. We generally use Ubiquiti airFiber 5XHD radios, but this is not required; any PtP radio will work.
  
−
* A Mikrotik hAP ac2 AREDN node
  
−  
−
The radio provides the wireless endpoint for one end of a backbone link, while the hAP links that radio into the rest of the AREDN network.
  
−  
−
=== Network ===
  
−
To connect these PtP links into the AREDN network we use an AREDN features called XLINKS. An XLINK is a point to point VLAN with a specific VLAN number for that connection. The VLAN is integrated into the AREDN network just link any other link. You can think of it as an AREDN tunnel, but without the overhead of that mechanism or the need for an Internet connection.
  
   
−
=== Mesh ===
 +
==== Radios ====
  +
A minimal backbone endpoint consists of two radios providing a point-to-point link between two sites. Generally Ubiquiti airFiber 5XHD radios are used. In some cases a point-to-multipoint setup is used (generally where tower space is limited). In these cases we use the Ubiquiti LTU-Rocket to provide the multipoint target, with 5XHD radios (with alternate firmware) at the other ends.
⚫
Backbone links appear in the mesh labeled as '''xlink''' but are no different from any other link in the network. We are not building a hierarchy with the backbone at the top and the rest of the mesh hanging below. But the nature of the backbone, how it connects, and the way the mesh routing protocol operates, these links will provide preferred pathways between physically distance locations. And that's the goal.
  
   
−
== Alternatives ==
 +
==== Routers ====
  +
Any router capable of supporting OSPF can be used to support the radios. Two options currently deployed are the Ubiquiti EdgeRouterX and the Mikrotik CRS112-8P-4S.
−
There are other approaches to this problem. The [[Lamorinda Network]] uses an [[wikipedia:Open_Shortest_Path_First|OSPF]] network of license radios, and then runs AREDN as a single "site" on top of it as one of its tenants.
  
   
−
== Previous Approach ==
 +
=== Software ===
  +
We plan to run OSPF across the backbone network (work in progress).
−
The setup for backbone links operated a simply switching VLAN2 (DtD) between all radios. This essentially makes all AREDN nodes at each site look like they're on one ethernet segment. It was not an ideal solution which we have moved away from as the backbone has grown.
  

Revision as of 10:40, 12 June 2023

Backbone Map.png

The goal of the Bay Area Backbone Project is to build a solid, fast, network between high sites in the Bay Area. This network will be available to support various amateur radio projects. The Bay Area Mesh is one of those supported projects.

Bay Area Mesh on the Backbone

Using the Bay Area Backbone to support the Bay Area Mesh as a number of advantages for the Mesh:

  • It easier to connect high sites to other high sites, especially when we're trying to connect different neighborhoods while avoiding mountain ridges.
  • High sites are often backed up with generator power. We provide battery backup ourselves, but that will only last so long.
  • High sites will be there when the Ham moves on. Because these are generally commercial sites with long histories of ham involvement, we are not a the whims of someones current housing situation or - in some cases - employment situation.
  • It's often easier for a neighborhood to connect up to a high site (or more than one) as they're less obstructed.

Status

The current health of the backbone is monitored here (internet)

Hardware

The mesh operates on the Backbone by creating point-to-point VLANs between mesh sites (these are called xlinks - see below). Mikrotik hAP ac2 nodes provide the the mesh endpoint hardware. The VLANs are passed across specific backbone links and traffic is not flooded across the backbone.

XLINKS

XLINKS are custom VLANs between sites which feed directly into the AREDN router. Think of them as DtD links, but only point-to-point.

Link VLAN A B Notes
San Bruno Mountain to Swallow 10 100.64.0.21 100.64.0.22
ORCA to Wolfback 11 100.64.0.17 100.64.0.18
ORCA to Fish Ranch 12 100.64.0.13 100.64.0.14
Fish Ranch to San Bruno Mountain 13 100.64.0.10 100.64.0.9
San Carlos to Sunol Ridge 14 100.64.0.6 100.64.0.5
San Bruno Mountain to San Carlos 15 100.64.0.1 100.64.0.2
San Bruno Mountain to Fire Station 8 16 100.64.0.25 100.64.0.26
Fire Station 8 to Mount Allison 17 100.64.0.29 100.64.0.30 Subject to change as site uses VLANs extensively
Oxford to Wolfback 18 100.64.0.33 100.64.0.34

Backbone links appear in the mesh labeled as xlink but are no different from any other link in the network. We are not building a hierarchy with the backbone at the top and the rest of the mesh hanging below. But the nature of the backbone, how it connects, and the way the mesh routing protocol operates, these links will provide preferred pathways between physically distance locations.

Backbone Links

Active

Planned

Proposed

Backbone Network Structure

Physical

Radios

A minimal backbone endpoint consists of two radios providing a point-to-point link between two sites. Generally Ubiquiti airFiber 5XHD radios are used. In some cases a point-to-multipoint setup is used (generally where tower space is limited). In these cases we use the Ubiquiti LTU-Rocket to provide the multipoint target, with 5XHD radios (with alternate firmware) at the other ends.

Routers

Any router capable of supporting OSPF can be used to support the radios. Two options currently deployed are the Ubiquiti EdgeRouterX and the Mikrotik CRS112-8P-4S.

Software

We plan to run OSPF across the backbone network (work in progress).

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