BluVPN:Network Layout

This article is a part of BluVPN.

In the core, BluVPN consists of "backbones", i.e. the servers who are interconnected in a mesh network and takes care of the core routing. Behind every backbone, or server, there should be a network which is routable from all the other parts of the network. The backbone is currently driven by tinc, which is a mesh vpn daemon. It creates a meshed "switch" and its interface name is "bluvpn"

 ________________
|                | -> bluvpn 10.159.0.2 <-> 10.159.0.0/24
|                |
|     gamma      |
|                |
|                | -> lanbr 10.159.2.1 <-> 10.159.2.0/24
|________________|

The setups for the tunX's can be found in BluVPN:tinc. The bridge lanbr can be bridged between a virtual adapter and a physical adapter, and it can even be a regular ethX, tapX or tunX, whatever suits you. One of these servers can serve multiple subnets, which is possible thanks to BluVPN:BGP.