IP Addressing & Routing

This page outlines how VONet assigns IP addresses and handles routing across the mesh. The system follows the same principles used by NYC Mesh: each node is assigned a number, and that number is used to generate its internal IP address.

Overview

Each node in VONet gets a unique number (Node ID). This number is used to assign IP addresses in the 10.0.0.0/8 private address space. The format is:

 10.NODEID.0.0/16

This makes addressing predictable, easy to manage, and scalable to thousands of nodes.

Example

If a node has ID 42, its assigned subnet is:

 10.42.0.0/16

From this block:

• The router might use 10.42.0.1
• Local clients might get addresses like 10.42.0.100, 10.42.0.101, etc.
• The node can route other traffic in that range as needed

This approach also makes it easier to set static routes, monitor performance, and assign services (like DNS or exit gateways) to specific addresses.

Internal IP Space

• Node subnets: 10.NODEID.0.0/16
• Management: 10.255.0.0/16 (reserved for tools, monitoring, etc.)
• Link-local: 169.254.x.x if needed for mesh-only testing
• End-user devices typically connect through NAT and get addresses in the node’s subnet

Public IPs

VONet will acquire public IPv4 blocks in /24 sizes. These are used for:

• SuperNodes and gateways
• Hosting services directly on the mesh
• Optional public IPs for advanced users

Public blocks will be routed via BGP at SuperNodes, which peer with upstream ISPs and the local Internet Exchange Point (IXP).

Routing

OSPF (Open Shortest Path First)

Used for mesh routing between:

• Nodes
• Hubs
• SuperNodes

Each node advertises its `10.NODEID.0.0/16` subnet into the mesh. OSPF ensures the best path is selected dynamically, and allows for automatic rerouting if a node goes offline.

OSPF areas may be introduced for large sections of the city.

BGP (Border Gateway Protocol)

Used between SuperNodes and for peering at the IXP.

BGP allows VONet to:

• Announce public IP space
• Balance traffic between multiple uplinks
• Peer directly with other networks
• Provide regional and national internet access

NAT and Gateways

• End-user traffic is NATed at the local node by default
• Internet-bound traffic exits through SuperNodes, where it is NATed again or routed using public IPs
• Public IPs can be assigned on request to specific nodes if hosting is needed

IPv6

IPv6 support is planned. The current plan is to assign:

• A /64 to each node
• Static IPv6 routes via OSPFv3
• Native IPv6 peering at the IXP where possible

Benefits of Number-Based Addressing

• Predictable IP layout
• Easy node identification
• Fewer IP conflicts
• Works with static routing or dynamic protocols
• Simplifies monitoring and diagnostics

Status

This system will be rolled out as part of the pilot network. We will publish Node ID assignments, gateway IPs, and routing details as they become available.

Want to Help?

If you’re interested in IP planning, routing design, or running a SuperNode, email support@vonet.org