Bay Area Backbone: Difference between revisions
No edit summary |
|||
| Line 7: | Line 7: | ||
=== San Bruno Mountain === |
=== San Bruno Mountain === |
||
| − | <span style="color: |
+ | <span style="color:green"> |
| − | '''Status''': Equipment installed. |
+ | '''Status''': Equipment installed. Active. |
</span> |
</span> |
||
'''Connection''': Non-AREDN, airFiber 5 GHz. |
'''Connection''': Non-AREDN, airFiber 5 GHz. |
||
| − | ==== |
+ | ====Notes==== |
| + | None |
||
| − | Dish has been checked and is power, and shows a four bar, active link status to San Bruno (re: site visit 22nd, July 2022). However the device does not connect to the UISP tool because the WAN connection to Matt Peterson's is not currently connected, Matt believes is is unplugged at his end. |
||
| − | |||
| − | ==== Cooperation ==== |
||
| − | This link is provided in cooperation with Matt. |
||
== [[San Bruno Mountain]] == |
== [[San Bruno Mountain]] == |
||
| − | === |
+ | ===Fish Ranch / ORCA=== |
| − | <span style="color: |
+ | <span style="color:green"> |
| − | '''Status''': Equipment installed. |
+ | '''Status''': Equipment installed. Active. |
</span> |
</span> |
||
'''Connection''': airFiber 5 GHz. |
'''Connection''': airFiber 5 GHz. |
||
| − | ==== |
+ | ====Notes==== |
| + | None |
||
| − | The connection to Fish Ranch appears active, as Fish Ranch indicates an active link on the radio. This would suggest that the San Bruno end is correctly pointed and powered, but not yet connected to the rest of the AREDN network. |
||
| − | ==== |
+ | ====Plans==== |
Immediate plans for changes at this site are unclear as the current owners want to do some significant upgrades before adding more equipment. We will probably help out with this project once scheduled (soon). After that the goal is to replace the NSM5 with a more powerful radio, finalize this end of the Fish Ranch link, and look at options for connecting south. |
Immediate plans for changes at this site are unclear as the current owners want to do some significant upgrades before adding more equipment. We will probably help out with this project once scheduled (soon). After that the goal is to replace the NSM5 with a more powerful radio, finalize this end of the Fish Ranch link, and look at options for connecting south. |
||
| − | === CCCC |
+ | === CCCC=== |
'''Status''': Proposed |
'''Status''': Proposed |
||
'''Connection:''' AREDN Mikrotik LHG 5 |
'''Connection:''' AREDN Mikrotik LHG 5 |
||
| − | ==== |
+ | ====Notes==== |
Evaluating installing a new dish pointing at CCCC during the next site visit. |
Evaluating installing a new dish pointing at CCCC during the next site visit. |
||
| − | == |
+ | ==[[4CCCC|CCCC]]== |
| − | ==== |
+ | ====Plans==== |
Re-evaluate the battery system and determine why it fails to provide the constant power required for all the equipment. |
Re-evaluate the battery system and determine why it fails to provide the constant power required for all the equipment. |
||
| − | === |
+ | ===Mount Diablo=== |
<span style="color:green"> |
<span style="color:green"> |
||
'''Status''': Equipment installed. Active. |
'''Status''': Equipment installed. Active. |
||
| Line 54: | Line 51: | ||
'''Connection''': Non-AREDN, airFiber 3 GHz. Acts as DtD. |
'''Connection''': Non-AREDN, airFiber 3 GHz. Acts as DtD. |
||
| − | ==== |
+ | ====Notes==== |
Connects via DtD over non-AREDN radios, so appears as wired AREDN connection, even though it isn't. |
Connects via DtD over non-AREDN radios, so appears as wired AREDN connection, even though it isn't. |
||
| − | === |
+ | ===Richmond Field Station === |
<span style="color:green"> |
<span style="color:green"> |
||
'''Status''': Equipment installed, Active. |
'''Status''': Equipment installed, Active. |
||
| Line 64: | Line 61: | ||
'''Connection''': Non-Ham, 5 Ghz AC gen2, unknown equipment. |
'''Connection''': Non-Ham, 5 Ghz AC gen2, unknown equipment. |
||
| − | ==== Notes |
+ | ==== Notes==== |
Connects via DtD over non-AREDN radios, so appears as a wires AREDN connection, even though it isn't. |
Connects via DtD over non-AREDN radios, so appears as a wires AREDN connection, even though it isn't. |
||
| − | === |
+ | ===San Bruno Mountain=== |
'''Status''': Proposed |
'''Status''': Proposed |
||
| − | == |
+ | ==[[Mount Diablo]]== |
Slides detailing the configuration can be found [[:File:MountDiablo Slide1.png|here]] and [[:File:MountDiablo Slide3.png|here]]. |
Slides detailing the configuration can be found [[:File:MountDiablo Slide1.png|here]] and [[:File:MountDiablo Slide3.png|here]]. |
||
| − | === |
+ | ===CCCC=== |
<span style="color:green"> |
<span style="color:green"> |
||
'''Status''': Equipment installed. Active. |
'''Status''': Equipment installed. Active. |
||
| Line 80: | Line 77: | ||
'''Connection''': Non-AREDN, airFiber 3 GHz. |
'''Connection''': Non-AREDN, airFiber 3 GHz. |
||
| − | ==== |
+ | ====Note ==== |
Connects via DtD over non-AREDN radio. |
Connects via DtD over non-AREDN radio. |
||
| − | == |
+ | ==Richmond Field Station (RFS)== |
| − | === |
+ | ===CCCC=== |
<span style="color:green"> |
<span style="color:green"> |
||
'''Status''': Equipment installed, Active. |
'''Status''': Equipment installed, Active. |
||
| Line 92: | Line 89: | ||
'''Connection''': Non-AREDN, 5 Ghz AC gen2, unknown equipment. |
'''Connection''': Non-AREDN, 5 Ghz AC gen2, unknown equipment. |
||
| − | ==== Notes |
+ | ==== Notes==== |
Connects via DtD over non-AREDN radio. |
Connects via DtD over non-AREDN radio. |
||
| − | == |
+ | ==[[Black Mountain]]== |
=== San Bruno Mountain === |
=== San Bruno Mountain === |
||
| Line 102: | Line 99: | ||
Without a good intermediate connection down the Peninsula, a link from Black Mountain to San Bruno is our best option. |
Without a good intermediate connection down the Peninsula, a link from Black Mountain to San Bruno is our best option. |
||
| − | === Mount Allison |
+ | === Mount Allison=== |
'''Status''': Planning |
'''Status''': Planning |
||
Final stages of planning a Non-AREDN 5 GHz link between Black Mountain and Mount Allison, in coordination with N9JIM. |
Final stages of planning a Non-AREDN 5 GHz link between Black Mountain and Mount Allison, in coordination with N9JIM. |
||
| − | == |
+ | ==[[Mount Allison]]== |
| − | === |
+ | ===Black Mountain=== |
Status: Planning |
Status: Planning |
||
Notes: A link from Mount Allison to Black Mountain passes directly over one of [https://he.net Hurricane Electric]'s data centers. They support putting microwave dishes on their roofs. |
Notes: A link from Mount Allison to Black Mountain passes directly over one of [https://he.net Hurricane Electric]'s data centers. They support putting microwave dishes on their roofs. |
||
| − | == |
+ | ==Needed Sites== |
| − | === East Bay |
+ | === East Bay=== |
The most southerly backbone site is in the Oakland Hills. There is a need for a number of high sites stretching down the East Bay to Fremont and Milpitas. |
The most southerly backbone site is in the Oakland Hills. There is a need for a number of high sites stretching down the East Bay to Fremont and Milpitas. |
||
| − | === |
+ | ===Peninsula=== |
The most southerly backbone site is San Bruno Mountain. There is a need for high sites stretching down though Burlington, Mountain View and Palo Alto. |
The most southerly backbone site is San Bruno Mountain. There is a need for high sites stretching down though Burlington, Mountain View and Palo Alto. |
||
=Notes= |
=Notes= |
||
| − | ===DtD connected nodes=== |
+ | ===DtD connected nodes === |
The backbone is currently being constructed using Part 15 devices acting as bridges between AREDN nodes. The AREDN nodes connect to bridges via the DtD port / VLAN 2. This essentially puts every node at every location in the Backbone on the same VLAN. Consequently, every broadcast from any node connected directly to any Backbone point will have its traffic retransmitted to every other node. This probably isn't a good thing. The Southern California Mesh solves this problem by having backbones nodes connect to each other using an AREDN tunnel over the "WAN" ... but in their case the "WAN" is in fact a VLAN running over their Part 15 devices. This gives them better control of the traffic on their backbone. |
The backbone is currently being constructed using Part 15 devices acting as bridges between AREDN nodes. The AREDN nodes connect to bridges via the DtD port / VLAN 2. This essentially puts every node at every location in the Backbone on the same VLAN. Consequently, every broadcast from any node connected directly to any Backbone point will have its traffic retransmitted to every other node. This probably isn't a good thing. The Southern California Mesh solves this problem by having backbones nodes connect to each other using an AREDN tunnel over the "WAN" ... but in their case the "WAN" is in fact a VLAN running over their Part 15 devices. This gives them better control of the traffic on their backbone. |
||
Revision as of 22:45, 3 September 2022
The Bay Area Backbone Project is building solid, fast, links between major high sites in the Bay Area, which in turn supports a more stable mesh network. Backbone sites are permanent locations, not dependent on amateur radio operators' homes or difficult to access places.
The current health of the backbone is monitored here (internet)
Fish Ranch / ORCA
San Bruno Mountain
Status: Equipment installed. Active.
Connection: Non-AREDN, airFiber 5 GHz.
Notes
None
San Bruno Mountain
Fish Ranch / ORCA
Status: Equipment installed. Active.
Connection: airFiber 5 GHz.
Notes
None
Plans
Immediate plans for changes at this site are unclear as the current owners want to do some significant upgrades before adding more equipment. We will probably help out with this project once scheduled (soon). After that the goal is to replace the NSM5 with a more powerful radio, finalize this end of the Fish Ranch link, and look at options for connecting south.
CCCC
Status: Proposed
Connection: AREDN Mikrotik LHG 5
Notes
Evaluating installing a new dish pointing at CCCC during the next site visit.
CCCC
Plans
Re-evaluate the battery system and determine why it fails to provide the constant power required for all the equipment.
Mount Diablo
Status: Equipment installed. Active.
Connection: Non-AREDN, airFiber 3 GHz. Acts as DtD.
Notes
Connects via DtD over non-AREDN radios, so appears as wired AREDN connection, even though it isn't.
Richmond Field Station
Status: Equipment installed, Active.
Connection: Non-Ham, 5 Ghz AC gen2, unknown equipment.
Notes
Connects via DtD over non-AREDN radios, so appears as a wires AREDN connection, even though it isn't.
San Bruno Mountain
Status: Proposed
Mount Diablo
Slides detailing the configuration can be found here and here.
CCCC
Status: Equipment installed. Active.
Connection: Non-AREDN, airFiber 3 GHz.
Note
Connects via DtD over non-AREDN radio.
Richmond Field Station (RFS)
CCCC
Status: Equipment installed, Active.
Connection: Non-AREDN, 5 Ghz AC gen2, unknown equipment.
Notes
Connects via DtD over non-AREDN radio.
Black Mountain
San Bruno Mountain
Status: Evaluating
Without a good intermediate connection down the Peninsula, a link from Black Mountain to San Bruno is our best option.
Mount Allison
Status: Planning
Final stages of planning a Non-AREDN 5 GHz link between Black Mountain and Mount Allison, in coordination with N9JIM.
Mount Allison
Black Mountain
Status: Planning
Notes: A link from Mount Allison to Black Mountain passes directly over one of Hurricane Electric's data centers. They support putting microwave dishes on their roofs.
Needed Sites
East Bay
The most southerly backbone site is in the Oakland Hills. There is a need for a number of high sites stretching down the East Bay to Fremont and Milpitas.
Peninsula
The most southerly backbone site is San Bruno Mountain. There is a need for high sites stretching down though Burlington, Mountain View and Palo Alto.
Notes
DtD connected nodes
The backbone is currently being constructed using Part 15 devices acting as bridges between AREDN nodes. The AREDN nodes connect to bridges via the DtD port / VLAN 2. This essentially puts every node at every location in the Backbone on the same VLAN. Consequently, every broadcast from any node connected directly to any Backbone point will have its traffic retransmitted to every other node. This probably isn't a good thing. The Southern California Mesh solves this problem by having backbones nodes connect to each other using an AREDN tunnel over the "WAN" ... but in their case the "WAN" is in fact a VLAN running over their Part 15 devices. This gives them better control of the traffic on their backbone.