Resolve overlapping routes

Two networks can use the same address range, for example two cloud VPCs that both use 172.17.0.0/16. When a device receives routes for both, the routes conflict. Route selection lets the user, or a script on the device, choose which of the routes the device uses.

Routes are set up under Network > Routes, see Routes. Route selection happens on the device, with the netzilo routes command.

How it works

  • By default a device uses every route it receives: all routes are selected.
  • Selecting routes is a choice on that device only. It does not change the routes in the dashboard or on other devices.
  • Selected is not the same as working. A selected route whose routing peers are all offline is removed from the device, and its traffic takes the device's normal path.
  • When two networks claim the same range, the client log shows Prefix [<range>] is already routed by peer [<key>]. HA routing disabled.

Select routes with the CLI

List the routes the device received:

netzilo routes list
Available Routes:

  - ID: aws-vpc-ireland
    Network: 172.17.0.0/16
    Status: Selected

  - ID: aws-vpc-ohio
    Network: 172.17.0.0/16
    Status: Selected

Both routes are selected, so they conflict. Select the one this device should use:

netzilo routes select aws-vpc-ireland

select deselects every other route unless you add -a. More examples:

# select several routes
netzilo routes select route1 route2
# add a route to the current selection
netzilo routes select -a route3
# select every route, including routes added later
netzilo routes select all
# stop using one route
netzilo routes deselect aws-vpc-ohio
# stop using every route, including routes added later
netzilo routes deselect all

netzilo routes select all restores the default behaviour.

Fix the overlap for everyone

Route selection is a workaround on each device. To remove the conflict for all users:

  • Give each network its own Network Identifier and distribution groups, so that a user receives only the network they need.
  • Publish narrower ranges, or renumber one of the networks.

Overlap with the user's own network

The same conflict happens when a home or hotel network uses the same range as an office route. The device's local route then wins, and traffic to that range stays on the local network. Check which path the device chooses:

SystemCommandExpected interface
Linuxip route get 192.168.1.10wt0
macOSroute -n get 192.168.1.10utun100
WindowsFind-NetRoute -RemoteIPAddress 192.168.1.10wt0

If the local interface is named, the user's network overlaps the route. Publish a narrower range or renumber the office network.

  • Routes - Create and manage network routes
  • CLI - The netzilo routes command
  • Exit nodes - Route internet traffic through a peer