Network Topology Overview

This is a technical draft of how VONet’s network is structured. We’re building a citywide community mesh network using proven open networking tools like OSPF and BGP. This structure is inspired by NYC Mesh but tailored for Las Vegas infrastructure and needs.

Core Technologies

• OSPF is used for dynamic internal routing between mesh-connected devices
• BGP is used for peering at the Internet Exchange Point and between core SuperNodes
• Layer 2 bridging is used locally in short-range clusters
• Layer 3 routing handles most of the traffic between segments, uplinks, and core nodes

Node Types and Roles

Node

A regular VONet connection point, typically installed at a home, apartment, or small business. These provide basic connectivity and may connect to a Hub or another nearby Node.

• Usually has one directional or omnidirectional antenna
• Connects wirelessly to a Hub or relay
• May be powered by a small router (MikroTik hAP, SXTsq, etc.)
• Runs OSPF to advertise its local route

Hub

A relay point that connects multiple nearby Nodes. Usually mounted on a rooftop, pole, or high structure with good line of sight to its surrounding neighborhood.

• Handles traffic from multiple Nodes
• Connects wirelessly or via Ethernet to a SuperNode or another Hub
• Uses OSPF to route traffic dynamically
• May include switches or local routing for Layer 2 bridging in small clusters

SuperNode

A major routing point and internet gateway. These are colocated systems or rooftop installs with fiber or high-speed wireless backhaul. SuperNodes handle peering, routing, and uplink decisions.

• Runs BGP to peer with other SuperNodes and the Internet Exchange Point
• Runs OSPF to route mesh traffic from Hubs and Nodes
• Hosts key infrastructure like DNS, exit gateways, or monitoring tools
• Maintains tunnels and policy routing for external traffic

Mesh Routing with OSPF

• All Nodes, Hubs, and SuperNodes run OSPF
• Routes are automatically updated as the topology changes
• Each node advertises its local subnet (or default route if acting as an uplink)
• OSPF areas may be used to segment different neighborhoods or reduce routing complexity
• Wireless link quality may influence OSPF cost metrics

Core Routing and Peering with BGP

• BGP is used at SuperNodes to manage:
  • Peering with other SuperNodes
  • Announcing VONet IP space
  • Connecting to the local Internet Exchange Point
  • Load-balancing across uplinks

• This setup allows VONet to function like an independent ISP while remaining community-owned
• Public IP blocks will be routed through SuperNodes that serve as internet exits

Traffic Flow

• Local traffic between VONet users stays inside the mesh
• Internet-bound traffic exits through the closest SuperNode with a working uplink
• Internal services like DNS, VoIP, and file sharing may also run within the mesh
• Exit traffic is load-balanced and policy-routed via BGP

Scalability and Redundancy

• Additional SuperNodes can be added for more uplinks or geographic coverage
• Hubs and Nodes can join or leave the network without breaking connectivity
• Redundant routes and failover paths are built into the OSPF topology

Status

This page reflects the planned technical layout of the network. It will be updated as pilot deployments begin and configs are tested in the real world.

Interested in Helping?

Email support@vonet.org if you'd like to help configure routing, test node roles, or support the rollout of SuperNodes and Hubs.