Prologue

Introduction Core Concepts Block Data & Operations Secure & Private by default User Cases Overall Workflow

Quick Start

Overview DNet Admin Overlay Cloud Provider End User

Run App on ĐNET

Run Tinc-VPN on ĐNET Tinc-VPN Introduction Tinc App Driver Tinc OVC Driver Data Files Folder DNetDB Structure Node Roles DNet Owner Node OVC Owner Node OVC Cloud Instance App User Node

Port App to ĐNET

Port Tinc-VPN to ĐNET Build From Source DNetDB CRUD OVC Implementation App Implementation App command line

Working with data

DNet Record OVC Record

Overlay Control (OVC) Instance for VPN

The ovc instance for VPN is registrated in DNetDB with its Public IP address and Public Key.

The Overlay Control (OVC) is the cloud backend for the dnet. The Tinc VPN node is configured as server with 1213 port open listening for incoming protocol messages from the Tinc VPN App. The Tinc enduser node retrieves the ovc info from block chain and has a configuration item ConnectTo pointing to this OVC Public Address or domain name.

A public IP address is needed for ovc node, and it can be:

  • a static public IP address or domain name or
  • a Dynamic DNS domain name or
  • port forward on router.

The DNet Driver automatically pulls the authorized dnet list from blockchain every 100 seconds and add the nodes' PubKey to ovc instance's hosts folder.

The tutorial to setup a private OVC node is available for testdnet.

Edit this page on GitHub