Bay Area Backbone

From Bay Area Mesh
Revision as of 20:59, 13 November 2023 by Kn6plv (talk | contribs)
Jump to navigation Jump to search
Bay Area Backbone, Goal 2023.png

The goal of the Bay Area Backbone Project is to provide a fast, IP microwave based networking between amateur high sites in the Bay Area. The backbone provides IP connectivity within the network and can provide public IPv4 address for full Internet connectivity when required.

The network is available to any amateur operator needing connectivity to, from or between supported sites.

Management

Sites

Want to become part of the network? We'll provide everything you need to get connected.

ARIN

American Registry for Internet Numbers

Organizations

Points of Contact

Networks

Autonomous System Numbers

FCC

Federal Communications Commision

  • FRN: 0031037245

Experimental Licenses

A number of the backbone links operate with experimental 6GHz licenses in the U-NII-5 band.

https://apps.fcc.gov/els

Network Structure

Radios

A minimal backbone endpoint consists of two radios providing a point-to-point link between two sites. Ideally a site provides at least two links so the network can be extended from that point. In some places we use point-to-multipoint radios to provide additional shared links from a single site. We currently deploy the following:

Routers

Any router capable of supporting OSPF can be used to support the radios. We currently deploy the following:

Software

The backbone network runs OSPF

Hardware

More details description of typical site hardware.

Services

A typical backbone node provide the following services:

  • Private IPv4 address: A subnet of 100.100.X.X/24 is assigned to the router. Addresses from this range can be automatically or statically allocated to devices connected to the router. All addresses can be routed to the Internet (but not from the Internet). The subnet is allocated to VLAN 1100 internally. A router may choose to restrict this using a firewall.
  • Public IPv4 address: Specific public IP address from the subnet 206.197.44.0/24 or 44.31.228.0/24 can be allocated to specific routers and/or ports. Traffic to these addresses can be routed to and from the Internet. Addresses are managed using policy based routing. No traffic is routed into the network for an address which is not allocated.
  • Public IPv6 address: A subnet of 2620:B8:A000::/64 is assigned to the router. Addresses are allocated to a device using SLAAC. Traffic to these addresses can be routed to and from the Internet. A router may choose to restrict this using a firewall or choose to not participate in IPv6 routing at all.

Links

Active

Planned

Proposed

Peering and IP Transit

The backbone network uses three IP Transit points to facilitate access to and from the public Internet using BGP.

Connections to these transit points are via Wireguard tunnels from the Oxford site. The Oxford site uses fiber as the primary with Starlink as the backup.

Peering Information

History

The first backbone link, between Fish Ranch and San Bruno Mountain, was installed on the 23rd November, 2021 and became operational on 3rd September, 2022. The goal was to provide a solid connection across the Bay which the AREDN network could use. It had been observed by the AREDN network builders in Southern California, that a better quality and more stable network could be constructed by creating a solid, well engineered backbone, to which local community AREDN networks could connect.

Projects

Bay Area Mesh on the Backbone

Using the Bay Area Backbone to support the Bay Area Mesh has 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 connections between mesh sites (these are called xlinks - see below). Mikrotik hAP ac2 nodes provide the the mesh endpoint hardware. The traffic is routed between the specified IP addresses of the xlink. The underlying network may encapsulate this traffic if desired. We often use VLANs.

XLINKS

XLINKS are custom connections between sites which feed directly into the AREDN router. Think of them as DtD links, but only point-to-point. By default we use VLAN 1100 for all XLINKs.

Link VLAN A B Notes
San Bruno Mountain to Swallow 100.101.12.101 100.101.12.103
ORCA to Wolfback 100.101.18.102 100.101.18.101
ORCA to Fish Ranch 100.101.13.101 100.101.13.102 Dues to an intermediate Switch, uses VLAN 1101
Fish Ranch to San Bruno Mountain (7) 100.101.14.101 100.101.14.103
San Carlos to Sunol Ridge 100.101.17.101 100.101.17.102
San Bruno Mountain (7) to San Carlos 100.101.12.101 100.101.12.102
San Bruno Mountain (7) to Fire Station 8 100.101.12.101 100.101.12.104
Fire Station 8 to Mount Allison - -
Oxford to Wolfback 100.101.18.101 100.101.18.103
Fish Ranch to San Bruno Mountain (4) 100.101.14.101 100.101.14.102
San Bruno Mountain (7) to Black Mountain (4) 20 100.101.12.101 100.101.12.105
Sunol Ridge to Mount Allison - -
CCCC to Wolfback 100.101.18.104 100.101.18.101

Backbone links appear in the mesh labeled as xlink but are no different from any other link in the network from AREDN's perspective.

WB6ECE Repeater Group Interconnect

WB6ECE Repeater Group operates a network on about a dozen sites south of the Bay Area. The interconnect project aims to share networks to provide greater redundancy and reduce duplicated effort.

The ultimate goal of the Interconnect project is to provide a BGP connection between the two. For the moment the networks are interconnected by each providing the other with IP addresses on their respective networks.

Interconnect Points

There are three interconnect points.

San Bruno Mountain (Building 7)

Routers at San Bruno Mountain are connected via a 1 Gbps link.

Forward Link
  • BAB IP: 44.31.128.190
  • WB6ECE IP: 44.31.128.189
  • Subnet: 44.31.128.188/30
  • Routes: 44.31.128.0/22
Reverse Link
  • WB6ECE IP: 206.197.44.37
  • Subnet: 206.197.44.0/24
  • Routes: 206.197.44.1/24
Black Mountain (Site 4)

Router at Black Mountain is connected to Site 5 via a 60 GHz link.

Forward Link
  • BAB IP: 44.31.128.222
  • WB6ECE IP: 44.31.128.221
  • Subnet: 44.31.128.220/30
  • Routes: 44.31.128.0/22
Reverse Link
  • WB6ECE IP: 206.197.44.38
  • Subnet: 206.197.44.0/24
  • Routes: 206.197.44.1/24
Mount Allison

Not currently active

Interconnect Links

  • San Bruno Mountain (Building 7) to Black Mountain (Site 4)
    • BAM: an VXLAN connection between these two sites provides a backup link for our backbone. The backup is managed using OSPF.
    • WB6ECE: an IP-over-IP provides them with a similar service. The backup is managed using OSPF.

Contacts

  • Tim Wilkinson - KN6PLV - tim@sfwem.net
Retrieved from "https://wiki.bayareamesh.us/index.php?title=Bay_Area_Backbone&oldid=2467"